Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Duplicate
-
Affects Version/s: 2.0.7
-
Fix Version/s: 2.0.9
-
Component/s: Dependencies
-
Labels:None
-
Number of attachments :
Description
I have two sun jars defined as system dependencies ...
<!-- AMSDK System Dependencies -->
<dependency>
<groupId>sun.amsdk</groupId>
<artifactId>amclientsdk</artifactId>
<version>2005q4</version>
<scope>system</scope>
<systemPath>${pom.basedir}/amsdk/1amclientsdk.jar</systemPath>
</dependency>
<dependency>
<groupId>sun.amsdk</groupId>
<artifactId>amservices</artifactId>
<version>2005q4</version>
<scope>system</scope>
<systemPath>${pom.basedir}/amsdk/am_services.jar</systemPath>
</dependency>
<dependency>
<groupId>sun.amsdk</groupId>
<artifactId>amconfig</artifactId>
<version>2005q4</version>
<scope>system</scope>
<systemPath>${pom.basedir}/amsdk</systemPath>
</dependency>
<!-- / AMSDK System Dependencies -->
The reason for the last on is that the sun stuff demands a file called 'AMConfig.properties' file which is actually in the ${pom.basedir}/amsdk dir.
It is absolutely crucial that 1amclientsdk.jar is in the classpath before am_services.jar as they define identical classes but the 1amclientsdk.jar versions are the ones I need (the 1 prefix is an attempt to force it to load early).
9 times out of 10, the 1amclientsdk.jar is not before the am_services.jar. I have confirmed this using the -X option.
Issue Links
| This issue relates to: | ||||
| MNG-1412 | dependency sorting in classpath |
|
|
|
| MANTTASKS-22 | artifact:dependencies does not respect in the generated classpath the order of the dependencies |
|
|
|
| MNG-3494 | local pom dependencies should get injected before inherited dependencies |
|
|
|
duplicate of
MNG-1412BTW, fixed in 2.0.9-SNAPSHOT...
MNG-1412BTW, fixed in 2.0.9-SNAPSHOT...