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
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:
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
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:
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
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
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},
