servicemix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean-Baptiste Onofré (JIRA) <j...@apache.org>
Subject [jira] Commented: (SMX4-354) OSGi bundles and versioning
Date Thu, 04 Feb 2010 15:51:33 GMT

    [ https://issues.apache.org/activemq/browse/SMX4-354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=57383#action_57383
] 

Jean-Baptiste Onofré commented on SMX4-354:
-------------------------------------------

Change applied on all service engine components.

> OSGi bundles and versioning
> ---------------------------
>
>                 Key: SMX4-354
>                 URL: https://issues.apache.org/activemq/browse/SMX4-354
>             Project: ServiceMix 4
>          Issue Type: Improvement
>            Reporter: Jean-Baptiste Onofré
>            Assignee: Jean-Baptiste Onofré
>
> Importing their own package may lead to real problems when deploying two
> different versions of such a bundle.  There is a high chance that the second
> one will use the classes from the first one instead of their own classes.
> Version ranges are also important to avoid some problems if the bundle is
> wired to a dependent bundle with a new major version.
> First, we need to upgrade to the maven-bundle-plugin 2.0.0 (in the parent
> pom for all bundles).
> We need to add the following instruction for the maven bundle plugin:
>      <_versionpolicy>[$(version;==;$(@)),$(version;+;$(@)))</_versionpolicy>
> Then for each bundle, we need to make sure each package exported is not
> imported.   For example, if we have:
>    <Export-Package>org.apache.commons.codec*</Export-Package>
> we need to add the following to imports:
>     !org.apache.commons.codec*
> This line needs to be added at the beginning of the Import-Package
> declaration.

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


Mime
View raw message