You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Olivier Lamy (JIRA)" <ji...@codehaus.org> on 2014/04/28 09:43:10 UTC

[jira] (MSHARED-307) Performance: The implementation of DefaultClassAnalyzer unnecessarily scans jar files bodies

     [ https://jira.codehaus.org/browse/MSHARED-307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Olivier Lamy reassigned MSHARED-307:
------------------------------------

    Assignee: Olivier Lamy

> Performance: The implementation of DefaultClassAnalyzer unnecessarily scans jar files bodies
> --------------------------------------------------------------------------------------------
>
>                 Key: MSHARED-307
>                 URL: https://jira.codehaus.org/browse/MSHARED-307
>             Project: Maven Shared Components
>          Issue Type: Bug
>          Components: maven-dependency-analyzer
>    Affects Versions: maven-dependency-analyzer-1.4
>            Reporter: Victor Bronstein
>            Assignee: Olivier Lamy
>
> The contract of the method is to provide a list of classes given a URL. In case of JAR files it would be enough to use JarFile#entries. However, since the implementation delegates to ClassFileVisitorUtils using an implementation of the visitor, the JAR files are being read completely, including the streams of the individual classes.
> This is a considerable performance hit. Specifically, in our project we have vast amount of Maven modules and do a dependency validation for them. By replacing the current implementation with one that uses JarFile#getEntries we were able to reduce the build time by 4 minutes.



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)