Hi Dave,
could you give some detail on what the exact error is and on how you actually
call 'test:single'?
Maven takes care of your test classpath, so to my knowledge you don't need to
set 'maven.test.classpath' if you have everything you need declared as a
dependency. At least I never had
Even your second mail is not specific enough to help us help you in any
meaningful
way. You might profit from reading this:
http://catb.org/~esr/faqs/smart-questions.html
As a first guess I'd like to know if jwebunit-htmlunit-plugin is the only
jwebunit
dependency you added in your pom? If
You are great and I will remember you when I'm rich and famous. When I
switched the dependency to jwebunit-core from jwebunit-htmlunit-plugin
the compilation errors went away and my unit test ran.
As a bonus, do you know where the output of the tests gets saved to? All
I'm told is that my unit
Cool, I'll remind you of that when you're rich and famous! :)
The test output goes to target/test-reports/.
-Lukas
laredotornado wrote:
You are great and I will remember you when I'm rich and famous. When I
switched the dependency to jwebunit-core from jwebunit-htmlunit-plugin
the
Hi Dave,
could you give some detail on what the exact error is and on how you actually
call 'test:single'?
Maven takes care of your test classpath, so to my knowledge you don't need to
set 'maven.test.classpath' if you have everything you need declared as a
dependency. At least I never had
Yes, I should have been more specific. Here's how I'm making the call ...
maven -Dtestcase=test.AddToMailingListTest test:single
and what happens is that I'm getting a bunch of compilation errors, even
though the libraries in question are listed as a dependency in my
project.xml file (I have
Maven 1.1 is very old, and a completely different architecture than maven
2.0. You may not get many answers
2009/10/2 laredotornado laredotorn...@gmail.com
Hi,
I'm using Maven 1.1 with maven-test-plugin-1.8.2.jar. When I run the
test:single target with my test class, I get a bunch of
Sadly, I don't have control over what version of Maven is used at this
company. Take your best shot, - Dave
Stephen Connolly-2 wrote:
Maven 1.1 is very old, and a completely different architecture than maven
2.0. You may not get many answers
2009/10/2 laredotornado
