[jira] (MDEP-396) Add support to use the baseVersion of an artifact instead of version for the destFileName
[ https://jira.codehaus.org/browse/MDEP-396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Kuhtz updated MDEP-396: --- Attachment: MDEP-396.diff New complete patch with testcase in CopyMojo. Add support to use the baseVersion of an artifact instead of version for the destFileName - Key: MDEP-396 URL: https://jira.codehaus.org/browse/MDEP-396 Project: Maven 2.x Dependency Plugin Issue Type: Improvement Components: copy Affects Versions: 2.6 Reporter: Andreas Kuhtz Attachments: baseVersionPatch.diff, MDEP-396.diff Add support to use the baseVersion of an artifact instead of version for the destFileName via plugin configuration. The problem occurs with maven 3 and SNAPSHOT artifacts where the name of the copied file contains the timestamped (unique) version instead of '-SNAPSHOT'. -- 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] (MDEP-396) Add support to use the baseVersion of an artifact instead of version for the destFileName
[ https://jira.codehaus.org/browse/MDEP-396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=319139#comment-319139 ] Andreas Kuhtz edited comment on MDEP-396 at 2/11/13 3:19 AM: - New complete patch with testcase in CopyMojo. Is this test enough or do you want more tests? was (Author: akuhtz): New complete patch with testcase in CopyMojo. Add support to use the baseVersion of an artifact instead of version for the destFileName - Key: MDEP-396 URL: https://jira.codehaus.org/browse/MDEP-396 Project: Maven 2.x Dependency Plugin Issue Type: Improvement Components: copy Affects Versions: 2.6 Reporter: Andreas Kuhtz Attachments: baseVersionPatch.diff, MDEP-396.diff Add support to use the baseVersion of an artifact instead of version for the destFileName via plugin configuration. The problem occurs with maven 3 and SNAPSHOT artifacts where the name of the copied file contains the timestamped (unique) version instead of '-SNAPSHOT'. -- 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] (MDEP-396) Add support to use the baseVersion of an artifact instead of version for the destFileName
Andreas Kuhtz created MDEP-396: -- Summary: Add support to use the baseVersion of an artifact instead of version for the destFileName Key: MDEP-396 URL: https://jira.codehaus.org/browse/MDEP-396 Project: Maven 2.x Dependency Plugin Issue Type: Improvement Components: copy Affects Versions: 2.6 Reporter: Andreas Kuhtz Attachments: baseVersionPatch.diff Add support to use the baseVersion of an artifact instead of version for the destFileName via plugin configuration. The problem occurs with maven 3 and SNAPSHOT artifacts where the name of the copied file contains the timestamped (unique) version instead of '-SNAPSHOT'. -- 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] (MDEP-396) Add support to use the baseVersion of an artifact instead of version for the destFileName
[ https://jira.codehaus.org/browse/MDEP-396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Kuhtz updated MDEP-396: --- Attachment: baseVersionPatch.diff Add support to use the baseVersion of an artifact instead of version for the destFileName - Key: MDEP-396 URL: https://jira.codehaus.org/browse/MDEP-396 Project: Maven 2.x Dependency Plugin Issue Type: Improvement Components: copy Affects Versions: 2.6 Reporter: Andreas Kuhtz Attachments: baseVersionPatch.diff Add support to use the baseVersion of an artifact instead of version for the destFileName via plugin configuration. The problem occurs with maven 3 and SNAPSHOT artifacts where the name of the copied file contains the timestamped (unique) version instead of '-SNAPSHOT'. -- 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
[ https://jira.codehaus.org/browse/SUREFIRE-827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=294763#comment-294763 ] Andreas Kuhtz commented on SUREFIRE-827: Works with current 2.13-SNAPSHOT (maven-surefire-plugin-2.13-20120228.152623-12 ) with testNG. 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 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
[jira] (SUREFIRE-831) Lexical error in surefire-plugin (TestNGExecutor.applyGroupMatching()) if the groupName of an excludedGroup contains a '-' sign
[
https://jira.codehaus.org/browse/SUREFIRE-831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=291256#comment-291256
]
Andreas Kuhtz commented on SUREFIRE-831:
The problem does not occur if a '_' is used insead of the '-' sign. I guess
it's related to the definition in
http://svn.apache.org/viewvc/maven/surefire/trunk/surefire-grouper/src/main/javacc/category-expression.jj?view=markuppathrev=1235805
{code:title=category-expression.jj}
STRING: ([A-Z, a-z, 0-9, _, $, #, .])+
{code}
which might be
{code:title=category-expression.jj}
STRING: ([A-Z, a-z, 0-9, _, -, $, #, .])+
{code}
Lexical error in surefire-plugin (TestNGExecutor.applyGroupMatching()) if the
groupName of an excludedGroup contains a '-' sign
---
Key: SUREFIRE-831
URL: https://jira.codehaus.org/browse/SUREFIRE-831
Project: Maven Surefire
Issue Type: Bug
Components: TestNG support
Affects Versions: 2.11, 2.12
Environment: Tested with maven-surefire-plugin-2.13-20120207.212404-8
Reporter: Andreas Kuhtz
This occurs even with the current SNAPSHOT release. The issue might be
related to SUREFIRE-828.
{code:title=pom.xml}
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-surefire-plugin/artifactId
configuration
excludedGroupsui-test/excludedGroups
/configuration
/plugin
{code}
{code}
Running TestSuite
org.apache.maven.surefire.util.SurefireReflectionException:
java.lang.reflect.InvocationTargetException; nested exceptio
n 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(ProviderFactory.java:165)
at
org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
at
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:103)
at
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74)
Caused by: org.apache.maven.surefire.testset.TestSetFailedException: null;
nested exception is java.lang.reflect.Invocat
ionTargetException: null
at
org.apache.maven.surefire.testng.TestNGExecutor.applyGroupMatching(TestNGExecutor.java:164)
at
org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:65)
at
org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:161)
at
org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:101)
at
org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:115)
... 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.java:140)
... 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(GroupMatcherParserTokenMana
ger.java:468)
at
org.apache.maven.surefire.group.parse.GroupMatcherParser.jj_scan_token(GroupMatcherParser.java:527)
at
org.apache.maven.surefire.group.parse.GroupMatcherParser.jj_3_7(GroupMatcherParser.java: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.java: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.java:335)
at
org.apache.maven.surefire.group.parse.GroupMatcherParser.jj_2_1(GroupMatcherParser.java:179)
at
[jira] (SUREFIRE-831) Lexical error in surefire-plugin (TestNGExecutor.applyGroupMatching()) if the groupName of an excludedGroup contains a '-' sign
Andreas Kuhtz created SUREFIRE-831:
--
Summary: Lexical error in surefire-plugin
(TestNGExecutor.applyGroupMatching()) if the groupName of an excludedGroup
contains a '-' sign
Key: SUREFIRE-831
URL: https://jira.codehaus.org/browse/SUREFIRE-831
Project: Maven Surefire
Issue Type: Bug
Components: TestNG support
Affects Versions: 2.12, 2.11
Environment: Tested with maven-surefire-plugin-2.13-20120207.212404-8
Reporter: Andreas Kuhtz
This occurs even with the current SNAPSHOT release. The issue might be related
to SUREFIRE-828.
{code:title=pom.xml}
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-surefire-plugin/artifactId
configuration
excludedGroupsui-test/excludedGroups
/configuration
/plugin
{code}
{code}
Running TestSuite
org.apache.maven.surefire.util.SurefireReflectionException:
java.lang.reflect.InvocationTargetException; nested exceptio
n 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(ProviderFactory.java:165)
at
org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
at
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:103)
at
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74)
Caused by: org.apache.maven.surefire.testset.TestSetFailedException: null;
nested exception is java.lang.reflect.Invocat
ionTargetException: null
at
org.apache.maven.surefire.testng.TestNGExecutor.applyGroupMatching(TestNGExecutor.java:164)
at
org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:65)
at
org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:161)
at
org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:101)
at
org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:115)
... 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.java:140)
... 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(GroupMatcherParserTokenMana
ger.java:468)
at
org.apache.maven.surefire.group.parse.GroupMatcherParser.jj_scan_token(GroupMatcherParser.java:527)
at
org.apache.maven.surefire.group.parse.GroupMatcherParser.jj_3_7(GroupMatcherParser.java: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.java: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.java:335)
at
org.apache.maven.surefire.group.parse.GroupMatcherParser.jj_2_1(GroupMatcherParser.java:179)
at
org.apache.maven.surefire.group.parse.GroupMatcherParser.expr(GroupMatcherParser.java:63)
at
org.apache.maven.surefire.group.parse.GroupMatcherParser.parse(GroupMatcherParser.java:56)
at
org.apache.maven.surefire.testng.utils.GroupMatcherMethodSelector.setGroups(GroupMatcherMethodSelector.java:7
6)
... 18 more
{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
