RE: Test plugin
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 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 get: The plugin 'org.apache.maven.plugins:maven-test-plugin' does not exist or no valid version could be found In the repo I can only find a maven groupid with the maven-test-plugin. Is there really a org.apache.maven.plugins maven-test-plugin? I'm confused. Regards, John - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: Test plugin
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 get: The plugin 'org.apache.maven.plugins:maven-test-plugin' does not exist or no valid version could be found In the repo I can only find a maven groupid with the maven-test-plugin. Is there really a org.apache.maven.plugins maven-test-plugin? I'm confused. Regards, John - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: Test-plugin versus jcoverage-plugin?
Hi David, When running maven test, I get the expected results: === [junit] Tests run: 6, Failures: 0, Errors: 0, Time elapsed: 4.875 sec === But, when I try maven jcoverage, I get: == [junit] Tests run: 6, Failures: 0, Errors: 6, Time elapsed: 0.344 sec [junit] [ERROR] TEST myclass FAILED BUILD FAILED File.. C:\Documents and Settings\dhartford\.maven\cache\maven-test-plugin-1. 6.2\plugin.jelly Element... fail Line.. 181 Column 54 There were test failures. == I've tried maven clean inbetween each step, and the jcoverage instrumentation seems to be fine, it's only when it tries to run the junit tests WITH jcoverage that the unit tests error out (and quickly too). I am running JDK5.0, so I'm not sure if that may be a problem or not. I have had success with EMMA for code coverage as an alternative (and have correctly removed all references to EMMA when trying to debug the jCoverage problem, particularly since I tried jcoverage before testing EMMA). The silly reason I want jCoverage is for the ready-to-go dashboard support, and for my peers to compare EMMA versus jCoverage for a tool for code-coverage. Really weird problem, 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 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.. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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 that were failing, there were two reasons: security failures (for the test that require a security manager I needed to add some additional permissions to the policy file) and test code trying to find some files on the hard drive (because the tests when run by JCoverage are in a different location). At this point, all of our projects are working successfully with JCoverage. We're not using JDK1.5, however. ..David.. -Original Message- From: Jörg Schaible [mailto:[EMAIL 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, Failures: 0, Errors: 0, Time elapsed: 4.875 sec === But, when I try maven jcoverage, I get: == [junit] Tests run: 6, Failures: 0, Errors: 6, Time elapsed: 0.344 sec [junit] [ERROR] TEST myclass FAILED BUILD FAILED File.. C:\Documents and Settings\dhartford\.maven\cache\maven-test-plugin-1. 6.2\plugin.jelly Element... fail Line.. 181 Column 54 There were test failures. == I had the same issue once and it was caused by the fact that jcoverage writes a lot of log entries and my test expected some specific log output. - Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Test-plugin versus jcoverage-plugin?
Ah, silly me missing the most obvious place, thanks David. The test-reports did get generated, and here is the error it states (for all 6 error cases for my test): == (class: org/blah/MyClass, method: init signature: (Ljava/util/Properties;)V) Illegal constant pool index java.lang.VerifyError: (class: org/blah/MyClass, method: init signature: (Ljava/util/Properties;)V) Illegal constant pool index = MyClass that is being tested only takes a Properties object for a Constructor (no empty constructor), and I have that setup in my TestClass in class-scope so each test method can use it once setUp() initializes that object. But...never seen an Illegal constant pool index error before, and after going through about 15 minutes of google on it, still not sure. Again, using maven test all this is fine, but maven jcoverage is erroring out based on the above error. -D -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 that were failing, there were two reasons: security failures (for the test that require a security manager I needed to add some additional permissions to the policy file) and test code trying to find some files on the hard drive (because the tests when run by JCoverage are in a different location). At this point, all of our projects are working successfully with JCoverage. We're not using JDK1.5, however. ..David.. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Test-plugin versus jcoverage-plugin?
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 Message- From: Darren Hartford [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 26, 2005 12:36 PM To: Maven Users List Subject: Test-plugin versus jcoverage-plugin? Hey all, Rather weird and obtuse problem. Running Maven 1.0.2 with maven-test-plugin 1.6.2 and maven-jcoverage-plugin 1.0.9 on Sun jdk 5.0. When running 'maven test' for some unit tests that I have (and known to work), everything runs fine. Running the junit-report plugin returns nice information for the site. However, when I run 'maven jcoverage', all the tests fail, and I can't get code-coverage report. What is happening? -D - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Test Plugin : maven.junit.sysproperties
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 in JIRA. You may vote for it - maybe it gets
programmed for the next release
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-693
--
Martin Skopp
Riege Software International GmbH
Support: mailto:[EMAIL PROTECTED], Information: http://www.riege.com
This email is intended to be viewed with a nonproportional font.
Public Key on http://www.keyserver.net, Key-ID: 3D4027B5
Fingerprint: 1970 C78D 9A1D 99FA 5CE4 5C0D 29E6 6A95 3D40 27B5
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Test Plugin : maven.junit.sysproperties
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
wrote:
I'm trying the set two properties for my JUnit tests using
'maven.junit.sysproperties'
maven.junit.sysproperties=mtconfig_env mtconfig_dir
mtconfig_env=${mtconfig_env}
mtconfig_dir=${basedir}/../mt_config/
This cause a stack overflow because mt_config is self referencing.
What I really want to achieve is to initialise mtconfig_env with an
environment varaible from the OS.
How do Maven property files load environment variables from the OS?
Thanks
Pat
This email and any files transmitted with it are confidential and intended
solely for the use of the individual or entity to whom they are addressed.
If you have received this email in error please notify the system manager.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
mailto:[EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
