You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by Daniel Kulp <dk...@apache.org> on 2013/10/08 18:14:08 UTC
Going to need some more releases....
Apparently the version ranges in some of the other bundles will exclude the new blueprint releases. Thus, we're going to need to do some minor patch releases to update the version ranges. JB is doing some testing to figure them out. Once we get a complete list and get them fixed, I'll start another round of releases.
When fixing this, what should we use for version ranges. Currently, we seem to have [1.0,1.2) which excludes the updated BP. Should we update that to [1.0,2) to avoid this with future BP releases?
--
Daniel Kulp
dkulp@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com
Re: Going to need some more releases....
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi all,
I checked and tested on Karaf trunk: only blueprint-cm should be updated.
I created:
https://issues.apache.org/jira/browse/ARIES-1124
and submitted a patch for that.
More over, for consistency, I created:
https://issues.apache.org/jira/browse/ARIES-1125
to update to blueprint-core 1.2.0 in all Aries modules.
So, we need a blueprint-cm 1.0.2 release with the "extended" version
range for blueprint-core.
Thanks,
Regards
JB
On 10/08/2013 06:14 PM, Daniel Kulp wrote:
>
> Apparently the version ranges in some of the other bundles will exclude the new blueprint releases. Thus, we're going to need to do some minor patch releases to update the version ranges. JB is doing some testing to figure them out. Once we get a complete list and get them fixed, I'll start another round of releases.
>
> When fixing this, what should we use for version ranges. Currently, we seem to have [1.0,1.2) which excludes the updated BP. Should we update that to [1.0,2) to avoid this with future BP releases?
>
>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com