maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vincent Massol" <>
Subject RE: Documentation of relevant goals in POM?
Date Sun, 09 May 2004 08:04:34 GMT

What Thomas is asking is for a project "goalmap". For example a person
who wants to build this maven project would just type "maven -G" and it
would only list the goals that make sense for this project.

I think the idea is interesting and several persons I've talked to at
TSSS2004 have raised this issue of being a bit lost about what goal they
should call to build such project.



> -----Original Message-----
> From: Thomas Christensen []
> Sent: 08 May 2004 23:54
> To: 'Maven Users List'
> Subject: Documentation of relevant goals in POM?
> Hi all
> I had a chat with Vincent Massol yesterday at the server side
> about documenting relevant goals in the project.xml. The aim here is
> make ant like integration with IDE's and making it easier to find out
> what goals are relevant for a project. I personally find it a problem
> that when I checkout a module I need to find tips on build in readme
> files in various places.
> The goals could be put in maven.xml and you could use the description
> these to make them more accessible but maven.xml should not be
> on all projects - that would be going back to ant in my opinion..
> In a current project I can use a database maven plugin to build the
> database and jboss plugin to launch this app in the container. But I
> don't want this to happen as the default goal which just builds the
> application as an ear. A new developer would have to read the
> how-to-build file in order to find out what goals can be used. F.ex.
> war goal doesn't  make sense in this context but ear does.
> Any thoughts on this?
> Thomas
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message