Sorry for the late response. First core was not compiling with m2. I tried now and had to change the scope of spring-mock to make classes compile.
Second, if you run mvn -X you can see how transitive dependencies are obtained, and there's no reference at all to log4j. Are you talking about any other application that uses other stuff besides acegi? If so you can run mvn -X, check who is using log4j and add a exclusion to that dependency. Also note that apacheds dependecies in pom.xml are not the snaphots as they are not available in ibiblio. I added this ones in the meantime. i imagine tests don't fail because that classes are not tested at all (http://www.acegisecurity.org/multiproject/acegi-security/clover/index.html). The fact that order of dependencies worked in m1 was a coincidence and was not intended at all, and thus that behaviour can change. Regards On 1/30/06, Luke Taylor <[EMAIL PROTECTED]> wrote: > Hi Carlos, > > Maven 1 seems to set up the classpath in the order the dependencies are > specified, hence we got round the problem by moving slf4j/nlog4j above > log4j in the list. I think nlog4j provides replacement classes for > log4j, which aren't directly compatible. > > The problem is discussed here: > > http://www.nabble.com/Re:-upgrading-to-nlog4j.1.2.17-p1089156.html > > If we can exclude log4j, that might do the trick. How is that achieved? > I think it's appearing as a transitive dependency from somewhere else... > > Thanks, > > Luke. > > Carlos Sanchez wrote: > > Hi, > > > > There's no option to specify the order, in m1 that wasn't a feature > > either. I don't know exactly what's the problem but there're ways to > > exclude log4j or force a specific version, is that what you're trying > > to do? > > > > On 1/29/06, Luke Taylor <[EMAIL PROTECTED]> wrote: > >> Hi Carlos, > >> > >> I have a small problem you might know the answer to. I was attempting to > >> add the latest apache-ds jar files to the M2 build. Apache DS is build > >> using slf4j and this can cause a very nasty IncompatibleClassChangeError > >> at logger-related code if log4j is used instead. With Maven 1, we got > >> round this by putting slf4j ahead of log4j in the project.xml. > >> > >> However, if I do this with Maven 2.0.2, log4j always seems to end up > >> ahead of slf4j, even if I put the latter at the top of the dependency list. > >> > >> Do you know if there's a way to exert more control over the order of > >> jars in the classpath with Maven 2, or how it decides the ordering? > >> > >> cheers, > >> > >> Luke. > >> > > -- > Luke Taylor. Monkey Machine Ltd. > PGP Key ID: 0x57E9523C http://www.monkeymachine.ltd.uk > > ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642 _______________________________________________ Home: http://acegisecurity.org Acegisecurity-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/acegisecurity-developer
