Hi,
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
Hi,
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]).
No, I haven't used dependency management. I simply referenced xerces
and/or xalan (don't
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,
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
finally got ClassNotFoundException because of a missing dependency Jar in
the lib folder; more precisely xalan:serializer:2.7.1
PS: I tested it with Maven 3.0.3 using Java 1.6.0_24, first on Solaris 11
Express and then on Mac OS X 10.6.7.
finally got ClassNotFoundException because of a missing dependency Jar in
the lib folder; more precisely xalan:serializer:2.7.1
PS: I tested it with Maven 3.0.3 using Java 1.6.0_24, first on Solaris 11
Express and then on Mac OS X 10.6.7.
Xalan and Xerces are special since they have been
