- This topic has 7 replies, 4 voices, and was last updated 19 years, 9 months ago by
David C Bauer.
-
AuthorPosts
-
greg.granatoMember– System Setup ——————————-
Operating System and version:
Eclipse version: 3.0.2
Eclipse build id: 200503110845
Fresh Eclipse install (y/n): y
If not, was it upgraded to its current version using the update manager?
Other installed external plugins:
Number of plugins in the <eclipse>/plugins directory that begin with org.eclipse.pde.*:
MyEclipse version: 3.8.4
Eclipse JDK version: 1.4.2.04
Application Server JDK version:
Are there any exceptions in the Eclipse log file?If this is a DB related question please answer the following:
RDBMS vendor and version:
JDBC driver vendor and version, and access type (thin, type-2, etc):
Connection URL:
Eclipse error logs related to com.genuitec.eclipse.sqlexplorer packages:– Message Body ——————————-
My class files are not being generated.
No errors are showing up in the task window.
No errors in error log.
The icon at the project level in package explorer is showing error but no files in any package are showing compile errors.
If I run clean and rebuild, the compiles don’t seem to be attempted – but its hard to tell – no errors in error log.-Greg
Riyad KallaMemberGreg, you said there is an error marker at the project level, what does it say? What are your Source and Output dirs set to? What kind of project is this?
greg.granatoMemberIm not sure how to answer the question about the error marker – the only feedback I have ever noted is error messages in the task window. As I’ve said, there are no such messages. Where would I find out what that error marker ‘says’? The source dir is <project>/src and the output dir is <project>/bin. The project type is simple java. It seems like the compile is not even being attempted.
N.B. I have reinstalled Eclipse 2.1 and the appropriate MyEclipse version and copied my projects to that workspace. Everything works fine there without modification including the compilation from the same source dir to the correct output dir. I can continue w/ 2.1 but would like to migrate to 3.0.
Riyad KallaMemberIm not sure how to answer the question about the error marker – the only feedback I have ever noted is error messages in the task window. As I’ve said, there are no such messages.
You can try hovering over the error marker and see if the tooltip pops up. Additionally go to your Problems view (not tasks) and click the Down arrow in the top right corner, go to Filters, and click Select All, then OK. Are there any new problems shown?
It seems like the compile is not even being attempted.
Create a brand new project, File > New > Project > Java Project. Create a new class, is it compiled into the output dir?
Alternatively, I’d like to know what makes you think that the classes aren’t being compiled. Have you navigated to your output dir using the Navigation view and seen the bin dir is empty? Keep in mind that the output dir is implicitly hidden in the Package view, so you won’t be able to see it there.
N.B. I have reinstalled Eclipse 2.1 and the appropriate MyEclipse version and copied my projects to that workspace. Everything works fine there without modification including the compilation from the same source dir to the correct output dir. I can continue w/ 2.1 but would like to migrate to 3.0.
Are you using a Eclipse 2.1 workspace with Eclipse 3.0? If so, this could be part of the problem. Be sure to shut down Eclipse 3.0, edit the shortcut you use to start it, then add the parameter: -clean to the end of the command line and fire it up. This will allow Eclipse to rebuild a fresh plugin cache in your workspace, as the plugin cache between 2.1 and 3.0 are severly different. Once you’ve done that you can remove the -clean argument.
greg.granatoMemberI know the class files were not generated because they were not on the disk 😉
Running the -clean option on the shortcut took a long time to bring up the IDE but did not fix the problem.
I created a new workspace and created the projects within it through the GUI. I then added all my souce and external jar back into those projects manually. After that, it all seemed to work – including the fact that a ‘problems’ window now appears which didn’t exist earlier. The class files are created on the disk where I expect them to be.
The problem appears to have been related to the fact that the workspace was 2.1 – but -clean did not fix it.
Thanks for the help.
Riyad KallaMemberI suggest that you create a new empty workspace for Eclipse 3 and slowly File > import your projects… sharing a workspace between Eclipse 2.1 and 3.0 is a lot like sharing a C:\Windows\System folder between Windows 98 and Windows XP.
RaseshMemberHi Guys,
I had a similar problem. And here’s how I solved. First I selected the “Problems View”, this shows all the errors in detail. The problem was that some paths to jar were included in the project and the folders didn’t even exit, I just removed those jars. So just make sure that all the jars mentioned in the Java Build Path or the project lib are existing. I hope this will help, no need to reinstall eclipse or create a new project.Rasesh
David C BauerMemberI was going crazy until I hit your post Rasesh! Worked like a champ. I just removed all the jars from the classpath, and added back everything in my WEB-INF/lib folder. Everything is fine now.
-
AuthorPosts