Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.0.9, 2.1.0-M1
-
Fix Version/s: 2.0.10
-
Component/s: Artifacts and Repositories, Dependencies
-
Labels:None
-
Complexity:Intermediate
-
Patch Submitted:Yes
-
Number of attachments :
Description
One part of Maven where class path ordering hasn't already been fixed in the past is the extension class path. Apart from a proposed patch, two logs from our IT testmng3599useHttpProxyForWebDAV are attached. Both were run against Maven 2.0.10-RC1, with the only difference being one using JDK 1.4 and the other one 1.6. Not only do these logs substantially differ, the build on JDK 1.6 even fails due to picking up the wrong extension classes.
A (currently disabled) IT is online.