You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Stefan Seifert (JIRA)" <ji...@apache.org> on 2017/03/29 12:59:41 UTC

[jira] [Resolved] (SLING-6746) Remove and ban maven-scr-plugin

     [ https://issues.apache.org/jira/browse/SLING-6746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stefan Seifert resolved SLING-6746.
-----------------------------------
    Resolution: Fixed

Completed: At revision: 1789357  

i added this message to the ban: "Felix SCR annotations and the maven-scr-plugin are no longer supported - please migrate to OSGi annotations or stick with Sling Parent 29."

> Remove and ban 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
>            Assignee: Stefan Seifert
>            Priority: Critical
>             Fix For: Parent 31
>
>
> 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)