Re: restricting maven -g

[Laurie Harper]

Sorry for the slow response, I was on vacation! I understand I can get 
Maven not provide so much functionality :-) but that's not quite what I 
was looking for. When someone checks out my source tree, I want them to 
be able to get the equivalent of 'ant -projecthelp' or something: 
essentially, I want them to see a list of 'what targets are specifically 
of interest for this project?' For example, if it's not a web app then 
the war targets wont be useful, but the user might want that plugin 
installed for use on other projects.

Hope that makes a bit more sense.

L.

Dominik Dahlem wrote:
Maven comes with plugins which provide most of the functionality you
need. If there are any plugin which are not needed in your development
environment you can delete them from the plugins list.
Since some plugins are moved out of the core newer version of maven just
contain only those which are commonly needed.
Dominik

On Fri, 2003-10-10 at 03:55, Laurie Harper wrote:

Maven's coming along fast! :-) The trouble is, now 'maven -g' produces a 
somewhat overwhelming amount of options. Is there any way to constrain 
the output to only list I expect my co-developers to care about?

L.



---------------------------------------------------------------------
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]