You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@servicemix.apache.org by boday <bo...@vektrel.com> on 2009/08/14 03:05:08 UTC
ServiceMix version hell...
I feel like I'm running in circles trying to get the dependency versions of
ServiceMix, Camel, Spring, Maven Plugins and namespaces to work well
together. Are others having issues with this?
I'm using SMX 3.3.1, Camel 1.6.1 and whatever spring-* versions that come
over 2.0.5-2.5.6.
The servicemix-* components haven't been released for 3.3.1 yet, so, I'm
using 3.2.3. Many examples/APIs require a newer version of Spring, so I've
played around with different SMX versions that use the newer Spring
version...2009.01, etc.
I've been working on setting up automated testing lately and have run into a
whole new set of issues. Many of the examples don't work because they need
a newer version of spring or camel, but if I add that dependency, something
else breaks, etc...
Overall, I'm spending way too much time trying to manage dependencies...
Is there a more stable version of these things that I should be using? I'd
love to go to SMX 4 and Camel 2, but they haven't been formally released
yet. Should I go to the FUSE releases?
I'm open to any advice at this point...thanks
-----
Ben - Senior Consultant
--
View this message in context: http://www.nabble.com/ServiceMix-version-hell...-tp24963608p24963608.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: ServiceMix version hell...
Posted by loboEsa <la...@gmail.com>.
Hi Jean I try to install(maven) my SA using the follow configuration in all
my SA and SUs
<plugins>
<plugin>
<groupId>org.apache.servicemix.tooling</groupId>
<artifactId>jbi-maven-plugin</artifactId>
<version>4.1</version>
<extensions>true</extensions>
<configuration>
<type>service-assembly</type>
</configuration>
</plugin>
</plugins>
and into SUs add
<dependencies>
<dependency>
<groupId>org.apache.servicemix</groupId>
<artifactId>servicemix-core</artifactId>
<version>3.3.1</version>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>org.apache.servicemix</groupId>
<artifactId>servicemix-file</artifactId>
<version>2009.01</version>
</dependency>
</dependencies>
When I try to install all my project this error apear:
[ERROR]BUILD ERROR
------------------------------------------------------------------------
The service unit file-sender-su does not have a dependency which is packaged
as a jbi-component or a project property 'componentName'
If I return jbi-maven-plugin version to 3.2.3 all be fine.
I find in other webpage that it is resolved with componentName property into
SU POM, and yes all be fine until I try to deploy the SA, ServiceMix tell my
that is not posible to install SA because is pending the installation of de
component in touble.
What is the correct version configuration to use the lastest ServiceMix
release (3.3.1) ?????
Is it posible to create meaven archetypes to version 3.3.1 ? The
instructions into the ServiceMix site create only a 3.2.3 version and use a
very old versions of components.
Thanks in advanced.
Jean-Baptiste Onofré wrote:
>
> Hi,
>
> We know that we need to improve the website and documentation. We're
> working on it (especially with the DocBook documentation which is in
> incubation for now).
>
> For your question, the jbi-maven-plugin versionning is independant from
> the container one (the "real" ServiceMix version). It's better to use
> the latest stable jbi-maven-plugin version which is currently the 4.1.
>
> Regards
> JB
>
> loboEsa wrote:
>> It's very frustrating a poor quality documentation and tutorial and the
>> versioning is very confused.
>>
>> It's a pity because I think ServiceMix is a very powerful product.
>>
>> I followed the instruction to install and create SUs with ServiceMix
>> 3.3.1
>> and all my SUs were created with 3.2.3 version. (I used mvn
>> archetype:create)
>>
>> I changed my SU's poms as follow:
>>
>> <dependency>
>> <groupId>org.apache.servicemix</groupId>
>> <artifactId>servicemix-core</artifactId>
>> <version>3.3.1</version>
>> <scope>provided</scope>
>> </dependency>
>> <dependency>
>> <groupId>org.apache.servicemix</groupId>
>> <artifactId>servicemix-file</artifactId>
>> <version>2009.01</version>
>> </dependency>
>>
>> but continue using jbi-maven-plugin 3.2.3
>>
>> How can I use jbi-maven-plugin 3.3.1 (or 2009.01) to create archetypes to
>> Servicemix 3.3.1 ??????
>>
>
>
--
View this message in context: http://www.nabble.com/ServiceMix-version-hell...-tp24963608p25813548.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
RE: ServiceMix version hell...
Posted by Eric Johnson <EM...@progress.com>.
To get wiki content into DocBook you could give this plug-in a try:
http://fusesource.org/forge/projects/CONFDOC
One of the guys at Progress built it and has been using it with a pretty decent level of success. It can basically turn a confluence space, or subset of a space, into a DocBook book.
-----Original Message-----
From: Jean-Baptiste Onofré [mailto:jb@nanthrax.net]
Sent: Thursday, October 08, 2009 12:04 AM
To: Eric Johnson
Cc: users@servicemix.apache.org
Subject: Re: ServiceMix version hell...
Hi Eric,
the documentation sandbox is here:
http://svn.apache.org/repos/asf/servicemix/sandbox/jbonofre/documentation/
Any help is welcome especially to add content (migrate wiki pages into
DocBook document and add content).
For the publication system, I have plan to use maven plugin (docbk or
doxia or home made) but if you have something already available, why not :)
Regards
JB
Eric Johnson wrote:
> Where is the DocBook documentation being developed? Do you need help setting up a publication system?
>
> -----Original Message-----
> From: Jean-Baptiste Onofré [mailto:jb@nanthrax.net]
> Sent: Wednesday, October 07, 2009 4:36 PM
> To: users@servicemix.apache.org
> Subject: Re: ServiceMix version hell...
>
> Hi,
>
> We know that we need to improve the website and documentation. We're
> working on it (especially with the DocBook documentation which is in
> incubation for now).
>
> For your question, the jbi-maven-plugin versionning is independant from
> the container one (the "real" ServiceMix version). It's better to use
> the latest stable jbi-maven-plugin version which is currently the 4.1.
>
> Regards
> JB
>
> loboEsa wrote:
>> It's very frustrating a poor quality documentation and tutorial and the
>> versioning is very confused.
>>
>> It's a pity because I think ServiceMix is a very powerful product.
>>
>> I followed the instruction to install and create SUs with ServiceMix 3.3.1
>> and all my SUs were created with 3.2.3 version. (I used mvn
>> archetype:create)
>>
>> I changed my SU's poms as follow:
>>
>> <dependency>
>> <groupId>org.apache.servicemix</groupId>
>> <artifactId>servicemix-core</artifactId>
>> <version>3.3.1</version>
>> <scope>provided</scope>
>> </dependency>
>> <dependency>
>> <groupId>org.apache.servicemix</groupId>
>> <artifactId>servicemix-file</artifactId>
>> <version>2009.01</version>
>> </dependency>
>>
>> but continue using jbi-maven-plugin 3.2.3
>>
>> How can I use jbi-maven-plugin 3.3.1 (or 2009.01) to create archetypes to
>> Servicemix 3.3.1 ??????
>>
Re: ServiceMix version hell...
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi Eric,
the documentation sandbox is here:
http://svn.apache.org/repos/asf/servicemix/sandbox/jbonofre/documentation/
Any help is welcome especially to add content (migrate wiki pages into
DocBook document and add content).
For the publication system, I have plan to use maven plugin (docbk or
doxia or home made) but if you have something already available, why not :)
Regards
JB
Eric Johnson wrote:
> Where is the DocBook documentation being developed? Do you need help setting up a publication system?
>
> -----Original Message-----
> From: Jean-Baptiste Onofré [mailto:jb@nanthrax.net]
> Sent: Wednesday, October 07, 2009 4:36 PM
> To: users@servicemix.apache.org
> Subject: Re: ServiceMix version hell...
>
> Hi,
>
> We know that we need to improve the website and documentation. We're
> working on it (especially with the DocBook documentation which is in
> incubation for now).
>
> For your question, the jbi-maven-plugin versionning is independant from
> the container one (the "real" ServiceMix version). It's better to use
> the latest stable jbi-maven-plugin version which is currently the 4.1.
>
> Regards
> JB
>
> loboEsa wrote:
>> It's very frustrating a poor quality documentation and tutorial and the
>> versioning is very confused.
>>
>> It's a pity because I think ServiceMix is a very powerful product.
>>
>> I followed the instruction to install and create SUs with ServiceMix 3.3.1
>> and all my SUs were created with 3.2.3 version. (I used mvn
>> archetype:create)
>>
>> I changed my SU's poms as follow:
>>
>> <dependency>
>> <groupId>org.apache.servicemix</groupId>
>> <artifactId>servicemix-core</artifactId>
>> <version>3.3.1</version>
>> <scope>provided</scope>
>> </dependency>
>> <dependency>
>> <groupId>org.apache.servicemix</groupId>
>> <artifactId>servicemix-file</artifactId>
>> <version>2009.01</version>
>> </dependency>
>>
>> but continue using jbi-maven-plugin 3.2.3
>>
>> How can I use jbi-maven-plugin 3.3.1 (or 2009.01) to create archetypes to
>> Servicemix 3.3.1 ??????
>>
RE: ServiceMix version hell...
Posted by Eric Johnson <EM...@progress.com>.
Where is the DocBook documentation being developed? Do you need help setting up a publication system?
-----Original Message-----
From: Jean-Baptiste Onofré [mailto:jb@nanthrax.net]
Sent: Wednesday, October 07, 2009 4:36 PM
To: users@servicemix.apache.org
Subject: Re: ServiceMix version hell...
Hi,
We know that we need to improve the website and documentation. We're
working on it (especially with the DocBook documentation which is in
incubation for now).
For your question, the jbi-maven-plugin versionning is independant from
the container one (the "real" ServiceMix version). It's better to use
the latest stable jbi-maven-plugin version which is currently the 4.1.
Regards
JB
loboEsa wrote:
> It's very frustrating a poor quality documentation and tutorial and the
> versioning is very confused.
>
> It's a pity because I think ServiceMix is a very powerful product.
>
> I followed the instruction to install and create SUs with ServiceMix 3.3.1
> and all my SUs were created with 3.2.3 version. (I used mvn
> archetype:create)
>
> I changed my SU's poms as follow:
>
> <dependency>
> <groupId>org.apache.servicemix</groupId>
> <artifactId>servicemix-core</artifactId>
> <version>3.3.1</version>
> <scope>provided</scope>
> </dependency>
> <dependency>
> <groupId>org.apache.servicemix</groupId>
> <artifactId>servicemix-file</artifactId>
> <version>2009.01</version>
> </dependency>
>
> but continue using jbi-maven-plugin 3.2.3
>
> How can I use jbi-maven-plugin 3.3.1 (or 2009.01) to create archetypes to
> Servicemix 3.3.1 ??????
>
Re: ServiceMix version hell...
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi,
We know that we need to improve the website and documentation. We're
working on it (especially with the DocBook documentation which is in
incubation for now).
For your question, the jbi-maven-plugin versionning is independant from
the container one (the "real" ServiceMix version). It's better to use
the latest stable jbi-maven-plugin version which is currently the 4.1.
Regards
JB
loboEsa wrote:
> It's very frustrating a poor quality documentation and tutorial and the
> versioning is very confused.
>
> It's a pity because I think ServiceMix is a very powerful product.
>
> I followed the instruction to install and create SUs with ServiceMix 3.3.1
> and all my SUs were created with 3.2.3 version. (I used mvn
> archetype:create)
>
> I changed my SU's poms as follow:
>
> <dependency>
> <groupId>org.apache.servicemix</groupId>
> <artifactId>servicemix-core</artifactId>
> <version>3.3.1</version>
> <scope>provided</scope>
> </dependency>
> <dependency>
> <groupId>org.apache.servicemix</groupId>
> <artifactId>servicemix-file</artifactId>
> <version>2009.01</version>
> </dependency>
>
> but continue using jbi-maven-plugin 3.2.3
>
> How can I use jbi-maven-plugin 3.3.1 (or 2009.01) to create archetypes to
> Servicemix 3.3.1 ??????
>
Re: ServiceMix version hell...
Posted by loboEsa <la...@gmail.com>.
It's very frustrating a poor quality documentation and tutorial and the
versioning is very confused.
It's a pity because I think ServiceMix is a very powerful product.
I followed the instruction to install and create SUs with ServiceMix 3.3.1
and all my SUs were created with 3.2.3 version. (I used mvn
archetype:create)
I changed my SU's poms as follow:
<dependency>
<groupId>org.apache.servicemix</groupId>
<artifactId>servicemix-core</artifactId>
<version>3.3.1</version>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>org.apache.servicemix</groupId>
<artifactId>servicemix-file</artifactId>
<version>2009.01</version>
</dependency>
but continue using jbi-maven-plugin 3.2.3
How can I use jbi-maven-plugin 3.3.1 (or 2009.01) to create archetypes to
Servicemix 3.3.1 ??????
--
View this message in context: http://www.nabble.com/ServiceMix-version-hell...-tp24963608p25791661.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: ServiceMix version hell...
Posted by Ulhas Bhole <ap...@gmail.com>.
Yes for servicemix-core it is 3.3.1 only components and archetypes have
version number 2009.0.
Here is a link to servicemix 3.3.1 tag pom.xml which list all dependency
version numbers in it.
http://svn.eu.apache.org/repos/asf/servicemix/smx3/tags/servicemix-3.3.1/pom.xml
for your reference here is the section that you need.
<servicemix-utils-version>1.1.0</servicemix-utils-version>
<servicemix-specs-version>1.1.0</servicemix-specs-version>
<servicemix-common-version>2009.01</servicemix-common-version>
<servicemix-shared-version>2009.01</servicemix-shared-version>
<servicemix-quartz-version>2009.01</servicemix-quartz-version>
<servicemix-jms-version>2009.01</servicemix-jms-version>
<servicemix-jsr181-version>2009.01</servicemix-jsr181-version>
<servicemix-http-version>2009.01</servicemix-http-version>
<servicemix-mail-version>2009.01</servicemix-mail-version>
<servicemix-osworkflow-version>2009.01</servicemix-osworkflow-version>
<servicemix-wsn2005-version>2009.01</servicemix-wsn2005-version>
<servicemix-lwcontainer-version>3.3.1</servicemix-lwcontainer-version>
<servicemix-bean-version>2009.01</servicemix-bean-version>
<servicemix-eip-version>2009.01</servicemix-eip-version>
<servicemix-script-version>2009.01</servicemix-script-version>
<servicemix-scripting-version>2009.01</servicemix-scripting-version>
<servicemix-validation-version>2009.01</servicemix-validation-version>
<servicemix-ftp-version>2009.01</servicemix-ftp-version>
<servicemix-xmpp-version>2009.01</servicemix-xmpp-version>
<servicemix-saxon-version>2009.01</servicemix-saxon-version>
<servicemix-truezip-version>2009.01</servicemix-truezip-version>
<servicemix-camel-version>2009.01</servicemix-camel-version>
<servicemix-cxf-bc-version>2009.01</servicemix-cxf-bc-version>
<servicemix-cxf-se-version>2009.01</servicemix-cxf-se-version>
<servicemix-drools-version>2009.01</servicemix-drools-version>
<servicemix-file-version>2009.01</servicemix-file-version>
<servicemix-snmp-version>2009.01</servicemix-snmp-version>
<servicemix-smpp-version>2009.01</servicemix-smpp-version>
<res-maven-plugin-version>4.0</res-maven-plugin-version>
<servicemix-build-version>1.0</servicemix-build-version>
<xfire-jsr181-api-version>1.0-M1</xfire-jsr181-api-version>
<xfire-version>1.2.5</xfire-version>
<mavenAssemblyPluginVersion>2.1</mavenAssemblyPluginVersion>
<xbean-version>3.4.3</xbean-version>
<spring-version>2.5.6</spring-version>
<activemq-version>5.2.0</activemq-version>
<activeio-version>3.1.0</activeio-version>
<camel-version>1.6.0</camel-version>
<jencks-version>2.1</jencks-version>
<jetty-version>6.1.14</jetty-version>
<geronimo-version>2.0.2</geronimo-version>
<servicemix-version>3.3.1-SNAPSHOT</servicemix-version>
<wsdl4j-version>1.6.2</wsdl4j-version>
<commons-beanutils-version>1.7.0</commons-beanutils-version>
<commons-fileupload-version>1.1.1</commons-fileupload-version>
<woodstox-version>3.2.6</woodstox-version>
<msv-version>20050913</msv-version>
<oro-version>2.0.8</oro-version>
<sitemesh-version>2.2.1</sitemesh-version>
<woden-version>1.0.0M6</woden-version>
<cxf-version>2.1.4</cxf-version>
<jaxb.version>2.1</jaxb.version>
<jaxb.impl.version>2.1.6</jaxb.impl.version>
<jaxb.xjc.version>2.1.6</jaxb.xjc.version>
<derby-version>10.2.2.0</derby-version>
<saxon-version>8.9</saxon-version>
Regards,
Ulhas Bhole
boday wrote:
> Freeman, what about the servicemix-core version (2009.01 doesn't
> exist...3.3?), jbi-maven-plugin version (3.2.3?) and camel version
> (1.6.1?)...
>
> Overall, I'm frustrated that so many of the examples don't work with my
> setup. You should require that the dependencies be listed with every code
> example so that I don't have to guess what version something will work in.
> For example, I've been trying to setup some integration tests but keep
> running into issues while following these examples...
>
> http://servicemix.apache.org/integration-testing-in-spring.html
> http://camel.apache.org/testing.html
> http://camel.apache.org/spring-testing.html
>
> thanks again...
>
>
>
> -----
> Ben - Senior Consultant
>
>
Re: ServiceMix version hell...
Posted by boday <bo...@vektrel.com>.
Freeman, what about the servicemix-core version (2009.01 doesn't
exist...3.3?), jbi-maven-plugin version (3.2.3?) and camel version
(1.6.1?)...
Overall, I'm frustrated that so many of the examples don't work with my
setup. You should require that the dependencies be listed with every code
example so that I don't have to guess what version something will work in.
For example, I've been trying to setup some integration tests but keep
running into issues while following these examples...
http://servicemix.apache.org/integration-testing-in-spring.html
http://camel.apache.org/testing.html
http://camel.apache.org/spring-testing.html
thanks again...
-----
Ben - Senior Consultant
--
View this message in context: http://www.nabble.com/ServiceMix-version-hell...-tp24963608p24973528.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: ServiceMix version hell...
Posted by Freeman Fang <fr...@gmail.com>.
On 2009-8-14, at 上午9:05, boday wrote:
>
> I feel like I'm running in circles trying to get the dependency
> versions of
> ServiceMix, Camel, Spring, Maven Plugins and namespaces to work well
> together. Are others having issues with this?
>
> I'm using SMX 3.3.1, Camel 1.6.1 and whatever spring-* versions that
> come
> over 2.0.5-2.5.6.
>
> The servicemix-* components haven't been released for 3.3.1 yet, so,
> I'm
> using 3.2.3. Many examples/APIs require a newer version of Spring,
> so I've
> played around with different SMX versions that use the newer Spring
> version...2009.01, etc.
Just one note here, after servicemix 3.3, we release servicemix
components and servicemix container separately(so that the components
could be shared by smx 3.x and 4.x), so the components version is
different with the container, for smx 3.3.1, it should use 2009.01,
hope this helps
Freeman
>
> I've been working on setting up automated testing lately and have
> run into a
> whole new set of issues. Many of the examples don't work because
> they need
> a newer version of spring or camel, but if I add that dependency,
> something
> else breaks, etc...
>
> Overall, I'm spending way too much time trying to manage
> dependencies...
>
> Is there a more stable version of these things that I should be
> using? I'd
> love to go to SMX 4 and Camel 2, but they haven't been formally
> released
> yet. Should I go to the FUSE releases?
>
> I'm open to any advice at this point...thanks
>
>
> -----
> Ben - Senior Consultant
>
> --
> View this message in context: http://www.nabble.com/ServiceMix-version-hell...-tp24963608p24963608.html
> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>
--
Freeman Fang
------------------------
Open Source SOA: http://fusesource.com