[
https://issues.apache.org/jira/browse/MNG-6572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17069821#comment-17069821
]
Hudson commented on MNG-6572:
-----------------------------
Build failed in Jenkins: Maven TLP » maven-studies » maven-metrics #4
See
https://builds.apache.org/job/maven-box/job/maven-studies/job/maven-metrics/4/
> use int or long instead of BigIntegers for little numbers in ComparableVersion
> ------------------------------------------------------------------------------
>
> Key: MNG-6572
> URL: https://issues.apache.org/jira/browse/MNG-6572
> Project: Maven
> Issue Type: Improvement
> Components: Artifacts and Repositories, Performance
> Affects Versions: 3.6.0
> Reporter: Herve Boutemy
> Assignee: Herve Boutemy
> Priority: Major
> Labels: up-for-grabs
> Fix For: 3.6.1
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> while working on MNG-6571, we found that this could enhance performance when
> many versions are compared: perhaps not in Maven builds, since this is
> probably negligible, but in other scenario where version comparison is used,
> this could be useful
> see
> https://github.com/apache/maven/blob/master/maven-artifact/src/main/java/org/apache/maven/artifact/versioning/ComparableVersion.java
> for every Integer, a BigInteger is currently used
> but for integer that have less than 10 digits, an int would be sufficient and
> would be a lot more efficient
> and for integers that are less than 19 digits, a long would be the way to go
> the biggest numbers we get usually is the timestamp of a SNAPSHOT, like
> {{20171015.230843}} (YYYYMMDD.HHmmss), then an int will be sufficient in the
> vast majority of case
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
