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

Robert Scholte commented on MNG-5001:
-------------------------------------

This one I know. The release plugin contains a check that its own version is a 
non-SNAPSHOT to ensure a stable release. However that won't work during 
integration tests. So this property is a hidden (awkward way of saying 
read-only) parameter. I was already suprised this worked. 
The solution here is probably to that during integration tests the version of 
the maven-release-plugin should be adjusted to something final (replace 
SNAPSHOT by ...) during the integrations tests.

> @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
>            Assignee: Sylwester Lachiewicz
>            Priority: Major
>             Fix For: 3.7.0-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.3.4#803005)

Reply via email to