For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub
- This topic has 5 replies, 4 voices, and was last updated 20 years, 10 months ago by
Scott Anderson.
-
AuthorPosts
-
satish_venMemberI hv Eclipse 3.1.1 with full SDK
I am installing Myeclipse 4.0
The installer throws me out with a message “Eclipse 3.1 RC3 or above required”
Just wondering whether MyEclipse 4.0 is not supported on Eclipse 3.1.1 ?Any help would be appreciated.
TIA
-SatishOctober 3, 2005 at 11:50 am #238576
support-eugeneMemberSame issue is discussed here https://www.genuitec.com/forums/topic/closed-fail-to-install-myeclipse-with-eclipse-3-1-1/&highlight=
I will quote Scott’s reply:
There’s a problem with the 4.0 installers that doesn’t recognized Eclipse 3.1.1 as a valid installation target. We’ll be releasing 4.0.1 today to remedy the issue. In the interim you can use the manual installer that is available in the downloads section as well. Sorry for the inconvenience, but we’re working quickly to try to address it.October 3, 2005 at 2:28 pm #238584
Adam CarboneMemberI used the update site to upgrade to 4.0.1. Now when I start eclipse I get a “An internal error occurred during: “Initializing Java tooling”.” and the following error in the eclipse log.
I was wondering if upgrading to 3.1.1 would solve this.Operating System and version: Fedora core 4
Eclipse version: 3.1.0
Eclipse build id: I20050627-1435
Fresh Eclipse install (y/n): Yes
If not, was it upgraded to its current version using the update manager?
Other installed external plugins: NONE
Number of plugins in the <eclipse>/plugins directory that begin with org.eclipse.pde.*: 8
MyEclipse version: 4.0.1
Eclipse JDK version: 1.5.0_05
Application Server JDK version:
Are there any exceptions in the Eclipse log file? See following!SESSION 2005-10-03 15:11:58.628 ———————————————–
eclipse.buildId=I20050627-1435
java.version=1.5.0_05
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US
Command-line arguments: -os linux -ws gtk -arch x86!ENTRY org.eclipse.core.runtime 4 2 2005-10-03 15:12:13.828
!MESSAGE An internal error occurred during: “Initializing Java tooling”.
!STACK 0
org.eclipse.jdt.internal.core.Assert$AssertionFailedException: Assertion failed; Path for IClasspathEntry must be absolute
at org.eclipse.jdt.internal.core.Assert.isTrue(Assert.java:89)
at org.eclipse.jdt.core.JavaCore.newLibraryEntry(JavaCore.java:3134)
at org.eclipse.jdt.internal.core.UserLibrary.createFromString(UserLibrary.java:182)
at org.eclipse.jdt.internal.core.UserLibraryManager.recreatePersistedUserLibraryEntry(UserLibraryManager.java:159)
at org.eclipse.jdt.internal.core.UserLibraryManager.getLibraryMap(UserLibraryManager.java:139)
at org.eclipse.jdt.internal.core.UserLibraryManager.getUserLibrary(UserLibraryManager.java:82)
at org.eclipse.jdt.internal.core.UserLibraryClasspathContainerInitializer.initialize(UserLibraryClasspathContainerInitializer.java:32)
at org.eclipse.jdt.internal.core.JavaModelManager.initializeContainer(JavaModelManager.java:1591)
at org.eclipse.jdt.internal.core.JavaModelManager.getClasspathContainer(JavaModelManager.java:1040)
at org.eclipse.jdt.core.JavaCore.getClasspathContainer(JavaCore.java:1326)
at org.eclipse.jdt.internal.core.JavaProject.getResolvedClasspath(JavaProject.java:2039)
at org.eclipse.jdt.internal.core.JavaProject.getResolvedClasspath(JavaProject.java:1947)
at org.eclipse.jdt.internal.core.search.JavaSearchScope.add(JavaSearchScope.java:108)
at org.eclipse.jdt.internal.core.search.JavaWorkspaceScope.initialize(JavaWorkspaceScope.java:84)
at org.eclipse.jdt.internal.core.search.JavaSearchScope.<init>(JavaSearchScope.java:62)
at org.eclipse.jdt.internal.core.search.JavaSearchScope.<init>(JavaSearchScope.java:58)
at org.eclipse.jdt.internal.core.search.JavaWorkspaceScope.<init>(JavaWorkspaceScope.java:29)
at org.eclipse.jdt.internal.core.JavaModelManager.getWorkspaceScope(JavaModelManager.java:1421)
at org.eclipse.jdt.internal.core.search.BasicSearchEngine.createWorkspaceScope(BasicSearchEngine.java:157)
at org.eclipse.jdt.core.search.SearchEngine.createWorkspaceScope(SearchEngine.java:392)
at org.eclipse.jdt.core.JavaCore$1.run(JavaCore.java:2623)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:76)– System Setup ——————————-
– Message Body ——————————-
October 3, 2005 at 6:14 pm #238600
Scott AndersonParticipantThe issue is likely that the Eclipse plugin cache got stale as it sometimes
does not cleanly rebuild after updates. To rectify the problem you’ll need
to restart Eclipse with the -clean flag one time: eclipse.exe -cleanOctober 4, 2005 at 9:04 am #238650
Adam CarboneMemberI’m running on linux there is no .exe file is there a way to have the binary launcher take these params as well? Also I have done a clean install and this still seems to be happening. Also I dont’ know if this is related but User Libraries are not being persisted when I close the ide. Saw that the error message said soemthign to do with user library.
October 4, 2005 at 10:29 am #238664
Scott AndersonParticipantI’m running on linux there is no .exe file is there a way to have the binary launcher take these params as well?
Yes. On Linux the launcher is simply called ‘eclipse’ and is in the Eclipse installation directory.
-
AuthorPosts
