Hi Dan,
I tested camel-jibx, camel-hdfs, camel-atom, camel-rss, camel-jibx
features. It deploys without problem.
It looks good to me now and equivalent to that we have on Camel 2.8.x.
Regards
JB
On 12/27/2011 04:00 AM, Daniel Kulp wrote:
On Tuesday, December 27, 2011 12:14:09 AM Guillaume N
On Tuesday, December 27, 2011 12:14:09 AM Guillaume Nodet wrote:
> I'm not talking short term here, so having to release the specs is
> good for me, especially if they include the changes i've been talking
> about.
> For the short term, I've no problems reverting to the previous working
> state.
T
On Monday, December 26, 2011 9:48:44 PM Guillaume Nodet wrote:
> Wouldn't it be easier to fix the imported version ranges of camel-soap
> instead ? If we think we should be able to deploy it on a plain JRE, we
> should import jaxb with no version range.
> I think that should be the case for most of
I'm not talking short term here, so having to release the specs is
good for me, especially if they include the changes i've been talking
about.
For the short term, I've no problems reverting to the previous working state.
On Mon, Dec 26, 2011 at 21:54, Jean-Baptiste Onofré wrote:
> Yes, but the m
Yes, but the modification is not in the Camel component, it's in the
ServiceMix spec (it's where the version range should be updated).
I can do the fix, but it requires a new release of ServiceMix specs.
Regards
JB
On 12/26/2011 09:48 PM, Guillaume Nodet wrote:
Wouldn't it be easier to fix th
Wouldn't it be easier to fix the imported version ranges of camel-soap instead ?
If we think we should be able to deploy it on a plain JRE, we should
import jaxb with no version range.
I think that should be the case for most of the JRE provided packages.
Also, I had done some experiments in deplo
Hi Guillaume,
first of all, merry Christmas to you and your family ;)
Let me try to explain the current situation.
In Camel, we have several features which depend on ServiceMix JAX-WS
Spec (for instance, camel-soap).
The ServiceMix Specs explicitly define an import package like:
javax.xml.bi
Do you have pointers to the problems ? All those packages are provided by
the JRE so they should not have to be installed imho.
Anyway, I'm in vacation until january so feel free to revert the xml
definition, i doubt i won't be able to do that this week.
On Monday, December 26, 2011, Daniel Kulp
I would like to see the changes from JB included. I run the test with Karaf
2.2.2, Karaf 2.2.4 and 2.2.5 and I could install all features without the
need to tune the jre.properties, the custom.properties or to install some
other features/bundles before. For the current Karaf (and SMX) versions I
d
Fully agree, it's what I did in my latest commits.
As I answered to Willem, I would prefer to have all features installable
out of the box and document the way we tune the jre.properties
(especially, starting from Karaf 2.2.5, we ship a jre.properties.cxf
commenting the packages).
I'm waitin
The discussions around the entire xml-specs/jaxb/etc... stuff in the features
file has shown that this commit has caused a lot more problems than it's
actually solving. Thus, I'm officially putting a -1 on this commit as it's
causing breakages in other components, causes cast exceptions and
11 matches
Mail list logo
