[
https://jira.codehaus.org/browse/MVERSIONS-164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arnout Engelen updated MVERSIONS-164:
-------------------------------------
Attachment: noMajorUpdates.patch
Patch that should fix the issue.
Not sure what to do with the PropertyVersionComparator inside PropertyVersions,
but this does pass all unit tests and produces the behavior I expected.
> allowMajorUpdates=false and allowSnapshots=true interfere
> ---------------------------------------------------------
>
> Key: MVERSIONS-164
> URL: https://jira.codehaus.org/browse/MVERSIONS-164
> Project: Maven 2.x Versions Plugin
> Issue Type: Bug
> Affects Versions: Backlog
> Reporter: Arnout Engelen
> Attachments: noMajorUpdates.patch, noMajorUpdatesTest.patch
>
>
> When setting 'allowMajorUpdates' to 'false' and 'allowSnapshots' to 'true',
> '1.0' will still be upgraded to '2.0-SNAPSHOT', presumable because it is
> considered to be below the 'upper bound' of '2.0'.
> This is obviously undesirable because setting 'allowMajorUpdates' to 'false'
> is likely to be intended to prevent upgrading to a version with API-breaking
> changes, and '2.0-SNAPSHOT' may already hold those API-breaking changes.
> Attached is a patch that adds a unit test showing the behavior.
--
This message is automatically generated by JIRA.
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
