[MSHARED-361] DefaultProjectDependencyAnalyzer.buildArtifactClassMap assumes dependencies are jar files (regression)

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: maven-dependency-analyzer-1.5
• Fix Version/s: maven-dependency-analyzer-1.6
• Component/s: maven-dependency-analyzer
• Environment: Mac OS 10.9, Maven 3.0.5, Oracle JDK 1.7.0_51; Windows 7, Maven 3.0.4, IBM JDK 1.6.0
• Assignee: Anders Hammar
• Reporter: Anders Hammar
• Created: 02/Oct/14 07:27
• Updated: 29/Oct/14 11:36
• Resolved: 29/Oct/14 11:36

Description

MSHARED-307 caused an regression seen with maven-dependency-plugin, see MDEP-466.

In DefaultProjectDependencyAnalyzer.buildArtifactClassMap, each dependency artifact is analyzed as a jar file which will fail when it is a directory structure (not a jar).

Issue Links

• is depended upon by: MDEP-466 analyze fails on multimodule project (regression)
• relates to: MSHARED-307 Performance: The implementation of DefaultClassAnalyzer unnecessarily scans jar files bodies