[jira] [Commented] (MNG-5001) @readonly Mojo parameter annotation doesn't work any more

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MNG-5001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17555865#comment-17555865 ] 

ASF GitHub Bot commented on MNG-5001:
-------------------------------------

slachiewicz closed pull request #240: [MNG-5001] Block the option to set Mojo parameters marked as @readonly
URL: https://github.com/apache/maven/pull/240




> @readonly Mojo parameter annotation doesn't work any more
> ---------------------------------------------------------
>
>                 Key: MNG-5001
>                 URL: https://issues.apache.org/jira/browse/MNG-5001
>             Project: Maven
>          Issue Type: Bug
>          Components: Plugin API
>    Affects Versions: 3.0-alpha-1, 3.0.2
>            Reporter: Jochen Ehret
>            Priority: Major
>             Fix For: 4.0.x-candidate
>
>         Attachments: log-maven-2.2.1.txt, log-maven-3.0.2.txt, pom.xml, readonlytest.zip
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> In Maven 2.2.1, the @readonly annotation works as described: You can't configure a Mojo parameter in the pom <configuration> section. If you do, the build will fail:
> {noformat}[INFO] Error configuring: test:test-plugin. Reason: ERROR: Cannot override read-only parameter: testParameter in goal: test:dumpParameter{noformat}
> In Maven 3.0.2, the @readonly seems to have no effect:
> {noformat}[INFO] --- test-plugin:0.0.1-SNAPSHOT:dumpParameter (test-exec) @ test-project ---
> testParameter: readonly parameter configured in pom{noformat}
> You can reproduce the behaviour with the attached example project. Log outputs for Maven 2.2.1 and 3.0.2 are also attached.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)