Agree,
I'm raising the Karaf Jira (if it's not already done) and I'm gonna work
on it.
Regards
JB
On 10/28/2011 11:51 AM, Gert Vanthienen wrote:
Jean-Baptiste,
Removing the<repository/> would avoid the issue, but it would also cause
the Camel descriptor to no longer be self-contained, so people would need to
read the documentation in order to get things working. One of the proposals
in the karaf-dev thread I referred to earlier, is to ensure that version
ranges are fully supported in the<repository/> element by first checking if
there's already a matching descriptor installed and, if not, go out and
resolve a suitable version using Pax Url's Maven version range support.
Personally, I'd just keep the tag for now and improve things at the Karaf
end first, as that would fix the same issue for e.g. some of the ServiceMix
features descriptors as well. Once the Karaf improvements have been made,
we can start using version ranges in the<repository/> references and get
the best of both worlds - a self-contained features descriptor that allows
for the flexibility to switch to a newer fix version as well.
Regards,
Gert Vanthienen
------------------------
FuseSource
Web: http://fusesource.com
Blog: http://gertvanthienen.blogspot.com/
On Fri, Oct 28, 2011 at 11:39 AM, Jean-Baptiste Onofré<j...@nanthrax.net>wrote:
Hi Gert,
+1 for a new Camel 2.8.3 release.
I would propose to remove the<repository/> tag for CXF.
It doesn't make sense to use a version range for the CXF feature, but still
specify a CXF version in the<repository/> tag.
I would prefer to document for the users that they have to install the cxf
feature first.
WDYT ?
Regards
JB
On 10/28/2011 10:23 AM, Gert Vanthienen wrote:
L.S.,
Over at the ServiceMix project, we are finalizing things for doing a
ServiceMix 4.4.0 release. The original plan was to use CXF 2.4.2 and
Camel
2.8.1 because of an issue with the CXF 2.4.3 release in combination with
Felix. However, Dan has volunteered to do a quick CXF 2.4.4 release to
help
us out which the CXF problem. Cfr.
http://servicemix.396122.n5.**nabble.com/Toward-ServiceMix-**
4-4-td4909262.htmlfor<http://servicemix.396122.n5.nabble.com/Toward-ServiceMix-4-4-td4909262.htmlfor>
some background...
Unfortunately, because of a<repository> reference in the Camel features
descriptor, that would mean we would also need a new Camel 2.8.x release
to
ensure everything works fine again. I'm aware that the release
announcement
for 2.8.2 only went out earlier this week, so just checking if we would
consider doing a Camel 2.8.3 release right after the CXF 2.4.4 release is
out. For the Apache ServiceMix project, this would definitely be highly
appreciated, as it would allow us to upgrade to the latest and greatest
Karaf, CXF and Camel for our upcoming release.
FWIW, in the meanwhile we're also working at both the Karaf and the
ServiceMix end to make a things a more reliable and maintainable when
upgrading parts of the application, so this should allow us to prevent
these
kinds of issues in the future, but for now we're still trying to align the
entire universe here ;)
Regards,
Gert Vanthienen
------------------------
FuseSource
Web: http://fusesource.com
Blog: http://gertvanthienen.**blogspot.com/<http://gertvanthienen.blogspot.com/>
--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
