Unfortunately no change at all. Junit4 still won't be used for compilation in the first run
//this fails mvn clean test //all of these work mvn clean compile mvn compile test mvn clean compile mvn compiler:testCompile mvn clean compile mvn test cheers, severin -----Ursprüngliche Nachricht----- Von: Jörg Schaible [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 28. März 2007 17:12 An: Maven Users List Betreff: RE: Dependency version ignored Try to add a depednencyManagement section to your POM where you define the proper version *and* declare the dep additionally in your list of dependencies. Ecker Severin wrote on Wednesday, March 28, 2007 5:09 PM: > Hi, > > I've tried to use exclusions on every dependency I had, no > success. I've run my build with -X which told me that > basically dozens of indirectly included dependencies (mostly > axis and the like) use junit 3.8.1. > > I doubt that bloating my pom file with all possible > dependencies on the build path trying to set exclusions is > the way to go. And I wouldn't like to be forced to go back to > junit 3.8 just because of this dependency issues. > > Does somebody have any further suggestions? > > Thanks and cheers, > Severin > > Ps.: are there any dates yet for maven 2.0.6? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
