• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Liutauras Vilda
  • Paul Clapham
Sheriffs:
  • paul wheaton
  • Tim Cooke
  • Henry Wong
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Piet Souris
Bartenders:
  • Mike London

MAVEN2: Same dependency - other version on classpath

 
Ranch Hand
Posts: 31
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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.
 
Saloon Keeper
Posts: 26546
187
Android Eclipse IDE Tomcat Server Redhat Java Linux
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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.
 
reply
    Bookmark Topic Watch Topic
  • New Topic