You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Dameon Hunt (JIRA)" <ji...@codehaus.org> on 2012/09/06 23:36:21 UTC
[jira] (SUREFIRE-911) Regression: Since Surefire version 2.12.x,
hyphens are not allowed in Group Names.
Dameon Hunt created SUREFIRE-911:
------------------------------------
Summary: Regression: Since Surefire version 2.12.x, hyphens are not allowed in Group Names.
Key: SUREFIRE-911
URL: https://jira.codehaus.org/browse/SUREFIRE-911
Project: Maven Surefire
Issue Type: Bug
Components: Maven Surefire Plugin
Affects Versions: 2.12.2
Environment: Windows.
Reporter: Dameon Hunt
We use TestNG groups for our tests and our group names for various classes have a hyphen in them (e.g. "TEST-FRONTEND"). When we tried to move from surefire version 2.11 to 2.12, it fails with the below error:
To reproduce, just execute a test case assigned to a testng group with a hyphen in it.
###################
[INFO] --- maven-surefire-plugin:2.12.3:test (default-test) @ RRTests ---
[INFO] Surefire report directory: C:\dev\eclipse\workspace\CyberSource_RR_Current_Lane-Hotness\
AV2\RRTests\target\surefire-reports
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running TestSuite
org.apache.maven.surefire.util.SurefireReflectionException: java.lang.reflect.InvocationTargetE
xception; nested exception is java.lang.reflect.InvocationTargetException: null
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:597)
at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils
.java:189)
at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactor
y.java:165)
at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java
:85)
at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:1
15)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)
Caused by: org.apache.maven.surefire.testset.TestSetFailedException: null; nested exception is
java.lang.reflect.InvocationTargetException: null
at org.apache.maven.surefire.testng.TestNGExecutor.applyGroupMatching(TestNGExecutor.ja
va:165)
at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:66)
at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirecto
ryTestSuite.java:159)
at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTes
tSuite.java:99)
at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:106)
... 9 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:597)
at org.apache.maven.surefire.testng.TestNGExecutor.applyGroupMatching(TestNGExecutor.ja
va:141)
... 13 more
Caused by: org.apache.maven.surefire.group.parse.TokenMgrError: Lexical error at line 1, column
3. Encountered: "-" (45), after : ""
at org.apache.maven.surefire.group.parse.GroupMatcherParserTokenManager.getNextToken(Gr
oupMatcherParserTokenManager.java:468)
at org.apache.maven.surefire.group.parse.GroupMatcherParser.jj_scan_token(GroupMatcherP
arser.java:527)
at org.apache.maven.surefire.group.parse.GroupMatcherParser.jj_3_7(GroupMatcherParser.j
ava:274)
at org.apache.maven.surefire.group.parse.GroupMatcherParser.jj_3R_3(GroupMatcherParser.
java:287)
at org.apache.maven.surefire.group.parse.GroupMatcherParser.jj_3_3(GroupMatcherParser.j
ava:279)
at org.apache.maven.surefire.group.parse.GroupMatcherParser.jj_3R_1(GroupMatcherParser.
java:320)
at org.apache.maven.surefire.group.parse.GroupMatcherParser.jj_3_1(GroupMatcherParser.j
ava:335)
at org.apache.maven.surefire.group.parse.GroupMatcherParser.jj_2_1(GroupMatcherParser.j
ava:179)
at org.apache.maven.surefire.group.parse.GroupMatcherParser.expr(GroupMatcherParser.jav
a:63)
at org.apache.maven.surefire.group.parse.GroupMatcherParser.parse(GroupMatcherParser.ja
va:56)
at org.apache.maven.surefire.testng.utils.GroupMatcherMethodSelector.setGroups(GroupMat
cherMethodSelector.java:82)
... 18 more
--
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-911) Regression: Since Surefire version 2.12.x,
hyphens are not allowed in Group Names.
Posted by "Kristian Rosenvold (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/SUREFIRE-911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Rosenvold updated SUREFIRE-911:
----------------------------------------
Fix Version/s: 2.13
> Regression: Since Surefire version 2.12.x, hyphens are not allowed in Group Names.
> ----------------------------------------------------------------------------------
>
> Key: SUREFIRE-911
> URL: https://jira.codehaus.org/browse/SUREFIRE-911
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
> Affects Versions: 2.12.2
> Environment: Windows.
> Reporter: Dameon Hunt
> Fix For: 2.13
>
>
> We use TestNG groups for our tests and our group names for various classes have a hyphen in them (e.g. "TEST-FRONTEND"). When we tried to move from surefire version 2.11 to 2.12, it fails with the below error:
> To reproduce, just execute a test case assigned to a testng group with a hyphen in it.
> ###################
> [INFO] --- maven-surefire-plugin:2.12.3:test (default-test) @ RRTests ---
> [INFO] Surefire report directory: C:\dev\eclipse\workspace\CyberSource_RR_Current_Lane-Hotness\
> AV2\RRTests\target\surefire-reports
> -------------------------------------------------------
> T E S T S
> -------------------------------------------------------
> Running TestSuite
> org.apache.maven.surefire.util.SurefireReflectionException: java.lang.reflect.InvocationTargetE
> xception; nested exception is java.lang.reflect.InvocationTargetException: null
> 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:597)
> at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils
> .java:189)
> at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactor
> y.java:165)
> at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java
> :85)
> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:1
> 15)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)
> Caused by: org.apache.maven.surefire.testset.TestSetFailedException: null; nested exception is
> java.lang.reflect.InvocationTargetException: null
> at org.apache.maven.surefire.testng.TestNGExecutor.applyGroupMatching(TestNGExecutor.ja
> va:165)
> at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:66)
> at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirecto
> ryTestSuite.java:159)
> at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTes
> tSuite.java:99)
> at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:106)
> ... 9 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:597)
> at org.apache.maven.surefire.testng.TestNGExecutor.applyGroupMatching(TestNGExecutor.ja
> va:141)
> ... 13 more
> Caused by: org.apache.maven.surefire.group.parse.TokenMgrError: Lexical error at line 1, column
> 3. Encountered: "-" (45), after : ""
> at org.apache.maven.surefire.group.parse.GroupMatcherParserTokenManager.getNextToken(Gr
> oupMatcherParserTokenManager.java:468)
> at org.apache.maven.surefire.group.parse.GroupMatcherParser.jj_scan_token(GroupMatcherP
> arser.java:527)
> at org.apache.maven.surefire.group.parse.GroupMatcherParser.jj_3_7(GroupMatcherParser.j
> ava:274)
> at org.apache.maven.surefire.group.parse.GroupMatcherParser.jj_3R_3(GroupMatcherParser.
> java:287)
> at org.apache.maven.surefire.group.parse.GroupMatcherParser.jj_3_3(GroupMatcherParser.j
> ava:279)
> at org.apache.maven.surefire.group.parse.GroupMatcherParser.jj_3R_1(GroupMatcherParser.
> java:320)
> at org.apache.maven.surefire.group.parse.GroupMatcherParser.jj_3_1(GroupMatcherParser.j
> ava:335)
> at org.apache.maven.surefire.group.parse.GroupMatcherParser.jj_2_1(GroupMatcherParser.j
> ava:179)
> at org.apache.maven.surefire.group.parse.GroupMatcherParser.expr(GroupMatcherParser.jav
> a:63)
> at org.apache.maven.surefire.group.parse.GroupMatcherParser.parse(GroupMatcherParser.ja
> va:56)
> at org.apache.maven.surefire.testng.utils.GroupMatcherMethodSelector.setGroups(GroupMat
> cherMethodSelector.java:82)
> ... 18 more
--
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-911) Regression: Since Surefire version 2.12.x,
hyphens are not allowed in Group Names.
Posted by "Kristian Rosenvold (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/SUREFIRE-911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Rosenvold closed SUREFIRE-911.
---------------------------------------
Resolution: Duplicate
Duplicates SUREFIRE-831
> Regression: Since Surefire version 2.12.x, hyphens are not allowed in Group Names.
> ----------------------------------------------------------------------------------
>
> Key: SUREFIRE-911
> URL: https://jira.codehaus.org/browse/SUREFIRE-911
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
> Affects Versions: 2.12.2
> Environment: Windows.
> Reporter: Dameon Hunt
> Fix For: 2.13
>
>
> We use TestNG groups for our tests and our group names for various classes have a hyphen in them (e.g. "TEST-FRONTEND"). When we tried to move from surefire version 2.11 to 2.12, it fails with the below error:
> To reproduce, just execute a test case assigned to a testng group with a hyphen in it.
> ###################
> [INFO] --- maven-surefire-plugin:2.12.3:test (default-test) @ RRTests ---
> [INFO] Surefire report directory: C:\dev\eclipse\workspace\CyberSource_RR_Current_Lane-Hotness\
> AV2\RRTests\target\surefire-reports
> -------------------------------------------------------
> T E S T S
> -------------------------------------------------------
> Running TestSuite
> org.apache.maven.surefire.util.SurefireReflectionException: java.lang.reflect.InvocationTargetE
> xception; nested exception is java.lang.reflect.InvocationTargetException: null
> 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:597)
> at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils
> .java:189)
> at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactor
> y.java:165)
> at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java
> :85)
> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:1
> 15)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)
> Caused by: org.apache.maven.surefire.testset.TestSetFailedException: null; nested exception is
> java.lang.reflect.InvocationTargetException: null
> at org.apache.maven.surefire.testng.TestNGExecutor.applyGroupMatching(TestNGExecutor.ja
> va:165)
> at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:66)
> at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirecto
> ryTestSuite.java:159)
> at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTes
> tSuite.java:99)
> at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:106)
> ... 9 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:597)
> at org.apache.maven.surefire.testng.TestNGExecutor.applyGroupMatching(TestNGExecutor.ja
> va:141)
> ... 13 more
> Caused by: org.apache.maven.surefire.group.parse.TokenMgrError: Lexical error at line 1, column
> 3. Encountered: "-" (45), after : ""
> at org.apache.maven.surefire.group.parse.GroupMatcherParserTokenManager.getNextToken(Gr
> oupMatcherParserTokenManager.java:468)
> at org.apache.maven.surefire.group.parse.GroupMatcherParser.jj_scan_token(GroupMatcherP
> arser.java:527)
> at org.apache.maven.surefire.group.parse.GroupMatcherParser.jj_3_7(GroupMatcherParser.j
> ava:274)
> at org.apache.maven.surefire.group.parse.GroupMatcherParser.jj_3R_3(GroupMatcherParser.
> java:287)
> at org.apache.maven.surefire.group.parse.GroupMatcherParser.jj_3_3(GroupMatcherParser.j
> ava:279)
> at org.apache.maven.surefire.group.parse.GroupMatcherParser.jj_3R_1(GroupMatcherParser.
> java:320)
> at org.apache.maven.surefire.group.parse.GroupMatcherParser.jj_3_1(GroupMatcherParser.j
> ava:335)
> at org.apache.maven.surefire.group.parse.GroupMatcherParser.jj_2_1(GroupMatcherParser.j
> ava:179)
> at org.apache.maven.surefire.group.parse.GroupMatcherParser.expr(GroupMatcherParser.jav
> a:63)
> at org.apache.maven.surefire.group.parse.GroupMatcherParser.parse(GroupMatcherParser.ja
> va:56)
> at org.apache.maven.surefire.testng.utils.GroupMatcherMethodSelector.setGroups(GroupMat
> cherMethodSelector.java:82)
> ... 18 more
--
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