Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
3.0-alpha-1, 3.0.2
-
None
Description
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:
[INFO] Error configuring: test:test-plugin. Reason: ERROR: Cannot override read-only parameter: testParameter in goal: test:dumpParameter
In Maven 3.0.2, the @readonly seems to have no effect:
[INFO] --- test-plugin:0.0.1-SNAPSHOT:dumpParameter (test-exec) @ test-project --- testParameter: readonly parameter configured in pom
You can reproduce the behaviour with the attached example project. Log outputs for Maven 2.2.1 and 3.0.2 are also attached.
Attachments
Attachments
Issue Links
- fixes
-
MJAR-264 finalName property can be set and is not immutable
- Open
-
MNG-5463 warn if maven-site-plugin's reportPlugins is configured in POM
- Closed
- is related to
-
MNG-5222 Maven 3 no longer logs warnings about deprecated plugin parameters.
- Closed
-
MNG-7464 Warn about using read-only parameters for Mojo in configuration
- Closed
-
MNG-5476 [REGRESSION] @required parameter not being enforced for arrays
- Closed
- relates to
-
MNG-5440 default-value on mojo parameter of type collection or array effectively make parameter read-only
- Closed
- links to