-
1. Re: When will 2009.01.0.4-fuse be ready in Maven2 repository?
joe.luo Aug 7, 2009 3:50 AM (in response to eruiz_eruiz) -
2. Re: When will 2009.01.0.4-fuse be ready in Maven2 repository?
eruiz_eruiz Aug 7, 2009 4:56 AM (in response to joe.luo)Thanks Joe,
I think that really I don't know when I have to use archetypes at http://repo.fusesource.com/maven2/org/apache/servicemix/tooling/ and when to use archetypes at http://repo.fusesource.com/maven2/org/apache/servicemix/ .
For example, which archetype should I use to create the project root: http://repo.fusesource.com/maven2/org/apache/servicemix/servicemix-pom or http://repo.fusesource.com/maven2/org/apache/servicemix/tooling/servicemix-root-pom/? Note that it seems none of both are updated, neither http://repo.fusesource.com/maven2/org/apache/servicemix/tooling/servicemix-root-pom/ nor http://repo.fusesource.com/maven2/org/apache/servicemix/servicemix-pom/
I read http://fusesource.com/products/enterprise-servicemix/#documentation but I didn't find any doc about this theme.
Can you give me some URL with documentation about the list of FUSE archetypes and when we can use to create services?
Thanks.
-
3. Re: When will 2009.01.0.4-fuse be ready in Maven2 repository?
eruiz_eruiz Aug 7, 2009 5:55 AM (in response to joe.luo)Hi Joe,
I'm not sure if it is a bug or I'm doing something wrong, but I cannot create a SU using the archetypes you commented.
Execute:
mvn -e archetype:create -DarchetypeArtifactId=servicemix-camel -DarchetypeGroupId=org.apache.servicemix -DarchetypeRepository=http://repo.open.iona.com/maven2 -DarchetypeVersion=2009.01.0.4-fuse
The following exception is thrown:
+ ... 16 more+
Caused by: org.apache.maven.archetype.old.ArchetypeDescriptorException: The META-INF/maven/archetype.xml descriptor cannot be found.
+ at org.apache.maven.archetype.old.DefaultOldArchetype.createArchetype(DefaultOldArchetype.java:187)+
+ at org.apache.maven.archetype.mojos.MavenArchetypeMojo.execute(MavenArchetypeMojo.java:230)+
+ ... 18 more+
Thanks for your help.
-
4. Re: When will 2009.01.0.4-fuse be ready in Maven2 repository?
joe.luo Aug 7, 2009 7:17 AM (in response to eruiz_eruiz)The maven archetype plugin is a sub-project of the core servicemix project and they might not be updated as frequent as the core servicemix project. Thus, you might need to manually modify the generated pom.xml file to pick up correct/latest version of components or plugins as necessary.
The servicemix-project-root archetype plugin will only create a root directory of a project and a simple root pom.xml file but nothing else. The link http://repo.fusesource.com/maven2/org/apache/servicemix/tooling/
listed all currently available archetype plugins. So you can use any listed archetype plugin here to create a service unit or a service assembly. For instance, to create a camel service unit, you can do:
mvn archetype:create -DremoteRepositories=http://repo.fusesource.com/maven2 -DarchetypeGroupId=org.apache.servicemix.tooling -DarchetypeArtifactId=servicemix-camel-service-unit -DarchetypeVersion=2009.01.0.3-fuse -DgroupId=com.disid -DartifactId=smx-camel-su
However, the link
http://repo.fusesource.com/maven2/org/apache/servicemix/
has all servicemix JBI components. They are the libraries goes to your "hotdeploy/" directory.
Here is a archetype-catalog.xml file: http://repo.fusesource.com/maven2/archetype-catalog.xml but unfortunately, it is a bit outdated. By the way, from the link:[http://repo.fusesource.com/maven2/org/apache/servicemix/tooling/], you should find the most frequently used and "latest" archetypes.
-
5. Re: When will 2009.01.0.4-fuse be ready in Maven2 repository?
joe.luo Aug 7, 2009 7:24 AM (in response to eruiz_eruiz)the archetype version 2009.01.0.4-fuse for servicemix-camel is not released yet. And the archetypeGroupId should be "org.apache.servicemix.tooling". As my previous comment, please run command below instead:
mvn archetype:create -DremoteRepositories=http://repo.fusesource.com/maven2 -DarchetypeGroupId=org.apache.servicemix.tooling -DarchetypeArtifactId=servicemix-camel-service-unit -DarchetypeVersion=2009.01.0.3-fuse -DgroupId=com.disid -DartifactId=smx-camel-su
-
6. Re: When will 2009.01.0.4-fuse be ready in Maven2 repository?
davaleri Oct 2, 2009 4:17 PM (in response to joe.luo)Will there be a release of ESB archetypes 2009.01.0.4-fuse? ESB 3.4.0.4 uses Components 2009.01.0.4-fuse. What version of the archetypes go best with Components 2009.01.0.4-fuse if there is no release planned for archetypes 2009.01.0.4?
-
7. Re: When will 2009.01.0.4-fuse be ready in Maven2 repository?
joe.luo Oct 5, 2009 12:46 PM (in response to davaleri)There won't be 2009.01.0.4-fuse release for archetypes. The latest one is 2009.02.0.0-fuse.
You could use archetype 2009.01.0.3-fuse version to create service unit/assembly for your project for working with Fuse ESB 3.4.0.4-fuse and it should work without problem. However, you might want to manually change generated component versions in your project pom.xml file to make it consistent with the version that Fuse ESB 3.4.0.4-fuse uses.
-
8. Re: When will 2009.01.0.4-fuse be ready in Maven2 repository?
mdavis Oct 7, 2009 8:50 AM (in response to eruiz_eruiz)Hello Joe. Just to clarify the confusion. The archetypes for ESB 3.4.0.4 are 2009.01.0.3 and the components for the hotdeploy folder are correct as in the release notes? See http://fusesource.com/wiki/display/ProdInfo/FUSEESBv3.4ReleaseNotes. Why not use archetypes 2009.02.0.2.?
Thanks,
Michelle Davis
Edited by: mdavis on Oct 7, 2009 12:45 PM
Edited by: mdavis on Oct 7, 2009 12:48 PM
Edited by: mdavis on Oct 7, 2009 12:49 PM
-
9. Re: When will 2009.01.0.4-fuse be ready in Maven2 repository?
joe.luo Oct 7, 2009 11:27 AM (in response to mdavis)The release note is correct and Fuse ESB 3.4.0.4-fuse uses JBI components of 2009.01.0.4-fuse version.
In general, the archetype you use for creating service unit should be same version as the JBI component. However, we did not release archetypes of 2009.01.0.4-fuse version. Therefore, you will need to use 2009.01.0.3-fuse instead and it should work without problem. And alternatively, you could manaully modify the pom.xml file that generated from archetype to make it consistent with actual JBI component version as I suggested above.
If you'd like, you could use 2009.02.0.0-fuse archetype to create service unit/assembly in your project and deploy generated SA into ESB 3.4.0.4-fuse and it should also work.