Hi Christian,
the issue is that Gemini has a different packaging and camel spring has a
dependency which tries to load classes from spring OSGi when activator in
manifest is triggered. Unfortunately it is not drop in replacement. :-(
I would suggest to update dependency in spring module or remo
> Fixed OSGI export declaration for vtdxml and jgroups (rev944 and
> rev955 respectively).
I need to catch some sleep :) Tomorrow I'd like to make an another
attempt to stage a 2.10.0 release. In the meantime feel free to spot
more blocking issues that should be addressed before release. :)
Later
> In rev943 I fixed the vtdxml package to
> org.apachextras.camel.component.vtdxml .
Fixed OSGI export declaration for vtdxml and jgroups (rev944 and
rev955 respectively).
--
Henryk Konsek
http://henryk-konsek.blogspot.com
> Release candidate has been rollbacked in rev941. I've also removed the
> 2.10.0 tag from SVN.
In rev943 I fixed the vtdxml package to org.apachextras.camel.component.vtdxml .
I also dropped previous release candidate from the Sonatype OSS
staging repository.
--
Henryk Konsek
http://henryk-kon
> I'll fix the package of the vtdxml component (to camel-extra).
>
> The problem with vtdxml manifest is that the osgi export property is
> broken. I'll fix it as well.
Release candidate has been rollbacked in rev941. I've also removed the
2.10.0 tag from SVN.
--
Henryk Konsek
http://henryk-kons
>> It seams the OSGI meta information are not complete (I miss the bundle
>> exports/imports):
I'll fix the package of the vtdxml component (to camel-extra).
The problem with vtdxml manifest is that the osgi export property is
broken. I'll fix it as well.
--
Henryk Konsek
http://henryk-konsek.b
> It seams the OSGI meta information are not complete (I miss the bundle
> exports/imports):
The release is staged, so it is not synchronized with Central yet.
I'll take a look at the things you mentioned. After we fix them, I'll
stage another release candidate.
--
Henryk Konsek
http://henryk-ko
A new patch release candidate apache-camel-2.9.4 final is out with
approximately 55 issues resolved so far: improvements and bug fixes [1].
Please find the staging repo here:
https://repository.apache.org/content/repositories/orgapachecamel-117/
The tarballs are here
https://repository.apache.o
It seams the OSGI meta information are not complete (I miss the bundle
exports/imports):
camel-vtdxml (150)
--
Manifest-Version = 1.0
Karaf-Info = Camel;camel-vtdxml=2.10.0
Bnd-LastModified = 1349849028761
Tool = Bnd-1.50.0
Built-By = cmueller
Implementation-Version = 2.10.0
Build-
Forget this post, it was because I did:
karaf@trun> install -s mvn:net.sourceforge.vtdxml/vtd-xml/2.1.0
instead of:
karaf@trun> install -s wrap:mvn:net.sourceforge.vtdxml/vtd-xml/2.1.0
Sorry for the noise...
Best,
Christian
On Wed, Oct 10, 2012 at 10:58 PM, Christian Müller <
christian.muel...@
-1
camel-vtdxml use the package "org.apache.camel.component.vtdxml" instead of
"org.apacheextras.camel.component.vtdxml".
We have to redo this release. Henryk, could you please take care of it?
Best,
Christian
On Wed, Oct 10, 2012 at 5:55 AM, Henryk Konsek wrote:
> On Thu, Oct 4, 2012 at 5:36
I tried to use the camel-vtdxml component (in SMX 4.5.0-SNAPSHOT), but got
the following exception:
karaf@root> list
START LEVEL 100 , List Threshold: 50
ID State Blueprint SpringLevel Name
...
[ 149] [Active ] [] [ ] [ 80]
mvn:net.sourceforge.vtdxml/
If I understood you right, gemini-blueprint is the replacement of
spring-dm. In this case, there is no need that both live together. I'm
right?
In this case, I don't understand what the issue is?
Best,
Christian
On Wed, Oct 10, 2012 at 12:53 PM, Benjamin Graf wrote:
> Hi everybody,
>
> I tried t
Hi everybody,
I tried to implement a new camel component for gemini-blueprint. It seems that
both components spring-osgi and gemini-blueprint can not live both together in
camel. Since camel-spring needs spring-osgi if used in an osgi environment. A
replacement should really be considered.
Any
14 matches
Mail list logo
