[jira] (SUREFIRE-847) surefire cannot run single testng test

2012-07-09 Thread Nikita Makarov (JIRA)

[ 
https://jira.codehaus.org/browse/SUREFIRE-847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=303013#comment-303013
 ] 

Nikita Makarov commented on SUREFIRE-847:
-

Where can I get 2.13-SNAPSHOT

 surefire cannot run single testng test 
 ---

 Key: SUREFIRE-847
 URL: https://jira.codehaus.org/browse/SUREFIRE-847
 Project: Maven Surefire
  Issue Type: Bug
  Components: TestNG support
Affects Versions: 2.12
 Environment: Windows 7 x64
Reporter: Nikita Makarov
Priority: Minor
 Fix For: 2.13

 Attachments: surefire-847_example.zip


 Trying to run single testng test class with command mvn test -Dtest=SomeTest 
 fails with message 
  [ERROR] Failed to execute goal 
 org.apache.maven.plugins:maven-surefire-plugin:2.12:test (default-test) on 
 project web-integration-tests: No tests were executed!
   (Set -DfailIfNoTests=false to ignore this error.) - [Help 1].

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (MEAR-153) Skinny Modules -- not just WARs

2012-07-09 Thread Roland Asmann (JIRA)

 [ 
https://jira.codehaus.org/browse/MEAR-153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Roland Asmann updated MEAR-153:
---

Attachment: AbstractEarModule.java.patch

Added a new attachment, please disregard the previous attachment!

This change makes the 'libDir' a parameter on the modules, so you can create 
skinny versions of your modules.

 Skinny Modules -- not just WARs
 ---

 Key: MEAR-153
 URL: https://jira.codehaus.org/browse/MEAR-153
 Project: Maven 2.x Ear Plugin
  Issue Type: Improvement
Affects Versions: 2.7
Reporter: Roland Asmann
 Attachments: AbstractEarModule.java.patch, SarModule.java.patch


 Currently it is only possible to have the plugin filter WARs to get them 
 'skinny', however this could be very useful for other modules as well!
 In my project I have both a WAR and a SAR that should share several 
 libraries. As standalone artifacts, they should both package it themselves, 
 but in the deployed EAR I get classloading-errors when they don't have the 
 libs shared in the EAR.
 I traced a solution to the method 'EarModule.getLibDir()', which is only 
 implemented with a value in the 'WebModule'-subclass.
 Since I am not familiar with all the module-types, I attached a solution that 
 ONLY handles the SarModule, but this can probably used in all other Modules 
 that contain libs as well.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (MEAR-154) SAR-Module dependencies are packaged inside the EAR

2012-07-09 Thread Roland Asmann (JIRA)

[ 
https://jira.codehaus.org/browse/MEAR-154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=303029#comment-303029
 ] 

Roland Asmann commented on MEAR-154:


Why didn't you say so in the first place!?

OK, I'll think about filing this in Maven core...

 SAR-Module dependencies are packaged inside the EAR
 ---

 Key: MEAR-154
 URL: https://jira.codehaus.org/browse/MEAR-154
 Project: Maven 2.x Ear Plugin
  Issue Type: Bug
Reporter: Roland Asmann
Assignee: Stéphane Nicoll

 When I package a SAR-Module into my EAR, all depencies to the SAR are 
 resolved and added to the EAR. The problem here is that these dependencies 
 are already packaged inside the SAR, making for a very large EAR and 
 sometimes classloading-problems!

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (MNGSITE-157) Download links not working

2012-07-09 Thread Marc Guenther (JIRA)
Marc Guenther created MNGSITE-157:
-

 Summary: Download links not working
 Key: MNGSITE-157
 URL: https://jira.codehaus.org/browse/MNGSITE-157
 Project: Maven Project Web Site
  Issue Type: Bug
 Environment: MacOSX 10.6, Safari 5.1.5
Reporter: Marc Guenther


Would it be possible to fix the download links on 
http://maven.apache.org/download.html for maven .tar.gz files?

When I click on apache-maven-3.0.4-bin.tar.gz, I get a file 
{{apache-maven-3.0.4-bin.tar.gz}} which is 6591bytes long. Uncompressing from 
the Finder does not work and closer inspection reveals that this is in fact a 
gzipped html file, which points you to the list of mirrors.

This has been confusing new users for years now. Does not seem too hard to 
fix...

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (MPMD-153) Support PMD/CPD against code in databases or accessible via URLs

2012-07-09 Thread Stuart Turton (JIRA)
Stuart Turton created MPMD-153:
--

 Summary: Support PMD/CPD against code in databases or accessible 
via URLs 
 Key: MPMD-153
 URL: https://jira.codehaus.org/browse/MPMD-153
 Project: Maven 2.x PMD Plugin
  Issue Type: Wish
Reporter: Stuart Turton


DB2, Oracle, Postgres etc. support procedural languages. 

Adding a CodeLoader that takes a Reader or an InputStream or URL would increase 
the number of possible sources of examinable code.   

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (MPMD-154) Support PLSQL language

2012-07-09 Thread Stuart Turton (JIRA)
Stuart Turton created MPMD-154:
--

 Summary: Support PLSQL language
 Key: MPMD-154
 URL: https://jira.codehaus.org/browse/MPMD-154
 Project: Maven 2.x PMD Plugin
  Issue Type: Wish
  Components: CPD, PMD
Reporter: Stuart Turton
Priority: Minor
 Attachments: PldocAST.jj, PldocAST.jjt, plsql-cpd.tgz

DB2, Oracle, EnterpriseDB and TimesTen databases support PLSQL.

Attached is the PLSQL (plus some SQL*Plus) Tokenizer extracted from the PLDoc 
project.



StuMacBook:pmd-plsql$ ./cpd_example.sh PLDoc(CPD) version: ${project.version}
LanguageFactory info - attempting to load language plsql
Searching for net.sourceforge.pmd.cpd.PlsqlLanguage using 
net.sourceforge.pmd.cpd.LanguageFactory
.. net.sourceforge.pmd.cpd.PlsqlLanguage using 
ClassLoader=sun.misc.Launcher$AppClassLoader@558fe7c3
.. net.sourceforge.pmd.cpd.PlsqlLanguage using 
sun.misc.Launcher.AppClassLoader
LanguageFactory warn - failed to load language Plsql
LanguageFactory info - attempting to load language PLSQL
Searching for net.sourceforge.pmd.cpd.PLSQLLanguage using 
net.sourceforge.pmd.cpd.LanguageFactory
.. net.sourceforge.pmd.cpd.PLSQLLanguage using 
ClassLoader=sun.misc.Launcher$AppClassLoader@558fe7c3
.. net.sourceforge.pmd.cpd.PLSQLLanguage using 
sun.misc.Launcher.AppClassLoader
Object(s) like ANONYMOUS. do not exist or system does not have enough 
permissions (SELECT_CATALOG_ROLE role).
PLSQLTokenizer: ignoreComments==true
PLSQLTokenizer: ignoreIdentifiers==true
PLSQLTokenizer: ignoreLiterals==true
Object(s) like APEX_PUBLIC_USER. do not exist or system does not have 
enough permissions (SELECT_CATALOG_ROLE role).
Object(s) like APPQOSSYS. do not exist or system does not have enough 
permissions (SELECT_CATALOG_ROLE role).
Object(s) like BI. do not exist or system does not have enough permissions 
(SELECT_CATALOG_ROLE role).
Object(s) like CACHEADM. do not exist or system does not have enough 
permissions (SELECT_CATALOG_ROLE role).
Object(s) like DIP. do not exist or system does not have enough permissions 
(SELECT_CATALOG_ROLE role).
Object(s) like HR_TRIG. do not exist or system does not have enough 
permissions (SELECT_CATALOG_ROLE role).
Object(s) like MDDATA. do not exist or system does not have enough 
permissions (SELECT_CATALOG_ROLE role).
Object(s) like MGMT_VIEW. do not exist or system does not have enough 
permissions (SELECT_CATALOG_ROLE role).
Object(s) like ORDDATA. do not exist or system does not have enough 
permissions (SELECT_CATALOG_ROLE role).
Object(s) like OWBSYS. do not exist or system does not have enough 
permissions (SELECT_CATALOG_ROLE role).
Object(s) like OWBSYS_AUDIT. do not exist or system does not have enough 
permissions (SELECT_CATALOG_ROLE role).
Object(s) like system.SH do not exist or system does not have enough 
permissions (SELECT_CATALOG_ROLE role).
Object(s) like SI_INFORMTN_SCHEMA. do not exist or system does not have 
enough permissions (SELECT_CATALOG_ROLE role).
Object(s) like SPATIAL_CSW_ADMIN_USR. do not exist or system does not have 
enough permissions (SELECT_CATALOG_ROLE role).
Object(s) like SPATIAL_WFS_ADMIN_USR. do not exist or system does not have 
enough permissions (SELECT_CATALOG_ROLE role).
Object(s) like TIMESTEN. do not exist or system does not have enough 
permissions (SELECT_CATALOG_ROLE role).
Object(s) like XS. do not exist or system does not have enough permissions 
(SELECT_CATALOG_ROLE role).

StuMacBook:pmd-plsql sturton$ 


 



--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (MNGSITE-157) Download links not working

2012-07-09 Thread Dennis Lundberg (JIRA)

[ 
https://jira.codehaus.org/browse/MNGSITE-157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=303101#comment-303101
 ] 

Dennis Lundberg commented on MNGSITE-157:
-

This is by design. The links go to the mirror system used by the ASF.

What we could do it put a note on the download page telling people to not 
right-click the links and choose Download link as...

 Download links not working
 --

 Key: MNGSITE-157
 URL: https://jira.codehaus.org/browse/MNGSITE-157
 Project: Maven Project Web Site
  Issue Type: Bug
 Environment: MacOSX 10.6, Safari 5.1.5
Reporter: Marc Guenther

 Would it be possible to fix the download links on 
 http://maven.apache.org/download.html for maven .tar.gz files?
 When I click on apache-maven-3.0.4-bin.tar.gz, I get a file 
 {{apache-maven-3.0.4-bin.tar.gz}} which is 6591bytes long. Uncompressing from 
 the Finder does not work and closer inspection reveals that this is in fact a 
 gzipped html file, which points you to the list of mirrors.
 This has been confusing new users for years now. Does not seem too hard to 
 fix...

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (MRELEASE-733) Can't release when specifying a workingDirectory - Base directory is a file. Using base directory as POM location.

2012-07-09 Thread Robert Scholte (JIRA)

 [ 
https://jira.codehaus.org/browse/MRELEASE-733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Scholte updated MRELEASE-733:


Description: 
My project is under source control in clearcase UCM.
When I update the {{maven-release-plugin}} from {{2.0}} to {{2.2.2}} my release 
fails. With version {{2.0}} everything works fine.

The configuration of the release plugin is like this:
{code:xml}
plugin
  groupIdorg.apache.maven.plugins/groupId
  artifactIdmaven-release-plugin/artifactId
  version2.2.2/version 
  configuration
workingDirectory${release.root}//workingDirectory  
  /configuration 
/plugin
{code}

I need to set the {{workingDirectory}} because in clearcase you can not perform 
the checkout of the tag inside the view. So in my jenkins I'll set 
release.root=${WORKSPACE}\checkout   

SCM looks like this
{code:xml}
scm
connectionscm:clearcase||load 
\Orbis_Reports|\Orbis_Project_Vob|MavenDeploymentEvaluation/connection
developerConnectionscm:clearcase||load 
\Orbis_Reports|\Orbis_Project_Vob|MavenDeploymentEvaluation/developerConnection
/scm
{code}
The project is very simple, i.e. one single pom.xml

{noformat}
[INFO] Invoking perform goals in directory 
D:\Views\hudson_slave\workspace\TestMax\test-reports-1.0.14-SNAPSHOT\Orbis_Reports
[INFO] Executing goals 'deploy'...
[DEBUG] Using ${maven.home} of: 'c:\dev\tools\apache-maven-3.0.3'.
[WARNING] Base directory is a file. Using base directory as POM location.
[DEBUG] Specified POM file is not named 'pom.xml'. Using the '-f' command-line 
option to accommodate non-standard filename...
[DEBUG] Executing: cmd.exe /X /C C:\dev\tools\apache-maven-3.0.3\bin\mvn.bat 
-B -X -D maven.repo.local=D:\m2 -f Orbis_Reports -s 
D:\Profiles\axiaz\.m2\settings.xml -D performRelease=true -P 
staging,orbis.developer deploy
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 3:10.172s
[INFO] Finished at: Thu Jan 26 22:50:07 CET 2012
[INFO] Final Memory: 4M/15M
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-release-plugin:2.2.1:perform (default-cli) on 
project test-reports: Error executing Maven. Working directory 
D:\Views\hudson_slave\workspace\TestMax\test-reports-1.0.14-SNAPSHOT\Orbis_Reports\Orbis_Reports
 does not exist! - [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal 
org.apache.maven.plugins:maven-release-plugin:2.2.1:perform (default-cli) on 
project test-reports: Error executing Maven.
at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)
at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at 
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at 
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: org.apache.maven.plugin.MojoExecutionException: Error executing 
Maven.
at 
org.apache.maven.plugins.release.PerformReleaseMojo.execute(PerformReleaseMojo.java:136)
at 
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
... 19 more
Caused by: org.apache.maven.shared.release.ReleaseExecutionException: Error 

[jira] (MNGSITE-157) Download links not working

2012-07-09 Thread Olivier Lamy (JIRA)

 [ 
https://jira.codehaus.org/browse/MNGSITE-157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Olivier Lamy reassigned MNGSITE-157:


Assignee: Olivier Lamy

 Download links not working
 --

 Key: MNGSITE-157
 URL: https://jira.codehaus.org/browse/MNGSITE-157
 Project: Maven Project Web Site
  Issue Type: Bug
 Environment: MacOSX 10.6, Safari 5.1.5
Reporter: Marc Guenther
Assignee: Olivier Lamy

 Would it be possible to fix the download links on 
 http://maven.apache.org/download.html for maven .tar.gz files?
 When I click on apache-maven-3.0.4-bin.tar.gz, I get a file 
 {{apache-maven-3.0.4-bin.tar.gz}} which is 6591bytes long. Uncompressing from 
 the Finder does not work and closer inspection reveals that this is in fact a 
 gzipped html file, which points you to the list of mirrors.
 This has been confusing new users for years now. Does not seem too hard to 
 fix...

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (MNGSITE-157) Download links not working

2012-07-09 Thread Olivier Lamy (JIRA)

 [ 
https://jira.codehaus.org/browse/MNGSITE-157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Olivier Lamy closed MNGSITE-157.


Resolution: Fixed

 Download links not working
 --

 Key: MNGSITE-157
 URL: https://jira.codehaus.org/browse/MNGSITE-157
 Project: Maven Project Web Site
  Issue Type: Bug
 Environment: MacOSX 10.6, Safari 5.1.5
Reporter: Marc Guenther
Assignee: Olivier Lamy

 Would it be possible to fix the download links on 
 http://maven.apache.org/download.html for maven .tar.gz files?
 When I click on apache-maven-3.0.4-bin.tar.gz, I get a file 
 {{apache-maven-3.0.4-bin.tar.gz}} which is 6591bytes long. Uncompressing from 
 the Finder does not work and closer inspection reveals that this is in fact a 
 gzipped html file, which points you to the list of mirrors.
 This has been confusing new users for years now. Does not seem too hard to 
 fix...

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (MNGSITE-158) Maven SuperPOM incorrectly documented

2012-07-09 Thread Bevan Thistlethwaite (JIRA)
Bevan Thistlethwaite created MNGSITE-158:


 Summary: Maven SuperPOM incorrectly documented
 Key: MNGSITE-158
 URL: https://jira.codehaus.org/browse/MNGSITE-158
 Project: Maven Project Web Site
  Issue Type: Bug
 Environment: All
Reporter: Bevan Thistlethwaite


Pages affected:
http://maven.apache.org/pom.html#The_Super_POM
Repository names have been changed from:
nameCentral Repository/name
urlhttp://repo.maven.apache.org/maven2/url
to:
nameMaven Plugin Repository/name
urlhttp://repo1.maven.org/maven2/url
http://maven.apache.org/ref/3.0.4/maven-model-builder/super-pom.html
http://www.sonatype.com/books/mvnref-book/reference/pom-relationships-sect-pom.html#ex-super-pom
This Super POM is a part of the Maven installation and can be found in the 
maven-3.0.3-uber.jar file in ${M2_HOME}/lib. If you look in this JAR file, you 
will find a file named pom-4.0.0.xml under the org.apache.maven.project 
package.
Should be: 
This Super POM is a part of the Maven installation and can be found in the 
maven-model-builder-3.0.4.jar file in ${M2_HOME}/lib. If you look in this JAR 
file, you will find a file named pom-4.0.0.xml under the org.apache.maven.model 
package.


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (SUREFIRE-847) surefire cannot run single testng test

2012-07-09 Thread Olivier Lamy (JIRA)

[ 
https://jira.codehaus.org/browse/SUREFIRE-847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=303105#comment-303105
 ] 

Olivier Lamy commented on SUREFIRE-847:
---

see 
http://maven.apache.org/guides/development/guide-testing-development-plugins.html

 surefire cannot run single testng test 
 ---

 Key: SUREFIRE-847
 URL: https://jira.codehaus.org/browse/SUREFIRE-847
 Project: Maven Surefire
  Issue Type: Bug
  Components: TestNG support
Affects Versions: 2.12
 Environment: Windows 7 x64
Reporter: Nikita Makarov
Priority: Minor
 Fix For: 2.13

 Attachments: surefire-847_example.zip


 Trying to run single testng test class with command mvn test -Dtest=SomeTest 
 fails with message 
  [ERROR] Failed to execute goal 
 org.apache.maven.plugins:maven-surefire-plugin:2.12:test (default-test) on 
 project web-integration-tests: No tests were executed!
   (Set -DfailIfNoTests=false to ignore this error.) - [Help 1].

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] (SUREFIRE-827) Surefire 2.12 cannot run a single test, regression from 2.11

2012-07-09 Thread Andrew Gaul (JIRA)

[ 
https://jira.codehaus.org/browse/SUREFIRE-827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=303106#comment-303106
 ] 

Andrew Gaul commented on SUREFIRE-827:
--

Kristian, going back to my example on 06 Feb 2012 with Apache commons-lang 3.1:

$ mvn test -Dtest=ImmutablePairTest#testBasic -Dparallel=classes 
-Dsurefire.version=2.11
...
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0

$ mvn test -Dtest=ImmutablePairTest#testBasic -Dparallel=classes 
-Dsurefire.version=2.12
...
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0

$ mvn test -Dtest=ImmutablePairTest#testBasic -Dparallel=classes 
-Dsurefire.version=2.13-SNAPSHOT
...
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0

Tested with maven-surefire-plugin-2.13-20120706.132117-19.jar .

 Surefire 2.12 cannot run a single test, regression from 2.11
 

 Key: SUREFIRE-827
 URL: https://jira.codehaus.org/browse/SUREFIRE-827
 Project: Maven Surefire
  Issue Type: Bug
  Components: Junit 4.7+ (parallel) support
Affects Versions: 2.12
 Environment: Ubuntu 11.10
Reporter: Andrew Gaul
Assignee: Kristian Rosenvold
 Fix For: 2.13

 Attachments: BUG-827.zip


 # Surefire 2.11
 $ mvn test -Dtest=DataTest#testDataServerGetNonExistentFile
 ...
 Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
 # Surefire 2.12
 mvn test -Dtest=DataTest#testDataServerGetNonExistentFile
 ...
 Tests run: 9, Failures: 0, Errors: 0, Skipped: 0

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira