Uploaded image for project: 'ActiveMQ Classic'
  1. ActiveMQ Classic
  2. AMQ-6271

activemq-osgi defines wrong range for org.springframework.osgi...

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Duplicate
    • 5.13.3, 5.14.0
    • 5.13.4, 5.14.0
    • OSGi/Karaf
    • None

    Description

      The generated bundle manifest in activemq-osgi bundle defines wrong range for Spring OSGi packages:

      org.springframework.osgi.context.support;resolution:=optional;version="[3,5)"
      

      where the pom defines following

      org.springframework.osgi*;version="[1,4]";resolution:=optional
      

      I think, the maven-bundle-plugin generates wrong version when the subpackages are defined in pom after the super-package, like this

      org.springframework*;version="[3,5)";resolution:=optional,
      org.springframework.jms*;version="[3,5)";resolution:=optional,
      org.springframework.osgi*;version="[1,4]";resolution:=optional,
      org.springframework.transaction*;version="[3,5)";resolution:=optional,
      

      In this case org.springframework.osgi* packages will have generated the [3,5) version because the super package org.springframework* is defined first. Bug in maven-bundle-plugin or a feature?

      Btw. why do we need the range [1,4] for org.springframework.osgi*? It was introduced by https://github.com/apache/activemq/commit/3a6d67e8f95320bea91b7c7106173c9b34773bc5#diff-d5b8d20ad29a25abf3fbd33c79dafc9e (AMQ-4727). Previously was [1.2,1.3] (eventually [1.2, 2) ) and it should be ok, because we have (and will have) no newer version of Spring DM

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              sobkowiak Krzysztof Sobkowiak
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: