Uploaded image for project: 'Maven Resolver'
  1. Maven Resolver
  2. MRESOLVER-68

Add caching around File.getCanonicalPath

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major
    • Resolution: Won't Fix
    • None
    • None
    • Resolver
    • None

    Description

      Maven Resolver spends a lot of time calculating the canonical path for a File, and subsequently interning the result, in order to generate an in memory lock object for the File. This can add up to 50% or more of the time in a build, especially when using maven-enforcer-plugin with the bannedDependencies rule with searchTransitive true.

      Caching these lookups will reduce build times, even for well behaved plugins.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              richarda Richard Atkins
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 10m
                  10m