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?
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!
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.
subject: MAVEN2: Same dependency - other version on classpath