> Will the plugin package house plugins too?
> They shouldn't be at the same level as all the other maven stuff.
We definintely need to distinguish between code-that-supports-plugins (ie,
any interfaces or object-models used internally) and plugins-themselves.
The first case is most definitely maven code. The 2nd case may or may
not be written by jakarta folks. 3rd parties may produce plugins under
their own package namespace.
For maven-supplied plugins, I think we should have a hierarchy, like
normal.
Hows about something like this:
// Infrastructure supporting plugins
org.apache.maven.plugin.*
// Stuff that makes up the plugin itself
// iff java code is required.
org.apache.maven.plugins.<plugin_name>.*
In order to maximize re-use, I still see folks writing mostly Ant tasks
in java code. Most maven plugins, I'm imagining at this point, will be
jellywerkzscripts, which may, at times, take on the personality of normal
ant build.xml files.
Anyhow, let's play with the code for a bit, because I'm not certain anyone
really knows exactly how this will pan out.
-bob
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
