Uploaded image for project: 'Sling'
  1. Sling
  2. SLING-11412

Ban aggregate OSGi artifacts

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • Bundle Parent 49
    • General
    • None

    Description

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

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

      Attachments

        Activity

          People

            kwin Konrad Windszus
            kwin Konrad Windszus
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0h
                0h
                Logged:
                Time Spent - 20m
                20m