Hi,
I'm using gwt, and Google folks had the strange idea to include some old
version of apache commons-* in the jar.
I get NoSuchMethodError in unit tests becausse I can't specify the classpath
ordering of my dependencies during tests.
Is there any surefire Hack I could use to EXCLUDE
I'm using gwt, and Google folks had the strange idea to include some old
version of apache commons-* in the jar.
I get NoSuchMethodError in unit tests becausse I can't specify the classpath
ordering of my dependencies during tests.
Even if you could hack Surefire to include the newer Commons
Defining what version of the jar to use in the depedencyManagement
section doesn't work here?
---
Todd Thiessen
-Original Message-
From: Wayne Fay [mailto:wayne...@gmail.com]
Sent: Wednesday, March 11, 2009 12:26 PM
To: Maven Users List
Subject: Re: classpath ordering
I'm
ordering
I'm using gwt, and Google folks had the strange idea to
include some
old version of apache commons-* in the jar.
I get NoSuchMethodError in unit tests becausse I can't specify the
classpath ordering of my dependencies during tests.
Even if you could hack Surefire to include
The issue is that gwt-dev INCLUDES org.apache.commons.* classes, it does not
depend on some commons-* as maven projet may expect (Gwt guys don't use
Maven)
I still think you should file a bug against GWT itself and ask them to
shade these classes if they're going to package them in their
