Community
Participate
Working Groups
Been using Eclipse for a year. Editing and compiling. Two days ago, it stopped compiling. I can run the project, but new edits don't take. I just upgraded to the latest Eclipse version to see if that solves the problem, and I still have the same problem. If I remove a class and try to use it, I get a java.lang.ClassNotFoundException: It knows where the class files are, saves the java files and runs the project, but it doesn't compile any new edits before it runs. Pete Antoniak
Is Project>Build automatically menu still set? PW
> java.lang.ClassNotFoundException: This might indicate that your install is broken. Please provide more details - Which build do you have? - Full .log
(In reply to Paul Webster from comment #1) > Is Project>Build automatically menu still set? > > PW Yes it it checked. I unchecked it, ran the project with same problem and then re-checked it and the problem persists.
(In reply to Dani Megert from comment #2) > > java.lang.ClassNotFoundException: > > This might indicate that your install is broken. Please provide more details > - Which build do you have? > - Full .log Broken install would explain the new version, but not the one that I have been running for a year. My Version: Eclipse Standard/SDK Version: Kepler Service Release 2 Build id: 20140224-0627 Full log file is too long for this text box. Partial log entries follows. I hope this helps. Thanks in advance. Pete !!ENTRY org.eclipse.ui 4 4 2014-04-08 12:43:07.167 !MESSAGE Conflicting handlers for org.eclipse.ui.edit.redo: {ActionHandler(org.eclipse.ui.operations.RedoActionHandler@41ae1c9e)} vs {ActionHandler(org.eclipse.ui.operations.RedoActionHandler@3c488812)} !ENTRY org.eclipse.egit.ui 2 0 2014-04-07 17:35:51.744 !MESSAGE Warning: The environment variable HOME is not set. The following directory will be used to store the Git user global configuration and to define the default location to store repositories: 'C:\Users\Pete'. If this is not correct please set the HOME environment variable and restart Eclipse. Otherwise Git for Windows and EGit might behave differently since they see different configuration options. This warning can be switched off on the Team > Git > Confirmations and Warnings preference page. java.io.IOException: Unable to resolve plug-in "platform:/plugin/org.eclipse.wst.common.snippets/icons/snippets_view.gif". at org.eclipse.core.internal.runtime.PlatformURLPluginConnection.parse(PlatformURLPluginConnection.java:64) at org.eclipse.core.internal.runtime.PlatformURLPluginConnection.resolve(PlatformURLPluginConnection.java:75) at org.eclipse.core.internal.boot.PlatformURLHandler.openConnection(PlatformURLHandler.java:67) at org.eclipse.osgi.framework.internal.protocol.URLStreamHandlerProxy.openConnection(URLStreamHandlerProxy.java:112) at java.net.URL.openConnection(Unknown Source) !ENTRY org.eclipse.ui 4 4 2014-04-05 17:11:11.433 !MESSAGE Conflicting handlers for org.eclipse.debug.ui.commands.eof: {org.eclipse.debug.internal.ui.views.console.ProcessConsolePageParticipant$EOFHandler@3b561af1} vs {org.eclipse.debug.internal.ui.views.console.ProcessConsolePageParticipant$EOFHandler@3b561af1} !SESSION 2014-04-05 17:16:11.961 ----------------------------------------------- eclipse.buildId=M20130204-1200 java.version=1.7.0_51 java.vendor=Oracle Corporation BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US Framework arguments: -product org.eclipse.epp.package.jee.product Command-line arguments: -os win32 -ws win32 -arch x86_64 -product org.eclipse.epp.package.jee.product !ENTRY org.eclipse.egit.ui 2 0 2014-04-02 13:24:45.931 !MESSAGE Warning: EGit couldn't detect the installation path "gitPrefix" of native Git. Hence EGit can't respect system level Git settings which might be configured in ${gitPrefix}/etc/gitconfig under the native Git installation directory. The most important of these settings is core.autocrlf. Git for Windows by default sets this parameter to true in this system level configuration. The Git installation location can be configured on the Team > Git > Configuration preference page's 'System Settings' tab. This warning can be switched off on the Team > Git > Confirmations and Warnings preference page.
(In reply to Peter Antoniak from comment #4) > (In reply to Dani Megert from comment #2) > > > java.lang.ClassNotFoundException: > > > > This might indicate that your install is broken. Please provide more details > > - Which build do you have? > > - Full .log > > Broken install would explain the new version, but not the one that I have > been running for a year. > > My Version: > Eclipse Standard/SDK > > Version: Kepler Service Release 2 > Build id: 20140224-0627 This download does e.g. not contain WST, which explains some of the errors and might also cause the project not to build if it is not a pure Java or PDE project. > Full log file is too long for this text box. You can attach it to this bug report. Also check in the 'Problems' view whether there are build path errors.
Created attachment 241804 [details] Two log files from bug report 432204 I renamed the .log file and ran each version using the same work space. The newly created .log file are attached. Not sure if both .log files are attached, so I will do this twice. Pete
Created attachment 241805 [details] Two log files from bug report 432204 I renamed the .log file and ran each version using the same work space. The newly created .log file are attached. Not sure if both .log files are attached, so I will do this twice. Pete
Is anyone looking at this? Pete Antoniak
Did you my change use this workspace with "Luna" as a test? If so, you may not be able to "go backwards" ... and will have to import your projects into a fresh workspace. You talked about "updating your previous install" ... but, since you are posting logs from both "standard edition" and "Java EE package" ... it's hard to know what you mean by "update" ... not sure knowing would help us much in diagnosing your problem ... but, just mentioning it as a point of confusion. (Its probably clear to you, though, which is what matters. :) It would help if you described more what you are trying to do. What kind of project is it? I ask because you obviously are using both "standard edition" and "Java EE package" ... so if your project is any sort of "Java EE project", or uses, for example, "faceted projects" then "standard edition" won't work well. (You can usually tell by looking in the .project file to see if there are builders or natures in there that mention "faceted project" ... or similar things you "don't want". Some of the issues/errors in the log don't appear to have anything to do with whether or not your "class compiles" ... but do indicate something, somewhere is in a bad state (so indirectly could be related). So, once you know what you are trying to do, I could suggest a few things to get things in a good state again. In rough order of "what to try" ... - Be sure all editors are closed, and restart, to see if that doesn't help. - Reset perspectives. Again close and restart. - One of my recent favorites ... start your Eclipse with a new, fresh workspace. Then "switch to ... " your old workspace and go through "full dialog sequence" where you select "copying settings" (from the new workspace to your old workspace ... this often resets some "defaults" which are otherwise sometimes hard to know about, or set). [May or may not want to import any preference you have saved away as your favorite preferences. ... I'd try without that at first.] - I normally don't suggest this ... but occasionally it helps, as a last resort ... if none of above help, start your eclipse install (just once) with "-clean" ... and this might help it straighten itself out. If none of those help you should probably start again with a fresh install, of what you really want to use (standard, or Java EE, and no extra plugins, to start with) and start with a fresh workspace, and then import your projects into the new workspace. Ideally you'd import them from your "Git repository" or what ever you use ... but if you literally have no "safe copy", then you can try to import "existing project" and just point to the project in old workspace. If none of that helps your compile problem, it should at least lead to a more helpful log of what core issue is. Good luck,
None of the logs are giving a hint why you can't compile anymore. It rather looks like your install is corrupt or you mixed old and new installs with the same workspace (I might be wrong of course). You can either try David's tips or just do a fresh install from http://www.eclipse.org/downloads/ that best suits your needs. Sorry, we can't offer more help.
