[jira] Resolved: (SMX4-344) Add version ranges for OSGi imports

["Chris Custine (JIRA)" <ji...@apache.org>]

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

Chris Custine resolved SMX4-344.
--------------------------------

    Resolution: Won't Fix

This is resolved in a better way by the use of the bnd version policy.  Previous static version ranges have been removed during the Karaf merge.

> Add version ranges for OSGi imports
> -----------------------------------
>
>                 Key: SMX4-344
>                 URL: https://issues.apache.org/activemq/browse/SMX4-344
>             Project: ServiceMix 4
>          Issue Type: Improvement
>    Affects Versions: 4.0.0
>            Reporter: Chris Custine
>            Assignee: Chris Custine
>
> When we generate bundles for NMR and Features, the bundle plugin calculates a specific version for import, based on the maven dependency version.  Since we depend on Karaf for the runtime versions of many libraries (Spring, Spring-DM, etc), each time Karaf updates a library, there are many pom's to change and bundles must be rebuilt so that constraints match the server versions.  
> Updating to use version ranges on Import-Package will add a little overhead when there are major version changes, but should cut down on a lot of the work between most releases.  I don't intend to hand craft every package in a bundle's imports, but spring and spring-dm are obvious opportunities for now.
>  

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.