Uploaded image for project: 'Maven'
  1. Maven
  2. MNG-6630

ComparableVersion.parseVersion is inefficient

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 3.6.0
    • 3.6.2
    • Core
    • None

    Description

      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

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            hboutemy Herve Boutemy
            oehme Stefan Oehme
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment