RE: Test plugin

2008-12-19 Thread John Coleman
Thanks Justin, it turns out I was looking at Maven 1 docs. I can run the test I want with test:single. John -Original Message- From: Edelson, Justin [mailto:justin.edel...@mtvstaff.com] Sent: 18 December 2008 14:07 To: Maven Users List Subject: RE: Test plugin This error

RE: Test plugin

2008-12-18 Thread Edelson, Justin
This error is accurate. There's no maven-test-plugin. test is a lifecycle phase, not a plugin. From: John Coleman [mailto:john.cole...@eurobase.com] Sent: Thu 12/18/2008 4:54 AM To: Maven Users List Subject: Test plugin When I try to run a test plugin goal I

RE: Test-plugin versus jcoverage-plugin?

2005-04-27 Thread Darren Hartford
, hopefully it is just because I'm trying to do this on JDK5? -D -Original Message- From: David Jackman [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 26, 2005 4:37 PM To: Maven Users List Subject: RE: Test-plugin versus jcoverage-plugin? I am even now getting jcoverage to work with our

RE: Test-plugin versus jcoverage-plugin?

2005-04-27 Thread David Jackman
PROTECTED] Sent: Wednesday, April 27, 2005 7:34 AM To: Maven Users List Subject: RE: Test-plugin versus jcoverage-plugin? Hi Darren, Darren Hartford wrote on Wednesday, April 27, 2005 3:31 PM: Hi David, When running maven test, I get the expected results: === [junit] Tests run: 6

RE: Test-plugin versus jcoverage-plugin?

2005-04-27 Thread Darren Hartford
-Original Message- From: David Jackman [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 27, 2005 10:20 AM To: Maven Users List Subject: RE: Test-plugin versus jcoverage-plugin? This wasn't the information I was asking for. What do the test reports say? For the tests I had

RE: Test-plugin versus jcoverage-plugin?

2005-04-26 Thread David Jackman
I am even now getting jcoverage to work with our many projects, and have run into this sort of issue a few times. So far, I've been able to get things to work, but it seems it's complaning about something different every time. What sorts of errors are you getting? ..David.. -Original

Re: Test Plugin : maven.junit.sysproperties

2003-08-29 Thread Martin Skopp
On Fri, 2003-08-29 at 12:05, Bateman, Patrick eMEDIA wrote: mtconfig_env=${mtconfig_env} mtconfig_dir=${basedir}/../mt_config/ This cause a stack overflow because mt_config is self referencing. self referencing properties do not work yet. A enhancement request is already file as MAVEN-693

Re: Test Plugin : maven.junit.sysproperties

2003-08-29 Thread Jefferson K. French
Something like this should work: property environment=env/ property name=mtconfig_env value=${env.mtconfig_env}/ assuming mtconfig_env is what it's called in the OS. If not, change the value after 'env.' accordingly. On Fri, 29 Aug 2003, at 11:05:23 [GMT +0100] Bateman, Patrick eMEDIA