Uploaded image for project: 'Weld'
  1. Weld
  2. WELD-1407

Cleaning up weld-osgi bundles versions: versions in bnd files shouldn't be hard coded and use maven versions

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • None
    • None
    • OSGi support
    • None

    Description

      While trying to use the 1.2.0.Beta1 of weld-osgi, launching weld-osgi bundles in felix wasn't working properly as some runtime dependencies were not satified

      Constraint violation for package 'org.jboss.weld.environment.se' when resolving module 14.0
        between existing export 14.0.org.jboss.weld.environment.se
         NO BLAME and uses constraint 2.0.org.jboss.weld.environment.se
         BLAMED ON [[14.0] package; (&(package=org.jboss.weld.environment.se)(version>=1.2.0.SNAPSHOT))]
      

      The problem is bnd files that generates OSGi manifest.mf have hard coded versions:

      in core / environments / osgi / core / integration / src / main / resources / META-INF / weld-osgi-core-integration.bnd

      ...
       org.jboss.weld.environment.se.events; \
       org.jboss.weld.environment.se.bindings; \
       org.jboss.weld.environment.se.threading; \
       org.jboss.weld.environment.se.beans; \
       org.jboss.weld.environment.se.discovery; \
       org.jboss.weld.environment.se.discovery.url; \
       org.jboss.weld.environment.se.contexts; \
       org.jboss.weld.messages; version=1.2.0-SNAPSHOT
      ...
      

      This should be fixed to avoid issues for the next release.

      Additional work may be needed to remove all the hard coded dependencies in theses files (mostly testing and checking if it's really necessary)

      Attachments

        Activity

          People

            sutan@redhat.com Sun Tan
            sutan@redhat.com Sun Tan
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: