cut off date the Friday after next.
Yep... that's why I brought it up. Did you want to write it up?
- Brett
Cheers,
Brett
Begin forwarded message:
From: Jason van Zyl <[EMAIL PROTECTED]>
Date: 22 August 2006 9:40:53 AM
To: Maven Developers List
Subject: Standards for Plugin P
s,
Brett
Begin forwarded message:
From: Jason van Zyl <[EMAIL PROTECTED]>
Date: 22 August 2006 9:40:53 AM
To: Maven Developers List
Subject: Standards for Plugin Parameters
Reply-To: "Maven Developers List"
List-Id: "Maven Developers List"
Message-Id: <[EMAIL PROTECTED
this already get
addressed in another way? I don't recall seeing it implemented, but I
could be wrong.
Cheers,
Brett
Begin forwarded message:
From: Jason van Zyl <[EMAIL PROTECTED]>
Date: 22 August 2006 9:40:53 AM
To: Maven Developers List
Subject: Standards for Plugin Par
+1
This sounds like a good proposal to me.
Brett Porter wrote:
+1 under current circumstances.
Bearing in mind the following:
a) we agreed to eliminate expression over time to an explicit "property"
(or some other name) that would just be property="jar.forcedCreate" -
this doesn't actually c
Brett Porter wrote:
+1 under current circumstances.
Bearing in mind the following:
a) we agreed to eliminate expression over time to an explicit "property"
(or some other name) that would just be property="jar.forcedCreate" -
this doesn't actually change anything
b) I'd actually like to be a
+1 under current circumstances.
Bearing in mind the following:
a) we agreed to eliminate expression over time to an explicit
"property" (or some other name) that would just be
property="jar.forcedCreate" - this doesn't actually change anything
b) I'd actually like to be able to eliminate it
Hi,
What about the properties common to many plugins
like the java version used in compiler, javadoc and aspectCompiler ?
Raphaël
2006/8/22, Barrie Treloar <[EMAIL PROTECTED]>:
> I've seen all sorts of format for parameters as with everything the
> format is arbitrary but it would be good to
I've seen all sorts of format for parameters as with everything the
format is arbitrary but it would be good to have a standard guideline
to follow.
Anyone else have any thoughts?
Any guidance on this would be good for consistency.
What is suggested looks good.
Hi,
While working on MJAR-7, John and I discussed a possible standard for
plugin parameters naming conventions. Which basically boil down to:
field/property = noun|verbNoun
expression= prefix.noun|verbNoun
So for MJAR-7 we have
field = forceCreation
expression = jar.forceCre
