Good day,
Actually, using @parameter only should be sufficient for it to be configured
via the pom. The @expression is used for setting the parameter via
commandline.
Anyway, Martin M., try specifying in your plugin tag the groupId and version
as well. It might still be trying to configure
org.apache.maven.plugins:maven-compiler-plugin:RELEASE instead of your
custom compiler plugin.
Cheers,
Franz
Jörg Schaible wrote:
>
> Hi Martin,
>
>
> there's no automation. You need to provide the expression for the
> parameter to initialize:
>
> [snip]
>
> /**
> * @parameter expression="${testParam}"
> **/
> private String testParam
>
> [snip]
>
> Within the expression you can also address other parts of the POM ...
> another typical parameter is:
>
> /**
> * The directory for the generated file.
> *
> * @parameter expression="${project.build.directory}"
> * @required
> */
> private String outputDirectory;
>
> - Jörg
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
--
View this message in context:
http://www.nabble.com/passing-custom-parameters-to-a-custom-compiler-plugin-tf2958426s177.html#a8292757
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
