[
https://issues.apache.org/jira/browse/SLING-6746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15947020#comment-15947020
]
Konrad Windszus commented on SLING-6746:
----------------------------------------
Agreed, can you make the according changes in parent? The enforcer rule sounds
useful in addition, I would just adjust the message so that it says something
like:
"maven-scr-plugin is incompatible with the manifest goal of the
maven-bundle-plugin. Please either remove Felix SCR annotations completely (and
migrate to OSGi annotations which are processed by the maven-bundle-plugin
itself) or use the SCR bnd plugin from
http://felix.apache.org/documentation/subprojects/apache-felix-maven-scr-plugin/apache-felix-scr-bndtools-use.html";
> Additional execution of maven-bundle-plugin:manifest is blanking out
> resources generated by maven-scr-plugin
> ------------------------------------------------------------------------------------------------------------
>
> Key: SLING-6746
> URL: https://issues.apache.org/jira/browse/SLING-6746
> Project: Sling
> Issue Type: Bug
> Components: General
> Affects Versions: Parent 30
> Reporter: Konrad Windszus
> Priority: Critical
>
> The additional execution of maven-bundle-plugin:manifest being added with
> SLING-6572 is basically overwriting the service descriptors and metatype
> resources which are written with maven-scr-plugin with empty files. Those
> empty files finally end up in the bundle. This affects all modules still
> leveraging the maven-scr-plugin for generating the service
> descriptors/metatype resources.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
