Introduction to m2eclipse

Previous | Next

By kongxx
via theserverside.com
Published: Jul 15 2008 / 14:57

The Eclipse IDE is the most widely used IDE for Java development today. At the same time, Apache Maven continues to mature, and has grown to be the industry standard for creating extensible and reliable enterprise builds. While it is certainly possible to develop applications in Eclipse and use Maven as a command-line build tool, most developers expect the IDE to know how to invoke and interact with the build tool they are using.

Vote up

Vote down

14
0
1199
352

Save Send Tags: java

Upcoming Links

See all the newest links

Comments

Add your comment

willcode4beer replied ago:

0 votes

Pretty good. The only issue being that having only one variable, "Maven Dependencies", doesn't express the Maven concept of scopes (compile, provided, runtime, test, system, and import).
So, you end up with extra libs being deployed when running servers from Eclipse.
Some, like Tomcat and JBoss don't work so well when they have the api libraries deployed in the app.

The plugin has come a long way though. It is greatly improved over previous releases.
Kudos to the m2eclipse developers

Eugene Kuleshov replied ago:

0 votes

It is worth to clarify that "Maven Dependencies" container represents Maven's "test" scope, which is required to compile tests (simply because Eclipse only allow to have single classpath for the entire project). However "Maven Dependencies" container is not being used to construct "runtime" and "test" classpath then you use "Java App" or "JUnit" launch configurations in Eclipse. Instead, m2eclipse contributes special classpath provider that uses appropriate Maven scope for those launch configurations. Similarly, WTP integration is taking "provided" scope into the account. If you see otherwise, please submit bug report and provide test project that would allow to reproduce it. Thanks.