[
https://issues.apache.org/jira/browse/SLING-6746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15947012#comment-15947012
]
Stefan Seifert commented on SLING-6746:
---------------------------------------
yes, we should remove maven-scr-plugin from parent - and it is not worth
investing any effort in making it play together because the is doing all that
maven-scr-plugin was doing before.
we may even use maven enforcer to ban the maven-scr-plugin from projects
updating to this parent pom - example:
https://github.com/wcm-io/wcm-io-tooling/blob/develop/maven/aem-global-parent/pom.xml#L158
> 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)
