] S:\pdv_cms\GDCAMS\src\pip\gdcams-pip-itest\target\classes
[DEBUG] S:\pdv_cms\GDCAMS\src\pip\gdcams-pip-itest\target\test-classes
As you can see, the classes and test-classes are at the end of the test
classpath, which now causes some problems.
The only thing I changed was the following
SurefirePlugin#constructSurefireBooter changes the classpath by doing:
...
getLog().debug( Test Classpath : );
// Check if we need to add configured classes/test classes
directories here.
// If they are configured, we should remove the default to avoid
conflicts
[EMAIL PROTECTED] wrote:
Hi,
if I´m running JUnit Tests with Surefire-2.4 I got the following
Use latest surefire plugin.
- Jörg
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
problem is still remaining in surefire-2.4.3, see my last posting.
- torsten
Jörg Schaible [EMAIL PROTECTED]
17.07.2008 11:47
Bitte antworten an
Maven Users List users@maven.apache.org
An
Maven Users List users@maven.apache.org
Kopie
Thema
RE: own classes and test-classes at the end
Try searching for spring hibernate ehcache
I admit, I have a whole bunch of old messages in Gmail and I searched there.
I'm not sure if the Nabble search in the maven2 section works just like
Gmail's.
The interesting messages have the word dependency or some form of that
word in them.
-- Lee
nope:
$ grep -io 'ehcache[^ ]\+' maven.log
ehcache:ehcache:1.2
ehcache:ehcache:1.2.
ehcache:ehcache:jar:1.2:compile
ehcache\ehcache\1.2\ehcache-1.2.jar,
ehcache\ehcache\1.2\ehcache-1.2.jar
ehcache:ehcache:1.2
ehcache:ehcache:1.2.
ehcache:ehcache:jar:1.2:compile
Well I have some progress -- the tests are finally failing in eclipse so i
can do some debugging.
Also, i changed the hibernate config to use the cache provider provided with
the ehcache jar -- but the tests are still bombing out because it claims it
cannot find the one in the hibernate jar :/
Check your Manifest.MF files and web.xml and other configuration files to make
sure there's not a reference to the wrong version somewhere. (Don't just use
the files in target; you'll need to crack open the packaged JAR/WAR/EAR and all
its JAR contents and look at all the config files and
Thanks all; I do appreciate the help. The root cause was (of all things) a
space after the class name in hibernate.properties :-/
Now I am back to why this was so hard to diagnose -- the tests, when run
from maven (on the command line), is not picking up changes to that file --
but when the
I don't know why the changed file wasn't detected.
Start running mvn clean {your phase here} ie mvn clean package or mvn
clean test rather than mvn test directly and Maven will delete
target/* before running, which should take care of these kinds of
problems.
Wayne
On 11/15/06, Trevor Torrez
I wiped it out and rechecked it out from source control; seems to be working
fine.
Thanks again.
On 11/15/06, Wayne Fay [EMAIL PROTECTED] wrote:
I don't know why the changed file wasn't detected.
Start running mvn clean {your phase here} ie mvn clean package or mvn
clean test rather than mvn
Hi; I am trying to convert our framework over to maven, and am running into
a bit of a snag. When trying run the tests, I get a class not found for
org.hibernate.cache.EhCacheProvider; but when running from eclipse (using
the eclipse maven plugin to setup the libraries) everything works fine.
I
This has been discussed before. You can find it in nabble, I think.
The issue has to do with spring wanting one version of hibernate and
hibernate wanting a version of ehcache and the versions conflict with each
other. In my case, using Quartz which wanted another version of ehcache, it
would
Ok; that almost makes sense; what, other than 'Quartz' should I search
nabble for? I cant find anything relevent.
Answers to any of the following questions would also be appreciated:
How do i find out which of the dependencies is requesting the bogus
version? The only thing 'maven site' shows
Run mvn -X and then grep the output for ehcache... You'll probably see
a different version getting pulled in by another dependency
somewhere...
Wayne
On 11/14/06, Trevor Torrez [EMAIL PROTECTED] wrote:
Ok; that almost makes sense; what, other than 'Quartz' should I search
nabble for? I cant
that's the correct behaviour - tests should not be part of the
release. You should move these test classes to project C which is used
by both.
On Fri, 25 Jun 2004 17:39:06 -0400, Sonnathi, Venkat
[EMAIL PROTECTED] wrote:
Hi,
I have two projects Project A, Project B. Project B depends
16 matches
Mail list logo