MAVEN2: Same dependency - other version on classpath

[Kim Lauwers]

Hi everybody,

I have a maven2 question:

I have this pom file:

	<dependencies>
		<dependency>
			<groupId>org.mule</groupId>
			<artifactId>mule-core</artifactId>
			<version>1.4.4</version>
		</dependency>
		<dependency>
			<groupId>org.mule.modules</groupId>
			<artifactId>mule-module-client</artifactId>
			<version>1.4.4</version>
		</dependency>	
		<dependency>
			<groupId>org.mule</groupId>
			<artifactId>mule-core</artifactId>
			<version>2.1.2</version>
		</dependency>
		<dependency>
			<groupId>org.mule.modules</groupId>
			<artifactId>mule-module-client</artifactId>
			<version>2.1.2</version>
		</dependency>
	</dependencies>

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.

[Tim Holloway]

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.