default-value is usually what plugin developers want, not expression.
[...]
In other words, expression results should not be allowed to
reflectively query the build state, as in ${project.build.directory},
Thanks for clarifying this. Until you get a proper documentation up and
running, I sugges
default-value is usually what plugin developers want, not expression.
The reason we support both is to allow a default value extracted from
the build state, but offer a name for the parameter that's different
from the member variable name. It's an artifact of running for awhile
without defa
> /**
> * @parameter expression="${project.build.outputDirectory}"
>*/
> private File outputDirectory;
>and
> /**
>* @parameter default-value="${project.build.outputDirectory}"
>*/
> private File outputDirectory;
Interesting problem. I usually prefer to use the expression
Hello,
The generated site documentation for many mojo parameters lacks the nice
info "Default value is " in the parameter summary although the
parameter effectively has a default value. Take for instance the site for
the maven-resources-plugin and its "outputDirectory" parameter [0].
This effect
