You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by Jean-Baptiste Onofré <jb...@nanthrax.net> on 2010/10/30 22:44:25 UTC
Dependency version alignment for ServiceMix 4.3.0
Hi all,
I begun to prepare ServiceMix 4 NMR and Features for the 4.3.0 release.
It means especially two things.
First, I update the features assembly to use the Camel 2.5.0 features
descriptor and avoid to override it. I updated the assembly to add
required bundle in the system repo.
Second, I aligned the dependencies set version to match Karaf, CXF and
Camel version (for exemple aopalliance bundle version, cglib version,
servicemix specs version, etc).
It means that I had to downgrade some dependencies version.
I propose:
- to align dependency to match Karaf, CXF and Camel dependencies version
(mostly Camel) to ServiceMix 4.3.0
- upgrade/submot a patch to Karaf, CXF and Camel to upgrade their
features descriptor.
For now, I stashed my changes waiting for your feedback.
Thanks,
Regards
JB
Re: Dependency version alignment for ServiceMix 4.3.0
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi Lukasz,
your proposal could work but, in a more general point of view, the
dependencies resolution should be make at runtime.
We can't start with the hypothesis that all projects are known by
ServiceMix.
For instance, if we want to plug Activiti BPM in ServiceMix, Activiti
guys can provide the features descriptor.
I'm more concerned by the fact that Karaf will provide better OBR
version management.
Regards
JB
On 11/02/2010 03:21 PM, Łukasz Dywicki wrote:
> Hi,
> Maybe my idea looks impossible but I am sure that it would make our life
> easier. All ASF middleware projects (SMX, Camel, ActiveMQ, CXF, Karaf)
> uses same artifacts but in different versions. Maybe extracting parent pom
> for all these projects is good idea?
> I know that will make cross project references - but with svn:externals it
> can be simply done.
> The releases in projects can be done in align with parent pom which would
> contain dependency management with Spring, Aries, Jetty and so on..
> Something like org.apache/apache pom + dependency management. What do you
> think?
>
> Best regards,
> Lukasz
>
>
> -----Original Message-----
> From: Jean-Baptiste Onofré [mailto:jb@nanthrax.net]
> Sent: Tuesday, November 02, 2010 12:27 PM
> To: dev@servicemix.apache.org
> Subject: Re: Dependency version alignment for ServiceMix 4.3.0
>
> Hi all,
>
> I made some progress around that.
>
> 1/ Camel 2.5.0 now uses Spring 3.0.4.RELEASE. Karaf 2.1.0 and ServiceMix
> use 3.0.3.RELEASE for now. I'm working on the Karaf 2.1.x branch to use
> the 3.0.4.RELEASE. It will be included in Karaf 2.1.1. Like this, Karaf,
> Camel and ServiceMix will use the same Spring version.
> ServiceMix will be based on Karaf 2.1.1 (and not 2.1.0).
> 2/ Camel 2.5.0 uses the ServiceMix bundles version before usage of the
> new naming convention. That's why we have a gap on quite all bundles. On
> the other hand, Camel uses directly commons-collections or commons-lang
> OSGi bundle. As these bundles suffer from some mistake in the export
> package statements, we have to use the ServiceMix wrap bundles for
> commons-collections and commons-lang. For these reasons, I will
> "override" the camel feature descriptor in ServiceMix.
> It means that ServiceMix will only use the Karaf features descriptor
> from the Karaf distribution, the other features descriptor (Camel,
> ActiveMQ, ODE, etc) are overrided in ServiceMix distribution.
> 3/ As we are going to use Karaf 2.1.1 and override Camel features
> descriptor, I'm gonna provide a bundle for Jetty 6.1.25 which provide
> important bug fixes (especially around performances). Jetty 6.1.25 will
> be used in Karaf 2.1.1 and ServiceMix (features and component).
>
> To summarize:
> - Step 1: I commit in Karaf 2.1.x branch to align dependencies with
> ServiceMix. Karaf 2.1.1 will be released soon after this commit.
> - ServiceMix 4.3.0 will use Karaf 2.1.1.
> - ServiceMix 4.3.0 will override features descriptor for ActiveMQ (due
> to a mistake in ActiveMQ 5.4.1 features descriptor, around console
> feature), Camel (due to dependency versions alignment), ODE (no features
> descriptor provided in ODE distribution).
>
> No objection ?
> If no, I have my planning for today :)
>
> I will keep you posted.
>
> Regards
> JB
>
> On 10/30/2010 10:44 PM, Jean-Baptiste Onofré wrote:
>> Hi all,
>>
>> I begun to prepare ServiceMix 4 NMR and Features for the 4.3.0 release.
>>
>> It means especially two things.
>>
>> First, I update the features assembly to use the Camel 2.5.0 features
>> descriptor and avoid to override it. I updated the assembly to add
>> required bundle in the system repo.
>>
>> Second, I aligned the dependencies set version to match Karaf, CXF and
>> Camel version (for exemple aopalliance bundle version, cglib version,
>> servicemix specs version, etc).
>> It means that I had to downgrade some dependencies version.
>>
>> I propose:
>> - to align dependency to match Karaf, CXF and Camel dependencies version
>> (mostly Camel) to ServiceMix 4.3.0
>> - upgrade/submot a patch to Karaf, CXF and Camel to upgrade their
>> features descriptor.
>>
>> For now, I stashed my changes waiting for your feedback.
>>
>> Thanks,
>> Regards
>> JB
>
RE: Dependency version alignment for ServiceMix 4.3.0
Posted by Łukasz Dywicki <lu...@code-house.org>.
Hi,
Maybe my idea looks impossible but I am sure that it would make our life
easier. All ASF middleware projects (SMX, Camel, ActiveMQ, CXF, Karaf)
uses same artifacts but in different versions. Maybe extracting parent pom
for all these projects is good idea?
I know that will make cross project references - but with svn:externals it
can be simply done.
The releases in projects can be done in align with parent pom which would
contain dependency management with Spring, Aries, Jetty and so on..
Something like org.apache/apache pom + dependency management. What do you
think?
Best regards,
Lukasz
-----Original Message-----
From: Jean-Baptiste Onofré [mailto:jb@nanthrax.net]
Sent: Tuesday, November 02, 2010 12:27 PM
To: dev@servicemix.apache.org
Subject: Re: Dependency version alignment for ServiceMix 4.3.0
Hi all,
I made some progress around that.
1/ Camel 2.5.0 now uses Spring 3.0.4.RELEASE. Karaf 2.1.0 and ServiceMix
use 3.0.3.RELEASE for now. I'm working on the Karaf 2.1.x branch to use
the 3.0.4.RELEASE. It will be included in Karaf 2.1.1. Like this, Karaf,
Camel and ServiceMix will use the same Spring version.
ServiceMix will be based on Karaf 2.1.1 (and not 2.1.0).
2/ Camel 2.5.0 uses the ServiceMix bundles version before usage of the
new naming convention. That's why we have a gap on quite all bundles. On
the other hand, Camel uses directly commons-collections or commons-lang
OSGi bundle. As these bundles suffer from some mistake in the export
package statements, we have to use the ServiceMix wrap bundles for
commons-collections and commons-lang. For these reasons, I will
"override" the camel feature descriptor in ServiceMix.
It means that ServiceMix will only use the Karaf features descriptor
from the Karaf distribution, the other features descriptor (Camel,
ActiveMQ, ODE, etc) are overrided in ServiceMix distribution.
3/ As we are going to use Karaf 2.1.1 and override Camel features
descriptor, I'm gonna provide a bundle for Jetty 6.1.25 which provide
important bug fixes (especially around performances). Jetty 6.1.25 will
be used in Karaf 2.1.1 and ServiceMix (features and component).
To summarize:
- Step 1: I commit in Karaf 2.1.x branch to align dependencies with
ServiceMix. Karaf 2.1.1 will be released soon after this commit.
- ServiceMix 4.3.0 will use Karaf 2.1.1.
- ServiceMix 4.3.0 will override features descriptor for ActiveMQ (due
to a mistake in ActiveMQ 5.4.1 features descriptor, around console
feature), Camel (due to dependency versions alignment), ODE (no features
descriptor provided in ODE distribution).
No objection ?
If no, I have my planning for today :)
I will keep you posted.
Regards
JB
On 10/30/2010 10:44 PM, Jean-Baptiste Onofré wrote:
> Hi all,
>
> I begun to prepare ServiceMix 4 NMR and Features for the 4.3.0 release.
>
> It means especially two things.
>
> First, I update the features assembly to use the Camel 2.5.0 features
> descriptor and avoid to override it. I updated the assembly to add
> required bundle in the system repo.
>
> Second, I aligned the dependencies set version to match Karaf, CXF and
> Camel version (for exemple aopalliance bundle version, cglib version,
> servicemix specs version, etc).
> It means that I had to downgrade some dependencies version.
>
> I propose:
> - to align dependency to match Karaf, CXF and Camel dependencies version
> (mostly Camel) to ServiceMix 4.3.0
> - upgrade/submot a patch to Karaf, CXF and Camel to upgrade their
> features descriptor.
>
> For now, I stashed my changes waiting for your feedback.
>
> Thanks,
> Regards
> JB
Re: Dependency version alignment for ServiceMix 4.3.0
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi all,
I made some progress around that.
1/ Camel 2.5.0 now uses Spring 3.0.4.RELEASE. Karaf 2.1.0 and ServiceMix
use 3.0.3.RELEASE for now. I'm working on the Karaf 2.1.x branch to use
the 3.0.4.RELEASE. It will be included in Karaf 2.1.1. Like this, Karaf,
Camel and ServiceMix will use the same Spring version.
ServiceMix will be based on Karaf 2.1.1 (and not 2.1.0).
2/ Camel 2.5.0 uses the ServiceMix bundles version before usage of the
new naming convention. That's why we have a gap on quite all bundles. On
the other hand, Camel uses directly commons-collections or commons-lang
OSGi bundle. As these bundles suffer from some mistake in the export
package statements, we have to use the ServiceMix wrap bundles for
commons-collections and commons-lang. For these reasons, I will
"override" the camel feature descriptor in ServiceMix.
It means that ServiceMix will only use the Karaf features descriptor
from the Karaf distribution, the other features descriptor (Camel,
ActiveMQ, ODE, etc) are overrided in ServiceMix distribution.
3/ As we are going to use Karaf 2.1.1 and override Camel features
descriptor, I'm gonna provide a bundle for Jetty 6.1.25 which provide
important bug fixes (especially around performances). Jetty 6.1.25 will
be used in Karaf 2.1.1 and ServiceMix (features and component).
To summarize:
- Step 1: I commit in Karaf 2.1.x branch to align dependencies with
ServiceMix. Karaf 2.1.1 will be released soon after this commit.
- ServiceMix 4.3.0 will use Karaf 2.1.1.
- ServiceMix 4.3.0 will override features descriptor for ActiveMQ (due
to a mistake in ActiveMQ 5.4.1 features descriptor, around console
feature), Camel (due to dependency versions alignment), ODE (no features
descriptor provided in ODE distribution).
No objection ?
If no, I have my planning for today :)
I will keep you posted.
Regards
JB
On 10/30/2010 10:44 PM, Jean-Baptiste Onofré wrote:
> Hi all,
>
> I begun to prepare ServiceMix 4 NMR and Features for the 4.3.0 release.
>
> It means especially two things.
>
> First, I update the features assembly to use the Camel 2.5.0 features
> descriptor and avoid to override it. I updated the assembly to add
> required bundle in the system repo.
>
> Second, I aligned the dependencies set version to match Karaf, CXF and
> Camel version (for exemple aopalliance bundle version, cglib version,
> servicemix specs version, etc).
> It means that I had to downgrade some dependencies version.
>
> I propose:
> - to align dependency to match Karaf, CXF and Camel dependencies version
> (mostly Camel) to ServiceMix 4.3.0
> - upgrade/submot a patch to Karaf, CXF and Camel to upgrade their
> features descriptor.
>
> For now, I stashed my changes waiting for your feedback.
>
> Thanks,
> Regards
> JB
Re: Dependency version alignment for ServiceMix 4.3.0
Posted by "Jamie G." <ja...@gmail.com>.
Regarding Karaf 2.1.1, if aligning the dependencies here can be seen
as a bug fix then I'm sure we can include it with the upcoming release
(2.1.x branch is being kept primarily for fixes, not new
features/enhancements).
Could you enter a Jira issue for Karaf 2.1.1 containing a patch with
the updated dependencies?
On Sun, Oct 31, 2010 at 6:08 AM, Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:
> Hi Gert,
>
> you have mostly right, it's mainly downgrade of our bundles (around the
> naming conventions).
>
> But, for instance, we have some upgrade to like Spring 3.0.4.RELEASE used in
> Camel.
>
> I propose to make a review on all dependencies to provide to you a complete
> overview.
>
> That I have in mind is:
> - align the dependencies in Karaf 2.1.1 (as it will be released soon just
> with some bug fixes)
> - align ServiceMix features
>
> I think that for ServiceMix 4.3.0, we can override the features descriptors
> but, as you said, we need to find a better way ;)
>
> I will send you a patch today.
>
> Thanks
> Regards
> JB
>
> On 10/31/2010 09:29 AM, Gert Vanthienen wrote:
>>
>> Jean-Baptiste,
>>
>> Thanks for looking into this! Personally, I'd rather see us override
>> a features descriptor than downgrade our own dependencies again. I
>> suspect the things to be downgraded are mostly our own bundles
>> revisions with the new naming, right? Or are there are real version
>> changes where our version was higher than the one provided by
>> Camel/Karaf/ActiveMQ? Could you send a list of bundles that need to
>> have their versions changed?
>>
>> After this release, I would propose we start working on
>> https://issues.apache.org/activemq/browse/SMX4-654 and also work with
>> the Camel/ActiveMQ/Karaf community to get the same thing done there.
>> That should make our lives a lot easier in the future...
>>
>> Regards,
>>
>> Gert Vanthienen
>> ------------------------
>> FuseSource
>> Web: http://fusesource.com
>> Blog: http://gertvanthienen.blogspot.com/
>>
>>
>>
>> On Sat, Oct 30, 2010 at 10:44 PM, Jean-Baptiste Onofré<jb...@nanthrax.net>
>> wrote:
>>>
>>> Hi all,
>>>
>>> I begun to prepare ServiceMix 4 NMR and Features for the 4.3.0 release.
>>>
>>> It means especially two things.
>>>
>>> First, I update the features assembly to use the Camel 2.5.0 features
>>> descriptor and avoid to override it. I updated the assembly to add
>>> required
>>> bundle in the system repo.
>>>
>>> Second, I aligned the dependencies set version to match Karaf, CXF and
>>> Camel
>>> version (for exemple aopalliance bundle version, cglib version,
>>> servicemix
>>> specs version, etc).
>>> It means that I had to downgrade some dependencies version.
>>>
>>> I propose:
>>> - to align dependency to match Karaf, CXF and Camel dependencies version
>>> (mostly Camel) to ServiceMix 4.3.0
>>> - upgrade/submot a patch to Karaf, CXF and Camel to upgrade their
>>> features
>>> descriptor.
>>>
>>> For now, I stashed my changes waiting for your feedback.
>>>
>>> Thanks,
>>> Regards
>>> JB
>>>
>
> --
> Jean-Baptiste Onofré
> ---------------------------------
> HomePage
> http://www.nanthrax.net
> ---------------------------------
> Contacts
> jbonofre@apache.org
> jb@nanthrax.net
> ---------------------------------
> OpenSource
> BuildProcess/AutoDeploy
> http://buildprocess.sourceforge.net
> Apache ServiceMix
> http://servicemix.apache.org
> -----------------------------------
> PGP : 17D4F086
>
Re: Dependency version alignment for ServiceMix 4.3.0
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi Gert,
you have mostly right, it's mainly downgrade of our bundles (around the
naming conventions).
But, for instance, we have some upgrade to like Spring 3.0.4.RELEASE
used in Camel.
I propose to make a review on all dependencies to provide to you a
complete overview.
That I have in mind is:
- align the dependencies in Karaf 2.1.1 (as it will be released soon
just with some bug fixes)
- align ServiceMix features
I think that for ServiceMix 4.3.0, we can override the features
descriptors but, as you said, we need to find a better way ;)
I will send you a patch today.
Thanks
Regards
JB
On 10/31/2010 09:29 AM, Gert Vanthienen wrote:
> Jean-Baptiste,
>
> Thanks for looking into this! Personally, I'd rather see us override
> a features descriptor than downgrade our own dependencies again. I
> suspect the things to be downgraded are mostly our own bundles
> revisions with the new naming, right? Or are there are real version
> changes where our version was higher than the one provided by
> Camel/Karaf/ActiveMQ? Could you send a list of bundles that need to
> have their versions changed?
>
> After this release, I would propose we start working on
> https://issues.apache.org/activemq/browse/SMX4-654 and also work with
> the Camel/ActiveMQ/Karaf community to get the same thing done there.
> That should make our lives a lot easier in the future...
>
> Regards,
>
> Gert Vanthienen
> ------------------------
> FuseSource
> Web: http://fusesource.com
> Blog: http://gertvanthienen.blogspot.com/
>
>
>
> On Sat, Oct 30, 2010 at 10:44 PM, Jean-Baptiste Onofré<jb...@nanthrax.net> wrote:
>> Hi all,
>>
>> I begun to prepare ServiceMix 4 NMR and Features for the 4.3.0 release.
>>
>> It means especially two things.
>>
>> First, I update the features assembly to use the Camel 2.5.0 features
>> descriptor and avoid to override it. I updated the assembly to add required
>> bundle in the system repo.
>>
>> Second, I aligned the dependencies set version to match Karaf, CXF and Camel
>> version (for exemple aopalliance bundle version, cglib version, servicemix
>> specs version, etc).
>> It means that I had to downgrade some dependencies version.
>>
>> I propose:
>> - to align dependency to match Karaf, CXF and Camel dependencies version
>> (mostly Camel) to ServiceMix 4.3.0
>> - upgrade/submot a patch to Karaf, CXF and Camel to upgrade their features
>> descriptor.
>>
>> For now, I stashed my changes waiting for your feedback.
>>
>> Thanks,
>> Regards
>> JB
>>
--
Jean-Baptiste Onofré
---------------------------------
HomePage
http://www.nanthrax.net
---------------------------------
Contacts
jbonofre@apache.org
jb@nanthrax.net
---------------------------------
OpenSource
BuildProcess/AutoDeploy
http://buildprocess.sourceforge.net
Apache ServiceMix
http://servicemix.apache.org
-----------------------------------
PGP : 17D4F086
Re: Dependency version alignment for ServiceMix 4.3.0
Posted by Gert Vanthienen <ge...@gmail.com>.
Jean-Baptiste,
Thanks for looking into this! Personally, I'd rather see us override
a features descriptor than downgrade our own dependencies again. I
suspect the things to be downgraded are mostly our own bundles
revisions with the new naming, right? Or are there are real version
changes where our version was higher than the one provided by
Camel/Karaf/ActiveMQ? Could you send a list of bundles that need to
have their versions changed?
After this release, I would propose we start working on
https://issues.apache.org/activemq/browse/SMX4-654 and also work with
the Camel/ActiveMQ/Karaf community to get the same thing done there.
That should make our lives a lot easier in the future...
Regards,
Gert Vanthienen
------------------------
FuseSource
Web: http://fusesource.com
Blog: http://gertvanthienen.blogspot.com/
On Sat, Oct 30, 2010 at 10:44 PM, Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:
> Hi all,
>
> I begun to prepare ServiceMix 4 NMR and Features for the 4.3.0 release.
>
> It means especially two things.
>
> First, I update the features assembly to use the Camel 2.5.0 features
> descriptor and avoid to override it. I updated the assembly to add required
> bundle in the system repo.
>
> Second, I aligned the dependencies set version to match Karaf, CXF and Camel
> version (for exemple aopalliance bundle version, cglib version, servicemix
> specs version, etc).
> It means that I had to downgrade some dependencies version.
>
> I propose:
> - to align dependency to match Karaf, CXF and Camel dependencies version
> (mostly Camel) to ServiceMix 4.3.0
> - upgrade/submot a patch to Karaf, CXF and Camel to upgrade their features
> descriptor.
>
> For now, I stashed my changes waiting for your feedback.
>
> Thanks,
> Regards
> JB
>