You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<li><p>Installed M2Eclipse extensions (in no particular order)</p></li>
198
199
<li><p>M2Eclipse 1.1+ lifecycle mapping metadata provided by maven plugin (see below)</p></li>
199
200
<li><p>Default lifecycle mapping metadata shipped with M2Eclipse</p></li>
200
-
</ol><p>M2Eclipse uses the first applicable mapping found.</p><h3><ahref="#lifecycle-mapping-metadata-provided-by-maven-plugin" name="lifecycle-mapping-metadata-provided-by-maven-plugin">Lifecycle mapping metadata provided by maven plugin</a></h3><p>Starting with m2e 1.1, maven plugin developers are able to provide lifecycle mapping metadata as part of the plugin itself. If present, such mapping metadata will be automatically used by m2e, thus eliminating the need for plugin specific project configurator and/or lifecycle mapping metadata in pom.xml.</p><p>[M2E compatible maven plugins](M2E compatible maven plugins “wikilink”) wiki page provides more information about developing m2e-compatible maven plugins that do not require external build lifecycle mapping configuration.</p><h3><ahref="#eclipse-workspace-lifecycle-mapping-metadata" name="eclipse-workspace-lifecycle-mapping-metadata">Eclipse workspace lifecycle mapping metadata</a></h3><p>Starting with M2Eclipse 1.2, it is now possible to configure lifecycle mapping metadata in m2e workspace preferences. Plugin goals can be ignored at workspace level using new quick-fix, which is available both from <code>pom.xml</code> editor and from Problems view. It is also possible to edit lifecycle mapping xml file directly. The file can be opened from Preferences->Maven->LifecycleMappings.</p><h2><ahref="#viewing-effective-lifecycle-mapping" name="viewing-effective-lifecycle-mapping">Viewing Effective Lifecycle Mapping</a></h2><p>Starting with M2Eclipse 1.1, it is now possible to see effective lifecycle mapping in Maven->LifecycleMapping project properties.</p><p><imgsrc="/assets/img/m2e-project-properties-lifecyclemapping.png" alt="Lifecycle""/></p><h2><ahref="#help-improve-m2eclipse-maven-plugin-coverage" name="help-improve-m2eclipse-maven-plugin-coverage">Help Improve M2Eclipse Maven Plugin Coverage</a></h2><p>First and foremost, you need to understand the desired behaviour. In most cases this should be limited to IDE usecase, i.e. editing sources and running tests, and not the complete Maven build, so plugin goals that publish build results to a remote repository can be ignored without any adverse side effects, while java source code generation most likely is necessary.</p><p>If the desired behaviour is applicable to other Maven projects using the plugin goal, we strongly recommend documenting your findings in m2e <ahref="https://bugs.eclipse.org/bugs/">bugzilla</a>. Please use “[mojo] plugin-artifact-id:goal support” bugzilla summary and make sure to <ahref="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=specific&order=relevance+desc&bug_status=__open__&product=m2e&content=mojo">search for existing records</a>. When submitting new request, please provide standalone example project and detailed description of desired behaviour when the project is imported in Eclipse workspace. This will allow other users and interested developers to track popularity of various Maven plugins and schedule implementation work accordingly.</p><p><ahref="/documentation/m2e-extension-development.html">M2E Extension Development</a> has pointers how to develop M2Eclipse extensions.</p><h2><ahref="#common-problems" name="common-problems">Common Problems</a></h2><p>Some Maven plugins are recognized as problematic and will produce error markers with a text similar to: <em>maven-dependency-plugin (goals “copy-dependencies”,“unpack”) is not supported by M2Eclipse</em></p><p>In version 1.0 there is no quick fix available for this but it is possible to define a lifecycle mapping for the plugin as well (as shown in <em>ignore plugin goal</em> above). Which removes the error marker.</p><h2>Eclipse 4.2 Adds Default Mapping</h2><p>If you are using Eclipse 4.2 and have troubles with mapping and won’t put mess into yours pom.xml create new file lifecycle-mapping-metadata.xml configure it in <strong>Windows -> Preferences -> Maven -> Lifecycle mapping</strong> . (don’t forget press <em>Reload workspace lifecycle mappings metadata</em> after each change of this file!).</p><p>If you have multiple Eclipse workspaces and/or work in a team, it is easy to get workspace-level configuration out-of-sync. This is unlikely to cause any confusion for <ignore /> mappings, but for <execute /> and <configurator /> mappings configuration in pom.xml or maven-plugin is strongly recommended.</p><p>Here is example based on eclipse/plugins/org.eclipse.m2e.lifecyclemapping.defaults_1.2.0.20120903-1050.jar/lifecycle-mapping-metadata.xml</p>
201
+
</ol><p>M2Eclipse uses the first applicable mapping found.</p><h3><ahref="#lifecycle-mapping-metadata-provided-by-maven-plugin" name="lifecycle-mapping-metadata-provided-by-maven-plugin">Lifecycle mapping metadata provided by maven plugin</a></h3><p>Starting with m2e 1.1, maven plugin developers are able to provide lifecycle mapping metadata as part of the plugin itself. If present, such mapping metadata will be automatically used by m2e, thus eliminating the need for plugin specific project configurator and/or lifecycle mapping metadata in pom.xml.</p><p>[M2E compatible maven plugins](M2E compatible maven plugins “wikilink”) wiki page provides more information about developing m2e-compatible maven plugins that do not require external build lifecycle mapping configuration.</p><h3><ahref="#eclipse-workspace-lifecycle-mapping-metadata" name="eclipse-workspace-lifecycle-mapping-metadata">Eclipse workspace lifecycle mapping metadata</a></h3><p>Starting with M2Eclipse 1.2, it is now possible to configure lifecycle mapping metadata in m2e workspace preferences. Plugin goals can be ignored at workspace level using new quick-fix, which is available both from <code>pom.xml</code> editor and from Problems view. It is also possible to edit lifecycle mapping xml file directly. The file can be opened from Preferences->Maven->LifecycleMappings.</p><h2><ahref="#viewing-effective-lifecycle-mapping" name="viewing-effective-lifecycle-mapping">Viewing Effective Lifecycle Mapping</a></h2><p>Starting with M2Eclipse 1.1, it is now possible to see effective lifecycle mapping in Maven->LifecycleMapping project properties.</p><p><imgsrc="/m2e/assets/img/m2e-project-properties-lifecyclemapping.png" alt="Lifecycle""/></p><h2><ahref="#help-improve-m2eclipse-maven-plugin-coverage" name="help-improve-m2eclipse-maven-plugin-coverage">Help Improve M2Eclipse Maven Plugin Coverage</a></h2><p>First and foremost, you need to understand the desired behaviour. In most cases this should be limited to IDE usecase, i.e. editing sources and running tests, and not the complete Maven build, so plugin goals that publish build results to a remote repository can be ignored without any adverse side effects, while java source code generation most likely is necessary.</p><p>If the desired behaviour is applicable to other Maven projects using the plugin goal, we strongly recommend documenting your findings in m2e <ahref="https://bugs.eclipse.org/bugs/">bugzilla</a>. Please use “[mojo] plugin-artifact-id:goal support” bugzilla summary and make sure to <ahref="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=specific&order=relevance+desc&bug_status=__open__&product=m2e&content=mojo">search for existing records</a>. When submitting new request, please provide standalone example project and detailed description of desired behaviour when the project is imported in Eclipse workspace. This will allow other users and interested developers to track popularity of various Maven plugins and schedule implementation work accordingly.</p><p><ahref="/documentation/m2e-extension-development.html">M2E Extension Development</a> has pointers how to develop M2Eclipse extensions.</p><h2><ahref="#common-problems" name="common-problems">Common Problems</a></h2><p>Some Maven plugins are recognized as problematic and will produce error markers with a text similar to: <em>maven-dependency-plugin (goals “copy-dependencies”,“unpack”) is not supported by M2Eclipse</em></p><p>In version 1.0 there is no quick fix available for this but it is possible to define a lifecycle mapping for the plugin as well (as shown in <em>ignore plugin goal</em> above). Which removes the error marker.</p><h2>Eclipse 4.2 Adds Default Mapping</h2><p>If you are using Eclipse 4.2 and have troubles with mapping and won’t put mess into yours pom.xml create new file lifecycle-mapping-metadata.xml configure it in <strong>Windows -> Preferences -> Maven -> Lifecycle mapping</strong> . (don’t forget press <em>Reload workspace lifecycle mappings metadata</em> after each change of this file!).</p><p>If you have multiple Eclipse workspaces and/or work in a team, it is easy to get workspace-level configuration out-of-sync. This is unlikely to cause any confusion for <ignore /> mappings, but for <execute /> and <configurator /> mappings configuration in pom.xml or maven-plugin is strongly recommended.</p><p>Here is example based on eclipse/plugins/org.eclipse.m2e.lifecyclemapping.defaults_1.2.0.20120903-1050.jar/lifecycle-mapping-metadata.xml</p>
0 commit comments