On Fri, 5 Jul 2002, James Strachan wrote:
> I understand the above is all possible by creating new goals in your
> maven.xml file; though I just thought it'd be nice to automate this, via
> command line options.
CLI has a 2-phase option, where we can stop processing at the first
non-option. This allows sub-commands like CVS has:
cvs -d <repo-info> <cmd> <cmd-options>
ie:
cvs -d [EMAIL PROTECTED] remove -f foo
Maybe we can allow a <goal> to process options after the goalname
on the commandline. -p is a global maven option, to pick the
project directory, while -t is defined by the test:test goal:
maven -p /path/to/the/project test -t GooberTest
Likewise maybe
maven -p /path/to/the/project report -r CheckStyle -r JDepend
..would run the 'repot' goal and generate only the JDepend and
CheckStyle reports, or something.
We will need a CliTagLib that plugins/goals could use to define the
options that they take individually. (You busy today, james?)
I'd just like to avoid adding anything for a specific plugin/goal to
the general maven framework. If we can make all of this part of a
plugin, that'd be my goal.
-bob
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
