[ http://jira.codehaus.org/browse/MNG-1213?page=all ]
John Casey updated MNG-1213:
Fix Version: documentation
> more info on the plugin summary
> ---
>
> Key: MNG-1213
> URL: http://jira.codehaus
more info on the plugin summary
---
Key: MNG-1213
URL: http://jira.codehaus.org/browse/MNG-1213
Project: Maven 2
Type: Task
Components: documentation
Reporter: Brett Porter
include:
- mojo.codehaus.org released plugins links
On Fri, 2003-06-27 at 09:19, Michal Maczka wrote:
> +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:
> >
> >
> >sr
> -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
> pro
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.}
Across the board in all plugins for values even for values that belong
to a particular plugin. So some
On Thu, 2003-06-26 at 14:44, bob mcwhirter wrote:
> > As far as property accessing within a plugin:
> >
> > ${maven.compile.target}
>
> So, just like normal, right?
I was actually thinking of just making property access the same across
the board so everywhere it's just
${plugins..}
So for exa
> As far as property accessing within a plugin:
>
> ${maven.compile.target}
So, just like normal, right?
> to access properties defined by the plugin itself and
>
> ${plugins.antlr.src.dir}
>
> to access properties defined in other plugins, this example showing
> access to the antlr plugin's
On Thu, 2003-06-26 at 12:51, Jason van Zyl wrote:
> On Thu, 2003-06-26 at 10:41, Jason van Zyl wrote:
>
>
> > ${plugins.antlr.src.dir}
> >
> > to access properties defined in other plugins, this example showing
> > access to the antlr plugin's properties.
>
> The only problem with this is that
On Thu, 2003-06-26 at 10:41, Jason van Zyl wrote:
> ${plugins.antlr.src.dir}
>
> to access properties defined in other plugins, this example showing
> access to the antlr plugin's properties.
The only problem with this is that jexl(velocity) doesn't deal with this
very well as I soon found out.
Hi,
I just wanted to summarize some of the past few emails regarding
properties use in plugins and the files used to define plugins.
As far as the files used to define plugins I think the best idea came
from Mark H. Wilkinson where the standard file names are used but they
are just placed in a di
10 matches
Mail list logo
