Re: Maven Plugin Tools - renaming expression
Perso, no special idea/comments on that.
The current expression looks fine and property too.
2012/5/13 Hervé BOUTEMY herve.bout...@free.fr:
As discussed previously, there was some interest in changing supported tags.
Now that Java 5 annotations support is ok, I already added some change in
MPLUGIN-194 [1]: you can remove ${ } when defining parameter expression
I just created MPLUGIN-196 issue [2] to rename expression to property,
where ${ } would even not be supported
Please comment: any objection? any better idea?
Regards,
Hervé
[1] https://jira.codehaus.org/browse/MPLUGIN-194
[2] https://jira.codehaus.org/browse/MPLUGIN-196
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Re: Maven Plugin Tools - renaming expression
I like these adjustments, but there's one spot which is probably even more
important: the specific goal-page.
Just an example:
---
failOnError:
Indicates whether the build will continue even if there are clean errors.
•Type: boolean
•Since: 2.2
•Required: No
•Expression: ${maven.clean.failOnError}
•Default: true
---
I'm not sure how we could make it clear how to use expressions/properties.
Some global description on this page?
Or an easy to copy-paste line like:
•Commandline argument: -Dmaven.clean.failOnError=
-Robert
Op Mon, 14 May 2012 17:59:58 +0200 schreef Olivier Lamy ol...@apache.org:
Perso, no special idea/comments on that.
The current expression looks fine and property too.
2012/5/13 Hervé BOUTEMY herve.bout...@free.fr:
As discussed previously, there was some interest in changing supported
tags.
Now that Java 5 annotations support is ok, I already added some change
in
MPLUGIN-194 [1]: you can remove ${ } when defining parameter expression
I just created MPLUGIN-196 issue [2] to rename expression to
property,
where ${ } would even not be supported
Please comment: any objection? any better idea?
Regards,
Hervé
[1] https://jira.codehaus.org/browse/MPLUGIN-194
[2] https://jira.codehaus.org/browse/MPLUGIN-196
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Re: Maven Plugin Tools - renaming expression
2012/5/14 Robert Scholte apa...@sourcegrounds.com:
I like these adjustments, but there's one spot which is probably even more
important: the specific goal-page.
Just an example:
---
failOnError:
Indicates whether the build will continue even if there are clean errors.
•Type: boolean
•Since: 2.2
•Required: No
•Expression: ${maven.clean.failOnError}
•Default: true
---
I'm not sure how we could make it clear how to use expressions/properties.
Some global description on this page?
Or an easy to copy-paste line like:
•Commandline argument: -Dmaven.clean.failOnError=
can come from project.properties or settings.properties.
So that's not the only way to configure that :-)
-Robert
Op Mon, 14 May 2012 17:59:58 +0200 schreef Olivier Lamy ol...@apache.org:
Perso, no special idea/comments on that.
The current expression looks fine and property too.
2012/5/13 Hervé BOUTEMY herve.bout...@free.fr:
As discussed previously, there was some interest in changing supported
tags.
Now that Java 5 annotations support is ok, I already added some change in
MPLUGIN-194 [1]: you can remove ${ } when defining parameter expression
I just created MPLUGIN-196 issue [2] to rename expression to
property,
where ${ } would even not be supported
Please comment: any objection? any better idea?
Regards,
Hervé
[1] https://jira.codehaus.org/browse/MPLUGIN-194
[2] https://jira.codehaus.org/browse/MPLUGIN-196
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven Enforcer version 1.1
Hi, The vote has passed with the following result: +1 (binding): Olivier Lamy, John Casey, Robert Scholte, Hervé Boutemy +1 (non binding): Mirko Friedenhagen, Tony Chemit I will promote the artifacts to the central repo. On 05/08/2012 10:46 PM, Paul Gier wrote: Hi, We solved 5 issues: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11530version=17443 There are still a couple of issues left in JIRA: https://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truejqlQuery=project+%3D+MENFORCER+AND+status+%3D+Open+ORDER+BY+priority+DESCmode=hide Staging repo: https://repository.apache.org/content/repositories/maven-058/ Staging site: http://maven.apache.org/enforcer-1.1/ http://maven.apache.org/plugins/maven-enforcer-plugin-1.1/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Maven Plugin Tools - renaming expression
Op Mon, 14 May 2012 22:13:52 +0200 schreef Olivier Lamy ol...@apache.org:
2012/5/14 Robert Scholte apa...@sourcegrounds.com:
I like these adjustments, but there's one spot which is probably even
more
important: the specific goal-page.
Just an example:
---
failOnError:
Indicates whether the build will continue even if there are clean
errors.
•Type: boolean
•Since: 2.2
•Required: No
•Expression: ${maven.clean.failOnError}
•Default: true
---
I'm not sure how we could make it clear how to use
expressions/properties.
Some global description on this page?
Or an easy to copy-paste line like:
•Commandline argument: -Dmaven.clean.failOnError=
can come from project.properties or settings.properties.
So that's not the only way to configure that :-)
True, although less usual, but that could be solved with an additional
maven.clean.failOnError/maven.clean.failOnError :P
I guess to keep it a bit clean we should either describe it on top of the
page or refer to a (new?) general plugin usage page.
-Robert
Op Mon, 14 May 2012 17:59:58 +0200 schreef Olivier Lamy
ol...@apache.org:
Perso, no special idea/comments on that.
The current expression looks fine and property too.
2012/5/13 Hervé BOUTEMY herve.bout...@free.fr:
As discussed previously, there was some interest in changing supported
tags.
Now that Java 5 annotations support is ok, I already added some
change in
MPLUGIN-194 [1]: you can remove ${ } when defining parameter
expression
I just created MPLUGIN-196 issue [2] to rename expression to
property,
where ${ } would even not be supported
Please comment: any objection? any better idea?
Regards,
Hervé
[1] https://jira.codehaus.org/browse/MPLUGIN-194
[2] https://jira.codehaus.org/browse/MPLUGIN-196
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
[ANN] Maven Enforcer 1.1 Released
The Maven team is pleased to announce the release of the Maven Enforcer, version 1.1 This plugin provides various configurable validation rules for Maven builds. http://maven.apache.org/enforcer/ http://maven.apache.org/plugins/maven-enforcer-plugin/ You should specify the version in your project's plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-enforcer-plugin/artifactId version1.1/version /plugin Release Notes - Maven 2.x Enforcer Plugin - Version 1.1 ** Bug * [MENFORCER-98] - requirePluginVersions rule is not compatible with maven 3.0-beta-1 * [MENFORCER-114] - Typo in Require Plugin Versions Documentation * [MENFORCER-125] - requireProperty documentation's example for property.version uses wrong regex ** Improvement * [MENFORCER-118] - DependencyConvergence gets better if it doesn't fail on snapshots of same baseVersion ** New Feature * [MENFORCER-128] - Fail the build if a dependency is overwriten with an incompatible lower version (patch) Enjoy, -The Maven team - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Maven Plugin Tools - renaming expression
I think these are both good ideas.
There's a couple of things expression currently supports that probably
shouldn't be supported under property to avoid confusion:
- ${project.*} as these should be specified under a default-value (they can't
be overridden by -Dproject.XXX, etc.).
- ${settings}, ${session}, etc. - Maven internal variables. It would be good to
have some other way to describe them that is not @parameter, and can avoid the
need for the redundant @readonly and @required they usually come with
Looking at that, it actually seems like readonly and required belong as
attributes of @parameter now too.
- Brett
On 14/05/2012, at 5:59 AM, Hervé BOUTEMY wrote:
As discussed previously, there was some interest in changing supported tags.
Now that Java 5 annotations support is ok, I already added some change in
MPLUGIN-194 [1]: you can remove ${ } when defining parameter expression
I just created MPLUGIN-196 issue [2] to rename expression to property,
where ${ } would even not be supported
Please comment: any objection? any better idea?
Regards,
Hervé
[1] https://jira.codehaus.org/browse/MPLUGIN-194
[2] https://jira.codehaus.org/browse/MPLUGIN-196
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
--
Brett Porter
br...@apache.org
http://brettporter.wordpress.com/
http://au.linkedin.com/in/brettporter
http://twitter.com/brettporter
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
