You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Konrad Windszus (Jira)" <ji...@apache.org> on 2022/06/24 05:44:00 UTC

[jira] [Created] (SLING-11412) Ban Aggregate OSGi artifacts

Konrad Windszus created SLING-11412:
---------------------------------------

             Summary: Ban Aggregate OSGi artifacts
                 Key: SLING-11412
                 URL: https://issues.apache.org/jira/browse/SLING-11412
             Project: Sling
          Issue Type: Improvement
          Components: General
            Reporter: Konrad Windszus
            Assignee: Konrad Windszus
             Fix For: Bundle Parent 49


According to http://docs.osgi.org/artifacts/

bq. .. it is generally recommended to use the individual artifacts, as this allows for more precise versioning. In particular, avoid using the osgi.cmpn artifact. After Release 7, the osgi.cmpn artifact is no longer published to Maven Central to encourage the use of the individual artifacts.

To enforce migration we should ban the osgi.cmpn and also the osgi.core artifacts via a Maven enforcer rule.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)