[
http://jira.codehaus.org/browse/MAPPASM-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MAPPASM-1.
--------------------------------
Resolution: Not A Bug
Assignee: Robert Scholte
MRELEASE-134 has been forwarded to MNG-3109.
It's a maven-core issue rather instead of an appassembler-maven-plugin issue,
so nothing we can do right here.
> appassembler-maven-plugin does not properly resolve version ranges
> ------------------------------------------------------------------
>
> Key: MAPPASM-1
> URL: http://jira.codehaus.org/browse/MAPPASM-1
> Project: Mojo AppAssembler Plugin
> Issue Type: Bug
> Environment: XP Pro SP2
> Reporter: David Hoffer
> Assignee: Robert Scholte
> Fix For: 1.x
>
>
> Similar to MRELEASE-134 in maven-release-plugin
> <version>[1.1.0,)</version>
> This version range can resolve to the latest dev SNAPSHOT. The appassembler
> 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
> forgotten 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
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
