You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Hudson (Jira)" <ji...@apache.org> on 2020/03/28 15:04:03 UTC
[jira] [Commented] (MNG-6630) ComparableVersion.parseVersion is
inefficient
[ https://issues.apache.org/jira/browse/MNG-6630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17069834#comment-17069834 ]
Hudson commented on MNG-6630:
-----------------------------
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/
> ComparableVersion.parseVersion is inefficient
> ---------------------------------------------
>
> Key: MNG-6630
> URL: https://issues.apache.org/jira/browse/MNG-6630
> Project: Maven
> Issue Type: Bug
> Components: core
> Affects Versions: 3.6.0
> Reporter: Stefan Oehme
> Assignee: Herve Boutemy
> Priority: Major
> Fix For: 3.6.2
>
>
> I'm currently optimizing a very large (2000+ submodule) project. ComparableVersion.parseVersion is one of the CPU/memory hotspots, because it creates a "canonical" String from the parsed parts, even though that String is only used by tests/debugging. It would be more efficient to only create that String on demand.
> See [https://github.com/apache/maven/pull/242]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)