You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by Gert Vanthienen <ge...@skynet.be> on 2008/03/04 22:07:04 UTC
Maven archetypes
L.S.,
Just a few thoughts for improving user experience with the Maven
archetypes, based on some changes I find myself making to the generated
pom.xml files every time I start a new SA project:
1. Is it still necessary to have the snapshot repositories in there? If
not, we should remove them as they only slow down the builds.
2. How about adding a new Maven archetype to start a SA project that would:
- create a project root directory with a parent pom.xml, containing
shared information like the <servicemix-version>
- create a subproject for the SA
3. Does anyone know of a way to access the information of the parent
pom.xml while executing the archetype itself? This would e.g. allow us
to generate a more usable default name for a SU project (e.g. something
like ${parent.name} :: Camel SU)
Wdyt?
Gert
Re: Maven archetypes
Posted by Bruce Snyder <br...@gmail.com>.
On Tue, Mar 4, 2008 at 2:07 PM, Gert Vanthienen
<ge...@skynet.be> wrote:
> L.S.,
>
>
> Just a few thoughts for improving user experience with the Maven
> archetypes, based on some changes I find myself making to the generated
> pom.xml files every time I start a new SA project:
>
> 1. Is it still necessary to have the snapshot repositories in there? If
> not, we should remove them as they only slow down the builds.
The snapshot repos can be removed in the branches but should probably
remain in the trunk since SNAPSHOTs are used only in the trunk.
> 2. How about adding a new Maven archetype to start a SA project that would:
> - create a project root directory with a parent pom.xml, containing
> shared information like the <servicemix-version>
> - create a subproject for the SA
We already have an archetype that creates a project root directory and
we can contribute. But adding the SA to it is a good idea.
> 3. Does anyone know of a way to access the information of the parent
> pom.xml while executing the archetype itself? This would e.g. allow us
> to generate a more usable default name for a SU project (e.g. something
> like ${parent.name} :: Camel SU)
Hmmm, good question. I'll have to look into this.
Bruce
--
perl -e 'print unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
);'
Apache ActiveMQ - http://activemq.org/
Apache Camel - http://activemq.org/camel/
Apache ServiceMix - http://servicemix.org/
Apache Geronimo - http://geronimo.apache.org/
Blog: http://bruceblog.org/