[
https://issues.apache.org/jira/browse/SLING-6746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15947000#comment-15947000
]
Stefan Seifert commented on SLING-6746:
---------------------------------------
the solution should be to completely remove the maven-scr-plugin and instead
add this bnd plugin to maven bundle plugin:
{noformat}
<_plugin>org.apache.felix.scrplugin.bnd.SCRDescriptorBndPlugin;destdir=${project.build.outputDirectory}</_plugin>
{noformat}
and
{code:xml}
<dependency>
<groupId>org.apache.felix</groupId>
<artifactId>org.apache.felix.scr.bnd</artifactId>
<version>1.7.2</version>
</dependency>
{code}
as discussed in SLING-6649 this should not go into sling parent, but has to be
defined for those project poms still using scr annotations until they migrate
to osgi annotations (or stick with an older version of sling parent).
> 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)
