Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Incomplete
-
1.4.1
-
None
-
None
-
Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T17:41:47+01:00)
Maven home: C:\Program Files\apache-maven-3.3.9
Java version: 1.8.0_102, vendor: Oracle Corporation
Java home: C:\Develop\jdk1.8.0_102\jre
Default locale: de_DE, platform encoding: Cp1252
OS name: "windows 7", version: "6.1", arch: "amd64", family: "dos"Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T17:41:47+01:00) Maven home: C:\Program Files\apache-maven-3.3.9 Java version: 1.8.0_102, vendor: Oracle Corporation Java home: C:\Develop\jdk1.8.0_102\jre Default locale: de_DE, platform encoding: Cp1252 OS name: "windows 7", version: "6.1", arch: "amd64", family: "dos"
Description
I noticed that DependencyConvergence can take up to 10 seconds or even more in modules with almost 300 direct and transitive dependencies (reported by dependency:tree).
These modules are part of a JEE project based on JBoss EAP 6.4 which imports a couple of EAP BOMs. Unfortunately I am not allowed to share this project.
I profiled the rule via VisualVM and these are the top 5 hotspots:
The number of parseVersion calls seems excessive.
See attached visualvm_settings.xml for reference.