[
http://jira.codehaus.org/browse/MVERSIONS-77?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=194325#action_194325
]
Stevo Slavic commented on MVERSIONS-77:
---------------------------------------
Since maven2 comparison rules are the way they are, if I understood well maven3
will use mercury, and mercury apparently handles well both maven2 three-part +
qualifier versions and multi-part versions (like four-part OSGi style
versions), I wanted to configure mercury to be used as comparison method for
all artifacts, to see how it would work with current maven2 and current
versions plugin (e.g. to check if that example from MVERSIONS-76 with spring
2.5.6 being recognized as newer than 2.5.6.SEC01 would work better or not). I
don't understand why you emphasized that some artifacts must use maven
comparison, I'm configuring single artifact, maven versions plugin, which
comparison method to use when checking for dependency updates, and I want it to
use mercury version comparison method for all artifacts, assuming that mercury
is working as described earlier.
Anyway, then I got to configuring versions plugin in project pom file which is
an XML file, with another plugin specific XML file. It's minor, or even trivial
issue that one has to create/maintain/document that yet another XML
configuration file. Bigger issue is that if one wanted to share versions plugin
configuration file across multiple projects, that configuration file would have
to be published on some URL as XML file and not, IMO in maven2 standard way of
sharing build settings across multiple maven2 projects, in form of maven2
artifact (like e.g. maven checkstyle plugin). Please correct me if I'm being
wrong.
BTW, rule-1.0.0.xsd doesn't restrict nor document possible values for
comparisonMethod attribute - does it mean one can besides using available
maven, mercury and numeric comparison methods, specify additional custom
comparison methods and provide their implementation? This same XSD also doesn't
specify/document default comparisonMethod attribute value.
> Support for configuring global comparisonMethod without requiring creation of
> rule-set xml
> ------------------------------------------------------------------------------------------
>
> Key: MVERSIONS-77
> URL: http://jira.codehaus.org/browse/MVERSIONS-77
> Project: Maven 2.x Versions Plugin
> Issue Type: Wish
> Affects Versions: 1.0
> Reporter: Stevo Slavic
> Priority: Minor
>
> Please support configuring global comparisonMethod, so that one isn't
> required to create and configure custom rule-set xml if a common version
> number scheme should be used for all artifacts version comparisons. This
> could be implemented as additional parameter to every plugin mojo (like
> rulesUri), defaulting to "maven". If reference to rule-set xml is configured
> via rulesUri along with new global comparisonMethod param, then any value
> configured as comparisonMethod attribute of ruleset should override global
> comparisonMethod.
--
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
