[
https://issues.apache.org/jira/browse/SLING-6746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15947004#comment-15947004
]
Konrad Windszus commented on SLING-6746:
----------------------------------------
This was kind of unexpected. Then we should IMHO completely remove the
maven-scr-plugin from the parent if it is now incompatible with other plugin
executions. That does not sound like a smooth migration path, therefore I would
rather propose to make the maven-bundle-plugin behave more reluctant before it
overwrites/blanks out those resources. Do you think this could be done in the
maven-bundle-plugin, or does it require a fix from bnd?
> 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)
