[
https://issues.apache.org/jira/browse/FELIX-4241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13794086#comment-13794086
]
Robert Munteanu commented on FELIX-4241:
----------------------------------------
The conflict seems to be with the explicit pluginExecution definition for the
maven-scr-plugin. If I remove that, all works fine.
We already make sure we run on incremental changes for this version of the
plugin [1], are you sure you still need that block?
[1]:
http://svn.apache.org/repos/asf/felix/trunk/scrplugin/maven-scr-plugin/src/main/resources/META-INF/m2e/lifecycle-mapping-metadata.xml
> Change default output directory for SCR annotations to
> ${project.build.directory}/classes
> -----------------------------------------------------------------------------------------
>
> Key: FELIX-4241
> URL: https://issues.apache.org/jira/browse/FELIX-4241
> Project: Felix
> Issue Type: Improvement
> Components: Maven SCR Plugin
> Affects Versions: maven-scr-plugin 1.14.0
> Reporter: Robert Munteanu
> Assignee: Carsten Ziegeler
> Priority: Minor
> Fix For: maven-scr-plugin 1.15.0
>
> Attachments: FELIX-4242-1.patch
>
>
> Currently the plugin outputs the generated files under
> ${project.build.directory}/scr-plugin-generated . This change allows it to
> place its contents in the same place as the java compiled classes and the
> MANIFEST.MF generated by the maven-bundle-plugin.
> The result is that the exploded bundle contents is placed into a single
> directory and can be used by tooling - such as the Sling IDE tools - to
> incrementally update a bundle running in an OSGi container without going
> through a full maven package + deploy cycle.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
