Erik Drolshammer wrote:
I don't know these properties well enough to conclude one way or the
other. Can someone (TM) help me with these?
There is currently no functional difference between "default-value" and
"expression", both will get you the values you want. See [0] and [1] for
some more details.
The "expression" is primarily meant to allow configuration from the CLI
via "-Dfoo=bar". Hence, as soon as you want a parameter to be
configurable from the CLI, you need to move the default values into
"default-value" anyway.
The other thing is that "default-value" will show up nicely in the
plugin doc, i.e. delivers more informative material for the user.
Compare the parameter descriptions in the summary tables on
http://mojo.codehaus.org/appassembler/appassembler-maven-plugin/assemble-mojo.html
and
http://mojo.codehaus.org/appassembler/appassembler-maven-plugin/generate-daemons-mojo.html
The @readonly annotation just prevents overriding parameters from the
POM and also hides them from the plugin doc.
Benjamin
[0]
http://www.nabble.com/Difference-between-default-value-and-expression-metatags-td5725581.html
[1]
http://www.nabble.com/Plugin-Parameters%3A-expression-vs.-default-value-td15109298.html
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
