[
https://issues.apache.org/jira/browse/FELIX-3358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13445703#comment-13445703
]
Carsten Ziegeler commented on FELIX-3358:
-----------------------------------------
Ok, I see, yes I agree we should try to make this a friendly plugin :)
Now, I think we could simply create a separate descriptor xml for each
component and then use the BuildContext to just process changed files and
regenerate the xml for those.
I'm still not against going the annotation processor way for the future, but
right now I think its the harder way to go :)
WDYT?
> 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
