You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Mike R. Haller (JIRA)" <ji...@codehaus.org> on 2008/03/20 10:48:46 UTC
[jira] Commented: (MRELEASE-334) Can't release project due to non
released dependencies
[ http://jira.codehaus.org/browse/MRELEASE-334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_127975 ]
Mike R. Haller commented on MRELEASE-334:
-----------------------------------------
We've got this issue too, with SNAPSHOT versions of a reporting plugin.
The maven release plugin permits the release of our projects due to the dependency on a SNAPSHOT reporting plugin, which doesn't make sense in most cases. I don't care about reports for a release, so there should be a configuration or command line parameter to exclude reporting plugins from the "no snapshot dependencies" verification.
> Can't release project due to non released dependencies
> ------------------------------------------------------
>
> Key: MRELEASE-334
> URL: http://jira.codehaus.org/browse/MRELEASE-334
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Affects Versions: 2.0-beta-7
> Reporter: Kamen Petroff
> Attachments: maven-release-manager.patch, maven-release-manager.patch
>
>
> I guess the problem is already known. But once again
> in maven-release-manager 1.0-alpha-4
> org/apache/maven/shared/release/phase/CheckDependencySnapshotsPhase.java
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira