No, this isn't the only change required.
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.
If we want to work on that, let me know when you've done the first bundle
and we can check that everything is ok before modifying all the other ones.
On Mon, Sep 7, 2009 at 10:06, Jean-Baptiste Onofré <[email protected]> wrote:
> Hi Guillaume,
>
> you have right, I have seen it when working on the bundles required by CXF.
> I guess that we only need to add ;version=${version} in the pom.xml of each
> bundle.
>
> I doesn't see any Jira on this topic yes.
>
> If all are right with this change, I raise a Jira task and begin today.
>
> Regards
> JB
>
>
> Guillaume Nodet wrote:
>
>> I think we have a problem with lots (if not all) of bundles we've
>> released.
>> Currently, they are importing their own package and do not use version
>> ranges.
>>
>> 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.
>>
>> So I kinda think we need to update all the poms to change those and
>> release
>> all those bundles.
>>
>>
>>
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com
