-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi everybody,
I am using maven and eclipse for more than five years now. All I have to say is that bringing these two together was crappy from the start and still is. So far what I can tell: 1. maven-eclipse-plugin does an excellent job. However integrating these two this way is just the wrong direction. The biggest problem here is eclipse itself what really sucks with its hyper intellectual virtual file system that has to be synced for every file that has been modified outside eclipse. Now if you have a really big project and change a very little thing such as adding a dependency, you have to go through the entire process of eclipse:eclipse and refreshing eclipse. This takes about 10 to 30 Minutes until Eclipse lets me continue to edit some file. Since eclipse 3.3 and 3.4 also phantom errors occur and I have to clean various projects to make the red crosses disappear. So far I am wrong here because the eclipse is to "blame". 2. m2eclipse is a nice idea and about what I am dreaming of. However it is so entirely full of bugs that it is completely useless for complex projects. Since my bug report was just rejected I stopped reporting bugs. But just to mention some here is that it automatically sets the "JRE System Library". In my case it has to be java6 for development. However the plugin is always smarter than I am and sets it back to java5 causing compilation errors. Further in another project I get ClassNotFoundErrors when launching from eclipse because m2eclipse misscalculates the classpath. Then if I use filtering and edit a filtered source-file m2eclipse does NOT update it (BTW there is a funny workaround to make filtering acceptable with mvn eclipse:eclipse). Besides when I have a look into the log of m2eclipse I get errors like: DEPRECATED: Binding aggregator mojos to lifecycle phases in the POM is considered dangerous. This feature has been deprecated. Please adjust your POM files accordingly. Offending mojo: org.apache.maven.plugins:maven-enforcer-plugin:1.0-alpha-3:enforce-once This does NOT show up, when I run maven on the commandline. What the hack is going on there. In the end using this plugin makes working with eclipse sometimes even slower than with 1. (eclipse:eclipse). While I edit some file, everything blocks and eclipse says it is "updating maven dependencies". Log says it is porcessing *javadoc.jar files - I dont want them. Too much magic as it seems... 3. Q4E / IAM Does NOT know about filtering. Does NOT understand scopes properly. Overall same problems with performance and blocking eclipse. In the end also useless for productive development in complex projects. So what is the chance? Wait for eclipse 4.0 supporting projects with sub-projects and wait some more years for one of the eclipse-plugins (2./3.) to work properly with this together? Bying IntelliJ Idea? Using Netbeans? I never tried this with maven. Any feedback? For the moment I have to stay with 1. because it is the only reliable way to make progress with my projects. Maybe there are some hints I have NOT yet discovered... Thanks for taking care... A frustrated lover of maven and eclipse ~ Jörg -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIikQwmPuec2Dcv/8RAiV3AJ4yfdeMntOA8RM7cEg8hsV8PjHhxwCfc9bk ZwbU9D2AdueiEJ+lrf3BoDQ= =fOaI -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
