Hello,
Am 31.10.2013, 10:36 Uhr, schrieb Hervé BOUTEMY <[email protected]>:
but for the way to configure the parameter (ie parameter vs expression),
it's
more than a convention, it's a change in plugin-tools in version 3.0,
done
when adding Java 5 annotations support: expression was the parameter name
provided as javadoc annotations, but it was changed in Java 5
annotations:
1. expanded to not need ${} in
http://jira.codehaus.org/browse/MPLUGIN-194
2. renamed to property in http://jira.codehaus.org/browse/MPLUGIN-196
I see, I was checking a random documentation page on the Web first because
I remebered having seen expressions as default values to be usefull in the
Mojos (and some did not had some).
I was first visiting this page:
http://maven.apache.org/plugin-tools/maven-plugin-tools-annotations/index.html
But as it did not describe the defaultValue/property so I was following
the link at the end to
http://maven.apache.org/developers/mojo-api-specification.html#The_Descriptor_and_Annotations
And I missed the fact that this is not describing the Java annotations but
the JavaDoc ones. So sorry for the confusion. (But maybe it would be
helpful to change the table header from "Annotations" to "JavaDoc Tag"?
And the new annotations page really need a detailed description (javadoc?)
of the annotation attributes or link to the apidoc, like:
http://maven.apache.org/plugin-tools/maven-plugin-annotations/apidocs/index.html
And this means that @Parameter( property = "maven.rar.skip" ) makes the
property available from the command line, no problem
Agreed, you diagnosted the right reason for my wrong comment :)
Bernd
--
http://www.zusammenkunft.net
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
