surefire-users@maven.apache.org Archives

Help with classpath issue

2009-11-05T19:06:40Z

Hello,

I'm currently running Maven 2.2.1.  When I try to put a 
META-INF/hibernate.xml in the testResources directory (and therefore get 
copied over to the test-classes/META-INF dir) all the tests fail looking 
for a NamedQuery that is in one of my classes.  However, when I run 
without the META-INF (and a clean before hand) the tests find the 
NamedQuery in the classes directory just fine.  I've also found that if 
I copy over all the source classes into the test-classes directory with 
the META-INF/hibernate.xml the tests pass as well.  It *looks* like the 
target/classes directory is put in the classpath that surefire gets, but 
not sure if it's setting up correctly or not.

Please let me know if any more information is needed, or if this should 
be a thread in another project... just figured I'd start here ;)

Thanks,
Ben

Here's the surefire...tmp file that sets up the classPath:

#surefire
#Thu Nov 05 14:00:14 GMT-05:00 2009
enableAssertions=true
report.0.types=java.lang.Boolean
report.2.types=java.io.File|java.lang.Boolean
report.0.params=true
report.1.types=java.io.File|java.lang.Boolean
testSuite.0.params=/home/bdouglas/eclipse-ws/RegressionSystem/TestcaseManager/target/test-classes|[**/Test*.java,

**/*Test.java, **/*TestCase.java]|[**/*$*]
report.1.params=/home/bdouglas/eclipse-ws/RegressionSystem/TestcaseManager/target/surefire-reports|true
classPathUrl.39=/home/bdouglas/.m2/repository/org/jvnet/mimepull/1.2/mimepull-1.2.jar
classPathUrl.38=/home/bdouglas/.m2/repository/com/sun/org/apache/xml/internal/resolver/20050927/resolver-20050927.jar
classPathUrl.37=/home/bdouglas/.m2/repository/com/sun/xml/stream/sjsxp/1.0.1/sjsxp-1.0.1.jar
classPathUrl.36=/home/bdouglas/.m2/repository/org/jvnet/staxex/stax-ex/1.2/stax-ex-1.2.jar
classPathUrl.35=/home/bdouglas/.m2/repository/com/sun/xml/stream/buffer/streambuffer/0.7/streambuffer-0.7.jar
classPathUrl.34=/home/bdouglas/.m2/repository/com/sun/xml/messaging/saaj/saaj-impl/1.3.1/saaj-impl-1.3.1.jar
report.2.params=/home/bdouglas/eclipse-ws/RegressionSystem/TestcaseManager/target/surefire-reports|true
classPathUrl.33=/home/bdouglas/.m2/repository/com/sun/xml/bind/jaxb-impl/2.1.7/jaxb-impl-2.1.7.jar
classPathUrl.32=/home/bdouglas/.m2/repository/javax/jws/jsr181-api/1.0-MR1/jsr181-api-1.0-MR1.jar
surefireClassPathUrl.2=/home/bdouglas/.m2/repository/org/apache/maven/surefire/surefire-api/2.4.3/surefire-api-2.4.3.jar
classPathUrl.31=/home/bdouglas/.m2/repository/javax/annotation/jsr250-api/1.0/jsr250-api-1.0.jar
surefireClassPathUrl.1=/home/bdouglas/.m2/repository/junit/junit/4.0/junit-4.0.jar
classPathUrl.30=/home/bdouglas/.m2/repository/javax/xml/soap/saaj-api/1.3/saaj-api-1.3.jar
surefireClassPathUrl.0=/home/bdouglas/.m2/repository/org/apache/maven/surefire/surefire-junit4/2.4.3/surefire-junit4-2.4.3.jar
classPathUrl.9=/home/bdouglas/.m2/repository/dom4j/dom4j/1.6.1/dom4j-1.6.1.jar
classPathUrl.8=/home/bdouglas/.m2/repository/asm/asm-attrs/1.5.3/asm-attrs-1.5.3.jar
classPathUrl.7=/home/bdouglas/.m2/repository/commons-collections/commons-collections/2.1.1/commons-collections-2.1.1.jar
classPathUrl.6=/home/bdouglas/.m2/repository/commons-logging/commons-logging/1.0.4/commons-logging-1.0.4.jar
classPathUrl.5=/home/bdouglas/.m2/repository/net/sf/ehcache/ehcache/1.2.3/ehcache-1.2.3.jar
classPathUrl.4=/home/bdouglas/.m2/repository/org/hibernate/hibernate/3.2.6.ga/hibernate-3.2.6.ga.jar
classPathUrl.3=/home/bdouglas/.m2/repository/javax/persistence/persistence-api/1.0/persistence-api-1.0.jar
classPathUrl.2=/home/bdouglas/.m2/repository/junit/junit/4.5/junit-4.5.jar
classPathUrl.1=/home/bdouglas/eclipse-ws/RegressionSystem/TestcaseManager/target/classes
report.2=org.apache.maven.surefire.report.XMLReporter
classPathUrl.0=/home/bdouglas/eclipse-ws/RegressionSystem/TestcaseManager/target/test-classes
childDelegation=false
report.1=org.apache.maven.surefire.report.BriefFileReporter
report.0=org.apache.maven.surefire.report.ForkingConsoleReporter
classPathUrl.29=/home/bdouglas/.m2/repository/javax/activation/activation/1.1/activation-1.1.jar
classPathUrl.28=/home/bdouglas/.m2/repository/javax/xml/stream/stax-api/1.0/stax-api-1.0.jar
classPathUrl.27=/home/bdouglas/.m2/repository/javax/xml/bind/jaxb-api/2.1/jaxb-api-2.1.jar
classPathUrl.26=/home/bdouglas/.m2/repository/javax/xml/ws/jaxws-api/2.1/jaxws-api-2.1.jar
classPathUrl.25=/home/bdouglas/.m2/repository/com/sun/xml/ws/jaxws-rt/2.1.4/jaxws-rt-2.1.4.jar
classPathUrl.24=/home/bdouglas/.m2/repository/mysql/mysql-connector-java/5.1.10/mysql-connector-java-5.1.10.jar
classPathUrl.23=/home/bdouglas/.m2/repository/c3p0/c3p0/0.9.1.2/c3p0-0.9.1.2.jar
classPathUrl.22=/home/bdouglas/.m2/repository/log4j/log4j/1.2.12/log4j-1.2.12.jar
classPathUrl.21=/home/bdouglas/.m2/repository/org/slf4j/slf4j-log4j12/1.4.2/slf4j-log4j12-1.4.2.jar
classPathUrl.20=/home/bdouglas/.m2/repository/javassist/javassist/3.4.GA/javassist-3.4.GA.jar
failIfNoTests=false
useManifestOnlyJar=true
classPathUrl.19=/home/bdouglas/.m2/repository/javax/transaction/jta/1.1/jta-1.1.jar
classPathUrl.18=/home/bdouglas/.m2/repository/org/hibernate/hibernate-core/3.3.0.SP1/hibernate-core-3.3.0.SP1.jar
testSuite.0.types=java.io.File|java.util.ArrayList|java.util.ArrayList
classPathUrl.17=/home/bdouglas/.m2/repository/org/hibernate/hibernate-annotations/3.4.0.GA/hibernate-annotations-3.4.0.GA.jar
classPathUrl.16=/home/bdouglas/.m2/repository/org/slf4j/slf4j-api/1.4.2/slf4j-api-1.4.2.jar
classPathUrl.15=/home/bdouglas/.m2/repository/org/hibernate/hibernate-commons-annotations/3.1.0.GA/hibernate-commons-annotations-3.1.0.GA.jar
classPathUrl.14=/home/bdouglas/.m2/repository/org/hibernate/ejb3-persistence/1.0.2.GA/ejb3-persistence-1.0.2.GA.jar
classPathUrl.13=/home/bdouglas/.m2/repository/org/hibernate/hibernate-entitymanager/3.4.0.GA/hibernate-entitymanager-3.4.0.GA.jar
classPathUrl.12=/home/bdouglas/.m2/repository/asm/asm/1.5.3/asm-1.5.3.jar
classPathUrl.11=/home/bdouglas/.m2/repository/cglib/cglib/2.1_3/cglib-2.1_3.jar
classPathUrl.10=/home/bdouglas/.m2/repository/antlr/antlr/2.7.6/antlr-2.7.6.jar
testSuite.0=org.apache.maven.surefire.junit4.JUnit4DirectoryTestSuite
classPathUrl.40=/home/bdouglas/.m2/repository/log4j/apache-log4j-extras/1.0/apache-log4j-extras-1.0.jar
useSystemClassLoader=true

deploy rpm to rpm repository using maven + mojo rpm plugin

2009-11-05T16:59:41Z

Hi guys,

i'm just starting to play around with maven as a candidate for our whole
build/deploy system for java applications.

we're been programming so far using Perl,  packaging with Rpm on Fedora and
Deploying it though a local yum repository.


We still haven't decided if we could ditch the yum/rpm idea all together and
swith to mvn repository,
but in case we won't,

Do you know* i**f there is a way to config mvn to upload the rpm (using
SCP?) to the yum repository* after
it finished building the RPM (today we use a build system based on make
files and in the end it scp's the rpm to the repository and run make there
to update the list of rpms).

thank you.

-- 
Eyal Edri

Using apache ant inside a surefire test

2009-10-21T10:02:01Z

Hi there,

 

I didn't  find a solution or even suggestion online to the following
issue I'm having. I've developed a small ant-Task and build it with
maven2. The ant task is supposed to throw a BuildException under certain
circumstances. To test the task, I've created two junit tests, which
invoke ant's Launcher during their test methods. One invocation is
expected to pass, one is expected to fail and produce the
BuildException.

 

Within the test method, I've surrounded the invocation to the Launchers
run method with try and catch, the Exception still propagates to
surrounding surefire plugin and causes the maven2 build to fail.

 

What should I do, to prevent the surefire plugin from seeing the
BuildException thrown by the ant task?

 

Greetings,

  Thomas

generating centralized findbugs report

2009-09-15T07:51:13Z

Hi,

I have a project that has the following structure:

- pom.xml
- project_1
	- pom.xml (extends ../pom.xml)
- other
	- other1
		- pom.xml (extends ../pom.xml)
         - other
		- pom.xml (extends ../pom.xml)
	pom.xml (extends ../pom.xml)
- project_2
	pom.xml (extens ../pom.xml)


I would like that whenever I run "mvn site" to have a single,  
centralized findbugs report in the /site, rather than multiple  
individual ones in subprojects.
Is that possible?

Thank you,
Mircea

Yet another question about annotations in Junit Tests

2009-07-06T19:12:24Z

Hello:
  Sorry I am new to Maven and Surefire but I think my problem should be
posted to this group.  

I like many others am having a problem running Junit 4.4 test cases when
running maven.  I have not seen a definitive solution to the problem.

I can manually execute the following class and the test fails in the
setUp() method as expected.  When I run this with maven, the @before
method is never called.    I have seen a couple of different postings in
various places that indicate that indicate that is fixed with the code
changes for running TestNG.  I have also seen some postings that
indicate that this problem is not fixed and may never get fixed.

My question is should maven and surefire be able to run this class and
fail in the setUp() method as coded?  
Is there something I can change in my pom to make it run in surefire as
a 4.4 Junit?


Currently using Maven 2.1.0, surefire 2.4.3 
   
    
        org.apache.maven.plugins
        maven-surefire-plugin
        
            always
            true
            
            
              **/*Tests.java
            
            
        
      


package support;

import junit.framework.Assert;

import org.junit.After;
import org.junit.Before;
import org.junit.Test;
import org.junit.internal.runners.JUnit4ClassRunner;
import org.junit.runner.RunWith;



@RunWith(JUnit4ClassRunner.class)
public class FooTests {
  
   @Before
  public void setUp() throws Exception {
  Assert.fail("foo");
  }
  
   @After
  public void tearDown() throws Exception {
  }
  
  @Test
  public void testFoo() {
  }
  
  public static void main(String[] args) {
    org.junit.runner.JUnitCore.main("support.FooTests");
  }
}

Debugging Hints

2009-06-12T05:30:29Z

Greetings all,

Does anyone have any debugging hints for surefire? I've got a perplexing problem, not helped
by the fact that surefire doesn't appear to tell me the source of the problem.

I've got a working surefire/testng system working, and have gone to add tests for a second
class. This class is nearly identical to the first, except that it processes a different data
set. The trouble is that surefire won't even load the second set of tests. The first one still
works fine, but as soon as the second class is added, 'BUILD FAILURE', with no indication
of why. After running maven with '--debug', I still get nothing. The TestSuite.txt file is
empty, and the console output doesn't indicate what the problem might be. 

The last line of the below shell excerpt says "... 16 more"; it sure would be useful to know
how to obtain those last 16 errors. Does anyone know how?

Cheers,
    - Steve Nunez

-------------------------------------------------------
 T E S T S
-------------------------------------------------------
Running TestSuite
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] There are test failures.

Please refer to /Users/nunez/Illation/Development/Scratch/test-app/trunk/drools-4.0.7/target/surefire-reports
for the individual test results.
[INFO] ------------------------------------------------------------------------
[DEBUG] Trace
org.apache.maven.BuildFailureException: There are test failures.

Please refer to /Users/nunez/Illation/Development/Scratch/test-app/trunk/drools-4.0.7/target/surefire-reports
for the individual test results.
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:699)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:540)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:519)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:356)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.MojoFailureException: There are test failures.

Please refer to /Users/nunez/Illation/Development/Scratch/test-app/trunk/drools-4.0.7/target/surefire-reports
for the individual test results.
at org.apache.maven.plugin.surefire.SurefirePlugin.execute(SurefirePlugin.java:575)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678)
... 16 more
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 7 seconds
[INFO] Finished at: Fri Jun 12 15:23:11 EST 2009
[INFO] Final Memory: 9M/23M
[INFO] ------------------------------------------------------------------------

Why isn't Surefire more easier and more sensible to use?

2009-05-19T01:22:04Z

Ive recently started using Surefire as part of a Maven project.

I was really surprised how inconvenient it was to use, and how things
about it seemed, well... stupid.

1. When running a suite of tests with "surefire:test
",
the main thing you want to see a summary of all failed tests. It is THE
most important and normal thing to look at. I was surprised to discover
Surefire doesnt produce this essential item by default. Instead, it
creates many individual reports, one per test, whether they passed or
failed.

2. Then, one has to run a second plugin and special goal just to get the
summary, which is what any normal person is going to be looking for. It
puts the summary in a different directory from the individual files. And
it doesnt produce this report as part of the normal build.

3. It generates the XML intermediate files that the report needs. It
also generates identical txt files, for no apparent reason. And
bizarrely, you can turn the XML off, but you cant turn the txt off.

And then you get weird situations where because the tests fail, the
build fails, and this actually stops the report generation which will
tell you what test failed :(
http://jira.codehaus.org/browse/SUREFIRE-507?page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel
http://www.eclipse.org/newsportal/article.php?id=216&group=eclipse.technology.iam#216

The whole thing seems like a classic case of programmer-centric, not
user-centric, thinking. This tool doesn't seem to have started with what
a typical user would want and then worked backwards to meet this goal.

I dont particularly enjoy criticizing some programmer's unpaid
contribution, but Surefire is a widely used piece of infrastructure, and
it should work better than it does.

-Ben

*Ben Hutchison
Senior Developer
* Level 2 476 St Kilda Road Melbourne VIC 3004
T 613 8807 5252 | F 613 8807 5203 | M 0423 879 534 |
www.ibsglobalweb.com

Unknown source for assertion in surefire driven JUnit test with Tellurium

2009-05-08T10:54:56Z

Hi,

I've started looking at the Tellurium web testing framework. I'm using
their template with Maven, Surefire and JUnit to drive the tests. It's
very easy to test it, just follow this guide.
http://code.google.com/p/aost/wiki/TenMinutesToTellurium

What happens is that when I have an assertion failure the JVM (?)
doesn't provide the source file and line number! See stacktrace (1)
This leads to a number of issues, i.e. you can't build reports. See
stacktrace (2)

I can't see that anything Tellurium-specific goes on here and neither
can the Tellurium maintainer.
Does anyone have a clue what might be causing this?

Using surefire 2.4.3.

Regards
/Ernst Persson

(1)
more target/surefire-reports/test.SomethingTestCase.txt
-------------------------------------------------------------------------------
Test set: test.SomethingTestCase
-------------------------------------------------------------------------------
Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 18.251
sec <<< FAILURE!
testDuplicateName(test.SomethingTestCase)  Time elapsed: 2.231 sec  <<< FAILURE!
java.lang.AssertionError: expected not same
	at org.junit.Assert.fail(Assert.java:74)
	at org.junit.Assert.failSame(Assert.java:437)
	at org.junit.Assert.assertNotSame(Assert.java:420)
	at org.junit.Assert.assertNotSame(Assert.java:430)
>>>> at test.SomethingTestCase.testDuplicateName(Unknown Source)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at org.junit.internal.runners.TestMethod.invoke(TestMethod.java:59)
	at org.junit.internal.runners.MethodRoadie.runTestMethod(MethodRoadie.java:98)
	at org.junit.internal.runners.MethodRoadie$2.run(MethodRoadie.java:79)
	at org.junit.internal.runners.MethodRoadie.runBeforesThenTestThenAfters(MethodRoadie.java:87)
	at org.junit.internal.runners.MethodRoadie.runTest(MethodRoadie.java:77)
	at org.junit.internal.runners.MethodRoadie.run(MethodRoadie.java:42)
	at org.junit.internal.runners.JUnit4ClassRunner.invokeTestMethod(JUnit4ClassRunner.java:88)
	at org.junit.internal.runners.JUnit4ClassRunner.runMethods(JUnit4ClassRunner.java:51)
	at org.junit.internal.runners.JUnit4ClassRunner$1.run(JUnit4ClassRunner.java:44)
	at org.junit.internal.runners.ClassRoadie.runUnprotected(ClassRoadie.java:27)
	at org.junit.internal.runners.ClassRoadie.runProtected(ClassRoadie.java:37)
	at org.junit.internal.runners.JUnit4ClassRunner.run(JUnit4ClassRunner.java:42)
	at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62)
	at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140)
	at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:127)
	at org.apache.maven.surefire.Surefire.run(Surefire.java:177)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:345)
	at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1009)

(2)
[ERROR] FATAL ERROR
[INFO] ------------------------------------------------------------------------
[INFO] String index out of range: -1
[INFO] ------------------------------------------------------------------------
[INFO] Trace
java.lang.StringIndexOutOfBoundsException: String index out of range: -1
	at java.lang.String.substring(String.java:1938)
	at org.apache.maven.plugins.surefire.report.SurefireReportGenerator.getErrorLineNumber(SurefireReportGenerator.java:638)
	at org.apache.maven.plugins.surefire.report.SurefireReportGenerator.constructFailureDetails(SurefireReportGenerator.java:600)
	at org.apache.maven.plugins.surefire.report.SurefireReportGenerator.doGenerateReport(SurefireReportGenerator.java:111)
	at org.apache.maven.plugins.surefire.report.SurefireReportMojo.executeReport(SurefireReportMojo.java:180)
	at org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:98)
	at org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:139)
	at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:269)
	at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:101)
	at org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:133)
	at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:100)
	at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483)
	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678)
	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:540)
	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:519)
	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371)
	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332)
	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)
	at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)
	at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)
	at org.apache.maven.cli.MavenCli.main(MavenCli.java:356)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
	at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
	at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
	at org.codehaus.classworlds.Launcher.main(Launcher.java:375)

PS I hope I'm not upsetting anyone by crossposting this, I really have
no idea where the problem is.

forking single tests from junit test suite

2009-03-23T14:01:59Z

Hi,

I need to test a feature for my project on large test input files.
To get that, I create TestCases from a single TestSuite dynamically. The
relevant part of the pom looks like:


> 			
> 				org.apache.maven.plugins
> 				maven-surefire-plugin
> 				
> 					plain
> 					false
> 					perTest
> 					-XX:+HeapDumpOnOutOfMemoryError
> 					
> 						**/IncrementalParsePhase1Test.java
> 						**/incremental/testparser/*.java
> 					
> 					
> 						**/IncrementalParsingTestSuite.java
> 					
> 				
> 			

In my TestSuite there runs a loop:


> for (int i = 0; i < Lexer.getCachedInput().size(); i++) {
> 				//brake for large test cases
> 				if (i % (1 + (Lexer.getCachedInput().size() / 20)) != 0)
> 					continue;
> 
> 				Range diffRange = new Range(i, i);
> 
> 				IncrementalParsePhase1Test test = new IncrementalParsePhase1Test(
> 						Lexer.getInputFileName(), Lexer.getCachedInput(),
> 						generatedStates, diffRange, rootAbsy, Lexer.getCachedInput().get(i).getSavedConfiguration());
> 				suite.addTest(test);
> 			}

The problem is, that maven does not seem to run every testCase in a new
vm, but reuses the old one (and somehow prevents the GC from cleaning
up old testcases), so earlier or later I run into a heap overflow.

This is especially bad, as I want to measure the performance of some operations and the GC
seems to interrupt my threads thus creating huge performance problems.

So is it possible to make surefire run each test in a single vm?

regards

Christoph

Junit target code dependencies are unresolved

2009-02-16T15:27:09Z

I've written a junit test case against a class that has dependencies (log4j
for instance). I've declared those dependencies in my pom.xml. I've declared
junit 3.8.1 as a test scoped dependency.

When I run mvn test I get errors on each test indicating that junit is not
resolving the references to the dependencies in the target code.  From the
surefire-reports--

   
Hello!
 
I've read the JIRA found here:
http://jira.codehaus.org/browse/SUREFIRE-257
and tried to incorporate its advice into my POM.
 
Currently, when I run "mvn clean install site", I get the following:

	

	C:\workspace\shares-trunk\shares-domain>mvn clean install site
	 
	C:\workspace\shares-trunk\shares-domain>set MAVEN_OPTS=-Xmx256m
	[INFO] Scanning for projects...
	[INFO]
------------------------------------------------------------------------
	[INFO] Building shares-domain
	[INFO]    task-segment: [clean, install, site]
	[INFO]
------------------------------------------------------------------------
	[INFO] [clean:clean]
	[INFO] Deleting directory
C:\workspace\shares-trunk\shares-domain\target
	[INFO] [resources:resources]
	[INFO] Using default encoding to copy filtered resources.
	[INFO] [compiler:compile]
	[INFO] Compiling 101 source files to
C:\workspace\shares-trunk\shares-domain\target\classes
	[INFO] [resources:testResources]
	[INFO] Using default encoding to copy filtered resources.
	[INFO] [compiler:testCompile]
	[INFO] Compiling 35 source files to
C:\workspace\shares-trunk\shares-domain\target\test-classes
	[INFO] [surefire:test]
	[INFO] Surefire report directory:
C:\workspace\shares-trunk\shares-domain\target\surefire-reports
	 
	-------------------------------------------------------
	 T E S T S
	-------------------------------------------------------
	
	......
	 
	Results :
	 
	Tests run: 54, Failures: 0, Errors: 0, Skipped: 0
	 
	[INFO] [jar:jar]
	[INFO] Building jar:
C:\workspace\shares-trunk\shares-domain\target\shares-domain-1.0-SNAPSHO
T.jar
	[INFO] [install:install]
	[INFO] Installing
C:\workspace\shares-trunk\shares-domain\target\shares-domain-1.0-SNAPSHO
T.jar to \.m2\repository\com\fideli
	
ty\shares\shares-domain\1.0-SNAPSHOT\shares-domain-1.0-SNAPSHOT.jar
	[INFO] Setting property: classpath.resource.loader.class =>
'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'.
	[INFO] Setting property: velocimacro.messages.on => 'false'.
	[INFO] Setting property: resource.loader => 'classpath'.
	[INFO] Setting property: resource.manager.logwhenfound =>
'false'.
	[INFO]
**************************************************************
	[INFO] Starting Jakarta Velocity v1.4
	[INFO] RuntimeInstance initializing.
	[INFO] Default Properties File:
org\apache\velocity\runtime\defaults\velocity.properties
	[INFO] Default ResourceManager initializing. (class
org.apache.velocity.runtime.resource.ResourceManagerImpl)
	[INFO] Resource Loader Instantiated:
org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader
	[INFO] ClasspathResourceLoader : initialization starting.
	[INFO] ClasspathResourceLoader : initialization complete.
	[INFO] ResourceCache : initialized. (class
org.apache.velocity.runtime.resource.ResourceCacheImpl)
	[INFO] Default ResourceManager initialization complete.
	[INFO] Loaded System Directive:
org.apache.velocity.runtime.directive.Literal
	[INFO] Loaded System Directive:
org.apache.velocity.runtime.directive.Macro
	[INFO] Loaded System Directive:
org.apache.velocity.runtime.directive.Parse
	[INFO] Loaded System Directive:
org.apache.velocity.runtime.directive.Include
	[INFO] Loaded System Directive:
org.apache.velocity.runtime.directive.Foreach
	[INFO] Created: 20 parsers.
	[INFO] Velocimacro : initialization starting.
	[INFO] Velocimacro : adding VMs from VM library template :
VM_global_library.vm
	[ERROR] ResourceManager : unable to find resource
'VM_global_library.vm' in any resource loader.
	[INFO] Velocimacro : error using  VM library template
VM_global_library.vm : org.apache.velocity.exception.ResourceNotFoundEx
	ception: Unable to find resource 'VM_global_library.vm'
	[INFO] Velocimacro :  VM library template macro registration
complete.
	[INFO] Velocimacro : allowInline = true : VMs can be defined
inline in templates
	[INFO] Velocimacro : allowInlineToOverride = false : VMs defined
inline may NOT replace previous VM definitions
	[INFO] Velocimacro : allowInlineLocal = false : VMs defined
inline will be  global in scope if allowed.
	[INFO] Velocimacro : initialization complete.
	[INFO] Velocity successfully started.
	[INFO] Preparing surefire-report:report
	[INFO] [resources:resources]
	[INFO] Using default encoding to copy filtered resources.
	[INFO] [compiler:compile]
	[INFO] Nothing to compile - all classes are up to date
	[INFO] [resources:testResources]
	[INFO] Using default encoding to copy filtered resources.
	[INFO] [compiler:testCompile]
	[INFO] Nothing to compile - all classes are up to date
	[INFO] [surefire:test]
	[INFO] Surefire report directory:
C:\workspace\shares-trunk\shares-domain\target\surefire-reports
	 
	-------------------------------------------------------
	 T E S T S
	-------------------------------------------------------
	
	 
	......
	 
	Results :
	 
	Tests run: 54, Failures: 0, Errors: 0, Skipped: 0
	 
	[INFO] Preparing surefire-report:report-only
	[INFO] No goals needed for project - skipping
	[INFO] [site:site]
	[WARNING] No URL defined for the project - decoration links will
not be resolved
	[INFO] Skipped "Surefire Report" report, file
"surefire-report.html" already exists for the English version.
	[INFO] Generating "Source Xref" report.
	[WARNING] Unable to locate Javadoc to link to - DISABLED
	[INFO] Generating "Test Source Xref" report.
	[INFO] Generating "Plugin Management" report.
	[INFO] Generating "Mailing Lists" report.
	[INFO] Generating "Continuous Integration" report.
	[INFO] Generating "Dependency Management" report.
	Downloading:
http://cfesstbos1:18080/nexus/content/groups/public/joda-time/joda-time-
jsptags/1.0.2/joda-time-jsptags-1.0.2.po
 
	m
	[INFO] Generating "Project License" report.
	[INFO] Generating "Project Team" report.
	[INFO] Generating "Source Repository" report.
	[INFO] Generating "About" report.
	[INFO] Generating "Issue Tracking" report.
	[INFO] Generating "Project Summary" report.
	[INFO] Generating "Project Plugins" report.
	[INFO] Generating "Dependencies" report.
	[INFO] Generating "Surefire Report" report.
	[INFO]
------------------------------------------------------------------------
	[INFO] BUILD SUCCESSFUL
	[INFO]
------------------------------------------------------------------------
	[INFO] Total time: 30 seconds
	[INFO] Finished at: Mon Jan 05 11:01:09 EST 2009
	[INFO] Final Memory: 35M/74M
	[INFO]
------------------------------------------------------------------------
	 
	C:\workspace\shares-trunk\shares-domain>

As you can see, my tests are executed twice, once as part of the
"install" goal and a second time under the "site" goal.  My POM has the
following declaration:

	
	    org.apache.maven.plugins
	    maven-surefire-report-plugin
	    2.4.3
	    
	     once
	     
	      ${project.reporting.outputDirectory}/../xref-test
	          
	     
	      
	       
	        report-only
	       
	      
	     
	     
	      
	       env.props.path
	       c:/environment.properties
	      
	     
	     
	      -Denv.props.path=c:/environment.properties
	     
	        
	   

No other surefire configuration is specified.  Given the conversation
occuring in SUREFIRE-257, I would assume that my tests would only be
executed once.  Should this be the case or is it expected that the tests
are run for each goal?
 
Thanks!
Leo

How to specify a specialized Juni TestRunner in surefire?

2008-11-10T21:37:48Z

Hi,
   Is there a way in surefire to specify a specialized JUnit TestRunner 
class?
   If yes, how?

   Regards --

Pinaki Poddar
Application & Integration Middleware

Running both Junit4 and TestNG test cases in single Maven project

2008-10-31T10:43:19Z

In my project I need to have both both Junit4 and TestNG test cases and
build using Maven2.

However I found that when I run 'mvn test' goll, Junit4 test cases are
ignored by Maven surfire plugin and only TestNG test cases are run. However
when I use JUnit3 and TestNG test cases together, both the test cases are
picked correctly. Can anyone propose a solution?

I have append my POM file for your reference.

Thanks in advance.

- Nalaka

    
        
            junit
            junit
            4.3.1
            test
        
        
            org.testng
            testng
            5.8
            test
            jdk15
        
    
    
        
            
                org.apache.maven.plugins
                maven-compiler-plugin
                2.0.2
                
                    1.5
                    1.5

Surefire XML output

2007-12-18T18:00:01Z



This may be a shot out there.

But i am having trouble with the XML output on the surefire report.

It does not print out the classname on the testcases, and I need it so i can
generate meaningful output from it.

I noticed XMLReport seems to look for a "group" if its filled in; however,
ours is not filled in. Also it doesnt seem like the test suites actually
write to it anyway. They do seem to put the classname in message.

So is there 

a) Anyweay to get the XML to output the classname for the testcases
b) Anyway to tell surefire to use a different reporter?


-- 
View this message in context: http://www.nabble.com/Surefire-XML-output-tp14402138p14402138.html
Sent from the Surefire - Users mailing list archive at Nabble.com.

Re: releasing 2.4

2007-10-30T07:33:49Z

Hi.

The best working version is 2.4-collab-SNAPSHOT. There is nothing
better yet. I'm working on it (not so often as I'd like to).

When there will be some valuable progress, I'll post on this ML.

2007/10/29, srinivas ramgopal :
>
> Hi
>
>
> So I guess that the patch contributed by Marat R. is usable. If so, what is
> the version of the fixed sure fire.
>
> If not, please let us know as when a workable version of surefire would be
> avialable...hopefully in two months, as 2007 end is already around the
> corner ! :)
>
>
> Thanks in advance for your valuable the time and interest.
>
>
>
>
> Brett Porter wrote:
> >
> > On 04/09/07, Marat Radchenko  wrote:
> >> I've seen that (and actually we are currently using
> >> 2.4-collab-SNAPSHOT version of surefire).
> >>
> >> What branch should I work with? trunk or collab?
> >
> > Patch against trunk. Collab is dead - but it has some fixes that need
> > to be ported to trunk (after removing the use of internal APIs)
> >
> >>
> >> Does anyone work on TestNG support? As far as I see Jesse Kuhnert did
> >> a bunch of work on it.
> >>
> >
> > I don't think he'll be doing any further work on it. Alex did do some
> > work on his branch - but that should be consistent with trunk at the
> > moment.
> >
> > Cheers,
> > Brett
> >
> > --
> > Brett Porter
> > Blog: http://www.devzuz.org/blogs/bporter/
> >
> >
>
> --
> View this message in context: http://www.nabble.com/releasing-2.4-tf4376174.html#a13473480
> Sent from the Surefire - Users mailing list archive at Nabble.com.
>
>

Re: releasing 2.4

2007-10-29T18:08:51Z


Hi


So I guess that the patch contributed by Marat R. is usable. If so, what is
the version of the fixed sure fire.

If not, please let us know as when a workable version of surefire would be
avialable...hopefully in two months, as 2007 end is already around the
corner ! :)


Thanks in advance for your valuable the time and interest.




Brett Porter wrote:
> 
> On 04/09/07, Marat Radchenko  wrote:
>> I've seen that (and actually we are currently using
>> 2.4-collab-SNAPSHOT version of surefire).
>>
>> What branch should I work with? trunk or collab?
> 
> Patch against trunk. Collab is dead - but it has some fixes that need
> to be ported to trunk (after removing the use of internal APIs)
> 
>>
>> Does anyone work on TestNG support? As far as I see Jesse Kuhnert did
>> a bunch of work on it.
>>
> 
> I don't think he'll be doing any further work on it. Alex did do some
> work on his branch - but that should be consistent with trunk at the
> moment.
> 
> Cheers,
> Brett
> 
> -- 
> Brett Porter
> Blog: http://www.devzuz.org/blogs/bporter/
> 
> 

-- 
View this message in context: http://www.nabble.com/releasing-2.4-tf4376174.html#a13473480
Sent from the Surefire - Users mailing list archive at Nabble.com.

Re: releasing 2.4

2007-09-04T09:06:28Z

On 04/09/07, Marat Radchenko  wrote:
> I've seen that (and actually we are currently using
> 2.4-collab-SNAPSHOT version of surefire).
>
> What branch should I work with? trunk or collab?

Patch against trunk. Collab is dead - but it has some fixes that need
to be ported to trunk (after removing the use of internal APIs)

>
> Does anyone work on TestNG support? As far as I see Jesse Kuhnert did
> a bunch of work on it.
>

I don't think he'll be doing any further work on it. Alex did do some
work on his branch - but that should be consistent with trunk at the
moment.

Cheers,
Brett

-- 
Brett Porter
Blog: http://www.devzuz.org/blogs/bporter/

Re: releasing 2.4

2007-09-04T09:03:02Z

OK then, let's get down to business :)

> Great - there's a bit of back story - we have 2 branches at present.
> http://docs.codehaus.org/display/MAVEN/Surefire+TestNG+refactoring

I've seen that (and actually we are currently using
2.4-collab-SNAPSHOT version of surefire).

What branch should I work with? trunk or collab?

Does anyone work on TestNG support? As far as I see Jesse Kuhnert did
a bunch of work on it.

Re: releasing 2.4

2007-09-04T08:37:22Z

On 04/09/2007, at 6:32 PM, Marat Radchenko wrote:

> Hi, Brett.
>
>> 2007
> That sounds promising :)
>
>> Welcome!
> Does this mean you'd like me to join? If yes then could you explain
> the process of working on surefire (maybe this should be moved to
> surefire-dev)?

Just the normal contribution process - if you find an issue you can  
take care of drop a comment to say you are working on it, ask  
questions if you are unsure, and submit patches. If you submit enough  
patches to show you know what you are doing on your own, someone will  
give you commit access.

We can certainly continue any discussion on surefire-dev.

>
>> We currently have a small number of issues to get done for 2.3.1 (see
>> JIRA). This is intended to be the stable release for some time.
> I've seen issues fo 2.3.1 however it doesn't cover many people needs.

Yep, it's just the current "plan", but if you prefer to work on 2.4  
things specifically that's fine of course.

>
>> 2.4 will focus on getting high test coverage across surefire itself
>> and stabilising TestNG + JUnit 4 support.
> That's what I am interested in

Great - there's a bit of back story - we have 2 branches at present.  
http://docs.codehaus.org/display/MAVEN/Surefire+TestNG+refactoring

Good luck :)

Cheers,
Brett

--
Brett Porter - brett@apache.org
Blog: http://www.devzuz.org/blogs/bporter/

Re: releasing 2.4

2007-09-04T08:32:36Z

Hi, Brett.

> 2007
That sounds promising :)

> Welcome!
Does this mean you'd like me to join? If yes then could you explain
the process of working on surefire (maybe this should be moved to
surefire-dev)?

> We currently have a small number of issues to get done for 2.3.1 (see
> JIRA). This is intended to be the stable release for some time.
I've seen issues fo 2.3.1 however it doesn't cover many people needs.

> 2.4 will focus on getting high test coverage across surefire itself
> and stabilising TestNG + JUnit 4 support.
That's what I am interested in

--
Marat Radchenko

Re: releasing 2.4

2007-09-04T08:16:53Z

On 04/09/2007, at 6:02 PM, Marat Radchenko wrote:

> Hi everyone!
>
> I've got two questions about surefire 2.4 release.
>
> First, could you tell me expected date/week/month/year when it will  
> be released?

2007

>
> Second, what are the reasons that surefire development process is so
> slow? Maybe you do not have enough developers? If so then I could join
> you in order to speed it up.

Welcome!

We currently have a small number of issues to get done for 2.3.1 (see  
JIRA). This is intended to be the stable release for some time.

2.4 will focus on getting high test coverage across surefire itself  
and stabilising TestNG + JUnit 4 support.

>
> I'm asking because my team (any many other teams I suppose) want to
> use Maven with testng and currently surefire has lots of troubles with
> it.

Cheers,
Brett

--
Brett Porter - brett@apache.org
Blog: http://www.devzuz.org/blogs/bporter/

releasing 2.4

2007-09-04T08:02:30Z

Hi everyone!

I've got two questions about surefire 2.4 release.

First, could you tell me expected date/week/month/year when it will be released?

Second, what are the reasons that surefire development process is so
slow? Maybe you do not have enough developers? If so then I could join
you in order to speed it up.

I'm asking because my team (any many other teams I suppose) want to
use Maven with testng and currently surefire has lots of troubles with
it.

Waiting for reply,
Marat Radchenko

maven surefire plugin issue

2007-08-15T03:16:29Z


Hi all,

I am using TestNg, Maven with surefire plugin (version as 2.4-collab).

I am getting java.lang.OutOfMemoryError: Java heap space on only certain
tests in Windows enviornment.
(This error does not occur in unix evniornment).

I set the following in maven.bat but in vain:

set MAVEN_OPTS=-XX:PermSize=256m -Xms512m -Xmx1024m

I do not want to disable the surefire reports in case the xml reports are to
long.

Your valuable input to resolve this issue is highly appreciated.

Thanks in advance.


-- 
View this message in context: http://www.nabble.com/maven-surefire-plugin-issue-tf4270489.html#a12154750
Sent from the Surefire - Users mailing list archive at Nabble.com.

Which version for testng 5.5?

2007-05-14T17:12:45Z

Hello,

I saw that surefire-testng 2.3 depends on testng 5.1, I tried testng 5.5
and it fails.
Which version of surefire will be compatible with 5.5?

Thanks,

Gael

Re: IsolatedClassLoader -> URL with spaces %20 problem

2007-02-20T02:02:07Z

Almost forgot...not that this is too interesting, but the test case below
calls a method getJarURLFromURLEntry( ) -- this method is from
org.hibernate.ejb.packaging.JarVisitor.java, and it looks like this:

public static final URL getJarURLFromURLEntry(URL url, String entry) throws
IllegalArgumentException {
    URL jarUrl;
    String file = url.getFile();
    if ( ! entry.startsWith( "/" ) ) entry = "/" + entry;
    file = file.substring( 0, file.length() - entry.length() );
    if ( file.endsWith( "!" ) ) file = file.substring( 0, file.length() - 1
);
    try {
        String protocol = url.getProtocol();

        if ( "jar".equals( protocol )
                || "wsjar".equals( protocol ) ) { //Websphere has it's own
way
            jarUrl = new URL( file );
        }
        else if ( "zip".equals( protocol ) ) { //Weblogic has it's own way
            //we have extracted the zip file, so it should be read as a file
            jarUrl = new URL( "file", null, file );
        }
        else if ("code-source".equals( url.getProtocol() ) ) {
            //OC4J prevent ejb.jar access (ie everything without path
            //fix contributed by the community
            jarUrl = new File(file).toURL();
        }
        else {
            jarUrl = new URL( protocol, url.getHost(), url.getPort(), file
);
        }
    }
    catch (MalformedURLException e) {
        throw new IllegalArgumentException(
                "Unable to determine JAR Url from " + url + ". Cause: " +
e.getMessage()
        );
    }
    return jarUrl;
}

On 2/19/07, Davis Ford  wrote:
>
> He, we're using maven 2.0.4 (although I just tried 2.0.5 and the same
> problem exists), and we're using Hibernate Entity Manager 3.2.1-ga, and
> we're on a Windows Platform.  These 3 things don't seem to work together.
>
> The problem is the default repo for maven jars contains spaces on windows
> C:\Documents and Settings\etc.
>
> Hibernate Entity Manager expects to find META-INF\persistence.xml on the
> classpath.  The general idea is to bury this in a jar that is loaded as a
> dependency on our maven repo classpath, right?
>
> Hibernate has code similar to this in
> org.hibernate.ejb.EjbConfiguration.java (I added logger and assertions):
>
> try {
>         Enumeration xmls = Thread.currentThread()
>         .getContextClassLoader()
>         .getResources( "META-INF/persistence.xml" );
>
>         if ( ! xmls.hasMoreElements() ) {
>         fail( "Could not find any META-INF/persistence.xml file in the
> classpath");
>         }
>         while ( xmls.hasMoreElements() ) {
>         URL url = xmls.nextElement();
>         LOGGER.debug( "Analyse of persistence.xml: " + url );
>         URL jarURL = getJarURLFromURLEntry( url,
> "/META-INF/persistence.xml" );
>         assertFalse("Jar URL should not contain spaces, "+jarURL,
> jarURL.toString().contains(" "));
>         }
>
> 1. Create a jar-file, install it in local maven repo.
> 2. Add META-INF\persistence.xml to the jar file
> 3. Add a dependency to a new maven test project
> 4. Paste in code like above -- test case will always fail when it tests
> for whitespace in the url.
>
> System.out.println(Thread.currentThread().getContextClassLoader().getClass().getCanonicalName());
>
>
> prints
>
> org.apache.maven.surefire.booter.IsolatedClassLoader
>
> If I run from Eclipse, I have no problems, and the above println prints
> instead:
>
> sun.misc.Launcher.AppClassLoader
>
> I am *desperate* for any kind of solution to this problem that does not
> require me to change the local maven repo to a url without spaces.
>
> I need the URLClassLoader (IsolatedClassLoader) to correctly deal with
> whitespace and replace it with %20.  If there is some other workaround --
> please let me know.  Hibernate ends up throwing an exception and returning
> null for the EntityManager which is an absolute show-stopper for us.
>
> Thank you in advance,
>
> Davis
>
>
>
>
>


-- 
Zeno Consulting, Inc.
http://www.zenoconsulting.biz
248.894.4922 phone
313.884.2977 fax

IsolatedClassLoader -> URL with spaces %20 problem

2007-02-20T01:41:47Z

He, we're using maven 2.0.4 (although I just tried 2.0.5 and the same
problem exists), and we're using Hibernate Entity Manager 3.2.1-ga, and
we're on a Windows Platform.  These 3 things don't seem to work together.

The problem is the default repo for maven jars contains spaces on windows
C:\Documents and Settings\etc.

Hibernate Entity Manager expects to find META-INF\persistence.xml on the
classpath.  The general idea is to bury this in a jar that is loaded as a
dependency on our maven repo classpath, right?

Hibernate has code similar to this in
org.hibernate.ejb.EjbConfiguration.java (I added logger and assertions):

try {
        Enumeration xmls = Thread.currentThread()
        .getContextClassLoader()
        .getResources( "META-INF/persistence.xml" );

        if ( ! xmls.hasMoreElements() ) {
        fail( "Could not find any META-INF/persistence.xml file in the
classpath");
        }
        while ( xmls.hasMoreElements() ) {
        URL url = xmls.nextElement();
        LOGGER.debug( "Analyse of persistence.xml: " + url );
        URL jarURL = getJarURLFromURLEntry( url, "/META-INF/persistence.xml"
);
        assertFalse("Jar URL should not contain spaces, "+jarURL,
jarURL.toString().contains(" "));
        }

1. Create a jar-file, install it in local maven repo.
2. Add META-INF\persistence.xml to the jar file
3. Add a dependency to a new maven test project
4. Paste in code like above -- test case will always fail when it tests for
whitespace in the url.

System.out.println(Thread.currentThread
().getContextClassLoader().getClass().getCanonicalName());

prints

org.apache.maven.surefire.booter.IsolatedClassLoader

If I run from Eclipse, I have no problems, and the above println prints
instead:

sun.misc.Launcher.AppClassLoader

I am *desperate* for any kind of solution to this problem that does not
require me to change the local maven repo to a url without spaces.

I need the URLClassLoader (IsolatedClassLoader) to correctly deal with
whitespace and replace it with %20.  If there is some other workaround --
please let me know.  Hibernate ends up throwing an exception and returning
null for the EntityManager which is an absolute show-stopper for us.

Thank you in advance,

Davis

Re: Surefire to run a custom testsuite

2006-08-29T14:38:06Z

I found the solution

http://jira.codehaus.org/browse/MSUREFIRE-113

On 8/22/06, Pablo Gutierrez  wrote:
>
> Hi all,
>
> I'm setting up maven for a project and I just get to the point where
> everything compiles.
>
> I'm having troubles running the test lifecycle phase because for our unit
> tests we use a
> customized testsuite, so when we run our unit tests with the standard text
> runner from junit, we
> pass the argument of the classs of out test suite.
>
> I wouldn't like to skip the test life cycle and running the unit tests on
> a separate process.
>
> Is there a way of specifying the class of the testsuite to the surefire
> plugin?
>
> Thanks,
> Pablo
>

Surefire to run a custom testsuite

2006-08-22T17:12:45Z

Hi all,

I'm setting up maven for a project and I just get to the point where
everything compiles.

I'm having troubles running the test lifecycle phase because for our unit
tests we use a
customized testsuite, so when we run our unit tests with the standard text
runner from junit, we
pass the argument of the classs of out test suite.

I wouldn't like to skip the test life cycle and running the unit tests on a
separate process.

Is there a way of specifying the class of the testsuite to the surefire
plugin?

Thanks,
Pablo