aspose file tools*
The moose likes Ant, Maven and Other Build Tools and the fly likes MAVEN2: Same dependency - other version on classpath Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Engineering » Ant, Maven and Other Build Tools
Bookmark "MAVEN2: Same dependency - other version on classpath" Watch "MAVEN2: Same dependency - other version on classpath" New topic
Author

MAVEN2: Same dependency - other version on classpath

Kim Lauwers
Ranch Hand

Joined: Sep 23, 2005
Posts: 31
Hi everybody,

I have a maven2 question:

I have this pom file:


Now I want to have mule version 1.4.4 AND mule version 2.1.2 on my classpath. But because of the fact that the groupid and artifactid are the same. Maven only puts the the first one on my classpath.
Can this be fixed?

Thanks,
Greetings Kim.


Programming today is a race between Software Engineers striving to build bigger and better idiot-proof Programs, and the Universe trying to produce bigger and better idiots.<br />So far, the Universe is winning!
Tim Holloway
Saloon Keeper

Joined: Jun 25, 2001
Posts: 16305
    
  21

It wouldn't matter if Maven could or not. The Java runtime won't stand for it. One and only one version of a class in a given classpath. No mix-and-match. Mostly because when you mix, they won't match, but also because it's part of the Java security model.


Customer surveys are for companies who didn't pay proper attention to begin with.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: MAVEN2: Same dependency - other version on classpath