You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Stephane Nicoll <st...@gmail.com> on 2007/08/07 11:29:36 UTC

archetype current status

Hi,

I am in the process of creating archetypes. Most of my archetypes have
a dependency on external components that change every time the product
is released (Say product has module A, A changes almost every time and
a new archetype is released with a dependency on a particular version
of A).

I've tried to make this process automatic (i.e. at creation time of
the archetype the version of A is replaced automatically.
Unfortunately filtering is not possible here since the archetype's pom
contains already stuff such as ${artifactId} ${groupId}, etc that
should *NOT* be filtered of course.

Does anyone know how to implement this use case? Does the "new
archetype" handle this? What's its status?

Thanks,
Stéphane

-- 
Large Systems Suck: This rule is 100% transitive. If you build one,
you suck" -- S.Yegge

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org