[
https://issues.apache.org/jira/browse/JCR-3136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting resolved JCR-3136.
--------------------------------
Resolution: Fixed
Fix Version/s: 2.3.3
Done in revision 1196706.
> Add m2e lifecycle mappings for Eclipse Indigo
> ---------------------------------------------
>
> Key: JCR-3136
> URL: https://issues.apache.org/jira/browse/JCR-3136
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: maven
> Reporter: Jukka Zitting
> Assignee: Jukka Zitting
> Priority: Minor
> Labels: eclipse, m2e, maven
> Fix For: 2.3.3
>
>
> When importing Jackrabbit to the latest Eclipse release (Indigo) that comes
> with m2e version 1.0, many of the POMs are flagged red because m2e doesn't
> know what to do with the custom plugin mappings we use in many components.
> This is a pretty contentious issue for m2e (see for example
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=350414), and ideally it should
> just work without any custom workarounds on our part.
> However, as a workaround until the core issue is solved, the best solution is
> to explicitly tell m2e what to do with these plugin mappings. The extra
> org.eclipse.m2e:lifecycle-mapping configuration is only active when used
> within Eclipse, so it doesn't affect
> normal builds.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
