You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Stephane Nicoll (JIRA)" <ji...@codehaus.org> on 2007/05/03 14:43:26 UTC
[jira] Commented: (MASSEMBLY-208) Assembly plugin does not resolve
version ranges correctly
[ http://jira.codehaus.org/browse/MASSEMBLY-208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94932 ]
Stephane Nicoll commented on MASSEMBLY-208:
-------------------------------------------
please stop creating issues in the plugin projects for that. This is most probably a Maven core issue and you should use the MNG project.
> Assembly plugin does not resolve version ranges correctly
> ---------------------------------------------------------
>
> Key: MASSEMBLY-208
> URL: http://jira.codehaus.org/browse/MASSEMBLY-208
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.1
> Environment: XP Pro SP2
> Reporter: David Hoffer
>
> Similar to MRELEASE-134 in maven-release-plugin
> <version>[1.1.0,)</version>
> This version range can resolve to the latest dev SNAPSHOT. The assembly plugin should ignore SNAPSHOTS as that is not intended by the unbounded high end of the version range.
> This document:
> http://docs.codehaus.org/display/MAVEN/Dependency+Mediation+and+Conflict+Resolution#DependencyMediationandConflictResolution-DependencyVersionRanges
> addressed the requirements for version ranges and stated that "Resolution of dependency ranges should not resolve to a snapshot (development version) unless it is included as an explicit boundary". I think this requirement was forgetten when version ranges were implemented.
--
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