[
https://issues.apache.org/jira/browse/FELIX-3358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13445256#comment-13445256
]
Timo Naroska commented on FELIX-3358:
-------------------------------------
Marking it as ignored means I don't get any feedback in the IDE during
development of SCR annotated classes. It also means that projects using scr
annotations are not usable in eclipse PDE (using m2e-tycho connectors) or
pax-exam tests run in the IDE. Both workflows require that the ds files are
created within the IDE.
I'd even prefer to have no lifecycle mapping at all rather than having it
ignored. Suppose someone with no knowledge about scr imports an scr project
into eclipse. Without the lifecycle mapping he gets an error in the pom, which
is bad, but at least you get a hint that something is amiss. Now, with the
ignore-lifecycle mapping scr is silently ignored. No warning, but also no ds
files being generated. This is something that can cost a poor developer hours
of investigation. JM2C
> Enhance the maven-scr-plugin to be compatible with recent Maven/Eclipse
> integrations
> ------------------------------------------------------------------------------------
>
> Key: FELIX-3358
> URL: https://issues.apache.org/jira/browse/FELIX-3358
> Project: Felix
> Issue Type: Improvement
> Components: Maven SCR Plugin
> Affects Versions: maven-scr-plugin-1.8.0
> Environment: Eclipse Indigo or newer
> Reporter: Robert Munteanu
> Fix For: maven-scr-plugin-1.8.2
>
> Attachments: m2e-lifecycle-mapping.diff
>
>
> With the recent changes brought to the Maven Eclipse integration, any unknown
> [0] plugins are flagged as problematic and an error is reported in the
> pom.xml . Typically this is solved by writing a thin integration layer
> between the Eclipse integration and the Maven plugin [1] or by instructing
> Eclipse to ignore some plugin executions.
> The new 1.1 version of the m2eclipse plugin will allow a Maven plugin ( with
> no links to Eclipse plugin development ) to use an enhanced API to become
> compatible out of the box with the Eclipse integration [2] .
> The maven-scr-plugin should take advantage of these new APIs to allow
> seamless integration with Eclipse.
> [0]: http://wiki.eclipse.org/M2E_plugin_execution_not_covered
> [1]: http://wiki.eclipse.org/M2E/Extension_Development
> [2]: http://wiki.eclipse.org/M2E_compatible_maven_plugins
--
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
