Dynamic dependency resolution, including workspace dependency resolution, is the first thing that comes to mind. m2e configures project compile and test classpath based on configuration it derives from pom.xml. As a developer you don't need to do anything beyond declared your dependencies in pom.xml, and m2e will automatically switch between workspace projects and artifacts resolved from (remote) artifacts repositories based on dependency versions declared in pom.xml and versions of workspace projects.
The rest really depends on what kind of projects you work on. For example, if you do java ee development, i.e. webapps and such, there are couple of m2e extensions that read maven-war-plugin configuration and configure workspace projects accordingly. There is also support for other common maven plugin and, to me the most important part, m2e is an open platform with many ways to integrate, so with some effort you can have very well integrated end-to-end user experience that behaves consistently from IDE to command line build to CI system. -- Regards, Igor On 12-08-31 10:06 AM, KARR, DAVID wrote:
I'm preparing a couple of presentations arguing a transition from Ant to Maven for an organization. I'm gathering background information about Maven-related tools. I noticed in a recent note here that m2e provides some features by interrogating the configuration of specific plugins in the project pom. Could some of you give me a list of several significant features in m2e that are provided by interrogating plugin configurations? _______________________________________________ m2e-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/m2e-users
_______________________________________________ m2e-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/m2e-users
