On 28 Jun 2002, Jason van Zyl wrote:
> The plugins probably won't change much in form, but the packaging will
> be different. Bob and I will probably have plugins working out of JARs
> by the end of the weekend as we're on a bit of a tear.
One thing that we need to decide on and subsequently do, is namespacing of
things within plugins. We're building 1 big-ass goal graph, referencing
things by name, and sharing data in 1 big-ass property context.
It'd be easy-enough to have <goal name="foo"> within plugin 'bar' to
get automatically munged into a bar:far target.
This way, we won't have multiple plugins fighting over <goal
name="prepare-filesystem"> or other commonly used names.
One alternative is to allow for private goals, visible only within
the plugin itself, which I think is possible to do. But, we may
still trample on public goal names.
As it stands now, some goals have a maven: prefix, some have a docs:
prefix, and some have no prefix.
Right now, bin/maven will look for whatever you ask for, and if not
found, falls back to prefixing it with maven: and trying again. This
won't make much sense in a world where we don't have all goals
prefixed with maven:.
Regarding folks not wanting to type
maven xdocs:site-report
Anyone can easily create their own aliases in $PROJECT/maven.xml
<goal name="frobnicate" prereqs="xdocs:site-report"/>
And if you give me a day or so, we could even have an explicit
<alias> tag:
<alias name="xdocs:site-report" to="frobnicate"/>
Syntax is easy.
-bob
("Math is hard.")
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
