Quantcast

Fwd: archetype-catalog.xml and its properties and goals elements, what populates them?

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Fwd: archetype-catalog.xml and its properties and goals elements, what populates them?

Hervé BOUTEMY
Forwarding this question to dev list, since I don't really know.

To me, catalog descriptor [1] should not contain goals or properties elements,
but archetype descriptor [2] should have goals instead (it already has
properties).

Any objection if I remove goals and properties elements from catalog
descriptor?
Then I'll release maven-archetype-plugin 2.0 without this goals feature, which
is not implemented: it will be postponed to 2.1+

Regards,

Hervé

[1] http://maven.apache.org/archetype/archetype-common/archetype-catalog.html
[2] http://maven.apache.org/archetype/archetype-common/archetype-
descriptor.html

----------  Message transmis  ----------

Sujet : Re: archetype-catalog.xml and its properties and goals elements, what
populates them?
Date : jeudi 16 septembre 2010, 00:11:46
De : lukewpatterson <[hidden email]>
À : [hidden email]


Anyone have any info/background on the <goals> and <properties> sections of
archetype-catalog.xml ?
--
View this message in context: http://maven.40175.n5.nabble.com/archetype-
catalog-xml-and-its-properties-and-goals-elements-what-populates-them-
tp2799170p2841463.html
Sent from the Maven - Users mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]


-------------------------------------------------------

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: Fwd: archetype-catalog.xml and its properties and goals elements, what populates them?

lukewpatterson
Hervé BOUTEMY wrote
Forwarding this question to dev list...
Yay! I have the attention of the right person at the right time.

Hervé BOUTEMY wrote
archetype descriptor [2] should have goals
I'll dump related thoughts here:

* I like the ability to add goals in archetype descriptor
* sometimes certain goals will always have to be executed after an archetype, why not allow it to be done automatically, less instructions for the archetype consumers to follow
* It cleanly augments the velocity templating with custom logic
* I use one-off Groovy+AntDSL mojos in my highly-specialized archetypes to "continue the conversation" started by archetype, I need the boost of logic to really add value to the archetype
* My follow-up goals have interactivity in CLI, not sure how m2e would handle that in its wizard
* the goals need to allow properties (e.g. "<goal>doit -DmyProperty=true</goal>)
* goals need to execute in order, currently I don't think order is respected with the catalog descriptor method

and somewhat-related:
* archetype has some default properties (package, artifactId), which is nice, but it is hard to override and/or not use them, e.g. if I add a "package" property, it shows up twice in the list displayed to user
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: Fwd: archetype-catalog.xml and its properties and goals elements, what populates them?

Hervé BOUTEMY
Le vendredi 17 septembre 2010, lukewpatterson a écrit :
> Hervé BOUTEMY wrote:
> > Forwarding this question to dev list...
>
> Yay! I have the attention of the right person at the right time.
yay! I have feedback at the right time, too.
And don't forget: patches are welcome.

>
> Hervé BOUTEMY wrote:
> > archetype descriptor [2] should have goals
>
> I'll dump related thoughts here:
>
> * I like the ability to add goals in archetype descriptor
> * sometimes certain goals will always have to be executed after an
> archetype, why not allow it to be done automatically, less instructions for
> the archetype consumers to follow
> * It cleanly augments the velocity templating with custom logic
> * I use one-off Groovy+AntDSL mojos in my highly-specialized archetypes to
> "continue the conversation" started by archetype, I need the boost of logic
> to really add value to the archetype
seems interesting: any pointer?

> * My follow-up goals have interactivity in CLI, not sure how m2e would
> handle that in its wizard
seems harder, yes

> * the goals need to allow properties (e.g. "<goal>doit
> -DmyProperty=true</goal>)
> * goals need to execute in order, currently I don't think order is
> respected with the catalog descriptor method

ok
as previuosly written, goals won't be here in maven-archetype-plugin 2.0, but
seems like this will be the big addition in 2.1
and your summary is interesting: writing a User Proposal [1] with it and a
Jira issue [2] would be great

>
> and somewhat-related:
> * archetype has some default properties (package, artifactId), which is
> nice, but it is hard to override and/or not use them, e.g. if I add a
> "package" property, it shows up twice in the list displayed to user
please open a Jira issue

Regards,

Hervé


[1] http://docs.codehaus.org/display/MAVENUSER/User+Proposals

[2] http://jira.codehaus.org/browse/ARCHETYPE

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: Fwd: archetype-catalog.xml and its properties and goals elements, what populates them?

lukewpatterson
Hervé BOUTEMY wrote
seems like this will be the big addition in 2.1
and your summary is interesting: writing a User Proposal [1] with it and a
Jira issue [2] would be great
didn't have time today to be the fully compliant citizen (coherent descriptions and patches), but I at least got some stuff dumped out there:

user proposal: http://docs.codehaus.org/display/MAVENUSER/Allow+goals+to+be+attached+to+post+Velocity+template+process+in+archetype+generation

related Jira: http://jira.codehaus.org/browse/ARCHETYPE-328


thanks
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: Fwd: archetype-catalog.xml and its properties and goals elements, what populates them?

Hervé BOUTEMY
great, thanks
for the moment, I'll focus on bugfixes for 2.0 but I'll work with you on this
after the release

Regards,

Hervé

Le dimanche 19 septembre 2010, lukewpatterson a écrit :

> Hervé BOUTEMY wrote:
> > seems like this will be the big addition in 2.1
> > and your summary is interesting: writing a User Proposal [1] with it and
> > a Jira issue [2] would be great
>
> didn't have time today to be the fully compliant citizen (coherent
> descriptions and patches), but I at least got some stuff dumped out there:
>
> user proposal:
> http://docs.codehaus.org/display/MAVENUSER/Allow+goals+to+be+attached+to+po
> st+Velocity+template+process+in+archetype+generation
> http://docs.codehaus.org/display/MAVENUSER/Allow+goals+to+be+attached+to+p
> ost+Velocity+template+process+in+archetype+generation
>
> related Jira:  http://jira.codehaus.org/browse/ARCHETYPE-328
> http://jira.codehaus.org/browse/ARCHETYPE-328
>
>
> thanks


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Loading...