Comments on: M2Eclipse Plugin is not for me http://twasink.net/blog/2009/06/m2eclipse-plugin-is-not-for-me/ Robert's Rambling Ruminations Regarding Reality Mon, 19 Jul 2010 23:02:46 -0400 http://wordpress.org/?v=2.8.4 hourly 1 By: Robert http://twasink.net/blog/2009/06/m2eclipse-plugin-is-not-for-me/comment-page-1/#comment-1027 Robert Thu, 25 Feb 2010 22:14:35 +0000 http://twasink.net/blog/?p=650#comment-1027 Like this: <pre> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-eclipse-plugin</artifactId> <version>2.5.1</version> <configuration> <downloadSources>true</downloadSources><!-- Having source code references is a "Good Thing" (tm) --> <downloadJavadocs>true</downloadJavadocs><!-- Having source code references is a "Good Thing" (tm) --> <buildOutputDirectory>${eclipse.classes.dir}</buildOutputDirectory><!-- Not having to re-compile everything inside Eclipse just because you've done a Maven clean is also a "Good Thing" (tm), but not everyone likes it, so it's configurable (and off by default) --> <useProjectReferences>true</useProjectReferences> </configuration> </plugin> </pre> Like this:

<plugin>
    <groupId>org.apache.maven.plugins</groupId>
    <artifactId>maven-eclipse-plugin</artifactId>
    <version>2.5.1</version>
    <configuration>
        <downloadSources>true</downloadSources><!-- Having source code references is a "Good Thing" (tm) -->
        <downloadJavadocs>true</downloadJavadocs><!-- Having source code references is a "Good Thing" (tm) -->
        <buildOutputDirectory>${eclipse.classes.dir}</buildOutputDirectory><!-- Not having to re-compile everything inside Eclipse just because you've done a Maven clean is also a "Good Thing" (tm), but not everyone likes it, so it's configurable (and off by default) -->
        <useProjectReferences>true</useProjectReferences>
    </configuration>
</plugin>
]]> By: EDH http://twasink.net/blog/2009/06/m2eclipse-plugin-is-not-for-me/comment-page-1/#comment-1017 EDH Thu, 11 Feb 2010 17:08:19 +0000 http://twasink.net/blog/?p=650#comment-1017 Are you sure about "Of course you can change the output-folder by modifying your pom.xml to have separate output-folders for your class-files". My experience is that a lot of Maven plugin cannot be configured to produce their output in a particular non-default location. 80 of your output will be produced in a separate folder, but 20 will still be produced in the same target folder, resulting in an even bigger nightmare. Or am I wrong ? I hope so. Are you sure about “Of course you can change the output-folder by modifying your pom.xml to have separate output-folders for your class-files”.
My experience is that a lot of Maven plugin cannot be configured to produce their output in a particular non-default location. 80 of your output will be produced in a separate folder, but 20 will still be produced in the same target folder, resulting in an even bigger nightmare.
Or am I wrong ? I hope so.

]]> By: Ustaman http://twasink.net/blog/2009/06/m2eclipse-plugin-is-not-for-me/comment-page-1/#comment-1016 Ustaman Tue, 09 Feb 2010 16:59:57 +0000 http://twasink.net/blog/?p=650#comment-1016 @Benedict 1. Of course you can change the output-folder by modifying your pom.xml to have separate output-folders for your class-files. U mean the output folder for eclipse could be configured to be different than the one in the pom.xml? How? @Benedict
1. Of course you can change the output-folder by modifying your pom.xml to have separate output-folders for your class-files.
U mean the output folder for eclipse could be configured to be different than the one in the pom.xml? How?

]]> By: Benedikt http://twasink.net/blog/2009/06/m2eclipse-plugin-is-not-for-me/comment-page-1/#comment-779 Benedikt Fri, 10 Jul 2009 12:40:09 +0000 http://twasink.net/blog/?p=650#comment-779 Just some notes from my experience with the plugin to address your issues: 1. Of course you can change the output-folder by modifying your pom.xml to have separate output-folders for your class-files. 2. You can tell the plugin which maven installation it should use and it doesn't break anything if you do so. 3. If you don't use the internamm maven builder then maven will use the JRE configured under "Installed JREs". Give it a try - it takes a little time getting used to but I wouldn't want to miss working with the plugin. Just some notes from my experience with the plugin to address your issues:

1. Of course you can change the output-folder by modifying your pom.xml to have separate output-folders for your class-files.
2. You can tell the plugin which maven installation it should use and it doesn’t break anything if you do so.
3. If you don’t use the internamm maven builder then maven will use the JRE configured under “Installed JREs”.

Give it a try – it takes a little time getting used to but I wouldn’t want to miss working with the plugin.

]]> By: Robert http://twasink.net/blog/2009/06/m2eclipse-plugin-is-not-for-me/comment-page-1/#comment-765 Robert Thu, 18 Jun 2009 21:01:58 +0000 http://twasink.net/blog/?p=650#comment-765 I will definitely keep an eye on it. Thanks, Brian. I will definitely keep an eye on it. Thanks, Brian.

]]> By: Brian Fox http://twasink.net/blog/2009/06/m2eclipse-plugin-is-not-for-me/comment-page-1/#comment-764 Brian Fox Thu, 18 Jun 2009 14:42:25 +0000 http://twasink.net/blog/?p=650#comment-764 I hope you take another look when M2e 0.9.9 is released. This version significantly alters how the maven and eclipse integration is performed. Instead of using the maven lifecycle inside the IDE, it instead delegates only certain pieces to maven plugins and the rest is left to eclipse. These changes should address all three of your concerns. I hope you take another look when M2e 0.9.9 is released. This version significantly alters how the maven and eclipse integration is performed. Instead of using the maven lifecycle inside the IDE, it instead delegates only certain pieces to maven plugins and the rest is left to eclipse. These changes should address all three of your concerns.

]]> By: Robert http://twasink.net/blog/2009/06/m2eclipse-plugin-is-not-for-me/comment-page-1/#comment-762 Robert Wed, 17 Jun 2009 13:12:53 +0000 http://twasink.net/blog/?p=650#comment-762 Maven is definitely not a "slam-dunk" decision to use, that's for sure. It has many benefits, but also a lot of pain. In our situation at work, Maven has been a nett win. It's just been (and continues to be) a very bumpy ride. Maven is definitely not a “slam-dunk” decision to use, that’s for sure. It has many benefits, but also a lot of pain.

In our situation at work, Maven has been a nett win. It’s just been (and continues to be) a very bumpy ride.

]]> By: John Smith http://twasink.net/blog/2009/06/m2eclipse-plugin-is-not-for-me/comment-page-1/#comment-761 John Smith Wed, 17 Jun 2009 13:10:20 +0000 http://twasink.net/blog/?p=650#comment-761 One more reason not to use maven. One more reason not to use maven.

]]> By: Dan Everton http://twasink.net/blog/2009/06/m2eclipse-plugin-is-not-for-me/comment-page-1/#comment-759 Dan Everton Tue, 16 Jun 2009 21:57:05 +0000 http://twasink.net/blog/?p=650#comment-759 The Eclipse IAM project (formerly Q4E) seems be the new hotness for Maven Eclipse integration. I've never had much luck with m2eclipse, but IAM at least seems to work on smaller projects without drastically slowing down smaller projects. http://www.eclipse.org/iam/ The Eclipse IAM project (formerly Q4E) seems be the new hotness for Maven Eclipse integration. I’ve never had much luck with m2eclipse, but IAM at least seems to work on smaller projects without drastically slowing down smaller projects.

http://www.eclipse.org/iam/

]]>