[jira] [Comment Edited] (MNG-3092) Resolution of version ranges with non-snapshot bounds can resolve to a snapshot version
[
https://issues.apache.org/jira/browse/MNG-3092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16486576#comment-16486576
]
Mohammad Norouzi edited comment on MNG-3092 at 5/23/18 1:45 AM:
We really need this. I also think the range should support a format with which
the version can be resolved with. We are moving away from SNAPSHOT to Semantic
Versioning and we want to include only semver format... so for example, when
the version range is like:
{code:java}
[1.0.0, 2.0.0){code}
We don't want other versions like 1.0.00 or 1.0.01 to be included. 1.0.0 and
1.0.1 are valid. This is causing issues and I am trying to create a patch to
customise maven which I am really hesitated to do.
was (Author: xbmono):
We really need this. I also think the range should support a format with which
the version can be resolved with. We are moving away from SNAPSHOT to Semantic
Versioning and we want to include only semver format... so for example, when
the version range is like:
{code:java}
[1.0.0, 2.0.0){code}
We don't want other versions like 1.0.00 or 1.0.01 to be included. 1.0.0 and
1.0.1 are valid. This is causing issues and I am trying to create a patch to
customise maven which I really hesitate to do so.
> Resolution of version ranges with non-snapshot bounds can resolve to a
> snapshot version
> ---
>
> Key: MNG-3092
> URL: https://issues.apache.org/jira/browse/MNG-3092
> Project: Maven
> Issue Type: Bug
> Components: Dependencies
>Reporter: Mark Hobson
>Priority: Major
> Fix For: 3.x / Backlog
>
> Attachments: MNG-3092.patch, MNG-3092.patch
>
>
> Contrary to the 2.0 design docs:
> "Resolution of dependency ranges should not resolve to a snapshot
> (development version) unless it is included as an explicit boundary."
> -- from
> http://docs.codehaus.org/display/MAVEN/Dependency+Mediation+and+Conflict+Resolution#DependencyMediationandConflictResolution-Incorporating%7B%7BSNAPSHOT%7D%7Dversionsintothespecification
> The following is equates to true:
> VersionRange.createFromVersionSpec( "[1.0,1.1]" ).containsVersion( new
> DefaultArtifactVersion( "1.1-SNAPSHOT" ) )
> The attached patch only allows snapshot versions to be contained in a range
> if they are equal to one of the boundaries. Note that this is a strict
> equality, so [1.0,1.2-SNAPSHOT] will not contain 1.1-SNAPSHOT.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-3092) Resolution of version ranges with non-snapshot bounds can resolve to a snapshot version
[
https://issues.apache.org/jira/browse/MNG-3092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16486576#comment-16486576
]
Mohammad Norouzi commented on MNG-3092:
---
We really need this. I also think the range should support a format with which
the version can be resolved with. We are moving away from SNAPSHOT to Semantic
Versioning and we want to include only semver format... so for example, when
the version range is like:
{code:java}
[1.0.0, 2.0.0){code}
We don't want other versions like 1.0.00 or 1.0.01 to be included. 1.0.0 and
1.0.1 are valid. This is causing issues and I am trying to create a patch to
customise maven which I really hesitate to do so.
> Resolution of version ranges with non-snapshot bounds can resolve to a
> snapshot version
> ---
>
> Key: MNG-3092
> URL: https://issues.apache.org/jira/browse/MNG-3092
> Project: Maven
> Issue Type: Bug
> Components: Dependencies
>Reporter: Mark Hobson
>Priority: Major
> Fix For: 3.x / Backlog
>
> Attachments: MNG-3092.patch, MNG-3092.patch
>
>
> Contrary to the 2.0 design docs:
> "Resolution of dependency ranges should not resolve to a snapshot
> (development version) unless it is included as an explicit boundary."
> -- from
> http://docs.codehaus.org/display/MAVEN/Dependency+Mediation+and+Conflict+Resolution#DependencyMediationandConflictResolution-Incorporating%7B%7BSNAPSHOT%7D%7Dversionsintothespecification
> The following is equates to true:
> VersionRange.createFromVersionSpec( "[1.0,1.1]" ).containsVersion( new
> DefaultArtifactVersion( "1.1-SNAPSHOT" ) )
> The attached patch only allows snapshot versions to be contained in a range
> if they are equal to one of the boundaries. Note that this is a strict
> equality, so [1.0,1.2-SNAPSHOT] will not contain 1.1-SNAPSHOT.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] Created: (MRELEASE-508) Add TFS support
Add TFS support --- Key: MRELEASE-508 URL: http://jira.codehaus.org/browse/MRELEASE-508 Project: Maven 2.x Release Plugin Issue Type: New Feature Components: scm Environment: any environment Reporter: Mohammad Norouzi We need to check-out from TFS (Team Foundation Server) and label (like tags in SVN) new release versions -- 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
[jira] Created: (MRELEASE-509) Release dependencies before releasing the projects
Release dependencies before releasing the projects --- Key: MRELEASE-509 URL: http://jira.codehaus.org/browse/MRELEASE-509 Project: Maven 2.x Release Plugin Issue Type: Wish Reporter: Mohammad Norouzi Consider we have project A which is dependent to B and C with SNAPSHOT version. then what if the project version manager was able to run the command with an option and the plugin first checks out all the snapshot versions and creates a release version for each and then create a release version for project which this plugin is fired and update all the pom files. -- 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
[jira] Commented: (MRELEASE-508) Add TFS support
[ http://jira.codehaus.org/browse/MRELEASE-508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=204161#action_204161 ] Mohammad Norouzi commented on MRELEASE-508: --- Thanks. So Do I have to close this issue? Add TFS support --- Key: MRELEASE-508 URL: http://jira.codehaus.org/browse/MRELEASE-508 Project: Maven 2.x Release Plugin Issue Type: New Feature Components: scm Environment: any environment Reporter: Mohammad Norouzi We need to check-out from TFS (Team Foundation Server) and label (like tags in SVN) new release versions -- 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
