[
https://issues.apache.org/activemq/browse/CAMEL-827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=45024#action_45024
]
Jonathan Anstey commented on CAMEL-827:
---------------------------------------
Hmmm... Looks like having archetype in the artifactId is the standard used at
the Maven project (even if it is redundant :)) We should probably go with that
then. So, how about this as the final list of archetypes:
camel-archetype-component (was camel-component)
camel-archetype-java (was camel-router)
camel-archetype-spring (was camel-router-spring)
camel-archetype-activemq (was camel-router-with-activemq)
> Add new Camel archetypes
> ------------------------
>
> Key: CAMEL-827
> URL: https://issues.apache.org/activemq/browse/CAMEL-827
> Project: Apache Camel
> Issue Type: New Feature
> Components: tooling
> Reporter: Jonathan Anstey
> Assignee: Hadrian Zbarcea
> Fix For: 1.5.0
>
> Attachments: addNewArchetypes.patch, archetypes.png
>
>
> Given that our archetypes will be showing up in m2eclipse after our next
> release, we should really have a few more options that will make it easier
> for someone to start using Camel.
> I propose a Spring XML based archetype which is basically the camel-router
> archetype with the Java DSL transposed to Spring XML. Another archetype shows
> how easy it is to start using Camel with ActiveMQ.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
