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
