[
https://issues.apache.org/jira/browse/FELIX-4651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14143070#comment-14143070
]
Carsten Ziegeler commented on FELIX-4651:
-----------------------------------------
I think the current behaviour of the scr plugin is now finally correct, it does
not influence the resources anymore and just adds the resource it generates
itself.
As you state, if you remove the maven-scr-plugin, you get the same behaviour.
All versions before 1.20.0 are actually buggy in this respect.
I think this is more a question of the bundle plugin to pick such stuff up
> maven-scr-plugin spoils the Include-Resource of the maven-bundle-plugin
> -----------------------------------------------------------------------
>
> Key: FELIX-4651
> URL: https://issues.apache.org/jira/browse/FELIX-4651
> Project: Felix
> Issue Type: Bug
> Affects Versions: maven-scr-plugin 1.19.0, maven-scr-plugin 1.20.0
> Reporter: Konrad Windszus
> Priority: Critical
> Attachments: testbundle.zip
>
>
> Whenever the maven-scr-plugin is included in the build plugins (and executed
> as well), it will enrich the Include-Resource path for the
> maven-bundle-plugin. Therefore all files from target/classes/META-INF are
> included!
> With maven-scr-plugin 1.19.0 or newer, this is no longer the case.
> Also if the maven-scr-plugin does not take part in the build those files
> below target/classes/META-INF are not included!
> I am not sure whether this is a bug in the old version of the
> maven-scr-plugin or the new version. Please shed some light on this issue.
> You can reproduce with attached sample project:
> - Run {{mvn clean package}} -> Generated META-INF/dummy.tld ends up in the
> bundle
> - Now modify the pom to include the maven-scr-plugin in version 1.19.0
> -> Generated META-INF/dummy.tld no longer ends up in bundle.
> The same behaviour if you completely remove the maven-scr-plugin from the
> pom.xml.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
