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

Konrad Windszus updated SLING-11412:
------------------------------------
    Description: 
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.

In addition to those aspects, using the individual artifacts keeps the class 
path leaner (particularly relevant for transitive dependencies).

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

  was:
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.


> 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
>            Priority: Major
>             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.
> In addition to those aspects, using the individual artifacts keeps the class 
> path leaner (particularly relevant for transitive dependencies).
> 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)

Reply via email to