[
https://issues.apache.org/jira/browse/TOMEE-623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13510047#comment-13510047
]
Harald Wellmann commented on TOMEE-623:
---------------------------------------
No, all these settings are specific to m2e and Eclipse, they do not affect
Maven, and you cannot define them in settings.xml.
Anyway, I've just noticed that you no longer need to modify POMs as of m2e 1.2.
You can now define the lifecycle mappings in a workspace config file or from
the IDE via Window | Preferences | Maven | Lifecycle Mappings.
(Editing the POMs is still possible and has the advantage of providing the
settings in a central place, as opposed to everyone having to modify their
workspace. OTOH, I do agree it's not really nice or intuitive to have IDE
specific settings in the POMs.)
So I attach a second version of the patch that does not add any m2e lifecycle
mappings to the POMs. Instead, there's a file etc/eclipse/lifecycle-mapping.xml
which needs to be merged with any mappings the user already has in their
workspace.
> Make TomEE m2e-friendly
> -----------------------
>
> Key: TOMEE-623
> URL: https://issues.apache.org/jira/browse/TOMEE-623
> Project: TomEE
> Issue Type: Improvement
> Affects Versions: 1.5.0
> Reporter: Harald Wellmann
> Fix For: 1.5.1
>
> Attachments: TOMEE-623.2.patch, TOMEE-623.patch
>
>
> Use Case
> * You are working with Eclipse Indigo or Juno and the latest m2e release for
> Maven support.
> * You want to import the TomEE/OpenEJB source tree to start hacking TomEE.
> Problem
> * Most subprojects have error markers caused by Maven plugins unknown to m2e.
> Solution:
> * Configure the org.eclipse.m2e:lifecycle-mapping Maven plugin in the
> pluginManagement section of the OpenEJB parent POM.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
