Just a wild guess, do you have a dependencyManagament handling these artifacts where the scope is defined? I've seen different behavior between Maven 2.x and 3.0.x due to this (MJBOSSPACK-40 [1]).
/Anders [1] http://jira.codehaus.org/browse/MJBOSSPACK-40 On Fri, Sep 16, 2011 at 22:43, WhiteMarlin <wes_mun...@cytoanalytics.com> wrote: > > Thorsten Heit wrote: >> >> ...snip ... >> >> But what puzzles me is that the archives created by Maven 2.2.1 and Maven >> 3.0.3 are different, and I don't see a reason why... >> >> ...snip... >> > > Hi there, > > Did you ever get anywhere with this? I'm seeing the same problem: Maven > 3.0.3 adds batik-js-1.7.jar and omits serializer-2.7.1.jar. > > Though I am not positive, I believe this is the cause of an exception I see > at runtime, the stack trace of which starts like this: > > java.lang.IllegalAccessError: > org/apache/xml/serializer/ExtendedContentHandler > at > org.apache.xalan.transformer.TransformerImpl.createSerializationHandler(TransformerImpl.java:1233) > ... > > Thanks! > > > -- > View this message in context: > http://maven.40175.n5.nabble.com/Incorrect-assembly-created-with-Maven-3-0-3-tp4393328p4811951.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
