You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by "Asmann, Roland" <Ro...@adesso.at> on 2012/07/23 15:34:00 UTC

Archetype parameter-values

Hi all,

We have recently created an Archetype for all our developers to use, but 
we ran into an issue today...

The project that is being created, should always use the latest version 
of our company's parent-POM. The thing here, is that I want to have the 
archetype-plugin insert this version into the new project automatically...

Is there a way to have the archetype-plugin resolve this version? Or can 
I perhaps write a simple class that is called by the Archetype in which 
I resolve this version myself?

Thanks.

-- 
Roland Asmann
Senior Software Engineer

adesso Austria GmbH
Floridotower 26. Stock              T +43 1 2198790-27
Floridsdorfer Hauptstr. 1           F +43 1 2198790-927
A-1210 Wien                         M +43 664 88657566
                                    E roland.asmann@adesso.at
                                    W www.adesso.at

-------------------------------------------------------------
             >>> business. people. technology. <<<
-------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: Archetype parameter-values

Posted by "Asmann, Roland" <Ro...@adesso.at>.
I was just looking into that plugin... Seems to do what I want, so I'll 
probably stick with that.

Thanks for the info, both of you!


On 23.07.2012 16:48, Wayne Fay wrote:
>> I don't think that there's any mechanism in place except to release a
>> new archetype for each new parent version.
>>
>> If you make a patch to add a feature to the archetype plugin I'll look at it.
>
> Perhaps a simple invocation of the versions-m-p:update-parent after
> archetype is done building the new project would be sufficient?
> Whether this is integrated into the archetype plugin directly or left
> as a manual step would be another question...
>
> Wayne
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>

-- 
Roland Asmann
Senior Software Engineer

adesso Austria GmbH
Floridotower 26. Stock              T +43 1 2198790-27
Floridsdorfer Hauptstr. 1           F +43 1 2198790-927
A-1210 Wien                         M +43 664 88657566
                                    E roland.asmann@adesso.at
                                    W www.adesso.at

-------------------------------------------------------------
             >>> business. people. technology. <<<
-------------------------------------------------------------

Re: Archetype parameter-values

Posted by Wayne Fay <wa...@gmail.com>.
> I don't think that there's any mechanism in place except to release a
> new archetype for each new parent version.
>
> If you make a patch to add a feature to the archetype plugin I'll look at it.

Perhaps a simple invocation of the versions-m-p:update-parent after
archetype is done building the new project would be sufficient?
Whether this is integrated into the archetype plugin directly or left
as a manual step would be another question...

Wayne

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


Re: Archetype parameter-values

Posted by Benson Margulies <bi...@gmail.com>.
I don't think that there's any mechanism in place except to release a
new archetype for each new parent version.

If you make a patch to add a feature to the archetype plugin I'll look at it.

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