[jira] Created: (MAVENUPLOAD-1334) JUnit-Toolkit version 0.4
JUnit-Toolkit version 0.4 - Key: MAVENUPLOAD-1334 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1334 Project: maven-upload-requests Issue Type: Task Reporter: Rupert Smith Attachments: junit-toolkit-0.4-bundle.jar http://www.thebadgerset.co.uk/junit-toolkit/junit-toolkit-0.3-bundle.jar http://www.thebadgerset.co.uk/junit-toolkit/ http://www.thebadgerset.co.uk/junit-toolkit/team-list.html JUnit Toolkit enhances JUnit with performance testing, asymptotic behaviour analysis, and concurrency testing. Version 0.4 adds a new test runner with more features and fixes all memory leaks that would prevent its use in longer running tests. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-1335) Please upload OpenOffice.org Java/Uno JARs 2.1.0
Please upload OpenOffice.org Java/Uno JARs 2.1.0 Key: MAVENUPLOAD-1335 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1335 Project: maven-upload-requests Issue Type: Task Reporter: Mirko Nasato OpenOffice.org includes some JARs that can be used in a standalone Java app to connect to a running OpenOffice.org instance. The OpenOffice.org team agreed to distributing those JARs through Maven 2 and assigned the task to myself http://www.openoffice.org/issues/show_bug.cgi?id=71358 Please find the bundles here http://jooreports.sourceforge.net/m2/openoffice.org-juh-2.1.0-bundle.jar http://jooreports.sourceforge.net/m2/openoffice.org-jurt-2.1.0-bundle.jar http://jooreports.sourceforge.net/m2/openoffice.org-ridl-2.1.0-bundle.jar http://jooreports.sourceforge.net/m2/openoffice.org-unoil-2.1.0-bundle.jar -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-1336) SoftEU URL Rewriter
SoftEU URL Rewriter --- Key: MAVENUPLOAD-1336 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1336 Project: maven-upload-requests Issue Type: Task Reporter: Petr Ferschmann URL Rewriter is a tool for rewriting URLs in Java Servlets. It is similar to apache mod_rewrite. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-1336) SoftEU URL Rewriter
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_85575 ] Petr Ferschmann commented on MAVENUPLOAD-1336: -- The package is cz.softeu instead of com.softeu. Just try the URL http://software.softeu.cz/rewriter/ and it redirects to com. > SoftEU URL Rewriter > --- > > Key: MAVENUPLOAD-1336 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1336 > Project: maven-upload-requests > Issue Type: Task >Reporter: Petr Ferschmann > > URL Rewriter is a tool for rewriting URLs in Java Servlets. It is similar to > apache mod_rewrite. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MPIR-60) Current head throws NPE when generating reports
[ http://jira.codehaus.org/browse/MPIR-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MPIR-60. --- Assignee: Vincent Siveton Resolution: Fixed Fixed for maven trunk and 2.0.x branch > Current head throws NPE when generating reports > --- > > Key: MPIR-60 > URL: http://jira.codehaus.org/browse/MPIR-60 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Bug >Reporter: Henning Schmiedehausen > Assigned To: Vincent Siveton > Fix For: 2.1 > > > The current head of this plugin does not generate the reports but throws NPEs: > java.lang.NullPointerException > at > org.codehaus.plexus.i18n.DefaultI18N.getBundle(DefaultI18N.java:141) > at > org.codehaus.plexus.i18n.DefaultI18N.getString(DefaultI18N.java:206) > at > org.apache.maven.report.projectinfo.LicenseReport.getName(LicenseReport.java:75) > at > org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:122) > at > org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:260) > at > org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:116) > at > org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:127) > at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:95) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:418) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:327) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:120) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:269) > 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) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-1335) Please upload OpenOffice.org Java/Uno JARs 2.1.0
[
http://jira.codehaus.org/browse/MAVENUPLOAD-1335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_85579
]
Dan Tran commented on MAVENUPLOAD-1335:
---
I happened to glance thru the request, here are my comments.
The dependencies use version = ${project.version}. You need change to the the
official version 2.1
why ?
org.openoffice
openoffice.org-jurt
is it better if
org.openoffice
jurt
since we need both groupId and artifactId to identify the jar. may be we dont
need to repeat
the groupId in the artifactId.
> Please upload OpenOffice.org Java/Uno JARs 2.1.0
>
>
> Key: MAVENUPLOAD-1335
> URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1335
> Project: maven-upload-requests
> Issue Type: Task
>Reporter: Mirko Nasato
>
> OpenOffice.org includes some JARs that can be used in a standalone Java app
> to connect to a running OpenOffice.org instance.
> The OpenOffice.org team agreed to distributing those JARs through Maven 2 and
> assigned the task to myself
> http://www.openoffice.org/issues/show_bug.cgi?id=71358
> Please find the bundles here
> http://jooreports.sourceforge.net/m2/openoffice.org-juh-2.1.0-bundle.jar
> http://jooreports.sourceforge.net/m2/openoffice.org-jurt-2.1.0-bundle.jar
> http://jooreports.sourceforge.net/m2/openoffice.org-ridl-2.1.0-bundle.jar
> http://jooreports.sourceforge.net/m2/openoffice.org-unoil-2.1.0-bundle.jar
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-1335) Please upload OpenOffice.org Java/Uno JARs 2.1.0
[
http://jira.codehaus.org/browse/MAVENUPLOAD-1335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_85580
]
Mirko Nasato commented on MAVENUPLOAD-1335:
---
I used ${project.version} to ensure that dependencies are in sync with the
current jar version; other projects use the same practice e.g. spring-web
http://mirrors.ibiblio.org/pub/mirrors/maven2/org/springframework/spring-web/2.0.2/spring-web-2.0.2.pom
Incidentally I used "2.1.0" as the version and not simply "2.1" because that's
the more accurate scheme used by installation packages and in the code.
As for using "openoffice.org" in the artifactId, I agree that it is an arguable
choice. However, "juh" "jurt" "ridl" and "unoil" alone are very
non-descriptive names. Imagine looking in the WEB-INF/lib of a webapp that
includes tens of different JARs, as is frequently the case: it would be very
difficult to tell what "juh" is and what "ridl" is, and even that they are at
all related. If you see "openoffice.org-juh" and "openoffice.org-ridl" at
least you immediately know they are for OpenOffice.org. It's similar to using
"commons-*" or "spring-*".
> Please upload OpenOffice.org Java/Uno JARs 2.1.0
>
>
> Key: MAVENUPLOAD-1335
> URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1335
> Project: maven-upload-requests
> Issue Type: Task
>Reporter: Mirko Nasato
>
> OpenOffice.org includes some JARs that can be used in a standalone Java app
> to connect to a running OpenOffice.org instance.
> The OpenOffice.org team agreed to distributing those JARs through Maven 2 and
> assigned the task to myself
> http://www.openoffice.org/issues/show_bug.cgi?id=71358
> Please find the bundles here
> http://jooreports.sourceforge.net/m2/openoffice.org-juh-2.1.0-bundle.jar
> http://jooreports.sourceforge.net/m2/openoffice.org-jurt-2.1.0-bundle.jar
> http://jooreports.sourceforge.net/m2/openoffice.org-ridl-2.1.0-bundle.jar
> http://jooreports.sourceforge.net/m2/openoffice.org-unoil-2.1.0-bundle.jar
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-1335) Please upload OpenOffice.org Java/Uno JARs 2.1.0
[
http://jira.codehaus.org/browse/MAVENUPLOAD-1335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_85581
]
Dan Tran commented on MAVENUPLOAD-1335:
---
my bad using ${project.version} woks
how about the name, how about openoffice-juh,? lots of projects use this
convention like you have mentioned.
> Please upload OpenOffice.org Java/Uno JARs 2.1.0
>
>
> Key: MAVENUPLOAD-1335
> URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1335
> Project: maven-upload-requests
> Issue Type: Task
>Reporter: Mirko Nasato
>
> OpenOffice.org includes some JARs that can be used in a standalone Java app
> to connect to a running OpenOffice.org instance.
> The OpenOffice.org team agreed to distributing those JARs through Maven 2 and
> assigned the task to myself
> http://www.openoffice.org/issues/show_bug.cgi?id=71358
> Please find the bundles here
> http://jooreports.sourceforge.net/m2/openoffice.org-juh-2.1.0-bundle.jar
> http://jooreports.sourceforge.net/m2/openoffice.org-jurt-2.1.0-bundle.jar
> http://jooreports.sourceforge.net/m2/openoffice.org-ridl-2.1.0-bundle.jar
> http://jooreports.sourceforge.net/m2/openoffice.org-unoil-2.1.0-bundle.jar
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-1335) Please upload OpenOffice.org Java/Uno JARs 2.1.0
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_85583 ] Mirko Nasato commented on MAVENUPLOAD-1335: --- Quoting from http://www.openoffice.org/about_us/summary.html Because of trademark issues, OpenOffice.org must insist that all public communications refer to the project and software as "OpenOffice.org" or "OpenOffice.org 1.x," and not "OpenOffice" or "Open Office." That's why all Linux packages are also named "openoffice.org-*". If the dot is a problem then "openofficeorg-juh", or maybe just "uno-juh" (although less descriptive)? > Please upload OpenOffice.org Java/Uno JARs 2.1.0 > > > Key: MAVENUPLOAD-1335 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1335 > Project: maven-upload-requests > Issue Type: Task >Reporter: Mirko Nasato > > OpenOffice.org includes some JARs that can be used in a standalone Java app > to connect to a running OpenOffice.org instance. > The OpenOffice.org team agreed to distributing those JARs through Maven 2 and > assigned the task to myself > http://www.openoffice.org/issues/show_bug.cgi?id=71358 > Please find the bundles here > http://jooreports.sourceforge.net/m2/openoffice.org-juh-2.1.0-bundle.jar > http://jooreports.sourceforge.net/m2/openoffice.org-jurt-2.1.0-bundle.jar > http://jooreports.sourceforge.net/m2/openoffice.org-ridl-2.1.0-bundle.jar > http://jooreports.sourceforge.net/m2/openoffice.org-unoil-2.1.0-bundle.jar -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-1335) Please upload OpenOffice.org Java/Uno JARs 2.1.0
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_85586 ] Dan Tran commented on MAVENUPLOAD-1335: --- ah, it is clear now ;-) > Please upload OpenOffice.org Java/Uno JARs 2.1.0 > > > Key: MAVENUPLOAD-1335 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1335 > Project: maven-upload-requests > Issue Type: Task >Reporter: Mirko Nasato > > OpenOffice.org includes some JARs that can be used in a standalone Java app > to connect to a running OpenOffice.org instance. > The OpenOffice.org team agreed to distributing those JARs through Maven 2 and > assigned the task to myself > http://www.openoffice.org/issues/show_bug.cgi?id=71358 > Please find the bundles here > http://jooreports.sourceforge.net/m2/openoffice.org-juh-2.1.0-bundle.jar > http://jooreports.sourceforge.net/m2/openoffice.org-jurt-2.1.0-bundle.jar > http://jooreports.sourceforge.net/m2/openoffice.org-ridl-2.1.0-bundle.jar > http://jooreports.sourceforge.net/m2/openoffice.org-unoil-2.1.0-bundle.jar -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MCLOVER-64) Support "statementContext"
Support "statementContext" -- Key: MCLOVER-64 URL: http://jira.codehaus.org/browse/MCLOVER-64 Project: Maven 2.x Clover Plugin Issue Type: New Feature Affects Versions: 2.3 Environment: maven 2.0.4 Reporter: David DIDIER Clover plugin already supports "contextFilters" but not "statementContext", allowing the user to define new filters. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (SUREFIRE-62) surefire xml report not wellformed on junit returning int
[ http://jira.codehaus.org/browse/SUREFIRE-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter moved MSUREFIRE-125 to SUREFIRE-62: Affects Version/s: (was: 2.1.2) 1.5.2 (2.1.2 plugin) Fix Version/s: (was: 2.2) 2.0 (2.2 plugin) Complexity: Intermediate Key: SUREFIRE-62 (was: MSUREFIRE-125) Project: Maven Surefire (was: Maven 2.x Surefire Plugin) > surefire xml report not wellformed on junit returning int > - > > Key: SUREFIRE-62 > URL: http://jira.codehaus.org/browse/SUREFIRE-62 > Project: Maven Surefire > Issue Type: Bug >Affects Versions: 1.5.2 (2.1.2 plugin) > Environment: Windows XP Pro, Java 1.5.0_06 >Reporter: Andreas Schödl > Fix For: 2.0 (2.2 plugin) > > Attachments: de.sag.dms.junit.SurefireXmlTest.txt, > SurefireXmlTest.java, TEST-de.sag.dms.junit.SurefireXmlTest.xml > > > Surefire XML reports are not well-formed, they contain unescaped "<" and ">" > characters when JUnit reports a failed assertEquals(1,2) with int. > Putting attached SurefireXmlTest into your tests directory brings XML-results > like the attached. > excerpt: > junit.framework.AssertionFailedError: expected:<1> but > was:<2> > As you see, the element content is properly escaped, but not the content of > attribute "message". -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (SUREFIRE-63) Disabling xml report generation
[ http://jira.codehaus.org/browse/SUREFIRE-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter moved MSUREFIRE-106 to SUREFIRE-63: Affects Version/s: (was: 1.5.3 (2.1.3 plugin)) 1.5.3 (2.1.3 plugin) Fix Version/s: (was: 2.0 (2.2 plugin)) 2.0 (2.2 plugin) Key: SUREFIRE-63 (was: MSUREFIRE-106) Project: Maven Surefire (was: Maven 2.x Surefire Plugin) > Disabling xml report generation > --- > > Key: SUREFIRE-63 > URL: http://jira.codehaus.org/browse/SUREFIRE-63 > Project: Maven Surefire > Issue Type: Improvement >Affects Versions: 1.5.3 (2.1.3 plugin) >Reporter: Vinod Panicker > Assigned To: Brett Porter > Fix For: 2.0 (2.2 plugin) > > > Currently the surefire plugin generates xml reports if report generation is > enabled. There is no way to turn it off completely. Since xml report > generation takes a lot of time, this severely impacts total build time. > It would be great to have an option to turn of xml report generation. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-1310) NanoXML Lite
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_85593 ] Tassilo Schweyer commented on MAVENUPLOAD-1310: --- fixed that license problem > NanoXML Lite > > > Key: MAVENUPLOAD-1310 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1310 > Project: maven-upload-requests > Issue Type: Task >Reporter: Tassilo Schweyer > > NanoXML Lite is an extremely small (6KB) XML parser -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MSITE-208) ... Link Not Generating
[ http://jira.codehaus.org/browse/MSITE-208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_85594 ] Dennis Lundberg commented on MSITE-208: --- mvn help:describe -DgroupId=org.apache.maven.plugins -DartifactId=maven-site-plugin > ... Link Not Generating > - > > Key: MSITE-208 > URL: http://jira.codehaus.org/browse/MSITE-208 > Project: Maven 2.x Site Plugin > Issue Type: Bug > Environment: Linux 2.6, Maven2.0.4, Java 6.0 >Reporter: Subhash Chandran > > I have the following in my src/site/site.xml: > > WizCrypt > img/logo.png > http://wizcrypt.wiztools.org/ > > For the banner, the link http://wizcrypt.wiztools.org/ is not getting > generated. The generated output: > http://wizcrypt.wiztools.org/ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SUREFIRE-65) IllegalAccessError with a dynamic proxy
[ http://jira.codehaus.org/browse/SUREFIRE-65?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated SUREFIRE-65: - Affects Version/s: 2.0 (2.2 plugin) Fix Version/s: 2.0 (2.2 plugin) > IllegalAccessError with a dynamic proxy > --- > > Key: SUREFIRE-65 > URL: http://jira.codehaus.org/browse/SUREFIRE-65 > Project: Maven Surefire > Issue Type: Bug >Affects Versions: 2.0 (2.2 plugin) >Reporter: Carlos Sanchez > Assigned To: Brett Porter > Fix For: 2.0 (2.2 plugin) > > > I found this regression in the code from the book, migration chapter, when > using 2.2-SNAPSHOT instead of 2.1.3 > --- > Test set: > org.springframework.aop.support.DelegatingIntroductionInterceptorTests > --- > Tests run: 10, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.141 sec > <<< FAILURE! > testIntroductionInterceptorWithInterfaceHierarchy(org.springframework.aop.support.DelegatingIntroductionInterceptorTests) > Time elapsed: 0 sec <<< ERROR! > java.lang.IllegalAccessError: class org.springframework.aop.support.$Proxy9 > cannot access its superinterface > org.springframework.aop.support.DelegatingIntroductionInterceptorTests$SubTimeStamped > at java.lang.reflect.Proxy.defineClass0(Native Method) > at java.lang.reflect.Proxy.getProxyClass(Unknown Source) > at java.lang.reflect.Proxy.newProxyInstance(Unknown Source) > at > org.springframework.aop.framework.JdkDynamicAopProxy.getProxy(JdkDynamicAopProxy.java:104) > at > org.springframework.aop.framework.JdkDynamicAopProxy.getProxy(JdkDynamicAopProxy.java:94) > at > org.springframework.aop.framework.ProxyFactory.getProxy(ProxyFactory.java:70) > at > org.springframework.aop.support.DelegatingIntroductionInterceptorTests.testIntroductionInterceptorWithInterfaceHierarchy(DelegatingIntroductionInterceptorTests.java:88) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SUREFIRE-66) JUnitBattery dies when TestSuite has an anonymous inner class
[
http://jira.codehaus.org/browse/SUREFIRE-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter updated SUREFIRE-66:
-
Affects Version/s: 1.5.2 (2.1.2 plugin)
1.5.3 (2.1.3 plugin)
Fix Version/s: 2.0 (2.2 plugin)
> JUnitBattery dies when TestSuite has an anonymous inner class
> -
>
> Key: SUREFIRE-66
> URL: http://jira.codehaus.org/browse/SUREFIRE-66
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 1.5.2 (2.1.2 plugin), 1.5.3 (2.1.3 plugin)
>Reporter: Mike Perham
> Assigned To: Brett Porter
> Fix For: 2.0 (2.2 plugin)
>
> Attachments: SimpleTestSuite.java, SurefireTest.java
>
>
> I have this method in my test suite:
> {code}
> private static File[] getWSDLFiles() {
> URL directoryURL =
> WSDLImportTestSuite.class.getResource("/com/webify/wsf/studio/core/wsdl/wsdls");
> if (directoryURL != null) {
> File directory = new File(directoryURL.getPath());
> FilenameFilter filter = new FilenameFilter() {
> public boolean accept(File dir, String name) {
> return name.endsWith(".wsdl");
> }
> };
> return directory.listFiles(filter);
> }
> else {
> return null;
> }
> }
> {code}
> And surefire fails with this exception:
> java.lang.NoSuchMethodException:
> com.webify.wsf.studio.core.wsdl.WSDLImportTestSuite$1.()
> at java.lang.Class.getConstructor0(Class.java:1937)
> at java.lang.Class.getConstructor(Class.java:1027)
> at
> org.apache.maven.surefire.battery.JUnitBattery.getTestConstructor(JUnitBattery.java:307)
> at
> org.apache.maven.surefire.battery.JUnitBattery.processTestClass(JUnitBattery.java:150)
> at
> org.apache.maven.surefire.battery.JUnitBattery.(JUnitBattery.java:81)
> at
> org.apache.maven.surefire.SurefireUtils.instantiateBattery(SurefireUtils.java:63)
> at
> org.apache.maven.surefire.Surefire.instantiateBatteries(Surefire.java:262)
> at org.apache.maven.surefire.Surefire.run(Surefire.java:140)
> at org.apache.maven.surefire.Surefire.run(Surefire.java:87)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SUREFIRE-97) Improve error stack trace when the error comes from the user's test code
[
http://jira.codehaus.org/browse/SUREFIRE-97?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter updated SUREFIRE-97:
-
Affects Version/s: 1.5.3 (2.1.3 plugin)
Fix Version/s: 2.0 (2.2 plugin)
> Improve error stack trace when the error comes from the user's test code
>
>
> Key: SUREFIRE-97
> URL: http://jira.codehaus.org/browse/SUREFIRE-97
> Project: Maven Surefire
> Issue Type: Improvement
>Affects Versions: 1.5.3 (2.1.3 plugin)
>Reporter: Vincent Massol
> Assigned To: Brett Porter
> Fix For: 2.0 (2.2 plugin)
>
>
> For example here's what's printed when my test code reports an error:
> {noformat}
> java.lang.reflect.InvocationTargetException
> 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:324)
> at
> org.apache.maven.surefire.SurefireBooter.main(SurefireBooter.java:785)
> Caused by: java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
> at
> org.apache.maven.surefire.SurefireUtils.instantiateBattery(SurefireUtils.java:54)
> at
> org.apache.maven.surefire.Surefire.instantiateBatteries(Surefire.java:262)
> at org.apache.maven.surefire.Surefire.run(Surefire.java:93)
> at org.apache.maven.surefire.Surefire.run(Surefire.java:87)
> at org.apache.maven.surefire.Surefire.run(Surefire.java:63)
> ... 5 more
> Caused by: java.lang.reflect.InvocationTargetException
> 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:324)
> at
> org.apache.maven.surefire.battery.JUnitBattery.processTestClass(JUnitBattery.java:130)
> at
> org.apache.maven.surefire.battery.JUnitBattery.(JUnitBattery.java:69)
> ... 14 more
> Caused by: java.lang.RuntimeException: System property "cargo.containers"
> must be defined.
> at
> org.codehaus.cargo.sample.java.AbstractCargoTestCase.addContainerToTest(AbstractCargoTestCase.java:157)
> {noformat}
> This is really not nice and hard to read as the real cause it buried down the
> stack trace. I would like surefire code to directly make the user's error be
> at the top of the thrown stack trace, i.e. surefire should not catch user
> exceptions. This is what I would expect to see:
> {noformat}
> java.lang.RuntimeException: System property "cargo.containers" must be
> defined.
> at
> org.codehaus.cargo.sample.java.AbstractCargoTestCase.addContainerToTest(AbstractCargoTestCase.java:157)
> {noformat}
> Thanks
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SUREFIRE-98) System properties are not set
[ http://jira.codehaus.org/browse/SUREFIRE-98?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated SUREFIRE-98: - Affects Version/s: 2.0 (2.2 plugin) Fix Version/s: 2.0 (2.2 plugin) > System properties are not set > - > > Key: SUREFIRE-98 > URL: http://jira.codehaus.org/browse/SUREFIRE-98 > Project: Maven Surefire > Issue Type: Improvement >Affects Versions: 2.0 (2.2 plugin) >Reporter: Brett Porter > Assigned To: Brett Porter >Priority: Blocker > Fix For: 2.0 (2.2 plugin) > > > see activemq-jaas -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SUREFIRE-96) The "pertest" option for forking mode should be renamed more appropriately
[ http://jira.codehaus.org/browse/SUREFIRE-96?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated SUREFIRE-96: - Affects Version/s: 1.5.2 (2.1.2 plugin) Fix Version/s: 2.0 (2.2 plugin) > The "pertest" option for forking mode should be renamed more appropriately > -- > > Key: SUREFIRE-96 > URL: http://jira.codehaus.org/browse/SUREFIRE-96 > Project: Maven Surefire > Issue Type: Improvement >Affects Versions: 1.5.2 (2.1.2 plugin) >Reporter: Jason van Zyl > Assigned To: Brett Porter > Fix For: 2.0 (2.2 plugin) > > > The option should be called "pertestcase" or "perbattery" or something akin. > Open to suggestions here. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SUREFIRE-92) Fix classloader separation of Test NG
[ http://jira.codehaus.org/browse/SUREFIRE-92?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated SUREFIRE-92: - Affects Version/s: 2.0 (2.2 plugin) Fix Version/s: 2.3 > Fix classloader separation of Test NG > - > > Key: SUREFIRE-92 > URL: http://jira.codehaus.org/browse/SUREFIRE-92 > Project: Maven Surefire > Issue Type: Sub-task >Affects Versions: 2.0 (2.2 plugin) >Reporter: Brett Porter > Fix For: 2.3 > > > Currently, all of the test classes go into the surefire classloader (as > before) so that TestNG can find them. > Using the context classloader might be the key to avoiding this. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SUREFIRE-90) Add Distributed testing ability
[ http://jira.codehaus.org/browse/SUREFIRE-90?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated SUREFIRE-90: - Fix Version/s: 2.4 Component/s: TestNG support > Add Distributed testing ability > --- > > Key: SUREFIRE-90 > URL: http://jira.codehaus.org/browse/SUREFIRE-90 > Project: Maven Surefire > Issue Type: Sub-task > Components: TestNG support > Environment: any >Reporter: Jesse Kuhnert >Priority: Minor > Fix For: 2.4 > > > TestNG now supports running distributed tests, determine feasability of > integrating this into surefire. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SUREFIRE-94) Implement getTestCount for TestNG
[ http://jira.codehaus.org/browse/SUREFIRE-94?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated SUREFIRE-94: - Affects Version/s: 2.0 (2.2 plugin) Fix Version/s: 2.3 > Implement getTestCount for TestNG > - > > Key: SUREFIRE-94 > URL: http://jira.codehaus.org/browse/SUREFIRE-94 > Project: Maven Surefire > Issue Type: Sub-task >Affects Versions: 2.0 (2.2 plugin) >Reporter: Brett Porter > Fix For: 2.3 > > > this isn't required for correct operation of the tests, but may be if a > reporter relies on the correct number in the runStarting method (currently, > it is unused). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SUREFIRE-89) Ensure java 1.4 compatibility
[ http://jira.codehaus.org/browse/SUREFIRE-89?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated SUREFIRE-89: - Fix Version/s: 2.0 (2.2 plugin) Component/s: TestNG support > Ensure java 1.4 compatibility > - > > Key: SUREFIRE-89 > URL: http://jira.codehaus.org/browse/SUREFIRE-89 > Project: Maven Surefire > Issue Type: Sub-task > Components: TestNG support > Environment: java <= 1.4 >Reporter: Jesse Kuhnert > Fix For: 2.0 (2.2 plugin) > > > The javadoc annotation finder works a little bit differently than the 1.5 > annotation finder, ensure that when running in a 1.4jvm people can run and > correctly see test results. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SUREFIRE-87) Add relevant parameters for configuring testng
[ http://jira.codehaus.org/browse/SUREFIRE-87?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated SUREFIRE-87: - Fix Version/s: 2.0 (2.2 plugin) Component/s: TestNG support > Add relevant parameters for configuring testng > -- > > Key: SUREFIRE-87 > URL: http://jira.codehaus.org/browse/SUREFIRE-87 > Project: Maven Surefire > Issue Type: Sub-task > Components: TestNG support > Environment: any >Reporter: Jesse Kuhnert > Fix For: 2.0 (2.2 plugin) > > > Add all of the normal testng parameters to runtime, like which groups to run, > an optional suite.xml file to use, etc. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SUREFIRE-84) Surefire causes OOM
[ http://jira.codehaus.org/browse/SUREFIRE-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated SUREFIRE-84: - Affects Version/s: 1.5.1 (2.1.1 plugin) Fix Version/s: 2.0 (2.2 plugin) > Surefire causes OOM > --- > > Key: SUREFIRE-84 > URL: http://jira.codehaus.org/browse/SUREFIRE-84 > Project: Maven Surefire > Issue Type: Bug >Affects Versions: 1.5.1 (2.1.1 plugin) >Reporter: Mike Perham > Assigned To: Brett Porter > Fix For: 2.0 (2.2 plugin) > > > We have a build with 30-40 modules which use JUnit to run a heavy load of > database integration testing. Our build has never worked with just 'mvn > clean install' since 2.0 - we get OOM errors within 5-10 modules (even with > -Xmx512m). When I enable the test skip flag, the entire build runs to > completion. I suspect there is a memory leak somewhere in surefire or its > classloader where things are not getting freed after each module's test run. > We are currently using surefire-plugin 2.1.1 since 2.1.2 has MSUREFIRE-59. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SUREFIRE-85) java.lang.NoClassDefFoundError: org/apache/maven/surefire/util/NestedCheckedException
[ http://jira.codehaus.org/browse/SUREFIRE-85?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated SUREFIRE-85: - Affects Version/s: 2.0 (2.2 plugin) Fix Version/s: 2.0 (2.2 plugin) > java.lang.NoClassDefFoundError: > org/apache/maven/surefire/util/NestedCheckedException > - > > Key: SUREFIRE-85 > URL: http://jira.codehaus.org/browse/SUREFIRE-85 > Project: Maven Surefire > Issue Type: Bug >Affects Versions: 2.0 (2.2 plugin) > Environment: Windows XP / Sun JDK 1.5.0_06 >Reporter: David J. M. Karlsen > Assigned To: Carlos Sanchez > Fix For: 2.0 (2.2 plugin) > > > java.lang.NoClassDefFoundError: > org/apache/maven/surefire/util/NestedCheckedException > Exception in thread "main" > is thrown during execution of the maven-surefire-plugin -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SUREFIRE-79) maven-surefire-plugin:2.2-SNAPSHOT fails with invalid option -ea when forking to a JDK < 1.4
[ http://jira.codehaus.org/browse/SUREFIRE-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated SUREFIRE-79: - Affects Version/s: 2.0 (2.2 plugin) Fix Version/s: 2.0 (2.2 plugin) > maven-surefire-plugin:2.2-SNAPSHOT fails with invalid option -ea when > forking to a JDK < 1.4 > - > > Key: SUREFIRE-79 > URL: http://jira.codehaus.org/browse/SUREFIRE-79 > Project: Maven Surefire > Issue Type: Bug >Affects Versions: 2.0 (2.2 plugin) > Environment: Win XP, Sun jdk 1.5.0_06 >Reporter: David J. M. Karlsen > Assigned To: Brett Porter > Fix For: 2.0 (2.2 plugin) > > > Launching a surefire test with a 1.3 JDK will fail as surefire sets -ea as a > default option: > [DEBUG] Configuring mojo > 'org.apache.maven.plugins:maven-surefire-plugin:2.2-SNAPSHOT:test' --> > . > Forking command line: C:\jdk1.3.1_18\bin\java.exe -ea -classpath < lots of > classes > > Unrecognized option: -ea > The -ea option is not available on a 1.3.1 JDK - effectively disabling > testing with a JDK < 1.4 with surefire. > also tried setting an empty > in the configuration - but this didn't seem to be read (at least > it's not mentioned while running with -X) > Probably the options should all be set within - and surefire should > not assume any default options. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SUREFIRE-82) Sometimes xml report has no time atribute in testcase element
[ http://jira.codehaus.org/browse/SUREFIRE-82?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated SUREFIRE-82: - Affects Version/s: 1.5.3 (2.1.3 plugin) Fix Version/s: 2.0 (2.2 plugin) > Sometimes xml report has no time atribute in testcase element > - > > Key: SUREFIRE-82 > URL: http://jira.codehaus.org/browse/SUREFIRE-82 > Project: Maven Surefire > Issue Type: Bug >Affects Versions: 1.5.3 (2.1.3 plugin) >Reporter: Carlos Sanchez > Assigned To: Brett Porter > Fix For: 2.0 (2.2 plugin) > > Attachments: MultithreadedTest.patch > > > Attached is a test that makes the xml report not have time attribute for some > testcase elements. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SUREFIRE-80) Prevent XML parser problems by changing default forkMode and childDelegation settings
[ http://jira.codehaus.org/browse/SUREFIRE-80?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated SUREFIRE-80: - Affects Version/s: 2.0 (2.2 plugin) Fix Version/s: 2.0 (2.2 plugin) > Prevent XML parser problems by changing default forkMode and childDelegation > settings > - > > Key: SUREFIRE-80 > URL: http://jira.codehaus.org/browse/SUREFIRE-80 > Project: Maven Surefire > Issue Type: Bug >Affects Versions: 2.0 (2.2 plugin) > Environment: Latest surefire as of May 1 >Reporter: Patrick Lightbody > Assigned To: Brett Porter >Priority: Blocker > Fix For: 2.0 (2.2 plugin) > > > With the latest releases surefire, the webwork tests ran just fine. > With the latest code in trunk, I get weird XML parser errors that only get > fixed once I set forkMode=once or childDelegation=false > See for yourself: > svn co https://svn.apache.org/repos/asf/incubator/webwork2 > cd webwork2 > mvn install > The error I get in various tests is: > javax.xml.parsers.FactoryConfigurationError: Provider for > javax.xml.parsers.SAXParserFactory cannot be found > at javax.xml.parsers.SAXParserFactory.newInstance(Unknown Source) > at com.opensymphony.xwork.util.DomHelper.parse(DomHelper.java:86) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SUREFIRE-77) Surefire fork fails under windows when command has several quotes
[ http://jira.codehaus.org/browse/SUREFIRE-77?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated SUREFIRE-77: - Affects Version/s: 1.5.3 (2.1.3 plugin) Fix Version/s: 2.0 (2.2 plugin) > Surefire fork fails under windows when command has several quotes > - > > Key: SUREFIRE-77 > URL: http://jira.codehaus.org/browse/SUREFIRE-77 > Project: Maven Surefire > Issue Type: Bug >Affects Versions: 1.5.3 (2.1.3 plugin) >Reporter: Carlos Sanchez > Assigned To: Carlos Sanchez > Fix For: 2.0 (2.2 plugin) > > > Same as MCOMPILER-30 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SUREFIRE-78) Surefire temporary files should be put in target rather than in the main project directory
[ http://jira.codehaus.org/browse/SUREFIRE-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated SUREFIRE-78: - Affects Version/s: 1.5.3 (2.1.3 plugin) Fix Version/s: 2.0 (2.2 plugin) > Surefire temporary files should be put in target rather than in the main > project directory > -- > > Key: SUREFIRE-78 > URL: http://jira.codehaus.org/browse/SUREFIRE-78 > Project: Maven Surefire > Issue Type: Bug >Affects Versions: 1.5.3 (2.1.3 plugin) >Reporter: Vincent Massol > Assigned To: Brett Porter >Priority: Minor > Fix For: 2.0 (2.2 plugin) > > > The following 3 files are cretaed in the main project directory. > surefire.properties > surefire-classloader.properties > surefire-system.properties > They should go in target/ > Thus if the build is stopped they're not left over in the main tree. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SUREFIRE-75) Surefire forking doesn't work on Java 1.3
[ http://jira.codehaus.org/browse/SUREFIRE-75?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated SUREFIRE-75: - Affects Version/s: 1.5.2 (2.1.2 plugin) 1.5.3 (2.1.3 plugin) Fix Version/s: 2.0 (2.2 plugin) > Surefire forking doesn't work on Java 1.3 > - > > Key: SUREFIRE-75 > URL: http://jira.codehaus.org/browse/SUREFIRE-75 > Project: Maven Surefire > Issue Type: Bug >Affects Versions: 1.5.2 (2.1.2 plugin), 1.5.3 (2.1.3 plugin) > Environment: Win XP / java sun 1.5.0_06. >Reporter: David J. M. Karlsen > Assigned To: Brett Porter > Fix For: 2.0 (2.2 plugin) > > > When using the forkMode option, and setting JVM to a: > Classic VM (build 1.3.1, J2RE 1.3.1 IBM Windows 32 build cn131-20030711a (JIT > enabled: jitc)) > which does not implement the java.lang.String.split method which was > introduced in java 1.4, the test will fail with the error message "There are > some test failure" because the fork fails: > Exception in thread "main" java.lang.NoSuchMethodError: java.lang.String: > method split(Ljava/lang/String;)[Ljava/lang/St > ring; not found > at > org.apache.maven.surefire.SurefireBooter.createForkingClassLoader(SurefireBooter.java:264) > at > org.apache.maven.surefire.SurefireBooter.main(SurefireBooter.java:628) > Configuration: > pertest > C:\Program Files\IBM\WebSphere Studio\Application > Developer\v5.1.2\runtimes\base_v5\java\jre\bin\java -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SUREFIRE-74) Surefire is giving classloader preferences to main sources before test sources
[ http://jira.codehaus.org/browse/SUREFIRE-74?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated SUREFIRE-74: - Affects Version/s: 2.0 (2.2 plugin) Fix Version/s: 2.0 (2.2 plugin) > Surefire is giving classloader preferences to main sources before test sources > -- > > Key: SUREFIRE-74 > URL: http://jira.codehaus.org/browse/SUREFIRE-74 > Project: Maven Surefire > Issue Type: Bug >Affects Versions: 2.0 (2.2 plugin) > Environment: Running on trunk as of May 1 >Reporter: Patrick Lightbody > Assigned To: Brett Porter >Priority: Blocker > Fix For: 2.0 (2.2 plugin) > > > Giving the classloader preferences to the main files before the test files is > opposite of what surefire used to do and different from all other test > environments (Ant, IDEA, etc). This is a problem for the XWork build. To > reproduce: > cvs -d :pserver:[EMAIL PROTECTED]:/cvs login > cvs -d :pserver:[EMAIL PROTECTED]:/cvs co xwork > cd xwork > mvn test > If you're using the releases surefire plugin, they will pass just fine. > If you're using the latest from trunk, they will fail. This is due to the > fact that the tests are picking up src/java/xwork-default.xml instead of > src/test/xwork-default.xml. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SUREFIRE-73) Surefire fails to start when the local repository and the project (pom.xml) lives in different window drives
[
http://jira.codehaus.org/browse/SUREFIRE-73?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter updated SUREFIRE-73:
-
Affects Version/s: 1.5.2 (2.1.2 plugin)
Fix Version/s: 2.0 (2.2 plugin)
> Surefire fails to start when the local repository and the project (pom.xml)
> lives in different window drives
>
>
> Key: SUREFIRE-73
> URL: http://jira.codehaus.org/browse/SUREFIRE-73
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 1.5.2 (2.1.2 plugin)
> Environment: Windows XP
> Java 1.5.0_06
> Maven 2.0.1
> Surefire fork mode: once
>Reporter: Martin Desruisseaux
> Assigned To: fabrizio giustina
> Fix For: 2.0 (2.2 plugin)
>
>
> We have the following situation:
> - Local repository in {{C:\Documents and Settings\user\.m2}}
> - A Maven 2 project in {{P:\MyProject}}.
> - Surefire fork mode set to "once".
> In this configuration, surefire fails with this (somewhat misleading) error
> message:
> {quote}
> Setting reports dir: {{P:\MyProject\target/surefire-reports}}
> BUILD ERROR
> There are some test failure.
> {quote}
> This message is misleading because it suggests that some user's tests failed,
> while actually Surefile didn't executed a single one. It even failed before
> to create the {{surefire-reports}} directory! So we have no indication about
> the cause, and printing the stack trace with the {{-e}} option doesn't help
> much (I suspect that this is because the stack trace was actually produced by
> a different virtual machine instance, and was not passed to the JVM running
> Maven). Running Maven with the {{-X}} option provides more hints however. We
> can see that Maven try to executes the following command:
> {{java -Xmx512M -enableassertions -classpath
> "C:\...snip...\.m2\repository\org\apache\maven\surefire\surefire-booter\1.5.2\surefire-booter-1.5.2.jar;
> C:\Java\Apache\Maven2\bin\..\core\plexus-utils-1.0.5.jar"
> org.apache.maven.surefire.SurefireBooter P:\MyProject}}
> Running this command manually gives the following output:
> {code}
> ClassLoader: typeclass sun.misc.Launcher$ExtClassLoader, value=...snip...
>: file:/C:/Java/1.5/jre/lib/ext/sunjce_provider.jar
>: file:/C:/Java/1.5/jre/lib/ext/sunpkcs11.jar
>(...snip...)
> ClassLoader: typeclass sun.misc.Launcher$AppClassLoader, value=...snip...
>: file:/C:/Documents ...snip... /.m2/repository/ ...snip..
> ./surefire-booter-1.5.2.jar
>: file:/C:/Java/Apache/Maven2/core/plexus-utils-1.0.5.jar
> ClassLoader: typeclass org.apache.maven.surefire.IsolatedClassLoader,
> value=...snip...
>: file:/P:/MyProjects/
>(...snip...)
>: file:/P:/Documents and
> Settings/user/.m2/repository/...snip.../surefire-1.5.2.jar
> Exception in thread "main" java.lang.ClassNotFoundException:
> org.apache.maven.surefire.Surefire
> at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
>(...snip...)
> {code}
> As you can see, the path for {{surefire-1.5.2.jar}} wrongly refer to the
> drive letter {{P:}}. It should be {{C:}} instead.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SUREFIRE-71) Forking documentation improvement to help with class loader constrainst issues
[ http://jira.codehaus.org/browse/SUREFIRE-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated SUREFIRE-71: - Affects Version/s: 1.5.3 (2.1.3 plugin) Fix Version/s: 2.0 (2.2 plugin) > Forking documentation improvement to help with class loader constrainst issues > -- > > Key: SUREFIRE-71 > URL: http://jira.codehaus.org/browse/SUREFIRE-71 > Project: Maven Surefire > Issue Type: Bug >Affects Versions: 1.5.3 (2.1.3 plugin) > Environment: maven 2.0.2 >Reporter: Ben Gidley > Assigned To: Brett Porter >Priority: Minor > Fix For: 2.0 (2.2 plugin) > > Attachments: maven-surefire-plugin-374325.patch > > > With (for example) JAXB2 forking surefire causes a > java.lang.LinkageError: loader constraints violated when linking > javax/xml/namespace/QName class > This is because by default when forking an Isolated class loader is used. > this can be resovled by turning child delegation on. > The documentation does not mention this and should be improved. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SUREFIRE-72) IsolatedClassloader.getResources returns duplicated results
[
http://jira.codehaus.org/browse/SUREFIRE-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter updated SUREFIRE-72:
-
Affects Version/s: 2.0 (2.2 plugin)
Fix Version/s: 2.0 (2.2 plugin)
> IsolatedClassloader.getResources returns duplicated results
> ---
>
> Key: SUREFIRE-72
> URL: http://jira.codehaus.org/browse/SUREFIRE-72
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 2.0 (2.2 plugin)
>Reporter: Carlos Sanchez
> Assigned To: Brett Porter
> Fix For: 2.0 (2.2 plugin)
>
>
> When calling classLoader.getResources("org/springframework/core/io") every
> result is twice in the resulting enumeration
> It doesn't happen in 2.1.3
> It may have to do with the fact that classes and test-classes are twice in
> the classpath output
> [INFO] [surefire:test]
> [DEBUG] dummy:dummy:jar:1.0 (selected for null)
> [DEBUG] org.apache.maven.surefire:surefire-booter:jar:2.0-SNAPSHOT:runtime
> (selected for runtime)
> [DEBUG] org.apache.maven.surefire:surefire-api:jar:2.0-SNAPSHOT:runtime
> (selected for runtime)
> [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.1:runtime (selected for
> runtime)
> [DEBUG] surefire-api: using locally installed snapshot
> [DEBUG] Adding to surefire test classpath: C:\Documents and
> Settings\csanchez\.m2\repository\org\codehaus\plexus\plexus-utils\1.1\plexus-utils-1.1.jar
> [DEBUG] Adding to surefire test classpath: C:\Documents and
> Settings\csanchez\.m2\repository\org\apache\maven\surefire\surefire-booter\2.0-SNAPSHOT\surefire-booter-2.0-SNAPSHOT.jar
> [DEBUG] Adding to surefire test classpath: C:\Documents and
> Settings\csanchez\.m2\repository\org\apache\maven\surefire\surefire-api\2.0-SNAPSHOT\surefire-api-2.0-SNAPSHOT.jar
> [DEBUG] dummy:dummy:jar:1.0 (selected for null)
> [DEBUG] Skipping disabled repository central
> [DEBUG] surefire-junit: using locally installed snapshot
> [DEBUG] Retrieving parent-POM from the repository for project:
> null:surefire-junit:jar:2.0-SNAPSHOT
> [DEBUG] Skipping disabled repository central
> [DEBUG] surefire-providers: using locally installed snapshot
> [DEBUG] Retrieving parent-POM from the repository for project:
> null:surefire-providers:pom:null
> [DEBUG] surefire: using locally installed snapshot
> [DEBUG] org.apache.maven.surefire:surefire-junit:jar:2.0-SNAPSHOT (selected
> for null)
> [DEBUG] junit:junit:jar:3.8.1:compile (selected for compile)
> [DEBUG] org.apache.maven.surefire:surefire-api:jar:2.0-SNAPSHOT:compile
> (selected for compile)
> [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.1:compile (selected for
> compile)
> [DEBUG] surefire-junit: using locally installed snapshot
> [DEBUG] surefire-api: using locally installed snapshot
> [DEBUG] Adding to surefire test classpath: C:\Documents and
> Settings\csanchez\.m2\repository\junit\junit\3.8.1\junit-3.8.1.jar
> [DEBUG] Adding to surefire test classpath: C:\Documents and
> Settings\csanchez\.m2\repository\org\codehaus\plexus\plexus-utils\1.1\plexus-utils-1.1.jar
> [DEBUG] Adding to surefire test classpath: C:\Documents and
> Settings\csanchez\.m2\repository\org\apache\maven\surefire\surefire-api\2.0-SNAPSHOT\surefire-api-2.0-SNAPSHOT.jar
> [DEBUG] Adding to surefire test classpath: C:\Documents and
> Settings\csanchez\.m2\repository\org\apache\maven\surefire\surefire-junit\2.0-SNAPSHOT\surefire-junit-2.0-SNAPSHOT.jar
> [DEBUG] Test Classpath :
> [DEBUG] c:\dev\spring\spring\m2\spring-core\target\test-classes
> [DEBUG] c:\dev\spring\spring\m2\spring-core\target\classes
> [DEBUG] c:\dev\spring\spring\m2\spring-core\target\classes
> [DEBUG] c:\dev\spring\spring\m2\spring-core\target\test-classes
> [DEBUG] C:\Documents and
> Settings\csanchez\.m2\repository\commons-collections\commons-collections\3.1\commons-collections-3.1.jar
> [DEBUG] C:\Documents and
> Settings\csanchez\.m2\repository\aopalliance\aopalliance\1.0\aopalliance-1.0.jar
> [DEBUG] C:\Documents and
> Settings\csanchez\.m2\repository\junit\junit\3.8.1\junit-3.8.1.jar
> [DEBUG] C:\Documents and
> Settings\csanchez\.m2\repository\commons-logging\commons-logging\1.0.4\commons-logging-1.0.4.jar
> [DEBUG] C:\Documents and
> Settings\csanchez\.m2\repository\javax\servlet\servlet-api\2.4\servlet-api-2.4.jar
> [DEBUG] C:\Documents and
> Settings\csanchez\.m2\repository\asm\asm\2.2.1\asm-2.2.1.jar
> [DEBUG] C:\Documents and
> Settings\csanchez\.m2\repository\asm\asm-commons\2.2.1\asm-commons-2.2.1.jar
> [DEBUG] C:\Documents and
> Settings\csanchez\.m2\repository\easymock\easymock\1.2_Java1.3\easymock-1.2_Java1.3.jar
> [DEBUG] C:\Documents and
> Settings\csanchez\.m2\repository\log4j\log4j\1.2.13\log4j-1.2.13.jar
> [DEBUG] Setting system property [localRepository]=[C:/Documents and
> Settings/csanchez/.m2/repository]
> [DEB
[jira] Updated: (SUREFIRE-69) systemClassLoader.getResource returns null
[ http://jira.codehaus.org/browse/SUREFIRE-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated SUREFIRE-69: - Affects Version/s: 1.5.3 (2.1.3 plugin) Fix Version/s: 2.0 (2.2 plugin) > systemClassLoader.getResource returns null > -- > > Key: SUREFIRE-69 > URL: http://jira.codehaus.org/browse/SUREFIRE-69 > Project: Maven Surefire > Issue Type: Bug >Affects Versions: 1.5.3 (2.1.3 plugin) >Reporter: Carlos Sanchez > Assigned To: Brett Porter >Priority: Critical > Fix For: 2.0 (2.2 plugin) > > Attachments: surefire-test.tgz > > > This code fails in m2 and succeeds in ant or eclipse: > ClassLoader systemClassLoader = ClassLoader.getSystemClassLoader(); > InputStream systemResourceAsStream = > systemClassLoader.getResourceAsStream( "test.txt" ); > URL resource = systemClassLoader.getResource( name ); > assertNotNull( resource ); > test.txt exists in target/test-classes -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SUREFIRE-91) Enable assertions for underlying jvm
[ http://jira.codehaus.org/browse/SUREFIRE-91?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated SUREFIRE-91: - Fix Version/s: 2.0 (2.2 plugin) > Enable assertions for underlying jvm > > > Key: SUREFIRE-91 > URL: http://jira.codehaus.org/browse/SUREFIRE-91 > Project: Maven Surefire > Issue Type: Sub-task > Environment: jre 1.5 > >Reporter: Jesse Kuhnert > Assigned To: Brett Porter > Fix For: 2.0 (2.2 plugin) > > > Some jre's don't have assertions enabled by default and require a runtime > parameter of "-ea" in order to use them. Since TestNG supports assertions and > it would be nice to use the short hand method occassionally, determine > feasability of either enabling them in the currently running jvm, or adding > the command line params to the bootloader. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SUREFIRE-86) Support TestNG
[ http://jira.codehaus.org/browse/SUREFIRE-86?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated SUREFIRE-86: - Fix Version/s: 2.0 (2.2 plugin) > Support TestNG > -- > > Key: SUREFIRE-86 > URL: http://jira.codehaus.org/browse/SUREFIRE-86 > Project: Maven Surefire > Issue Type: New Feature >Reporter: Mike Perham > Assigned To: Brett Porter > Fix For: 2.0 (2.2 plugin) > > Attachments: maven-patches.tgz, maven-surefire-plugin-patch.txt, > maven-surefire-report-maven-plugin-patch.txt, surefire-patch.txt, > surefire-patch.txt, surefire-patch.txt, surefire-patch.txt, > surefire-report-maven-plugin-patch.txt, testng-4.4.5-jdk14.jar, > testng-4.4.5-jdk15.jar > > > Add support for running unit tests with TestNG. > http://www.testng.org -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SUREFIRE-93) Correct call to getMethod().getExtraOutput in reporter
[ http://jira.codehaus.org/browse/SUREFIRE-93?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated SUREFIRE-93: - Fix Version/s: 2.0 (2.2 plugin) > Correct call to getMethod().getExtraOutput in reporter > -- > > Key: SUREFIRE-93 > URL: http://jira.codehaus.org/browse/SUREFIRE-93 > Project: Maven Surefire > Issue Type: Sub-task >Reporter: Brett Porter > Assigned To: Brett Porter > Fix For: 2.0 (2.2 plugin) > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SUREFIRE-81) systemProperties and NPE
[
http://jira.codehaus.org/browse/SUREFIRE-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter updated SUREFIRE-81:
-
Fix Version/s: 2.0 (2.2 plugin)
> systemProperties and NPE
>
>
> Key: SUREFIRE-81
> URL: http://jira.codehaus.org/browse/SUREFIRE-81
> Project: Maven Surefire
> Issue Type: Bug
>Reporter: Jason Dillon
> Assigned To: Brett Porter
>Priority: Blocker
> Fix For: 2.0 (2.2 plugin)
>
>
> I've got in my pom:
> {code}
>
>
>
> {code}
> And then configured the surefire plugin to set a system property:
> {code}
>
> org.apache.maven.plugins
> maven-surefire-plugin
>
>
>
> ${jdbc.schema}
>
>
>
> {code}
> Which ends up resulting in:
> {noformat}
> [DEBUG] (f) systemProperties = {dbunit.connection.schema=null}
> ...
> [DEBUG] Trace
> java.lang.NullPointerException
> at java.util.Hashtable.put(Hashtable.java:393)
> at java.util.Properties.setProperty(Properties.java:102)
> at java.lang.System.setProperty(System.java:656)
> at
> org.apache.maven.test.SurefirePlugin.processSystemProperties(SurefirePlugin.java:408)
> at
> org.apache.maven.test.SurefirePlugin.execute(SurefirePlugin.java:335)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:415)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:531)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:485)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:455)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:303)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:270)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:139)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:249)
> 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:324)
> 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)
> {noformat}
> If I put any value into the property, like
> {code}
>
> foo
>
> {code}
> Then it works as expected, no NPE and the property gets set.
> But I need to set the property to an empty string... why on earth does this
> get turned into a null?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SUREFIRE-83) TestNG tests are not executed if invoked by */*Test.java naming pattern
[ http://jira.codehaus.org/browse/SUREFIRE-83?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated SUREFIRE-83: - Fix Version/s: 2.0 (2.2 plugin) > TestNG tests are not executed if invoked by */*Test.java naming pattern > --- > > Key: SUREFIRE-83 > URL: http://jira.codehaus.org/browse/SUREFIRE-83 > Project: Maven Surefire > Issue Type: Bug > Environment: Windows XP, Maven 2.0.4, Surefire from snapshot server >Reporter: Andreas Guther > Assigned To: Brett Porter > Fix For: 2.0 (2.2 plugin) > > Attachments: my-app-2.zip > > > I created an example project and added two testng tests, one ending with > *Test.java, one with a not Test containing name. Surefire seems to be able > to find the test but does not execute the tests inside the class (one should > succeed, one should fail). The console output is below. I will attach my > example project in zip format to the issue report. > C:\workspace\my-app>mvn test > [INFO] Scanning for projects... > [INFO] > > [INFO] Building Maven Quick Start Archetype > [INFO]task-segment: [test] > [INFO] > > [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] > Compiling 2 source files to C:\workspace\my-app\target\test-classes > [INFO] [surefire:test] > [INFO] Surefire report directory: C:\workspace\my-app\target\surefire-reports > --- > T E S T S > --- > Running com.mycompany.app.AppTest > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.015 sec > Running com.mycompany.app.TestNgJavaOneTngTest > Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.016 sec > Results : > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0 > [INFO] > > [INFO] BUILD SUCCESSFUL > [INFO] > > [INFO] Total time: 2 seconds > [INFO] Finished at: Tue May 02 07:14:11 PDT 2006 > [INFO] Final Memory: 4M/508M > [INFO] > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SUREFIRE-95) stop output to test-output directory
[ http://jira.codehaus.org/browse/SUREFIRE-95?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated SUREFIRE-95: - Fix Version/s: 2.0 (2.2 plugin) > stop output to test-output directory > > > Key: SUREFIRE-95 > URL: http://jira.codehaus.org/browse/SUREFIRE-95 > Project: Maven Surefire > Issue Type: Sub-task >Reporter: Brett Porter > Assigned To: Brett Porter > Fix For: 2.0 (2.2 plugin) > > Attachments: pom.xml, surefire-patch.txt, surefire-patch.txt > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SUREFIRE-70) settting System property "basedir" is evil.
[ http://jira.codehaus.org/browse/SUREFIRE-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated SUREFIRE-70: - Fix Version/s: 2.0 (2.2 plugin) > settting System property "basedir" is evil. > --- > > Key: SUREFIRE-70 > URL: http://jira.codehaus.org/browse/SUREFIRE-70 > Project: Maven Surefire > Issue Type: Bug > Environment: maven 2.1-snapshot embedder, latest surefire plugin, > Netbeans IDE. >Reporter: Milos Kleint > Assigned To: Brett Porter >Priority: Blocker > Fix For: 2.0 (2.2 plugin) > > > when running in embedded environment, the surefire plugin seems to influence > the embedding application by setting system properties, like "basedir". plus > some custom additional per project. > In netbeans, this causes all ant-based projects to stop working after > building a m2 project once. See MEVENIDE-412. > The proper way of setting the environment variables is either not to set them > at all (when building 2 projects at the same time, we can get strange results > as the 2 builds both write the same props but different values) or to reset > them back to whatever the value was previosly. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SUREFIRE-76) classpath line is too long in fork mode
[ http://jira.codehaus.org/browse/SUREFIRE-76?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated SUREFIRE-76: - Fix Version/s: 2.0 (2.2 plugin) > classpath line is too long in fork mode > --- > > Key: SUREFIRE-76 > URL: http://jira.codehaus.org/browse/SUREFIRE-76 > Project: Maven Surefire > Issue Type: Bug >Reporter: Brett Porter > Assigned To: Brett Porter > Fix For: 2.0 (2.2 plugin) > > Attachments: MSUREFIRE-104-1.diff, MSUREFIRE-104-2.diff > > > since we started putting the whole set of jars on the classpath, this has > become a problem. > It can probably be avoided. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SUREFIRE-68) forkMode=pertest shows Results: line after every battery, not at the end.
[ http://jira.codehaus.org/browse/SUREFIRE-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated SUREFIRE-68: - Fix Version/s: 2.0 (2.2 plugin) > forkMode=pertest shows Results: line after every battery, not at the end. > - > > Key: SUREFIRE-68 > URL: http://jira.codehaus.org/browse/SUREFIRE-68 > Project: Maven Surefire > Issue Type: Bug >Reporter: Brett Porter > Assigned To: Brett Porter > Fix For: 2.0 (2.2 plugin) > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SUREFIRE-67) [surefire-testng] SurefireReportMojo.executeReport() throws a java.lang.NumberFormatException
[ http://jira.codehaus.org/browse/SUREFIRE-67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated SUREFIRE-67: - Fix Version/s: 2.0 (2.2 plugin) > [surefire-testng] SurefireReportMojo.executeReport() throws a > java.lang.NumberFormatException > - > > Key: SUREFIRE-67 > URL: http://jira.codehaus.org/browse/SUREFIRE-67 > Project: Maven Surefire > Issue Type: Bug >Reporter: Vincent Siveton > Assigned To: Brett Porter >Priority: Blocker > Fix For: 2.0 (2.2 plugin) > > Attachments: surefire-api_diff > > > NumberFormat.getInstance() uses the current default locale in the jvm. > The patch specifies the English Locale. > Here is the full stacktrace: > [INFO] Generate "Maven Surefire Report" report. > java.lang.NumberFormatException: For input string: "0,031" > at > sun.misc.FloatingDecimal.readJavaFormatString(FloatingDecimal.java:1224) > at java.lang.Float.parseFloat(Float.java:394) > at > org.codehaus.mojo.surefire.ReportTestSuite.startElement(ReportTestSuite.java:78) > at > com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startElement(AbstractSAXParser.java:533) > at > com.sun.org.apache.xerces.internal.impl.dtd.XMLDTDValidator.startElement(XMLDTDValidator.java:798) > at > com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanStartElement(XMLDocumentFragmentScannerImpl.java:878) > at > com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$ContentDispatcher.scanRootElementHook(XMLDocumentScannerImpl.java:1157) > at > com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1794) > at > com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:368) > at > com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:834) > at > com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764) > at > com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148) > at > com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1242) > at javax.xml.parsers.SAXParser.parse(SAXParser.java:375) > at javax.xml.parsers.SAXParser.parse(SAXParser.java:311) > at > org.codehaus.mojo.surefire.ReportTestSuite.(ReportTestSuite.java:59) > at > org.codehaus.mojo.surefire.SurefireReportParser.parseXMLReportFiles(SurefireReportParser.java:42) > at > org.codehaus.mojo.surefire.SurefireReportGenerator.doGenerateReport(SurefireReportGenerator.java:44) > at > org.codehaus.mojo.surefire.SurefireReportMojo.executeReport(SurefireReportMojo.java:77) > at > org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:117) > at > org.apache.maven.plugins.site.SiteMojo.generateReportsPages(SiteMojo.java:1055) > at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:397) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) > 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
[jira] Updated: (SUREFIRE-64) TestNG tests that cause commons-logging to load fail
[ http://jira.codehaus.org/browse/SUREFIRE-64?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated SUREFIRE-64: - Fix Version/s: 2.0 (2.2 plugin) > TestNG tests that cause commons-logging to load fail > > > Key: SUREFIRE-64 > URL: http://jira.codehaus.org/browse/SUREFIRE-64 > Project: Maven Surefire > Issue Type: Bug > Environment: (Using latest from SVN as of May 1) >Reporter: Patrick Lightbody > Assigned To: Brett Porter > Fix For: 2.0 (2.2 plugin) > > Attachments: test.zip > > > If a TestNG test uses commons-logging (either directly or a class that is > tested does), this error is returned: > == > [INFO] Surefire report directory: > /Users/plightbo/autoriginate/hostedqa/test/target/surefire-reports > --- > T E S T S > --- > [Utils] FAILED TO CREATE CLASS class com.acme.FooTest > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] java.lang.reflect.InvocationTargetException; nested exception is > org.testng.TestNGException: java.lang.reflect.InvocationTargetException > Invalid class loader hierarchy. You have more than one version of > 'org.apache.commons.logging.Log' visible, which is not allowed. > == -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-2756) parent resolution is done first before property interpolation
[ http://jira.codehaus.org/browse/MNG-2756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_85597 ] Jan Palmquist commented on MNG-2756: I have a somewhat similar problem, however I guess that the attached example is a bit missleading since the properties supplied in the child pom might (?) not have been examined at the time of -block evaluation... Either way, I'm also *VERY* interested in having properties expanded while evaluating the -block contents. Even if only properties defined in settings.xml or supplied by -D to the mvn-command will affect the evaluation. I'm currently working in a project with many active developers. The project is therefore brached into several development tracks - each track being developed 'independently' of the other over a limited period of time. Regularily, the branches are merged back together in order to keep the project aligned over time. This stragegy is necessary in order keep the environment within each branch stable enough for CI to work and developers productive writing code and not struggling with problems that other branches might introduce... Anyway, keeping the pom-hierarchy (and individual poms) configurable with respect to (in my case) groupIds configurable using parameters would make the recurring merging activities a lot easier... The current workaround is to let each branch have its own repository and have all developers remember to delete their local repository when they change development track... > parent resolution is done first before property interpolation > - > > Key: MNG-2756 > URL: http://jira.codehaus.org/browse/MNG-2756 > Project: Maven 2 > Issue Type: Bug > Components: Inheritance and Interpolation >Affects Versions: 2.0.x, 2.1.x >Reporter: Franz Allan Valencia See > Fix For: 2.0.x > > Attachments: parent-filtering.zip > > > Possible problems > * using properties in the parent tag > * using proeprties in the repositories tag with the parent being unknown > except to that repo > Attach is a sample project whose child project does not get built. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (SUREFIRE-99) Surefire plugin fails if JUnit is not available
[ http://jira.codehaus.org/browse/SUREFIRE-99?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter moved MSUREFIRE-151 to SUREFIRE-99: Affects Version/s: (was: 2.0 (2.2 plugin)) 2.0 (2.2 plugin) Fix Version/s: (was: 2.3) 2.3 Key: SUREFIRE-99 (was: MSUREFIRE-151) Project: Maven Surefire (was: Maven 2.x Surefire Plugin) > Surefire plugin fails if JUnit is not available > --- > > Key: SUREFIRE-99 > URL: http://jira.codehaus.org/browse/SUREFIRE-99 > Project: Maven Surefire > Issue Type: Bug >Affects Versions: 2.0 (2.2 plugin) >Reporter: Simon Kepp Nielsen > Assigned To: Kenney Westerhof >Priority: Critical > Fix For: 2.3 > > Attachments: error.txt, no-test-framework-patch.txt > > > The Surefire Plugin fails with the following message, if JUnit is not > available on the test classpath: > [INFO] No Java test frameworks found > This means, that you have to include JUnit in the classpath, even for > projects that do not have any unit-tests (e.g. ressource projects or your > first Hello World project). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (SUREFIRE-101) Plugin not longer sets system properties when forking is on and debugging information is not correct
[
http://jira.codehaus.org/browse/SUREFIRE-101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter moved MSUREFIRE-145 to SUREFIRE-101:
-
Affects Version/s: (was: 2.0 (2.2 plugin))
2.0 (2.2 plugin)
Fix Version/s: (was: 2.3)
2.3
Key: SUREFIRE-101 (was: MSUREFIRE-145)
Project: Maven Surefire (was: Maven 2.x Surefire Plugin)
> Plugin not longer sets system properties when forking is on and debugging
> information is not correct
>
>
> Key: SUREFIRE-101
> URL: http://jira.codehaus.org/browse/SUREFIRE-101
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 2.0 (2.2 plugin)
>Reporter: Vincent Massol
> Assigned To: Vincent Massol
>Priority: Blocker
> Fix For: 2.3
>
> Attachments: MSUREFIRE-145.zip
>
>
> The following code is in SurefirePlugin.java:
> {code:java}
> processSystemProperties( !fork.isForking() );
> if ( getLog().isDebugEnabled() )
> {
> showMap( systemProperties, "system property" );
> }
> {code}
> 2 problems:
> 1) fork.isForking() is false when forking is enabled and thus system
> properties are not set:
> {code:java}
> protected void processSystemProperties( boolean setInSystem )
> {
> [...]
> if ( setInSystem )
> {
> // Add all system properties configured by the user
> Iterator iter = systemProperties.keySet().iterator();
> while ( iter.hasNext() )
> {
> String key = (String) iter.next();
> String value = systemProperties.getProperty( key );
> System.setProperty( key, value );
> }
> }
> }
> {code}
> 2) showMap() is called regardless of whether the system properties are set
> or not, leading to the following kind of misleading logs:
> {noformat}
> [...]
> [DEBUG] Setting system property [cargo.jetty4x.port]=[8280]
> [DEBUG] Setting system property [cargo.jetty6x.port]=[8280]
> [DEBUG] Setting system property [cargo.jetty5x.port]=[8280]
> [...]
> {noformat}
> Those properties are actually NOT set.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (SUREFIRE-100) environmentVariables does not work with windows
[ http://jira.codehaus.org/browse/SUREFIRE-100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter moved MSUREFIRE-49 to SUREFIRE-100: Affects Version/s: (was: 1.5.2 (2.1.2 plugin)) 2.0 (2.2 plugin) Fix Version/s: (was: 2.3) 2.3 Key: SUREFIRE-100 (was: MSUREFIRE-49) Project: Maven Surefire (was: Maven 2.x Surefire Plugin) > environmentVariables does not work with windows > --- > > Key: SUREFIRE-100 > URL: http://jira.codehaus.org/browse/SUREFIRE-100 > Project: Maven Surefire > Issue Type: Bug >Affects Versions: 2.0 (2.2 plugin) > Environment: windows >Reporter: Dan Tran > Fix For: 2.3 > > Attachments: MSUREFIRE-49.log > > > MSUREFIRE-44 added environmentVariables fields to all additional environment > variables to be added to when forking the test > It works on UNIX but not windows. Suspect it is platform specific problem > for windows in plexus-util's cli library > Here is the plugin configuration to reproduce the problem > >maven-surefire-plugin > > >value > > once > > > and the stack trace is > > [[DEBUG] Adding to surefire test classpath: > c:\dev\maven\maven-2.0.2\core\plexus- > utils-1.1.jar > Environment: key=value added. > java -classpath "C:\Documents and > Settings\dtran\.m2\repository\org\apache\maven > \surefire\surefire-booter\1.5.3-SNAPSHOT\surefire-booter-1.5.3-SNAPSHOT.jar;c:\d > ev\maven\maven-2.0.2\core\plexus-utils-1.1.jar" > org.apache.maven.surefire.Surefi > reBooter C:\dev\maven\src\surefire\surefire > [INFO] > - > --- > [ERROR] BUILD ERROR > [INFO] > - > --- > [INFO] There are some test failure. > [INFO] > - > --- > [DEBUG] Trace > org.apache.maven.lifecycle.LifecycleExecutionException: There are some test > fail > ure. > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa > ultLifecycleExecutor.java:556) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi > fecycle(DefaultLifecycleExecutor.java:472) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau > ltLifecycleExecutor.java:451) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan > dleFailures(DefaultLifecycleExecutor.java:303) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen > ts(DefaultLifecycleExecutor.java:270) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi > fecycleExecutor.java:139) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:249) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. > java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces > sorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:324) > 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.MojoExecutionException: There are some > test f > ailure. > at > org.apache.maven.test.SurefirePlugin.execute(SurefirePlugin.java:404) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi > nManager.java:415) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa > ultLifecycleExecutor.java:531) > ... 16 more > [INFO] > - > --- > [INFO] Total time: 4 seconds > [INFO] Finished at: Sat Jan 21 10:18:59 PST 2006 > [INFO] Final Memory: 3M/6M > [INFO] > - > --- -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (SUREFIRE-103) 2.3-SNAPSHOT fails to deserialize an object due to ClassNotFoundException (regression)
[
http://jira.codehaus.org/browse/SUREFIRE-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter moved MSUREFIRE-150 to SUREFIRE-103:
-
Affects Version/s: (was: 2.3)
2.0 (2.2 plugin)
Fix Version/s: (was: 2.3)
2.3
Key: SUREFIRE-103 (was: MSUREFIRE-150)
Project: Maven Surefire (was: Maven 2.x Surefire Plugin)
> 2.3-SNAPSHOT fails to deserialize an object due to ClassNotFoundException
> (regression)
> --
>
> Key: SUREFIRE-103
> URL: http://jira.codehaus.org/browse/SUREFIRE-103
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 2.0 (2.2 plugin)
>Reporter: Andrew Perepelytsya
> Fix For: 2.3
>
> Attachments:
> FAILED_org.mule.test.transformers.SerializedUMOMessageTransformersTestCase.txt,
>
> FAILED_TEST-org.mule.test.transformers.SerializedUMOMessageTransformersTestCase.xml,
> org.mule.test.transformers.SerializedUMOMessageTransformersTestCase.txt,
> RELEASE-m2-run.txt, SNAPSHOT-m2-run.txt,
> TEST-org.mule.test.transformers.SerializedUMOMessageTransformersTestCase.xml
>
>
> Ok, I know how tricky it can be to explain such bug, but I'll try. We've
> switched to using 2.3-SNAPSHOT version of the plugin to get the fix for this
> error when test reports failed the build in case of test errors without
> generating any report. This part works fine now, but it has introduced a
> regression.
> I'm attaching the test failure reports(it always worked before). To reproduce
> the error (tricky part) - I can only think of checking out Mule project SVN
> source as of r2315 from http://svn.codehaus.org/mule/ What you need is only a
> top-level dir and mule-core.
> {panel}
> mvn test -Dtest=SerializedUMOMessageTransformersTestCase
> {panel}
> r2315 has 2.3-SNAPSHOT plugin version declared in a top-level pom. Change it
> to RELEASE, and the problem is again gone.
> I'm also attaching m2 debug output for SNAPSHOT and RELEASE runs, hope it
> helps.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (SUREFIRE-109) VM Forking manifests itself behind HTTP proxy
[ http://jira.codehaus.org/browse/SUREFIRE-109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter moved MSUREFIRE-161 to SUREFIRE-109: - Affects Version/s: (was: 2.3) 2.0 (2.2 plugin) Fix Version/s: (was: 2.3) 2.3 Component/s: (was: classloading) plugin Key: SUREFIRE-109 (was: MSUREFIRE-161) Project: Maven Surefire (was: Maven 2.x Surefire Plugin) > VM Forking manifests itself behind HTTP proxy > - > > Key: SUREFIRE-109 > URL: http://jira.codehaus.org/browse/SUREFIRE-109 > Project: Maven Surefire > Issue Type: Bug > Components: plugin >Affects Versions: 2.0 (2.2 plugin) > Environment: win2k, java 1.5 >Reporter: Ben Hood > Fix For: 2.3 > > Attachments: mvn_trace.txt > > > I have reason to believe that the forking behaviour of the surefire execution > has adverse effects when executed behind an HTTP proxy in combination with > DTD resolution (e.g. the loading of Spring beans). > Whilst using surefire to test a project (the acegi module from the mule > project, svn respo : http://svn.codehaus.org/mule/trunk/mule/modules/acegi , > revision 2859) I was getting DTD resolution errors (see attached trace). > I orginally posted this over at Spring: > http://opensource.atlassian.com/projects/spring/browse/SPR-2466. > Trying to get Eclipse to attach to the Maven debug process I set up (i.e. > running maven with MAVEN_OPTS="-Xdebug -Xnoagent > -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=8787"), I found out > that this won't work because the plugin executing the code forks a new VM. > After telling the maven surefire-plugin not to fork with this setting: > > > > org.apache.maven.plugins > maven-surefire-plugin > > never > > > > > the problem with the DTD resolution from Spring went away. > Under normal circumstances, the DTD should get resolved from within the > classpath, as it is bundled in the jar. > So therefore I conclude that it is indeed a maven classloading / VM issue and > not a Spring issue as first thought. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (SUREFIRE-106) Classloading problem for getting a resource
[ http://jira.codehaus.org/browse/SUREFIRE-106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter moved MSUREFIRE-115 to SUREFIRE-106: - Affects Version/s: (was: 1.5.3 (2.1.3 plugin)) (was: 2.0 (2.2 plugin)) 2.0 (2.2 plugin) Fix Version/s: (was: 2.3) 2.3 Key: SUREFIRE-106 (was: MSUREFIRE-115) Project: Maven Surefire (was: Maven 2.x Surefire Plugin) > Classloading problem for getting a resource > --- > > Key: SUREFIRE-106 > URL: http://jira.codehaus.org/browse/SUREFIRE-106 > Project: Maven Surefire > Issue Type: Bug >Affects Versions: 2.0 (2.2 plugin) > Environment: Maven 2.0.4 > Windows XP >Reporter: Wim Deblauwe > Assigned To: Kenney Westerhof >Priority: Blocker > Fix For: 2.3 > > Attachments: maven-surefire-plugin-2.2-UseSystemClassLoader.patch, > surefire-2.0-UseSystemClassLoader.patch, surefire-test.zip, > workaround-for-fork.zip > > > We are using Betwixt and some of our unit tests fail when run using > surefire, but run fine in IntelliJ or Maven 1. Betwixt looks for > descriptors with the name of the class + .betwixt to control how > something is written out in XML. It uses the construct: > myClass.getResource() to find the .betwixt file. > E.g. com.mycomp.MyClass -> com/mycomp/MyClass.betwixt > We have a betwixt file for the java.util.Date class. However, betwixt > seems to be unable to pick it up when using surefire. I have created a > small test that shows the problem and have attached it. > I tried with version 2.2 using different configurations (never, once, > pertest) and with version 2.1.3 (default configuration) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (SUREFIRE-115) Surefire-JUnit does not recognize "suite"-methods
[
http://jira.codehaus.org/browse/SUREFIRE-115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter moved MSUREFIRE-131 to SUREFIRE-115:
-
Affects Version/s: (was: 2.0 (2.2 plugin))
2.0 (2.2 plugin)
Fix Version/s: (was: 2.3)
2.3
Key: SUREFIRE-115 (was: MSUREFIRE-131)
Project: Maven Surefire (was: Maven 2.x Surefire Plugin)
> Surefire-JUnit does not recognize "suite"-methods
> -
>
> Key: SUREFIRE-115
> URL: http://jira.codehaus.org/browse/SUREFIRE-115
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 2.0 (2.2 plugin)
>Reporter: Philip Gerlach
> Fix For: 2.3
>
> Attachments: commons-events-pom.xml,
> maven-surefire-junit-trunk-412516.patch,
> maven-surefire-junit-trunk-492590.patch, surefire-test.zip
>
>
> Since Surefire-JUnit doesn't support JUnit4 yet, i tried to use a
> "suite"-method like
> --
> public static junit.framework.Test suite() {
>return new junit.framework.JUnit4TestAdapter(Foo.class);
> }
> -
> to run it, but Surefire-JUnit did not recognize these methods and treated
> them like PojoTests what obviously lead to TestFailures.
> So I fetched the source code from the repository and searched for the
> problem. I found two if-conditons in JUnitTestSet and JUnitDirectoryTestSuite
> that did not test for the "suite"-mechanism, so I wrote a new static method
> to test for this situation and integrated it in the if-conditions.
> Now the "suite"-methods work for my JUnit4 Tests and should do also for
> others ;-)
> The patch is attached.
> P.S. Since this it is the first time, I'm trying to bugfix something for an
> open source-project, please just let me know, if I have done something wrong
> with this process.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (SUREFIRE-113) surefire-providers-2.0.pom contains strange dependencies which generate error
[
http://jira.codehaus.org/browse/SUREFIRE-113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter moved MSUREFIRE-124 to SUREFIRE-113:
-
Fix Version/s: (was: 2.3)
2.3
Key: SUREFIRE-113 (was: MSUREFIRE-124)
Project: Maven Surefire (was: Maven 2.x Surefire Plugin)
> surefire-providers-2.0.pom contains strange dependencies which generate error
> -
>
> Key: SUREFIRE-113
> URL: http://jira.codehaus.org/browse/SUREFIRE-113
> Project: Maven Surefire
> Issue Type: Bug
>Reporter: Olivier Lamy
> Fix For: 2.3
>
> Attachments: log.txt, poms.zip
>
>
> This pom contains :
>
> ${project.groupId}
> surefire-api
> ${project.version}
>
> This generate strange error in certain case.
> I have replaced with :
>
> org.apache.maven.surefire
> surefire-api
> 2.0
> And works fine.
> The stack trace says
> WARNING] Unable to get resource from repository central
> (http://repo1.maven.org/maven2)
> [DEBUG] Unable to download the artifact from any repository
> Try downloading the file manually from the project website.
> Then, install it using the command:
> mvn install:install-file -DgroupId=org.apache.maven.surefire
> -DartifactId=surefire-api \
> -Dversion=2.4.1 -Dpackaging=jar -Dfile=/path/to/file
> Path to dependency:
> 1) dummy:dummy:jar:1.0
> 2) org.apache.maven.surefire:surefire-junit:jar:2.0
> 3) org.apache.maven.surefire:surefire-api:jar:2.4.1
> org.apache.maven.surefire:surefire-api:jar:2.4.1
> from the specified remote repositories:
> rec-ap2 (http://57.200.214.247/maven2),
> central (http://repo1.maven.org/maven2),
> continuum-repo-snapshots (http://57.200.214.247/continuum-repo/),
> apache.snapshots (http://svn.apache.org/maven-snapshot-repository),
> rec-ap2-snapshots (http://57.200.214.247/snapshots)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (SUREFIRE-104) unable to establish my own http protocol handler for unit tests
[ http://jira.codehaus.org/browse/SUREFIRE-104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter moved MSUREFIRE-123 to SUREFIRE-104: - Affects Version/s: (was: 2.0 (2.2 plugin)) 2.0 (2.2 plugin) Fix Version/s: (was: 2.3) 2.3 Key: SUREFIRE-104 (was: MSUREFIRE-123) Project: Maven Surefire (was: Maven 2.x Surefire Plugin) > unable to establish my own http protocol handler for unit tests > --- > > Key: SUREFIRE-104 > URL: http://jira.codehaus.org/browse/SUREFIRE-104 > Project: Maven Surefire > Issue Type: Bug >Affects Versions: 2.0 (2.2 plugin) > Environment: jse 5.0 (osx) >Reporter: Andy Fyfe > Fix For: 2.3 > > Attachments: protocol.zip > > > In order to establish my own http protocol handler, I set the system property > java.protocol.handler.pkgs and ensure that the tests require a fork. The > test runs fine under maven 1.0.2, but fails under maven 2.0.4. I have tried > both surefire 2.1.3 and 2.2, and both with the childDelegation option. > The test sees the system property properly set, but the test's protocol > handler is not actually used. > The attached zip file demonstrates this problem (run "maven test" and "mvn > test"). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (SUREFIRE-105) Documentation link on website does not point to surefire parameter docs
[ http://jira.codehaus.org/browse/SUREFIRE-105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter moved MSUREFIRE-160 to SUREFIRE-105: - Affects Version/s: (was: 2.0 (2.2 plugin)) 2.0 (2.2 plugin) Fix Version/s: (was: 2.3) 2.3 Component/s: (was: documentation) plugin Key: SUREFIRE-105 (was: MSUREFIRE-160) Project: Maven Surefire (was: Maven 2.x Surefire Plugin) > Documentation link on website does not point to surefire parameter docs > --- > > Key: SUREFIRE-105 > URL: http://jira.codehaus.org/browse/SUREFIRE-105 > Project: Maven Surefire > Issue Type: Bug > Components: plugin >Affects Versions: 2.0 (2.2 plugin) > Environment: irrelevant >Reporter: Harold Shinsato > Assigned To: fabrizio giustina >Priority: Minor > Fix For: 2.3 > > > On page http://maven.apache.org/plugins/maven-surefire-plugin/howto.html, and > the very end, there is a promise that "There are other parameters that you > can configure like testFailureIgnore, reportsDirectory, and so on. For full > documentation, click here." > Clicking "here" only leads back to the empty index page. Where are the docs > for the parameters? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (SUREFIRE-107) Odd Filename/inner class dependant behavior (and some junit tests)
[
http://jira.codehaus.org/browse/SUREFIRE-107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter moved MSUREFIRE-132 to SUREFIRE-107:
-
Affects Version/s: (was: 2.0 (2.2 plugin))
2.0 (2.2 plugin)
Fix Version/s: (was: 2.3)
2.3
Key: SUREFIRE-107 (was: MSUREFIRE-132)
Project: Maven Surefire (was: Maven 2.x Surefire Plugin)
> Odd Filename/inner class dependant behavior (and some junit tests)
> --
>
> Key: SUREFIRE-107
> URL: http://jira.codehaus.org/browse/SUREFIRE-107
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 2.0 (2.2 plugin)
>Reporter: Bryce Nordgren
>Priority: Minor
> Fix For: 2.3
>
> Attachments: surefire-junit-tests.patch
>
>
> I started this because I couldn't get maven 2 to recognize the tests which
> came with Jakarta commons-events. The problem boils down to the fact that
> there are many files/classes which implement tests, but they are all collated
> by a single TestSuite, called AllTestSuite.java, which extends TestCase. I
> am able to make maven run the tests merely by renaming this file to
> AllSuiteTest.java, and no other changes.
> I tried adding an {{}} element with the original name, but this did
> not pick up the tests. Surefire reliably reports that there are no tests to
> run.
> I did some remedial testing with junit tests (coded against the
> surefire-junit trunk). I was unable to reproduce this behavior, but I did
> uncover wierd behavior with TestCases as inner classes. The patch against
> surefire-junit trunk is included and includes only minor changes to the POM
> and the tests I wrote.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (SUREFIRE-118) Cannot override read-only parameter: classpathElements
[ http://jira.codehaus.org/browse/SUREFIRE-118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter moved MSUREFIRE-58 to SUREFIRE-118: Affects Version/s: (was: 1.5.2 (2.1.2 plugin)) 2.0 (2.2 plugin) Fix Version/s: (was: 2.3) 2.3 Key: SUREFIRE-118 (was: MSUREFIRE-58) Project: Maven Surefire (was: Maven 2.x Surefire Plugin) > Cannot override read-only parameter: classpathElements > -- > > Key: SUREFIRE-118 > URL: http://jira.codehaus.org/browse/SUREFIRE-118 > Project: Maven Surefire > Issue Type: Bug >Affects Versions: 2.0 (2.2 plugin) >Reporter: Jesper Zedlitz >Priority: Minor > Fix For: 2.3 > > Attachments: additionalClasspaths.patch > > > When calling "mvn site" on a multi-module project the goal "surefire:test" > fails for the second project: > Error configuring: org.apache.maven.plugins:maven-surefire-plugin. Reason: > ERROR: Cannot override read-only parameter: classpathElements in goal: > surefire:test > "mvn test" works and runs the tests on all modules. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (SUREFIRE-114) Surefire plugin throws NoSuchMethodException when errors occur during TestSetup decorator
[ http://jira.codehaus.org/browse/SUREFIRE-114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter moved MSUREFIRE-119 to SUREFIRE-114: - Affects Version/s: (was: 2.0 (2.2 plugin)) 2.0 (2.2 plugin) Fix Version/s: (was: 2.3) 2.3 Key: SUREFIRE-114 (was: MSUREFIRE-119) Project: Maven Surefire (was: Maven 2.x Surefire Plugin) > Surefire plugin throws NoSuchMethodException when errors occur during > TestSetup decorator > - > > Key: SUREFIRE-114 > URL: http://jira.codehaus.org/browse/SUREFIRE-114 > Project: Maven Surefire > Issue Type: Bug >Affects Versions: 2.0 (2.2 plugin) >Reporter: Dan Fabulich > Assigned To: Kenney Westerhof > Fix For: 2.3 > > Attachments: setup-bug.zip > > > I've included an example maven project, "setup-bug.zip". It was created by > doing "mvn archetype:create -DgroupId=com.mycompany.app > -DartifactId=setup-bug" and then modifying AppTest.java to use a "TestSetup" > decorator. > Normally JUnit runs your setUp()/tearDown() methods once for every test > method... so if you've got a TestCase with methods testFoo and testBar, JUnit > will normally run like this: setUp testFoo tearDown setUp testBar tearDown. > You can use a TestSetup decorator to run your setUp function just once for > the class: TestSetup.setUp testFoo testBar TestSetup.tearDown. > In the example given, the test's setup method throws a RuntimeException (as > tests sometimes do). Instead of handling this gracefully, Maven Surefire > throws a NoSuchMethodException as it attempts to call .getName() on the > TestSetup object (which isn't guaranteed to have a name). > Running com.mycompany.app.AppTest > org.apache.maven.surefire.booter.SurefireExecutionException: > com.mycompany.app.AppTest; nested exception is > java.lang.reflect.UndeclaredThrowableException: null; nested exception is > org.apache.maven.surefire.testset.TestSetFailedException: > com.mycompany.app.AppTest; nested exception is > java.lang.reflect.UndeclaredThrowableException: null > org.apache.maven.surefire.testset.TestSetFailedException: > com.mycompany.app.AppTest; nested exception is > java.lang.reflect.UndeclaredThrowableException: null > java.lang.reflect.UndeclaredThrowableException > at $Proxy0.addError(Unknown Source) > at junit.framework.TestResult.addError(TestResult.java:36) > at junit.framework.TestResult.runProtected(TestResult.java:133) > at junit.extensions.TestSetup.run(TestSetup.java:23) > 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:324) > at > org.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:210) > at > org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:135) > at > org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:122) > at org.apache.maven.surefire.Surefire.run(Surefire.java:129) > 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:324) > at > org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:225) > at > org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:747) > Caused by: java.lang.NoSuchMethodException: > com.mycompany.app.AppTest$AppTestSetup.getName() > at java.lang.Class.getMethod(Class.java:986) > at > org.apache.maven.surefire.junit.TestListenerInvocationHandler.getStackTraceWriter(TestListenerInvocationHandler.java:171) > at > org.apache.maven.surefire.junit.TestListenerInvocationHandler.handleAddError(TestListenerInvocationHandler.java:160) > at > org.apache.maven.surefire.junit.TestListenerInvocationHandler.invoke(TestListenerInvocationHandler.java:134) > ... 18 more > [INFO] > > [ERROR] BUILD FAILURE > [INFO] > > You can workaround this by hardcoding a public String getName() method on the > TestSetup object and ensuring that it's public. -- This message is automatically generated by JIRA. -
[jira] Moved: (SUREFIRE-111) argLine with -Xmx option has no effect
[ http://jira.codehaus.org/browse/SUREFIRE-111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter moved MSUREFIRE-129 to SUREFIRE-111: - Affects Version/s: (was: 2.0 (2.2 plugin)) 2.0 (2.2 plugin) Fix Version/s: (was: 2.3) 2.3 Key: SUREFIRE-111 (was: MSUREFIRE-129) Project: Maven Surefire (was: Maven 2.x Surefire Plugin) > argLine with -Xmx option has no effect > -- > > Key: SUREFIRE-111 > URL: http://jira.codehaus.org/browse/SUREFIRE-111 > Project: Maven Surefire > Issue Type: Bug >Affects Versions: 2.0 (2.2 plugin) >Reporter: Per Olesen > Fix For: 2.3 > > Attachments: OutOfMemoryError.log > > > In v2.1.3 of surefire plugin, this worked fine: > > org.apache.maven.plugins > maven-surefire-plugin > > pertest > -Xmx1024M > > > > But after doing a "mvn -U" and getting a v2.2 of the plugin, my tests starts > failing with OutOfMemoryException again. Doing a "mvn -X" shows me, that it > actually has read the option: > > [DEBUG] Configuring mojo > 'org.apache.maven.plugins:maven-surefire-plugin:2.2:test' --> > [DEBUG] (f) argLine = -Xmx1024M > > But maybe it is not applying the argline? > Forcing it to run with v2.1.3 makes everyting work again. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (SUREFIRE-117) ability to add dependency to jvm's classpath rather in surefirebooter classloader
[ http://jira.codehaus.org/browse/SUREFIRE-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter moved MSUREFIRE-121 to SUREFIRE-117: - Affects Version/s: (was: 2.0 (2.2 plugin)) 2.0 (2.2 plugin) Fix Version/s: (was: 2.3) 2.3 Key: SUREFIRE-117 (was: MSUREFIRE-121) Project: Maven Surefire (was: Maven 2.x Surefire Plugin) > ability to add dependency to jvm's classpath rather in surefirebooter > classloader > - > > Key: SUREFIRE-117 > URL: http://jira.codehaus.org/browse/SUREFIRE-117 > Project: Maven Surefire > Issue Type: Bug >Affects Versions: 2.0 (2.2 plugin) > Environment: xp >Reporter: Dan Tran > Assigned To: Kenney Westerhof > Fix For: 2.3 > > Attachments: MSUREFIRE-121-booter.patch, MSUREFIRE-121.plugin.patch, > MSUREFIRE-121.plugin.patch2, MSUREFIRE-121.plugin.patch3 > > > I have a usecase where i have a jar file got loaded by -Xbootclasspath, that > jar file then loads classes from another jar ( my dependency) > expected in the classpath. > The problem is that surefire plugin does not add my dependencies at JVM > commanline thru -classpath option, but after the JVM starts -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (SUREFIRE-110) classesDirectory set in pom.xml is ignored
[
http://jira.codehaus.org/browse/SUREFIRE-110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter moved MSUREFIRE-126 to SUREFIRE-110:
-
Affects Version/s: (was: 2.0 (2.2 plugin))
2.0 (2.2 plugin)
Fix Version/s: (was: 2.3)
2.3
Key: SUREFIRE-110 (was: MSUREFIRE-126)
Project: Maven Surefire (was: Maven 2.x Surefire Plugin)
> classesDirectory set in pom.xml is ignored
> --
>
> Key: SUREFIRE-110
> URL: http://jira.codehaus.org/browse/SUREFIRE-110
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 2.0 (2.2 plugin)
> Environment: Maven 2.0.4, Windows XP, jdk1.5.0_06
>Reporter: Roger Butenuth
>Priority: Critical
> Fix For: 2.3
>
> Attachments: maven-surefire-plugin-trunk-410868.patch,
> surefire-booter-trunk-410867.patch
>
>
> The configuration of classesDirectory in the surefire configuration in the
> pom is ignored. This bug is new in 2.2, everything worked fine with surefire
> 2.1.3.
> Snippet from pom:
>
> org.apache.maven.plugins
> maven-surefire-plugin
> 2.2
> true
>
> once
> xml
>
> ${project.build.directory}/emma-classes
> false
>
>
> Debug output:
> First, with surefire 2.1.3:
> [DEBUG] Configuring mojo
> 'org.apache.maven.plugins:maven-surefire-plugin:2.1.3:test' -->
> [DEBUG] (f) basedir = c:\example\server
> [DEBUG] (f) childDelegation = true
> [DEBUG] (f) classesDirectory = c:\example\server\target\emma-classes
> [DEBUG] (f) classpathElements = [c:\example\server\target\classes,
> c:\example\server\target\test-classes,
> C:\WINDOWS\Profiles\butenuth\.m2\repository\emma\emma\2.0.5312\emma-2.0.5312.jar,
>
> C:\WINDOWS\Profiles\butenuth\.m2\repository\junit\junit\3.8.1\junit-3.8.1.jar,
>
> C:\WINDOWS\Profiles\butenuth\.m2\repository\de\sdm\calculator\interface\1.0-SNAPSHOT\interface-1.0-SNAPSHOT.jar]
> [DEBUG] (f) forkMode = once
> [DEBUG] (f) jvm = java
> [DEBUG] (f) localRepository = [local] ->
> file://C:\WINDOWS\Profiles\butenuth\.m2\repository
> [DEBUG] (f) pluginArtifacts = [junit:junit:jar:3.8.1:runtime,
> org.apache.maven.surefire:surefire:jar:1.5.3:runtime,
> org.apache.maven.surefire:surefire-booter:jar:1.5.3:runtime,
> org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime,
> org.apache.maven:maven-plugin-api:jar:2.0:runtime,
> org.apache.maven:maven-artifact:jar:2.0:runtime]
> [DEBUG] (f) printSummary = false
> [DEBUG] (f) reportFormat = xml
> [DEBUG] (f) reportsDirectory = c:\example\server\target/surefire-reports
> [DEBUG] (f) testClassesDirectory = c:\example\server\target\test-classes
> [DEBUG] (f) testFailureIgnore = true
> [DEBUG] (f) useFile = true
> [DEBUG] -- end configuration --
> [INFO] [surefire:test]
> [INFO] Setting reports dir: c:\example\server\target/surefire-reports
> [DEBUG] Test Classpath :
> [DEBUG] c:\example\server\target\test-classes
> [DEBUG] c:\example\server\target\emma-classes <- my classes before
> default classes
> [DEBUG] c:\example\server\target\classes<- is it correct
> they are still in classpath?
> [DEBUG] c:\example\server\target\test-classes
> Next, with surefire 2.2, classesDirectory is completely ignored:
> [DEBUG] Configuring mojo
> 'org.apache.maven.plugins:maven-surefire-plugin:2.2:test' -->
> [DEBUG] (f) basedir = c:\example\server
> [DEBUG] (f) childDelegation = false
> [DEBUG] (f) classesDirectory = c:\example\server\target\emma-classes
> [DEBUG] (f) classpathElements = [c:\example\server\target\classes,
> c:\example\server\target\test-classes,
> C:\WINDOWS\Profiles\butenuth\.m2\repository\emma\emma\2.0.5312\emma-2.0.5312.jar,
>
> C:\WINDOWS\Profiles\butenuth\.m2\repository\junit\junit\3.8.1\junit-3.8.1.jar,
>
> C:\WINDOWS\Profiles\butenuth\.m2\repository\de\sdm\calculator\interface\1.0-SNAPSHOT\interface-1.0-SNAPSHOT.jar]
> [DEBUG] (f) disableXmlReport = false
> [DEBUG] (f) forkMode = once
> [DEBUG] (f) jvm = java
> [DEBUG] (f) localRepository = [local] ->
> file://C:\WINDOWS\Profiles\butenuth\.m2\repository
> [DEBUG] (f) parallel = false
> [DEBUG] (f) pluginArtifactMap =
> {org.codehaus.plexus:plexus-utils=org.codehaus.plexus:plexus-utils:jar:1.1:runtime,
>
> org.apache.maven.surefire:surefire-api=org.apache.maven.surefire:surefire-api:jar:2.0:runtime,
>
> org.apache.maven:maven-artifact=org.apache.maven:maven-artifact:jar:2.0:runtime,
>
> org.apache.maven:maven-plugin-api=org.apache.maven:maven-plugin-api:jar:2.0:runtime,
>
> org.apache.maven.surefire:surefire-booter=org.apache.maven.surefire:surefire-booter:jar:2.0:runtime}
> [DEBUG] (f) printSummary = false
> [DEBUG] (f) projectArti
[jira] Moved: (SUREFIRE-112) StringIndexOutOfBoundsException building reports from TestNG tests
[ http://jira.codehaus.org/browse/SUREFIRE-112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter moved MSUREFIRE-138 to SUREFIRE-112: - Affects Version/s: (was: 2.0 (2.2 plugin)) 2.0 (2.2 plugin) Fix Version/s: (was: 2.3) 2.3 Component/s: (was: TestNG support) plugin Key: SUREFIRE-112 (was: MSUREFIRE-138) Project: Maven Surefire (was: Maven 2.x Surefire Plugin) > StringIndexOutOfBoundsException building reports from TestNG tests > -- > > Key: SUREFIRE-112 > URL: http://jira.codehaus.org/browse/SUREFIRE-112 > Project: Maven Surefire > Issue Type: Bug > Components: plugin >Affects Versions: 2.0 (2.2 plugin) >Reporter: Howard M. Lewis Ship > Fix For: 2.3 > > Attachments: pom.xml, TEST-Application Services.xml, testng.xml > > > [INFO] Generate "Maven Surefire Report" report. > java.lang.StringIndexOutOfBoundsException: String index out of range: -1 > at java.lang.String.substring(String.java:1768) > at > org.codehaus.mojo.surefire.ReportTestSuite.startElement(ReportTestSuite.java:85) > at > com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startElement(AbstractSAXParser.java:533) > at > com.sun.org.apache.xerces.internal.impl.dtd.XMLDTDValidator.startElement(XMLDTDValidator.java:798) > at > com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanStartElement(XMLDocumentFragmentSc > annerImpl.java:878) > at > com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$ContentDispatcher.scanRootElementHook(XMLDocum > entScannerImpl.java:1157) > at > com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XML > DocumentFragmentScannerImpl.java:1794) > at > com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScanne > rImpl.java:368) > at > com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:834) > at > com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764) > at > com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148) > at > com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1242) > at javax.xml.parsers.SAXParser.parse(SAXParser.java:375) > at javax.xml.parsers.SAXParser.parse(SAXParser.java:311) > at > org.codehaus.mojo.surefire.ReportTestSuite.(ReportTestSuite.java:59) > at > org.codehaus.mojo.surefire.SurefireReportParser.parseXMLReportFiles(SurefireReportParser.java:42) > at > org.codehaus.mojo.surefire.SurefireReportGenerator.doGenerateReport(SurefireReportGenerator.java:44) > at > org.codehaus.mojo.surefire.SurefireReportMojo.executeReport(SurefireReportMojo.java:77) > at > org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:117) > It would be nice if the class name was included in the @name > attribute. In fact, this may be the source of the problem? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (SUREFIRE-108) Depencencies get precedence over test sources in classpath
[ http://jira.codehaus.org/browse/SUREFIRE-108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter moved MSUREFIRE-144 to SUREFIRE-108: - Affects Version/s: (was: 2.0 (2.2 plugin)) 2.0 (2.2 plugin) Fix Version/s: (was: 2.3) 2.3 Key: SUREFIRE-108 (was: MSUREFIRE-144) Project: Maven Surefire (was: Maven 2.x Surefire Plugin) > Depencencies get precedence over test sources in classpath > -- > > Key: SUREFIRE-108 > URL: http://jira.codehaus.org/browse/SUREFIRE-108 > Project: Maven Surefire > Issue Type: Bug >Affects Versions: 2.0 (2.2 plugin) >Reporter: Gilles Scokart > Fix For: 2.3 > > > Here is a concrete example : > I write a plugin for cruisecontrol. The cruise control jar contains a > log4J.properties. I have placed a log4j.properties in my test ressources > directory (I alsoe tried to place it in the main ressource directory). > When I run the test in eclipse, my log4j.property is used. When I run it > from maven, it is the log4j.properties contained in cruisecontrol.jar that is > used. > When I modify the cruisecontrol jar store in my repositry to remove its > log4j.properties, the log4j.properties of the test ressource directory is > used. > I also made a test with a class instead of a property file. I have > re-written a class defined in my dependency (same name, same package) in my > test source directory. The result is the same. In eclipse my class is used, > in maven, it is the class present in the dependency that is used. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (SUREFIRE-116) [regression] Test-resources not on classpath in forkMode always
[ http://jira.codehaus.org/browse/SUREFIRE-116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter moved MSUREFIRE-109 to SUREFIRE-116: - Affects Version/s: (was: 2.0 (2.2 plugin)) 2.0 (2.2 plugin) Fix Version/s: (was: 2.3) 2.3 Key: SUREFIRE-116 (was: MSUREFIRE-109) Project: Maven Surefire (was: Maven 2.x Surefire Plugin) > [regression] Test-resources not on classpath in forkMode always > --- > > Key: SUREFIRE-116 > URL: http://jira.codehaus.org/browse/SUREFIRE-116 > Project: Maven Surefire > Issue Type: Bug >Affects Versions: 2.0 (2.2 plugin) >Reporter: Geoffrey De Smet > Fix For: 2.3 > > > Before surefire plugin 2.2 at spring-richclient: > - our build succeeded > - ValidationResultsTests worked > - true due to an unrelated testcase: > HandlerTest > - pertest > Since 2.2: > - our build failes > - ValidtorResultTests failed too > - while it's still true (how can it > fail in that case?) > - pertest or always (same result) > The entire discussion (with stacktraces etc) on the user list is here: > http://article.gmane.org/gmane.comp.jakarta.turbine.maven.user/45131 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (SUREFIRE-119) With testng, incorrect test numbers are reported if setup method throws exception.
[ http://jira.codehaus.org/browse/SUREFIRE-119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter moved MSUREFIRE-140 to SUREFIRE-119: - Affects Version/s: (was: 2.0 (2.2 plugin)) 2.0 (2.2 plugin) Fix Version/s: (was: 2.3) 2.3 Key: SUREFIRE-119 (was: MSUREFIRE-140) Project: Maven Surefire (was: Maven 2.x Surefire Plugin) > With testng, incorrect test numbers are reported if setup method throws > exception. > -- > > Key: SUREFIRE-119 > URL: http://jira.codehaus.org/browse/SUREFIRE-119 > Project: Maven Surefire > Issue Type: Bug >Affects Versions: 2.0 (2.2 plugin) > Environment: Maven 2.0.4 > Java 1.5.0_06 > Windows XP >Reporter: Mark Reynolds >Priority: Minor > Fix For: 2.3 > > Attachments: project.zip > > > If an exception is thrown in a testng setup method, the testing related > numbers displayed by the plugin are incorrect. > For example... > Run a build with a single testng test class with three tests. If everything > passes, the output looks like this: > --- > T E S T S > --- > Running mypackage.TestClassOne > Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.046 sec > Results : > Tests run: 3, Failures: 0, Errors: 0, Skipped: 0 > If the same test class throws an exception in the setup method [annotated > with @Configuration(beforeTestMethod=true)], the output looks like this > --- > T E S T S > --- > Running mypackage.TestClassOne > Tests run: 6, Failures: 1, Errors: 0, Skipped: 5, Time elapsed: 0.156 sec > <<< FAILURE! > Results : > Tests run: 6, Failures: 1, Errors: 0, Skipped: 5 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (SUREFIRE-120) When you a JUnit TestSuite (with no test methods), no tests are run
[ http://jira.codehaus.org/browse/SUREFIRE-120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter moved MSUREFIRE-113 to SUREFIRE-120: - Affects Version/s: (was: 2.0 (2.2 plugin)) 2.0 (2.2 plugin) Fix Version/s: (was: 2.3) 2.3 Key: SUREFIRE-120 (was: MSUREFIRE-113) Project: Maven Surefire (was: Maven 2.x Surefire Plugin) > When you a JUnit TestSuite (with no test methods), no tests are run > - > > Key: SUREFIRE-120 > URL: http://jira.codehaus.org/browse/SUREFIRE-120 > Project: Maven Surefire > Issue Type: Bug >Affects Versions: 2.0 (2.2 plugin) >Reporter: Dan Fabulich > Assigned To: Mike Perham >Priority: Blocker > Fix For: 2.3 > > Attachments: MSUREFIRE-113.patch, suitebug.zip, > surefire-junit-2.1-SNAPSHOT.jar > > > In the attached Maven project, I started with the default Maven getting > started archetype and then created an AppTestSuite class, which extends > TestSuite and defines the static suite() method, but it has no test methods > of its own. Then I added an configuration that specified > **/AppTestSuite.java. But when I run > "mvn test", it claims that "There are no tests to run." > I've watched this happening in a debugger. The problem is in > surefire-api-2.0.jar in PojoTestSet , on line 249. When attempting to > acquire a list of the number of tests to run, instead of invoking the suite > method and counting the number of tests that come out, it's attempting to > discoverTestMethods on the object (methods whose names begin with "test*"), > which naturally won't work for suites. > This is a really serious issue that's going to block testing for us. (We > happen to attach a TestSetup decorator to our suite, so we do need to run > these tests as a suite rather than as individual test cases.) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (SUREFIRE-122) With forkmode once, XML reports are cumulative
[ http://jira.codehaus.org/browse/SUREFIRE-122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter moved MSUREFIRE-114 to SUREFIRE-122: - Affects Version/s: (was: 2.0 (2.2 plugin)) 2.0 (2.2 plugin) Fix Version/s: (was: 2.3) 2.3 Key: SUREFIRE-122 (was: MSUREFIRE-114) Project: Maven Surefire (was: Maven 2.x Surefire Plugin) > With forkmode once, XML reports are cumulative > -- > > Key: SUREFIRE-122 > URL: http://jira.codehaus.org/browse/SUREFIRE-122 > Project: Maven Surefire > Issue Type: Bug >Affects Versions: 2.0 (2.2 plugin) >Reporter: Daniel Kulp > Assigned To: Jason van Zyl > Fix For: 2.3 > > Attachments: XMLReporter-patch.txt > > > With forkmode set to once, the resulting XML files seem to include the test > results of all the tests in the previous suites as well as it's own. > pseudo example: > ATest is run, it has 2 test methods. The ATest.xml report says 2 tests run > and passed > BTest is run, it has 2 test methods. The BTest.xml report says 4 tests run > and passed. > CTest is run, it has 3 test methods. The CTest.xml report says 7 tests run > and passed. > When we use cruisecontrol or other reporting tools, it then say 13 tests run > and passed instead of 5. What's worse, if a test in ATest fails, it's > listed as a failure in all the tests so you get 3 tests failed, not 1. > Plus, it's harder to figure out which test suite reallly had the failure. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (SUREFIRE-128) Argline splits on spaces, should not when quoted
[
http://jira.codehaus.org/browse/SUREFIRE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter moved MSUREFIRE-139 to SUREFIRE-128:
-
Affects Version/s: (was: 2.0 (2.2 plugin))
2.0 (2.2 plugin)
Fix Version/s: (was: 2.3)
2.3
Key: SUREFIRE-128 (was: MSUREFIRE-139)
Project: Maven Surefire (was: Maven 2.x Surefire Plugin)
> Argline splits on spaces, should not when quoted
>
>
> Key: SUREFIRE-128
> URL: http://jira.codehaus.org/browse/SUREFIRE-128
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 2.0 (2.2 plugin)
>Reporter: Andrea Aime
>Priority: Blocker
> Fix For: 2.3
>
>
> I need to run surefire with the following argline:
> -javaagent:\"${user.home}\.m2\repository\aspectj\aspectjweaver\1.5.0\aspectjweaver-1.5.0.jar\"
> -javaagent:\"C:\Documents
> Settings\wolf\.m2\repository\aspectj\aspectjweaver\1.5.0\aspectjweaver-1.5.0.jar\"
> The problem is, ForkConfiguration splits the arguments blindly with
> StringUtils.split and the above turns into three
> separate arguments:
> -javaagent:"C:\Documents
> and
> Settings\wolf\.m2\repository\aspectj\aspectjweaver\1.5.0\aspectjweaver-1.5.0.jar"
> And the the vm complains it cannot find the jar C:\Documents.
> When quoted, the split should not happen!
> The following method proved to support quoting properly when splitting on
> spaces (I'm using it in UmlGraph):
> public static String[] tokenize(String s) {
> ArrayList r = new ArrayList();
> String remain = s;
> int n = 0, pos;
> remain = remain.trim();
> while (remain.length() > 0) {
> if (remain.startsWith("\"")) {
> // Field in quotes
> pos = remain.indexOf('"', 1);
> if (pos == -1)
> break;
> r.add(remain.substring(1, pos));
> if (pos + 1 < remain.length())
> pos++;
> } else {
> // Space-separated field
> pos = remain.indexOf(' ', 0);
> if (pos == -1) {
> r.add(remain);
> remain = "";
> } else
> r.add(remain.substring(0, pos));
> }
> remain = remain.substring(pos + 1);
> remain = remain.trim();
> // - is used as a placeholder for empy fields
> if (r.get(n).equals("-"))
> r.set(n, "");
> n++;
> }
> return r.toArray(new String[0]);
> }
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (SUREFIRE-125) Surefire finds test classes but ignores test methods and configuration methods with TestNG and includes tag
[ http://jira.codehaus.org/browse/SUREFIRE-125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter moved MSUREFIRE-134 to SUREFIRE-125: - Affects Version/s: (was: 2.0 (2.2 plugin)) 2.0 (2.2 plugin) Fix Version/s: (was: 2.3) 2.3 Key: SUREFIRE-125 (was: MSUREFIRE-134) Project: Maven Surefire (was: Maven 2.x Surefire Plugin) > Surefire finds test classes but ignores test methods and configuration > methods with TestNG and includes tag > --- > > Key: SUREFIRE-125 > URL: http://jira.codehaus.org/browse/SUREFIRE-125 > Project: Maven Surefire > Issue Type: Bug >Affects Versions: 2.0 (2.2 plugin) > Environment: Maven 2.0.4 > Surefire Plugin 2.2 > TestNG 4.7 jdk15 (using annotations) > Sun JDK 1.5_06 > Windows XP SP 2 >Reporter: Mark Reynolds > Assigned To: fabrizio giustina > Fix For: 2.3 > > Attachments: maven-surefire-plugin-patch.txt, maven2-testng.zip, > surefire-patch.txt > > > Attachment contains 2 projects which are identical except for how the test > cases are referenced. In one project they are referenced via a suite xml > file. In the second they are referenced using the includes tag. I believe > they should produce identical results. > Both projects find all 6 test classes, but only the one using a suite xml > file actually executes the configuration methods and test methods. The > project using an includes tag completely ignores the configuratiion methods > and test methods. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (SUREFIRE-121) System properties set on the command line get clobbered
[ http://jira.codehaus.org/browse/SUREFIRE-121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter moved MSUREFIRE-112 to SUREFIRE-121: - Affects Version/s: (was: 2.0 (2.2 plugin)) 2.0 (2.2 plugin) Fix Version/s: (was: 2.3) 2.3 Key: SUREFIRE-121 (was: MSUREFIRE-112) Project: Maven Surefire (was: Maven 2.x Surefire Plugin) > System properties set on the command line get clobbered > --- > > Key: SUREFIRE-121 > URL: http://jira.codehaus.org/browse/SUREFIRE-121 > Project: Maven Surefire > Issue Type: Bug >Affects Versions: 2.0 (2.2 plugin) > Environment: Linux, Maven 2.0.4, Sun JDK 1.5U5, bash 3.0 >Reporter: Brenton Leanhardt >Priority: Minor > Fix For: 2.3 > > > Some system properties get clobbered if you set them on the command line. For > example, > mvn clean test -Dtest=LoginTest -Dselenium.user=test32 > The 'test' system property will work, but the 'selenium.user' property will > be null at runtime. I have tried: > * hard coding the system property in the unit test, this worked fine. > * setting the system properties in the pom file, this worked fine also. > * tried an older version of the surefire plugin, this worked fine. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (SUREFIRE-124) Empty system property value from POM pluginManagement defaulting to the value of another property.
[
http://jira.codehaus.org/browse/SUREFIRE-124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter moved MSUREFIRE-111 to SUREFIRE-124:
-
Affects Version/s: (was: 1.5.3 (2.1.3 plugin))
2.0 (2.2 plugin)
Fix Version/s: (was: 2.3)
2.3
Key: SUREFIRE-124 (was: MSUREFIRE-111)
Project: Maven Surefire (was: Maven 2.x Surefire Plugin)
> Empty system property value from POM pluginManagement defaulting to the value
> of another property.
> --
>
> Key: SUREFIRE-124
> URL: http://jira.codehaus.org/browse/SUREFIRE-124
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 2.0 (2.2 plugin)
> Environment: Maven 2.0.4/Linux
>Reporter: Randy Watler
>Priority: Minor
> Fix For: 2.3
>
>
> The "test.empty" system property ends up with the value "defined.value".
>
> org.apache.maven.plugins
> maven-surefire-plugin
> 2.1.3
>
>
> test.defined
> defined.value
>
>
> test.empty
>
>
>
>
> [DEBUG] (f) systemProperties = {test.defined=defined.value,
> test.empty=defined.value}
> Here is the workaround, (test.empty ends up with value ""):
>
> org.apache.maven.plugins
> maven-surefire-plugin
> 2.1.3
>
>
> test.empty
>
>
>
> test.defined
> defined.value
>
>
>
> [DEBUG] (f) systemProperties = {test.defined=defined.value, test.empty=}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (SUREFIRE-123) SurefireBooter can initialize classloader with badly formed URLs
[ http://jira.codehaus.org/browse/SUREFIRE-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter moved MSUREFIRE-148 to SUREFIRE-123: - Fix Version/s: (was: 2.3) 2.3 Key: SUREFIRE-123 (was: MSUREFIRE-148) Project: Maven Surefire (was: Maven 2.x Surefire Plugin) > SurefireBooter can initialize classloader with badly formed URLs > > > Key: SUREFIRE-123 > URL: http://jira.codehaus.org/browse/SUREFIRE-123 > Project: Maven Surefire > Issue Type: Bug >Reporter: Jeremy Boynes > Assigned To: Brett Porter > Fix For: 2.3 > > Attachments: urlEncode.patch > > > In SurefireBooter.createClassLoader() the path is converted to a URL using > File f = new File( url ); > urls.add( f.toURL() ); > File.toURL does not perform URL encoding so the resulting URL may contain > invalid characters. This is an issue on Windows machines where the default > maven repository is in "C:\Documents and Settings\user\.m2\..." (the filename > contains spaces). If a test accesses a resource that is loaded from a > dependency jar then the URL returned to that test is malformed. > With JDK 1.4 this can be fixed using > urls.add( f.toURI().toURL() ); > as toURI() does encode the path. If surefire still needs to run under pre-1.4 > JVMs this would need to be explicitly encoded. I'm willing to supply a patch > for that if wanted. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (SUREFIRE-130) Support tests written in Jython
[ http://jira.codehaus.org/browse/SUREFIRE-130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter moved MSUREFIRE-122 to SUREFIRE-130: - Fix Version/s: (was: 2.3) 2.3 Key: SUREFIRE-130 (was: MSUREFIRE-122) Project: Maven Surefire (was: Maven 2.x Surefire Plugin) > Support tests written in Jython > --- > > Key: SUREFIRE-130 > URL: http://jira.codehaus.org/browse/SUREFIRE-130 > Project: Maven Surefire > Issue Type: New Feature >Reporter: Charlie Groves > Assigned To: fabrizio giustina > Fix For: 2.3 > > Attachments: jythonProvider.tar.gz, jythonProviderTest.tar.gz, > MSUREFIRE-122-maven-surefire-plugin.patch, > MSUREFIRE-122-surefire-providers.patch > > > I've written a first pass at a surefire-provider for JUnit and Python > unittest TestCases written in Jython. Before I continue any further I'd like > to make sure that the provider is wanted and that I'm heading in the right > direction. > To do the minimum to get it up and running, I've hooked into the > maven-surefire-plugin to hook my provider into the system somewhat like the > TestNG provider did. maven-surefire-plugin passes a path(defaults to > src/test/jython) to the provider. The provider searches the path for files > matching include patterns and loads those as Python modules. For every class > in the matching modules that extends junit or unittest TestCase, it makes a > SurefireTestSuite and exposes them for running. Sound like a decent approach? > To give it a spin, apply maven-surefire-plugin.patch, mvn install on the > surefire-jython project and run mvn test in jythonProviderTest. It's just > contains a single Junit testcase with a failing and passing test. > I haven't even checked what happens when the jython tests throw exceptions, > and I know there's alot to be done as far as making it a usable plugin, but I > felt like getting some feedback before continuing. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (SUREFIRE-131) Excluding tests with command line pattern
[
http://jira.codehaus.org/browse/SUREFIRE-131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter moved MSUREFIRE-135 to SUREFIRE-131:
-
Affects Version/s: (was: 2.0 (2.2 plugin))
2.0 (2.2 plugin)
Fix Version/s: (was: 2.3)
2.3
Key: SUREFIRE-131 (was: MSUREFIRE-135)
Project: Maven Surefire (was: Maven 2.x Surefire Plugin)
> Excluding tests with command line pattern
> -
>
> Key: SUREFIRE-131
> URL: http://jira.codehaus.org/browse/SUREFIRE-131
> Project: Maven Surefire
> Issue Type: New Feature
>Affects Versions: 2.0 (2.2 plugin)
> Environment: All environments running JUnit tests
>Reporter: Johannes Carlén
> Fix For: 2.3
>
>
> I'd like to be able to exclude certain tests from being run. An example of
> this could be a scenario where I'd like just the unit tests and not the
> integration tests to run. In our case, we name all integration test with the
> postfix "IntTest" instead of just "Test".
> This is now possible through configuring the plugin in the pom, however it is
> not possible to decide at the command line if I just like to run some tests
> and not all.
> Example of use with this implementation would be:
> mvn -Dexclude=*IntTest test
> which would run all tests - excluding those that ends with IntTest
> The amount of code needed for implementation is minimal. In
> SurefirePlugin.java:
> Just add a property - something like:
> /**
> * Specify this parameter to exclude test by their name. It follows
> * the same conventions as the test parameter.
> *
> * @parameter expression="${exclude}"
> *
> */
> private String exclude;
> Add this code at line 527
> if ( this.exclude != null )
> {
> String exclude = "**/" + this.exclude + ".java";
> excludes.add(exclude);
> getLog().debug( "Excluding test with pattern :" + exclude
> );
> }
> ...and that's all.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (SUREFIRE-129) add a property to skip tests execution (but not tests compilation)
[ http://jira.codehaus.org/browse/SUREFIRE-129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter moved MSUREFIRE-128 to SUREFIRE-129: - Affects Version/s: (was: 2.0 (2.2 plugin)) 2.0 (2.2 plugin) Fix Version/s: (was: 2.3) 2.3 Key: SUREFIRE-129 (was: MSUREFIRE-128) Project: Maven Surefire (was: Maven 2.x Surefire Plugin) > add a property to skip tests execution (but not tests compilation) > -- > > Key: SUREFIRE-129 > URL: http://jira.codehaus.org/browse/SUREFIRE-129 > Project: Maven Surefire > Issue Type: New Feature >Affects Versions: 2.0 (2.2 plugin) > Environment: all >Reporter: Olivier Lamy > Assigned To: Brett Porter > Fix For: 2.3 > > Attachments: MSUREFIRE-128.patch > > > Adding a simple property called maven.test.skip.exec in order to skip the > tests executions but not the test compilation (related to > http://jira.codehaus.org/browse/MJAR-43) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (SUREFIRE-127) Wrong issue-site URL on website
[ http://jira.codehaus.org/browse/SUREFIRE-127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter moved MSUREFIRE-152 to SUREFIRE-127: - Affects Version/s: (was: 1.5.3 (2.1.3 plugin)) (was: 1.5.2 (2.1.2 plugin)) (was: 1.5.1 (2.1.1 plugin)) 2.0 (2.2 plugin) Fix Version/s: (was: 2.3) 2.3 Key: SUREFIRE-127 (was: MSUREFIRE-152) Project: Maven Surefire (was: Maven 2.x Surefire Plugin) > Wrong issue-site URL on website > --- > > Key: SUREFIRE-127 > URL: http://jira.codehaus.org/browse/SUREFIRE-127 > Project: Maven Surefire > Issue Type: Bug >Affects Versions: 2.0 (2.2 plugin) > Environment: N/A >Reporter: David J. M. Karlsen > Fix For: 2.3 > > > Issue tracking (from > http://maven.apache.org/plugins/maven-surefire-plugin/issue-tracking.html) on > site defined as "http://jira.codehaus.org/browse/MPA";, should be > "http://jira.codehaus.org/browse/MSUREFIRE";. > Probably a POM inheritance error. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (SUREFIRE-134) Display location of test failures/errors on summary
[ http://jira.codehaus.org/browse/SUREFIRE-134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter moved MSUREFIRE-141 to SUREFIRE-134: - Fix Version/s: (was: 2.3) 2.3 Key: SUREFIRE-134 (was: MSUREFIRE-141) Project: Maven Surefire (was: Maven 2.x Surefire Plugin) > Display location of test failures/errors on summary > --- > > Key: SUREFIRE-134 > URL: http://jira.codehaus.org/browse/SUREFIRE-134 > Project: Maven Surefire > Issue Type: Improvement >Reporter: Mark Holster > Assigned To: Brett Porter >Priority: Minor > Fix For: 2.3 > > Attachments: error-failure-location.txt > > > Currently the surefire summary only indicates wheather or not there are test > failures/errors. On large projects with alot of tests, finding the test that > fails can be difficult. The attached patch add the locations (source and test > method) that causes the test failures/errors to the summary. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (SUREFIRE-135) when fork is enabled, Surefire should use the same JVM running Maven (i.e. use java.home sysprop), rather than expecting java to be in the system PATH
[
http://jira.codehaus.org/browse/SUREFIRE-135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter moved MSUREFIRE-127 to SUREFIRE-135:
-
Affects Version/s: (was: 2.0 (2.2 plugin))
2.0 (2.2 plugin)
Fix Version/s: (was: 2.3)
2.3
Key: SUREFIRE-135 (was: MSUREFIRE-127)
Project: Maven Surefire (was: Maven 2.x Surefire Plugin)
> when fork is enabled, Surefire should use the same JVM running Maven (i.e.
> use java.home sysprop), rather than expecting java to be in the system PATH
> --
>
> Key: SUREFIRE-135
> URL: http://jira.codehaus.org/browse/SUREFIRE-135
> Project: Maven Surefire
> Issue Type: Improvement
>Affects Versions: 2.0 (2.2 plugin)
>Reporter: Ian Springer
> Assigned To: Fabrice BELLINGARD
> Fix For: 2.3
>
>
> Here's the thread from maven-users:
> +1
> (Haven't been bitten by this yet, but it is certainly not intuitive.)
> On 6/1/06, Mike Perham <[EMAIL PROTECTED]> wrote:
> > +1
> >
> > -Original Message-
> > From: Ian Springer [mailto:[EMAIL PROTECTED]
> > Sent: Thursday, June 01, 2006 2:36 PM
> > To: Maven Users List
> > Subject: RE: forking surefire VM
> >
> > I think the default should be the same JVM that launched Maven (i.e.
> > System.getProperty("java.home") + File.pathSeparator + "bin" +
> > File.pathSeparator + "java"). This seems more intuitive.
> >
> > -Original Message-
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
> > Carlos Sanchez
> > Sent: Thursday, June 01, 2006 3:20 PM
> > To: Maven Users List
> > Subject: Re: forking surefire VM
> >
> > http://maven.apache.org/plugins/maven-surefire-plugin/test-mojo.html
> >
> > jvm: Option to specify the jvm (or path to the java executable) to use
> > with the forking options. For the default we will assume that java is
> > in the path.
> >
> >
> > On 6/1/06, Ruel Loehr <[EMAIL PROTECTED]> wrote:
> > > I've seen this as well. There is an option for setting which vm to
> > use, I had to use it work around the problem. Maybe you could open a
> > jira issue for it.
> > >
> > > Ruel Loehr
> > > JBoss QA
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (SUREFIRE-126) ComponentLookupException when running unit tests from Eclipse IDE
[ http://jira.codehaus.org/browse/SUREFIRE-126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter moved MSUREFIRE-118 to SUREFIRE-126: - Fix Version/s: (was: 2.3) 2.3 Key: SUREFIRE-126 (was: MSUREFIRE-118) Project: Maven Surefire (was: Maven 2.x Surefire Plugin) > ComponentLookupException when running unit tests from Eclipse IDE > - > > Key: SUREFIRE-126 > URL: http://jira.codehaus.org/browse/SUREFIRE-126 > Project: Maven Surefire > Issue Type: Bug > Environment: Maven 2.0.4, Eclipse 3.2RC4 >Reporter: Rahul Thakur > Fix For: 2.3 > > Attachments: DatabaseMojoTest.java > > > When I unit tests for a Mojo from within Eclipse I get the following Exception > snip --- > org.codehaus.plexus.component.repository.exception.ComponentLookupException: > Component descriptor cannot be found in the component repository: > org.apache.maven.plugin.Mojoorg.apache.maven.plugins:plexus-plugin:1.0.0-SNAPSHOT:greet. > at > org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:323) > at > org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:440) > at org.codehaus.plexus.PlexusTestCase.lookup(PlexusTestCase.java:222) > at > org.apache.maven.plugin.testing.AbstractMojoTestCase.lookupMojo(AbstractMojoTestCase.java:164) > at > org.codehaus.plexus.m2.PlexusGreeterMojoTest.testMojoLookup(PlexusGreeterMojoTest.java:40) > 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 junit.framework.TestCase.runTest(TestCase.java:154) > at junit.framework.TestCase.runBare(TestCase.java:127) > at junit.framework.TestResult$1.protect(TestResult.java:106) > at junit.framework.TestResult.runProtected(TestResult.java:124) > at junit.framework.TestResult.run(TestResult.java:109) > at junit.framework.TestCase.run(TestCase.java:118) > at junit.framework.TestSuite.runTest(TestSuite.java:208) > at junit.framework.TestSuite.run(TestSuite.java:203) > at > org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:128) > at > org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) > at > org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:457) > at > org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:670) > at > org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386) > at > org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196) > --- snip - > Attached the Mojo test that was blowing up -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (SUREFIRE-136) The plugin does not use JAVA_HOME variable and launches default JVM
[ http://jira.codehaus.org/browse/SUREFIRE-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter moved MSUREFIRE-156 to SUREFIRE-136: - Fix Version/s: (was: 2.3) 2.3 Key: SUREFIRE-136 (was: MSUREFIRE-156) Project: Maven Surefire (was: Maven 2.x Surefire Plugin) > The plugin does not use JAVA_HOME variable and launches default JVM > --- > > Key: SUREFIRE-136 > URL: http://jira.codehaus.org/browse/SUREFIRE-136 > Project: Maven Surefire > Issue Type: Improvement > Environment: Windows 2000, Maven 2.0.4 >Reporter: Andrey Somov > Assigned To: Carlos Sanchez >Priority: Minor > Fix For: 2.3 > > Attachments: MSUREFIREREP-25.log > > > The plugin does not use JAVA_HOME variable and launches default JVM (in this > case default is not defined): > [INFO] Surefire report directory: > D:\tools\workspace\DB2Monster\monster-axis\target\surefire-reports > 'java' is not recognized as an internal or external command, > operable program or batch file. > [INFO] > > [ERROR] BUILD FAILURE > [INFO] > > JAVA_HOME does not necessary point to the default JVM. > The plugin shall use the same JVM as Maven. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (SUREFIRE-132) Running tests in JAR files
[ http://jira.codehaus.org/browse/SUREFIRE-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter moved MSUREFIRE-107 to SUREFIRE-132: - Affects Version/s: (was: 2.0 (2.2 plugin)) 2.0 (2.2 plugin) Fix Version/s: (was: 2.3) 2.3 Key: SUREFIRE-132 (was: MSUREFIRE-107) Project: Maven Surefire (was: Maven 2.x Surefire Plugin) > Running tests in JAR files > -- > > Key: SUREFIRE-132 > URL: http://jira.codehaus.org/browse/SUREFIRE-132 > Project: Maven Surefire > Issue Type: New Feature >Affects Versions: 2.0 (2.2 plugin) >Reporter: Hugo Palma >Priority: Minor > Fix For: 2.3 > > > AFAIK it's not possible to run tests that are in a dependency jar and not in > the tested module source files. > It would be great if this was possible. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (SUREFIRE-133) Review Plugin Documentation
[ http://jira.codehaus.org/browse/SUREFIRE-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter moved MSUREFIRE-147 to SUREFIRE-133: - Fix Version/s: (was: 2.3) 2.3 Key: SUREFIRE-133 (was: MSUREFIRE-147) Project: Maven Surefire (was: Maven 2.x Surefire Plugin) > Review Plugin Documentation > --- > > Key: SUREFIRE-133 > URL: http://jira.codehaus.org/browse/SUREFIRE-133 > Project: Maven Surefire > Issue Type: Task >Reporter: Allan Ramirez > Assigned To: Allan Ramirez > Fix For: 2.3 > > Original Estimate: 1 day > Time Spent: 23 hours > Remaining Estimate: 1 hour > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (SUREFIRE-139) JUnit 4 integration
[ http://jira.codehaus.org/browse/SUREFIRE-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter moved MSUREFIRE-84 to SUREFIRE-139: Fix Version/s: (was: 2.3) 2.3 Component/s: (was: Junit 4.x support) plugin Key: SUREFIRE-139 (was: MSUREFIRE-84) Project: Maven Surefire (was: Maven 2.x Surefire Plugin) > JUnit 4 integration > --- > > Key: SUREFIRE-139 > URL: http://jira.codehaus.org/browse/SUREFIRE-139 > Project: Maven Surefire > Issue Type: Wish > Components: plugin >Reporter: Shinobu Kawai >Priority: Minor > Fix For: 2.3 > > > It would be great if we could integrate surefire plugin with JUnit 4 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (SUREFIRE-138) Add option to redirect stdout from tests to a file
[ http://jira.codehaus.org/browse/SUREFIRE-138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter moved MSUREFIRE-136 to SUREFIRE-138: - Affects Version/s: (was: 1.5.3 (2.1.3 plugin)) (was: 2.0 (2.2 plugin)) 2.0 (2.2 plugin) Fix Version/s: (was: 2.3) 2.3 Key: SUREFIRE-138 (was: MSUREFIRE-136) Project: Maven Surefire (was: Maven 2.x Surefire Plugin) > Add option to redirect stdout from tests to a file > -- > > Key: SUREFIRE-138 > URL: http://jira.codehaus.org/browse/SUREFIRE-138 > Project: Maven Surefire > Issue Type: Improvement >Affects Versions: 2.0 (2.2 plugin) >Reporter: Carlos Sanchez > Assigned To: Carlos Sanchez > Fix For: 2.3 > > Attachments: MSUREFIRE-136-maven-surefire-plugin.patch, > MSUREFIRE-136-surefire-booter.patch > > > Instead of > --- > T E S T S > --- > Running org.apache.maven.wagon.providers.webdav.WebDavWagonTest > 17:59:47.546 EVENT Stopping Acceptor > ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=10007] > 17:59:47.546 EVENT Stopped SocketListener on 0.0.0.0:10007 > 17:59:47.546 EVENT Stopped ServletHttpContext[/dav] > 17:59:47.546 EVENT Stopped [EMAIL PROTECTED] > Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.406 sec > show just > --- > T E S T S > --- > Running org.apache.maven.wagon.providers.webdav.WebDavWagonTest > Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.406 sec -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (SUREFIRE-137) provide option to list all of the test cases which failed when running a build
[ http://jira.codehaus.org/browse/SUREFIRE-137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter moved MSUREFIRE-143 to SUREFIRE-137: - Fix Version/s: (was: 2.3) 2.3 Key: SUREFIRE-137 (was: MSUREFIRE-143) Project: Maven Surefire (was: Maven 2.x Surefire Plugin) > provide option to list all of the test cases which failed when running a build > -- > > Key: SUREFIRE-137 > URL: http://jira.codehaus.org/browse/SUREFIRE-137 > Project: Maven Surefire > Issue Type: Improvement >Reporter: james strachan > Fix For: 2.3 > > Attachments: MSUREFIRE-143-maven-surefire-plugin.patch, > MSUREFIRE-143-maven-surefire-plugin.patch, MSUREFIRE-143-surefire-api.patch, > MSUREFIRE-143-surefire-api.patch > > > Lots of projects I work on have large numbers of test cases; the execution of > the tests takes up many screens. We are often see the output... > Results : > Tests run: 1496, Failures: 0, Errors: 5, Skipped: 0 > [INFO] > > [ERROR] BUILD FAILURE > [INFO] > > [INFO] There are test failures. > [INFO] > > [INFO] For more information, run Maven with the -e switch > [INFO] > > > Then we have to page up manually grepping for <<< FAILURE which can take a > while. It would be good to just list the failed test cases in the output -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (SUREFIRE-140) Add Parameter that the output of the test to System.out only appears in the surefire logfiles
[ http://jira.codehaus.org/browse/SUREFIRE-140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter moved MSUREFIRE-158 to SUREFIRE-140: - Affects Version/s: (was: 2.0 (2.2 plugin)) Fix Version/s: (was: 2.4) 2.4 Key: SUREFIRE-140 (was: MSUREFIRE-158) Project: Maven Surefire (was: Maven 2.x Surefire Plugin) > Add Parameter that the output of the test to System.out only appears in the > surefire logfiles > - > > Key: SUREFIRE-140 > URL: http://jira.codehaus.org/browse/SUREFIRE-140 > Project: Maven Surefire > Issue Type: New Feature >Reporter: Fabian Bauschulte > Fix For: 2.4 > > > Many Tests are using a logger that prints to the console. Sometimes you > cannot see the summary because there a lot of logging messages. It would be > very helpful to have a parameter, that this output only appears in the > surefire log files. If a test fails, you have the output in the place you > need it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (SUREFIRE-143) Wishing for a gui flag to run the junit swing testrunner like in maven 1
[ http://jira.codehaus.org/browse/SUREFIRE-143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter moved MSUREFIRE-146 to SUREFIRE-143: - Affects Version/s: (was: 2.0 (2.2 plugin)) Fix Version/s: (was: 2.4) 2.4 Key: SUREFIRE-143 (was: MSUREFIRE-146) Project: Maven Surefire (was: Maven 2.x Surefire Plugin) > Wishing for a gui flag to run the junit swing testrunner like in maven 1 > - > > Key: SUREFIRE-143 > URL: http://jira.codehaus.org/browse/SUREFIRE-143 > Project: Maven Surefire > Issue Type: Wish >Reporter: Meghan Claire Pike > Fix For: 2.4 > > > Wishing for a gui flag to run the junit swing testrunner like in maven 1 > test:ui in maven 2.0 would be sweet. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (SUREFIRE-142) Create new surefire:integration-test mojo for IT
[ http://jira.codehaus.org/browse/SUREFIRE-142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter moved MSUREFIRE-50 to SUREFIRE-142: Affects Version/s: (was: 1.5.1 (2.1.1 plugin)) Fix Version/s: (was: 2.4) 2.4 Key: SUREFIRE-142 (was: MSUREFIRE-50) Project: Maven Surefire (was: Maven 2.x Surefire Plugin) > Create new surefire:integration-test mojo for IT > > > Key: SUREFIRE-142 > URL: http://jira.codehaus.org/browse/SUREFIRE-142 > Project: Maven Surefire > Issue Type: Task >Reporter: Vincent Massol > Fix For: 2.4 > > > See > http://www.nabble.com/-PROPOSAL-Integration-testing-proposal-for-Maven-2.0.x-t980095.html -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (SUREFIRE-141) Surefire should provide a pluggable means to specify a custom provider
[ http://jira.codehaus.org/browse/SUREFIRE-141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter moved MSUREFIRE-159 to SUREFIRE-141: - Affects Version/s: (was: 2.3) Fix Version/s: (was: 2.4) 2.4 Key: SUREFIRE-141 (was: MSUREFIRE-159) Project: Maven Surefire (was: Maven 2.x Surefire Plugin) > Surefire should provide a pluggable means to specify a custom provider > -- > > Key: SUREFIRE-141 > URL: http://jira.codehaus.org/browse/SUREFIRE-141 > Project: Maven Surefire > Issue Type: New Feature >Reporter: Micah Whitacre >Priority: Critical > Fix For: 2.4 > > > The current way that surefire determines which provider to use is hard coded > and based on a project's dependencies. I would like to write a custom > surefire-provider and be able to specify to use that provider without having > to patch the surefire plugin. In my case I want to write a surefire-provider > that will run Eclipse PDE Junits which wouldn't neccessarily have a specific > dependency listed -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (SUREFIRE-144) Ability to have surefire to setup additional environment variable in fork mode
[ http://jira.codehaus.org/browse/SUREFIRE-144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter moved MSUREFIRE-44 to SUREFIRE-144: Affects Version/s: (was: 1.5.1 (2.1.1 plugin)) Fix Version/s: (was: 1.5.2 (2.1.2 plugin)) 1.5.2 (2.1.2 plugin) Key: SUREFIRE-144 (was: MSUREFIRE-44) Project: Maven Surefire (was: Maven 2.x Surefire Plugin) > Ability to have surefire to setup additional environment variable in fork > mode > --- > > Key: SUREFIRE-144 > URL: http://jira.codehaus.org/browse/SUREFIRE-144 > Project: Maven Surefire > Issue Type: Bug > Environment: xp, windows, solaris, linux >Reporter: Dan Tran > Fix For: 1.5.2 (2.1.2 plugin) > > Attachments: MSUREFILE-44-plugin.patch, > MSUREFILE-44-surefile-booter.patch > > > In order to run JNI test case, we need to setup share library env path -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (SUREFIRE-146) forkMode=pertest fails to call setUp
[ http://jira.codehaus.org/browse/SUREFIRE-146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter moved MSUREFIRE-20 to SUREFIRE-146: Affects Version/s: (was: 1.5.1 (2.1.1 plugin)) Fix Version/s: (was: 1.5.2 (2.1.2 plugin)) 1.5.2 (2.1.2 plugin) Complexity: (was: Intermediate) Key: SUREFIRE-146 (was: MSUREFIRE-20) Project: Maven Surefire (was: Maven 2.x Surefire Plugin) > forkMode=pertest fails to call setUp > > > Key: SUREFIRE-146 > URL: http://jira.codehaus.org/browse/SUREFIRE-146 > Project: Maven Surefire > Issue Type: Bug > Environment: Maven 2.0.1 running maven-surefire-plugin 2.1.1 >Reporter: Matt Brozowski > Assigned To: Carlos Sanchez >Priority: Blocker > Fix For: 1.5.2 (2.1.2 plugin) > > Attachments: surefire-sample.zip > > > The surefire plugin is failing to call the setUp method when > forkMode=pertest. I will attach a very simple test project that will make it > easy to verify this. Below is the 'trimmed' output if mvn -X > -DforkMode=pertest test for the sample project. I suspect that the tearDown > method is not getting called either but could not think of a simple way to > verify that case for a 'pertest' configuration. > [DEBUG] Configuring mojo > 'org.apache.maven.plugins:maven-surefire-plugin:2.1.1:test' --> > [DEBUG] (f) basedir = /Users/brozow/tmp/surefire-sample > [DEBUG] (f) childDelegation = true > [DEBUG] (f) classesDirectory = > /Users/brozow/tmp/surefire-sample/target/classes > [DEBUG] (f) classpathElements = > [/Users/brozow/tmp/surefire-sample/target/classes, > /Users/brozow/tmp/surefire-sample/target/test-classes, > /Users/brozow/.m2/repository/junit/junit/3.8.1/junit-3.8.1.jar] > [DEBUG] (f) forkMode = pertest > [DEBUG] (f) jvm = java > [DEBUG] (f) localRepository = [local] -> file:///Users/brozow/.m2/repository > [DEBUG] (f) pluginArtifacts = [junit:junit:jar:3.8.1, > org.apache.maven.surefire:surefire-booter:jar:1.5, > org.apache.maven.surefire:surefire:jar:1.5.1, > org.codehaus.plexus:plexus-utils:jar:1.0.4, > org.apache.maven:maven-plugin-api:jar:2.0, > org.apache.maven:maven-artifact:jar:2.0] > [DEBUG] (f) printSummary = true > [DEBUG] (f) reportFormat = brief > [DEBUG] (f) reportsDirectory = > /Users/brozow/tmp/surefire-sample/target/surefire-reports > [DEBUG] (f) testClassesDirectory = > /Users/brozow/tmp/surefire-sample/target/test-classes > [DEBUG] (f) useFile = true > [DEBUG] -- end configuration -- > [INFO] [surefire:test] > --- > T E S T S > --- > [surefire] Running com.example.SurefireTest > [surefire] Tests run: 1, Failures: 1, Errors: 0, Time elapsed: 0.051 sec > FAILURE !! > Results : > [surefire] Tests run: 1, Failures: 1, Errors: 0 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (SUREFIRE-145) Remove or fix strange "battery = null" messages displayed on the console
[ http://jira.codehaus.org/browse/SUREFIRE-145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter moved MSUREFIRE-37 to SUREFIRE-145: Fix Version/s: (was: 1.5.2 (2.1.2 plugin)) 1.5.2 (2.1.2 plugin) Key: SUREFIRE-145 (was: MSUREFIRE-37) Project: Maven Surefire (was: Maven 2.x Surefire Plugin) > Remove or fix strange "battery = null" messages displayed on the console > > > Key: SUREFIRE-145 > URL: http://jira.codehaus.org/browse/SUREFIRE-145 > Project: Maven Surefire > Issue Type: Bug >Reporter: Vincent Massol > Assigned To: Carlos Sanchez > Fix For: 1.5.2 (2.1.2 plugin) > > > Here's an example: > [INFO] [surefire:test] > [INFO] Setting reports dir: > C:\dev\cargo\trunk\core\api\module\target/surefire-reports > battery = null(org.apache.maven.surefire.battery.DirectoryBattery) > --- > T E S T S > --- > battery = null(org.apache.maven.surefire.battery.JUnitBattery) > battery = null(org.apache.maven.surefire.battery.JUnitBattery) > battery = null(org.apache.maven.surefire.battery.JUnitBattery) > battery = null(org.apache.maven.surefire.battery.JUnitBattery) > battery = null(org.apache.maven.surefire.battery.JUnitBattery) > battery = null(org.apache.maven.surefire.battery.JUnitBattery) > battery = null(org.apache.maven.surefire.battery.JUnitBattery) > battery = null(org.apache.maven.surefire.battery.JUnitBattery) > battery = null(org.apache.maven.surefire.battery.JUnitBattery) > battery = null(org.apache.maven.surefire.battery.JUnitBattery) > battery = null(org.apache.maven.surefire.battery.JUnitBattery) > battery = null(org.apache.maven.surefire.battery.JUnitBattery) > battery = null(org.apache.maven.surefire.battery.JUnitBattery) > battery = null(org.apache.maven.surefire.battery.JUnitBattery) > battery = null(org.apache.maven.surefire.battery.JUnitBattery) > battery = null(org.apache.maven.surefire.battery.JUnitBattery) > [surefire] Running org.codehaus.cargo.module.application.ApplicationXmlTest > [surefire] Tests run: 9, Failures: 0, Errors: 0, Time elapsed: 0,471 sec > [surefire] Running > org.codehaus.cargo.module.application.ApplicationXmlVersionTest > [surefire] Tests run: 8, Failures: 0, Errors: 0, Time elapsed: 0,02 sec > [surefire] Running org.codehaus.cargo.module.DtdTest > [surefire] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 0,03 sec > [surefire] Running org.codehaus.cargo.module.ejb.EjbJarXmlTest > [surefire] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 0,07 sec > [surefire] Running org.codehaus.cargo.module.ejb.orion.OracleEjbJarXmlTest > [surefire] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 0,05 sec > [surefire] Running > org.codehaus.cargo.module.ejb.weblogic.WeblogicEjbJarXmlTest > [surefire] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 0,07 sec > [surefire] Running org.codehaus.cargo.module.ejb.websphere.IbmEjbJarBndXmiTest > [surefire] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,01 sec > [surefire] Running org.codehaus.cargo.module.JarArchiveTest > [surefire] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 0,01 sec > [surefire] Running org.codehaus.cargo.module.webapp.orion.OracleWebXmlTest > [surefire] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,02 sec > [surefire] Running org.codehaus.cargo.module.webapp.WarArchiveTest > [surefire] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 0,11 sec > [surefire] Running org.codehaus.cargo.module.webapp.weblogic.WeblogicXmlTest > [surefire] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 0,02 sec > [surefire] Running org.codehaus.cargo.module.webapp.websphere.IbmWebBndXmiTest > [surefire] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0 sec > [surefire] Running org.codehaus.cargo.module.webapp.WebXmlMergerTest > [surefire] Tests run: 23, Failures: 0, Errors: 0, Time elapsed: 0,481 sec > [surefire] Running org.codehaus.cargo.module.webapp.WebXmlTest > [surefire] Tests run: 64, Failures: 0, Errors: 0, Time elapsed: 0,501 sec > [surefire] Running org.codehaus.cargo.module.webapp.WebXmlVersionTest > [surefire] Tests run: 8, Failures: 0, Errors: 0, Time elapsed: 0,02 sec > [surefire] Running org.codehaus.cargo.module.XmlEntityResolverTest > [surefire] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0 sec -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (SUREFIRE-148) Old syntax for specifying system properties should still be supported
[ http://jira.codehaus.org/browse/SUREFIRE-148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter moved MSUREFIRE-64 to SUREFIRE-148: Affects Version/s: (was: 1.5.3 (2.1.3 plugin)) Fix Version/s: (was: 1.5.3 (2.1.3 plugin)) 1.5.3 (2.1.3 plugin) Key: SUREFIRE-148 (was: MSUREFIRE-64) Project: Maven Surefire (was: Maven 2.x Surefire Plugin) > Old syntax for specifying system properties should still be supported > - > > Key: SUREFIRE-148 > URL: http://jira.codehaus.org/browse/SUREFIRE-148 > Project: Maven Surefire > Issue Type: Bug >Reporter: Vincent Massol > Assigned To: Dan Tran > Fix For: 1.5.3 (2.1.3 plugin) > > > The old syntax is: > > myprop > myvalue > > New syntax (the one currently in SVN trunk): > myvalue > I much prefer the new compact syntax but we should offer backward > compatibility for existing users. > Please keep the new syntax somehow though (I've modified my builds to use it > and I would hate to have to go back to the old syntax! :-)). > Thanks -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (SUREFIRE-149) workingDirectory in fork mode is not working
[ http://jira.codehaus.org/browse/SUREFIRE-149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter moved MSUREFIRE-60 to SUREFIRE-149: Affects Version/s: (was: 1.5.3 (2.1.3 plugin)) Fix Version/s: (was: 1.5.3 (2.1.3 plugin)) 1.5.3 (2.1.3 plugin) Key: SUREFIRE-149 (was: MSUREFIRE-60) Project: Maven Surefire (was: Maven 2.x Surefire Plugin) > workingDirectory in fork mode is not working > > > Key: SUREFIRE-149 > URL: http://jira.codehaus.org/browse/SUREFIRE-149 > Project: Maven Surefire > Issue Type: Bug > Environment: xp, linux >Reporter: Dan Tran > Assigned To: Jason van Zyl >Priority: Blocker > Fix For: 1.5.3 (2.1.3 plugin) > > Attachments: MSUREFIRE-60.patch > > > MSUREFIRE-52 resets jvm working directory (user.dir) to the old value. We > need to make sure > cli's workingDirectory and system property's user.dir to have the same value > in fork mode -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (SUREFIRE-147) Surefire plugin is failing
[ http://jira.codehaus.org/browse/SUREFIRE-147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter moved MSUREFIRE-38 to SUREFIRE-147: Fix Version/s: (was: 1.5.2 (2.1.2 plugin)) 1.5.2 (2.1.2 plugin) Key: SUREFIRE-147 (was: MSUREFIRE-38) Project: Maven Surefire (was: Maven 2.x Surefire Plugin) > Surefire plugin is failing > -- > > Key: SUREFIRE-147 > URL: http://jira.codehaus.org/browse/SUREFIRE-147 > Project: Maven Surefire > Issue Type: Bug > Environment: maven-surefire-plugin-2.1.2-20060102.001705-3 >Reporter: Vincent Massol > Assigned To: Emmanuel Venisse > Fix For: 1.5.2 (2.1.2 plugin) > > > C:\dev\maven\trunks\plugins\maven-clover-plugin>mvn clean install > [INFO] Scanning for projects... > [INFO] > > [INFO] Building Maven Clover Plugin > [INFO]task-segment: [clean, install] > [INFO] > > [INFO] snapshot org.apache.maven.plugins:maven-clean-plugin:2.0.1-SNAPSHOT: > checking for updates from snapshots > [INFO] [clean:clean] > [INFO] Deleting directory > C:\dev\maven\trunks\plugins\maven-clover-plugin\target > [INFO] snapshot org.apache.maven.plugins:maven-plugin-plugin:2.0.1-SNAPSHOT: > checking for updates from snapshots > [INFO] snapshot org.apache.maven.plugins:maven-resources-plugin:2.2-SNAPSHOT: > checking for updates from snapshots > [INFO] snapshot > org.apache.maven.plugins:maven-compiler-plugin:2.0.1-SNAPSHOT: checking for > updates from snapshots > [INFO] snapshot > org.apache.maven.plugins:maven-surefire-plugin:2.1.2-SNAPSHOT: checking for > updates from snapshots > Downloading: > http://snapshots.maven.codehaus.org/maven2/org/apache/maven/plugins/maven-surefire-plugin/2.1.2-SNAPSHOT/maven-surefi > re-plugin-2.1.2-20060102.001705-3.pom > 2K downloaded > Downloading: > http://snapshots.maven.codehaus.org/maven2/org/apache/maven/plugins/maven-surefire-plugin/2.1.2-SNAPSHOT/maven-surefi > re-plugin-2.1.2-20060102.001705-3.jar > 8K downloaded > [INFO] snapshot org.apache.maven.plugins:maven-jar-plugin:2.1-SNAPSHOT: > checking for updates from snapshots > [INFO] snapshot org.apache.maven.plugins:maven-install-plugin:2.1-SNAPSHOT: > checking for updates from snapshots > [INFO] [plugin:descriptor] > [INFO] Using 2 extractors. > [INFO] Applying extractor for language: java > [INFO] Extractor for language: java found 4 mojo descriptors. > [INFO] Applying extractor for language: bsh > [INFO] Extractor for language: bsh found 0 mojo descriptors. > [INFO] [resources:resources] > [INFO] Using default encoding to copy filtered resources. > [WARNING] > Artifact junit:junit:jar:3.8.1 retains local scope 'test' overriding > broader scope 'compile' > given by a dependency. If this is not intended, modify or remove the > local scope. > [INFO] snapshot org.codehaus.plexus:plexus-compiler-javac:1.6-SNAPSHOT: > checking for updates from snapshots > [INFO] snapshot org.codehaus.plexus:plexus-compilers:1.6-SNAPSHOT: checking > for updates from snapshots > [INFO] snapshot org.codehaus.plexus:plexus-compiler:1.6-SNAPSHOT: checking > for updates from snapshots > [INFO] snapshot org.codehaus.plexus:plexus-compiler-api:1.6-SNAPSHOT: > checking for updates from snapshots > [INFO] snapshot org.codehaus.plexus:plexus-compiler-manager:1.6-SNAPSHOT: > checking for updates from snapshots > [INFO] [compiler:compile] > Compiling 5 source files to > C:\dev\maven\trunks\plugins\maven-clover-plugin\target\classes > [INFO] [resources:testResources] > [INFO] Using default encoding to copy filtered resources. > [INFO] [compiler:testCompile] > Compiling 1 source file to > C:\dev\maven\trunks\plugins\maven-clover-plugin\target\test-classes > [INFO] snapshot org.apache.maven.surefire:surefire:1.5.2-SNAPSHOT: checking > for updates from snapshots > Downloading: > http://snapshots.maven.codehaus.org/maven2/org/apache/maven/surefire/surefire/1.5.2-SNAPSHOT/surefire-1.5.2-20060101. > 232902-4.pom > 751b downloaded > [INFO] snapshot org.apache.maven.surefire:surefire-booter:1.5.2-SNAPSHOT: > checking for updates from snapshots > Downloading: > http://snapshots.maven.codehaus.org/maven2/org/apache/maven/surefire/surefire-booter/1.5.2-SNAPSHOT/surefire-booter-1 > .5.2-20060102.001256-4.pom > 805b downloaded > Downloading: > http://snapshots.maven.codehaus.org/maven2/org/apache/maven/surefire/surefire/1.5.2-SNAPSHOT/surefire-1.5.2-20060101. > 232902-4.jar > 60K downloaded > Downloading: > http://snapshots.maven.codehaus.org/maven2/org/apache/maven/surefire/surefire-booter/1.5.2-SNAPSHOT/surefire-booter-1 > .5.2-20060102.001256-4.jar > 10K downloaded > [INFO] [surefire:test] > [INFO] Setting r
