[
https://issues.apache.org/activemq/browse/SM-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61128#action_61128
]
Gert Vanthienen commented on SM-1946:
-------------------------------------
Personally, I'd rather see us move to one archetype per component / use case,
e.g. a single servicemix-ftp-service-unit archetype which has sample
configuration for a poller, sender and probably a marshaler. I think it would
be easier for our users if every component would at least have a consistently
named archetype (<component>-service-unit).
For the archetype catalog, the goal of the archetype catalog subproject is to
generate a catalog file with all the archetypes for a specific version in it,
which seems to work fine on my machine.
> Upgrade archetypes and provide a clean version
> ----------------------------------------------
>
> Key: SM-1946
> URL: https://issues.apache.org/activemq/browse/SM-1946
> Project: ServiceMix
> Issue Type: Improvement
> Components: archetypes
> Reporter: Jean-Baptiste Onofré
> Assignee: Jean-Baptiste Onofré
> Fix For: archetypes-2010.01
>
>
> The current archetypes available are totally deprecated and not really clean.
> I gonna make a new release based on 2010.01 components and cleaning the
> generated resources.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
