Hi,
I'll do the Plugin Summary again as a few people missed it and I
probably didn't explain myself clearly.
As far as plugin property access I am proposing:
${plugins.<short-plugin-id.<property>}
Across the board in all plugins for values even for values that belong
to a particular plugin. So something like:
${plugins.antlr.srcDir}
Inside and outside the Antlr plugin.
Users would then override the properties using the same exact notation
where:
plugins.antlr.srcDir = /path
As far as the structure of the plugin, I propose what Mark H. Wilkinson
suggested where we use different directories to distinguish between
build time and runtime. So the structure would look something like:
<plugin>
src/
plugin-resources/
plugin-runtime/
project.properties | run time
maven.xml |
project.properties |
maven.xml | build time
After the 1.0 release these things will never change. But with the
separation now in place and for clarity and uniformity and ease of
documentation I think would be a good thing.
I think the majority of people use the plugins we provide and we can
take care of all our plugins.
I will ask on the user list, if there is a hue and a cry then I can
probably rig something. But I would wager that the majority of people
use the standard plugins that ship with Maven.
So these cannot change in the lifecycle of 1.x and I don't see them
having to change after that either.
--
jvz.
Jason van Zyl
[EMAIL PROTECTED]
http://tambora.zenplex.org
In short, man creates for himself a new religion of a rational
and technical order to justify his work and to be justified in it.
-- Jacques Ellul, The Technological Society
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
