[
https://jira.codehaus.org/browse/MRELEASE-768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stevo Slavic closed MRELEASE-768.
---------------------------------
Resolution: Not A Bug
Not a bug, works ok - just reference to A dependency was wrong.
> Prepare wrongly reports snapshot dependencies existence for project's war
> module attachedClasses
> ------------------------------------------------------------------------------------------------
>
> Key: MRELEASE-768
> URL: https://jira.codehaus.org/browse/MRELEASE-768
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
> Affects Versions: 2.3.1
> Environment: maven 3.0.4
> jdk 1.6 x64 update 32
> Reporter: Stevo Slavic
> Priority: Minor
>
> P
> |--W (+A)
> |--J (depends on A)
> P is parent and aggregator module with two child modules W (war) and J (jar).
> W module has maven-war-plugin:2.2 configured to
> [attachClasses|http://maven.apache.org/plugins/maven-war-plugin/war-mojo.html#attachClasses]
> resulting in additional artifact A with Ws classes attached to the build. A
> is declared as (provided) dependency of J.
> Problem is that P cannot be release prepared - snapshot dependencies check
> fails for J module on A dependency. It seems that maven release plugin isn't
> aware that the W will also produce A artifact.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
