> -----Original Message----- > From: Trygve Laugst�l [mailto:[EMAIL PROTECTED] > Sent: 09 May 2004 19:22 > To: Maven Users List > Subject: Re: Documentation of relevant goals in POM? > > How do you recon maven can know about the relevant goals?
I guess nothing magical. Simply a goalmap. For example: <goalmap> <goal refid="jar"/> <goal refid="mycustomgoal"/> [...] </goalmap> This would be optional and the developer of the project would list the main goals. "maven -G" would list those goals with their descriptions. -Vincent > > If a <type> tag is added to the POM it could make things easier to guess > the right goal. For bigger projects I usually have a goal called > 'help' which is the default goal. > > -- > Trygve > > On Sun, 9 May 2004 10:04:34 +0200, Vincent Massol <[EMAIL PROTECTED]> > wrote: > > > Hi, > > > > 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. > > > > Thoughts? > > > > Thanks > > -Vincent > > > >> -----Original Message----- > >> From: Thomas Christensen [mailto:[EMAIL PROTECTED] > >> 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 > > symposium > >> about documenting relevant goals in the project.xml. The aim here is > > to > >> 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 > > on > >> these to make them more accessible but maven.xml should not be > > required > >> 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. > > the > >> war goal doesn't make sense in this context but ear does. > >> > >> Any thoughts on this? > >> > >> Thomas > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [EMAIL PROTECTED] > >> For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
