Friday 13 November 2015

Painful Eclipse Gotchas

1. Validation on Startup

Validation happens on startup. With a lot of xml files in the project like ours, this can take minutes as it downloads Schema etc.

It would be better if this was disabled by default.

2. Update SVN Cache

Interestingly, this is a painful one where the eclipse locks up when opening up an existing workspace. If it doesn't crash it sits there at 99% forever (reports say it comes back after 30min)

The workaround is the delete the .project file of your Servers project. You will have to recreate your server however this is much less pain than waiting for it to finish.

3. Maven import doesn't create Java Projects

The Maven import imports the project but the classpath doesn't get set. What seemed to fix this is make the maven-compiler-plugin and maven-jar-plugin the same version (at least I think this is was solved the issue)

4. Server Deployment Location

Normally I set up the TCServer (tomcat) on my local machine and have multiple instances etc. The problem is I like to deploy to my server location rather than the .metadata folder. Imagine traversing to the location in the metadata folder, its difficult to remember (okay a right-click "Open Deployment Location" may work).  I think this should be a default, especially if one works in multiple workspaces.