[jira] Updated: (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 ] Kristian Rosenvold updated SUREFIRE-143: Component/s: Maven 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 > Components: Maven Surefire Plugin >Reporter: Meghan Claire Pike > Fix For: Backlog > > > 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] Updated: (SUREFIRE-130) Support tests written in Jython
[ http://jira.codehaus.org/browse/SUREFIRE-130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold updated SUREFIRE-130: Component/s: Maven 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 > Components: Maven Surefire Plugin >Reporter: Charlie Groves > Fix For: Backlog > > 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] Updated: (SUREFIRE-184) [PATCH] make the basedir system property optional
[ http://jira.codehaus.org/browse/SUREFIRE-184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold updated SUREFIRE-184: Component/s: Maven Surefire Plugin > [PATCH] make the basedir system property optional > - > > Key: SUREFIRE-184 > URL: http://jira.codehaus.org/browse/SUREFIRE-184 > Project: Maven Surefire > Issue Type: Improvement > Components: Maven Surefire Plugin > Environment: tested on Win2K with cygwin and JDK1.5, but this is > indifferent. >Reporter: Antoine Levy-Lambert > Fix For: Backlog > > Attachments: patch.txt > > > I wanted to run the ant testcases using the maven-surefire-plugin (I actually > built all the ant jars using maven). > The problem is that the plugin sets a system property basedir that ant cannot > override. Since the BuildFileTest s are heavily dependent upon this property > that ant normally sets to be the directory of the build file, most tests fail > ... > Here a patch adding the possibility not to set the basedir by setting a > configuration attribute omitbasedir to true. > The pom.xml of maven-surefile-plugin was also missing a dependency to > surefire-api (or at least I needed to add this to build properly). > Regards, > Antoine -- 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-515) Executes nested classes that are not tests
[ http://jira.codehaus.org/browse/SUREFIRE-515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold updated SUREFIRE-515: Component/s: Junit 4.x support JUnit 3.x support Unsure if this is 3 or 4. Probably fixed.needs retest > Executes nested classes that are not tests > -- > > Key: SUREFIRE-515 > URL: http://jira.codehaus.org/browse/SUREFIRE-515 > Project: Maven Surefire > Issue Type: Bug > Components: JUnit 3.x support, Junit 4.x support >Affects Versions: 2.4.3 >Reporter: Thomas Diesler > > When using excludes like this > > maven-surefire-plugin > > > org/jboss/bpm/pattern/**/*APITest.java > > > org/jboss/bpm/pattern/** > > > > surefire executes the nested classes > Running > org.jboss.bpm.pattern.control.synchronization.SynchronizationTest$TaskB > Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec > Running > org.jboss.bpm.pattern.control.synchronization.SynchronizationTest$TaskC > Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 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] Updated: (SUREFIRE-454) To set testResource base on indivdule JUnit test
[ http://jira.codehaus.org/browse/SUREFIRE-454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold updated SUREFIRE-454: Component/s: Maven Surefire Plugin > To set testResource base on indivdule JUnit test > > > Key: SUREFIRE-454 > URL: http://jira.codehaus.org/browse/SUREFIRE-454 > Project: Maven Surefire > Issue Type: New Feature > Components: Maven Surefire Plugin >Reporter: Jia Lu > Fix For: Backlog > > > Hi, > I am wondering if you can add a feature to allow user to set the testResource > base on individule JUnit test or provide some hook before running individule > JUnit test that I can use ant run plugin to copy resource file for this test. > e.g. there are two JUnit tests A and B, Test A uses different resource files > from Test B. so we don't want use testResource to copy same resource file > for both A and B. We want something can copy resource file depend on which > JUnit test runs. > Thank you. -- 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-627) maven surefire additionalClasspathElements single test
[
http://jira.codehaus.org/browse/SUREFIRE-627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Rosenvold updated SUREFIRE-627:
Component/s: Maven Surefire Plugin
> maven surefire additionalClasspathElements single test
> --
>
> Key: SUREFIRE-627
> URL: http://jira.codehaus.org/browse/SUREFIRE-627
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
> Environment: MAC
>Reporter: Yaman Ustuntas
>
> hi,
> I have one main and one test config file which is shared by several maven
> projects. While testing, I am specifying the classpath to the directory where
> the test config file is.
> This works fine if the whole project is tested/build but it doesn't work
> while running single tests. The config file is not found in the classpath.
> here is the config:
>
> maven-surefire-plugin
>
>
>${project.parent.basedir}/conf/test
>
>
>
> any ideas why surefire ignores the property for running single tests?
> thank you
--
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-677) Improve param documentation
[ http://jira.codehaus.org/browse/SUREFIRE-677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold updated SUREFIRE-677: Fix Version/s: 2.7.2 > Improve param documentation > --- > > Key: SUREFIRE-677 > URL: http://jira.codehaus.org/browse/SUREFIRE-677 > Project: Maven Surefire > Issue Type: Bug > Components: documentation, Maven Failsafe Plugin, Maven Surefire > Plugin >Affects Versions: 2.7.1 > Environment: n/a >Reporter: Anders Hammar >Priority: Minor > Fix For: 2.7.2 > > Attachments: maven-failsafe-plugin.patch, maven-surefire-plugin.patch > > > Update/improve param documentation. -- 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-678) Fixes to the upgrade check doc
[ http://jira.codehaus.org/browse/SUREFIRE-678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold updated SUREFIRE-678: Fix Version/s: 2.7.2 > Fixes to the upgrade check doc > -- > > Key: SUREFIRE-678 > URL: http://jira.codehaus.org/browse/SUREFIRE-678 > Project: Maven Surefire > Issue Type: Improvement > Components: documentation >Affects Versions: 2.7.1 > Environment: n/a >Reporter: Anders Hammar > Fix For: 2.7.2 > > Attachments: upgradeCheckDoc.patch > > > Fixing some grammar and making some improvements to the doc update of > SUREFIRE-670. -- 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: (SCM-589) Upgrade Plexus Utils to avoid filehandle leak
[ http://jira.codehaus.org/browse/SCM-589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed SCM-589. Resolution: Fixed fixed rev 1052805. > Upgrade Plexus Utils to avoid filehandle leak > - > > Key: SCM-589 > URL: http://jira.codehaus.org/browse/SCM-589 > Project: Maven SCM > Issue Type: Bug >Affects Versions: 1.4 > Environment: linux >Reporter: Grant Gardner >Assignee: Olivier Lamy >Priority: Minor > Fix For: 1.5 > > > Plexus-utils 1.5.6 has a bad filehandle leak (non destroyed Runtime.exec) in > CommandLine.addSystemEnvironment() which is called by the VSS, svnexe and the > AccuRev providers. > 2.0.5 seems to work. -- 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: (SCM-590) Subversion --trust-server-cert option
[ http://jira.codehaus.org/browse/SCM-590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed SCM-590. Resolution: Fixed fixed rev 1052814 and 1052815. > Subversion --trust-server-cert option > - > > Key: SCM-590 > URL: http://jira.codehaus.org/browse/SCM-590 > Project: Maven SCM > Issue Type: Improvement > Components: maven-scm-provider-svn >Affects Versions: 1.4 >Reporter: Olivier Lamy >Assignee: Olivier Lamy > Fix For: 1.5 > > > It would be useful to be able to pass the --trust-server-cert option to the > svn command. -- 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: (MRELEASE-628) Subversion --trust-server-cert option
[ http://jira.codehaus.org/browse/MRELEASE-628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed MRELEASE-628. - Resolution: Fixed Fix Version/s: 2.2 Assignee: Olivier Lamy fixed tru SCM fix. > Subversion --trust-server-cert option > - > > Key: MRELEASE-628 > URL: http://jira.codehaus.org/browse/MRELEASE-628 > Project: Maven 2.x Release Plugin > Issue Type: Improvement > Components: perform, prepare >Affects Versions: 2.1 >Reporter: John Turner >Assignee: Olivier Lamy > Fix For: 2.2 > > > It would be useful to be able to pass the --trust-server-cert option to the > svn command. -- 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
