> -----Original Message-----
> From: Jason van Zyl [mailto:[EMAIL PROTECTED]
> Sent: Friday, June 27, 2003 3:08 PM
> To: Maven Developers List
> Subject: Plugin Summary
>
> 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
>
+1
> 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.
Never say never ;)
>But with the
> separation now in place and for clarity and uniformity and ease of
> documentation I think would be a good thing.
>
I propose:
<plugin>
src/
main/
resources/
java/
runtime/
project.properties | run time
maven.xml |
test/
resources/
java/
project.properties |
maven.xml | build time
xdocs/
Michal
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
