[jira] (MANTTASKS-225) http://maven.apache.org/ant-tasks/examples/mvn.html#Using_the_Java_Task defines args element but does not use it
SebbASF created MANTTASKS-225: - Summary: http://maven.apache.org/ant-tasks/examples/mvn.html#Using_the_Java_Task defines args element but does not use it Key: MANTTASKS-225 URL: https://jira.codehaus.org/browse/MANTTASKS-225 Project: Maven 2.x Ant Tasks Issue Type: Bug Reporter: SebbASF Priority: Minor The java task example defines an "args" element, but does not use it in the body. This is confusing. Either remove the definition, or add the element to the body and provide an example that uses it. -- 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] (MNG-5178) Substitute environment variable M2_HOME by M3_HOME
[
https://jira.codehaus.org/browse/MNG-5178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=289008#comment-289008
]
SebbASF commented on MNG-5178:
--
If this is done, it may break scripts etc that rely on M2_HOME variable.
So any such change should be well publicised as an incompatible change.
If it can be done in such a way that M2_HOME still works when using Maven 3, so
much the better.
> Substitute environment variable M2_HOME by M3_HOME
> --
>
> Key: MNG-5178
> URL: https://jira.codehaus.org/browse/MNG-5178
> Project: Maven 2 & 3
> Issue Type: Wish
> Components: Command Line
>Reporter: Oliver B. Fischer
>Priority: Minor
>
> Maven 3 uses the environment variable {{M2_HOME}} to point to it's
> installation directory. This variable should be replaced by {{M3_HOME}} to
> allow users to have parallel installations of Maven 2 and Maven 3 without any
> special handling of the environment variable {{M2_HOME}}.
--
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] (MNG-5232) Mvn release plugin problems with too many - in name
Erwin Mueller created MNG-5232: -- Summary: Mvn release plugin problems with too many - in name Key: MNG-5232 URL: https://jira.codehaus.org/browse/MNG-5232 Project: Maven 2 & 3 Issue Type: Bug Components: Plugins and Lifecycle Affects Versions: 3.0.3 Environment: Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100) Maven home: /home/devent/apps/apache-maven-3.0.3 Java version: 1.7.0_b147-icedtea, vendor: Oracle Corporation Java home: /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.1/jre Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "3.1.9-1.fc16.i686", arch: "i386", family: "unix" Reporter: Erwin Mueller Priority: Blocker Attachments: mvn-release-prepare.log Have maven problems with modules containing too many "-"? I have projects that are named: globalpom-groovy/ globalpom-groovy/globalpom-groovy/pom.xml < parent pom globalpom-groovy/globalpom-groovy-izpack/pom.xml globalpom-groovy/globalpom-groovy-izpack-snglejar/pom.xml globalpom-groovy/globalpom-groovy-testutils/pom.xml But if I do mvn release:prepare inside of globalpom-groovy/globalpom-groovy/, then I get the error: [INFO] Executing: /bin/sh -c cd /mnt/read/projects/com.anrisoftware/globalpom/globalpom-groovy/globalpom- groovy && git add -- pom.xml -izpack/pom.xml -izpack-singlejar/pom.xml - testutils/pom.xml [INFO] Working directory: /mnt/read/projects/com.anrisoftware/globalpom/globalpom-groovy/globalpom- groovy [INFO] [INFO] Reactor Summary: [INFO] [INFO] Global POM Groovy . FAILURE [12.365s] [INFO] Global POM Groovy IzPack .. SKIPPED [INFO] Global POM Groovy IzPack Single Jar ... SKIPPED [INFO] Global POM Groovy Test Utilities .. SKIPPED [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 13.066s [INFO] Finished at: Sat Jan 21 15:45:50 CET 2012 [INFO] Final Memory: 12M/152M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-release- plugin:2.0:prepare (default-cli) on project globalpom-groovy: Unable to commit files [ERROR] Provider message: [ERROR] The git-add command failed. [ERROR] Command output: [ERROR] fatal: pathspec 'globalpom-groovy/-izpack/pom.xml' did not match any files Of course that's wrong 'globalpom-groovy/-izpack/pom.xml' should be '../globalpom-groovy-izpack/pom.xml', or something like that. -- 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-789) Junit Category: Tests without category fail with the message "initializationError(org.junit.runner.manipulation.Filter)" when groups is set and forkMode=always
[ https://jira.codehaus.org/browse/SUREFIRE-789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold updated SUREFIRE-789: Fix Version/s: 2.12 > Junit Category: Tests without category fail with the message > "initializationError(org.junit.runner.manipulation.Filter)" when groups is > set and forkMode=always > --- > > Key: SUREFIRE-789 > URL: https://jira.codehaus.org/browse/SUREFIRE-789 > Project: Maven Surefire > Issue Type: Bug >Affects Versions: 2.11 >Reporter: nkeywal >Assignee: Kristian Rosenvold > Fix For: 2.12 > > Attachments: NoCategoryTest.java > > > See attached file, to be added to the integration tests in the > junit48-categories project. With forkMode=once, there is no effect, and the > existing test passes, with forkMode=always, the test fails. -- 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-816) regression: java.lang.Exception: No tests found matching from org.junit.runner.Request$1@1808199
[
https://jira.codehaus.org/browse/SUREFIRE-816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=289038#comment-289038
]
Kristian Rosenvold commented on SUREFIRE-816:
-
Sooner than you think ;)
> regression: java.lang.Exception: No tests found matching from
> org.junit.runner.Request$1@1808199
> -
>
> Key: SUREFIRE-816
> URL: https://jira.codehaus.org/browse/SUREFIRE-816
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.11
> Environment: maven 3.0.3
>Reporter: David J. M. Karlsen
>Assignee: Kristian Rosenvold
>
> In 2.11 I get:
> {noformat}
> java.lang.Exception: No tests found matching from
> org.junit.runner.Request$1@1808199 at
> org.junit.internal.requests.FilterRequest.getRunner(FilterRequest.java:37)
> at org.junit.runner.JUnitCore.run(JUnitCore.java:136) at
> org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:61)
>at
> org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:140)
> 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:188)
>at
> org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:166)
> at
> org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:86)
> at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:101)
> at
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74)
> {noformat}
> this passed fine with 2.10.
> The test-class uses parameters - and in this execution no parameters are
> returned, and hence no tests should be executed either.
--
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
