[jira] (MRELEASE-783) release:update-versions should not need SCM config
[
https://jira.codehaus.org/browse/MRELEASE-783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=304261#comment-304261
]
Ondrej Zizka commented on MRELEASE-783:
---
Probably, thanks for the tip; but still :)
> release:update-versions should not need SCM config
> --
>
> Key: MRELEASE-783
> URL: https://jira.codehaus.org/browse/MRELEASE-783
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
>Reporter: Ondrej Zizka
>
> Currently, on a project without configured, {{mvn
> release:update-versions}} ends up with:
> {code}
> Failed to execute goal
> org.apache.maven.plugins:maven-release-plugin:2.0:update-versions
> (default-cli) on project wicketstuff-dojo: Missing required setting: scm
> connection or developerConnection must be specified.
> {code}
> Updating versions recursively definitely does not need SCM.
> Could this restriction be removed? Thanks.
--
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-783) release:update-versions should not need SCM config
[
https://jira.codehaus.org/browse/MRELEASE-783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=304260#comment-304260
]
Brett Porter commented on MRELEASE-783:
---
Perhaps the versions-maven-plugin would be more suitable for this scenario?
> release:update-versions should not need SCM config
> --
>
> Key: MRELEASE-783
> URL: https://jira.codehaus.org/browse/MRELEASE-783
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
>Reporter: Ondrej Zizka
>
> Currently, on a project without configured, {{mvn
> release:update-versions}} ends up with:
> {code}
> Failed to execute goal
> org.apache.maven.plugins:maven-release-plugin:2.0:update-versions
> (default-cli) on project wicketstuff-dojo: Missing required setting: scm
> connection or developerConnection must be specified.
> {code}
> Updating versions recursively definitely does not need SCM.
> Could this restriction be removed? Thanks.
--
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-783) release:update-versions should not need SCM config
[
https://jira.codehaus.org/browse/MRELEASE-783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=304259#comment-304259
]
Ondrej Zizka commented on MRELEASE-783:
---
Maven 3.0.4
> release:update-versions should not need SCM config
> --
>
> Key: MRELEASE-783
> URL: https://jira.codehaus.org/browse/MRELEASE-783
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
>Reporter: Ondrej Zizka
>
> Currently, on a project without configured, {{mvn
> release:update-versions}} ends up with:
> {code}
> Failed to execute goal
> org.apache.maven.plugins:maven-release-plugin:2.0:update-versions
> (default-cli) on project wicketstuff-dojo: Missing required setting: scm
> connection or developerConnection must be specified.
> {code}
> Updating versions recursively definitely does not need SCM.
> Could this restriction be removed? Thanks.
--
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-783) release:update-versions should not need SCM config
Ondrej Zizka created MRELEASE-783:
-
Summary: release:update-versions should not need SCM config
Key: MRELEASE-783
URL: https://jira.codehaus.org/browse/MRELEASE-783
Project: Maven 2.x Release Plugin
Issue Type: Improvement
Reporter: Ondrej Zizka
Currently, on a project without configured, {{mvn
release:update-versions}} ends up with:
{code}
Failed to execute goal
org.apache.maven.plugins:maven-release-plugin:2.0:update-versions (default-cli)
on project wicketstuff-dojo: Missing required setting: scm connection or
developerConnection must be specified.
{code}
Updating versions recursively definitely does not need SCM.
Could this restriction be removed? Thanks.
--
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-800) redirectTestOutputToFile is not taken into account in all cases with JUnit47 provider
[
https://jira.codehaus.org/browse/SUREFIRE-800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=304256#comment-304256
]
Kristian Rosenvold commented on SUREFIRE-800:
-
This fix had to be reverted & reopened since the additional runner indirection
was causing severe problems
> redirectTestOutputToFile is not taken into account in all cases with JUnit47
> provider
> -
>
> Key: SUREFIRE-800
> URL: https://jira.codehaus.org/browse/SUREFIRE-800
> Project: Maven Surefire
> Issue Type: Bug
> Components: Junit 4.7+ (parallel) support
>Affects Versions: 2.10
> Environment: all
>Reporter: nkeywal
>
> With the following class:
> {noformat}
> public class Test0 {
> public Test0(){
> System.out.println("Constructor");
> }
> @Test
> public void testT0() throws Exception {
> System.out.println("testT0");
> }
> @Test
> public void testT1() throws Exception {
> System.out.println("testT1");
> }
> @BeforeClass
> public static void setUpBeforeClass() throws Exception {
> System.out.println("setUpBeforeClass");
> }
> @AfterClass
> public static void tearDownAfterClass() throws Exception {
> System.out.println("tearDownAfterClass");
> }
> @Before
> public void setUp() throws Exception {
> System.out.println("setUp");
> }
> @After
> public void tearDown() throws Exception {
> System.out.println("tearDown");
> }
> }
> {noformat}
> Some elements of the output are not redirected with JUNit47.
> {noformat}
> Concurrency config is parallel='none', perCoreThreadCount=true,
> threadCount=2, useUnlimitedThreads=false
> setUpBeforeClass
> Constructor
> Constructor
> tearDownAfterClass
> Running Test0
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.01 sec
> {noformat}
> While it's ok with with JUNit4:
> {noformat}
> ---
> T E S T S
> ---
> Running Test0
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.09 sec
> {noformat}
--
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-800) redirectTestOutputToFile is not taken into account in all cases with JUnit47 provider
[
https://jira.codehaus.org/browse/SUREFIRE-800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Rosenvold updated SUREFIRE-800:
Fix Version/s: (was: 2.12)
> redirectTestOutputToFile is not taken into account in all cases with JUnit47
> provider
> -
>
> Key: SUREFIRE-800
> URL: https://jira.codehaus.org/browse/SUREFIRE-800
> Project: Maven Surefire
> Issue Type: Bug
> Components: Junit 4.7+ (parallel) support
>Affects Versions: 2.10
> Environment: all
>Reporter: nkeywal
>
> With the following class:
> {noformat}
> public class Test0 {
> public Test0(){
> System.out.println("Constructor");
> }
> @Test
> public void testT0() throws Exception {
> System.out.println("testT0");
> }
> @Test
> public void testT1() throws Exception {
> System.out.println("testT1");
> }
> @BeforeClass
> public static void setUpBeforeClass() throws Exception {
> System.out.println("setUpBeforeClass");
> }
> @AfterClass
> public static void tearDownAfterClass() throws Exception {
> System.out.println("tearDownAfterClass");
> }
> @Before
> public void setUp() throws Exception {
> System.out.println("setUp");
> }
> @After
> public void tearDown() throws Exception {
> System.out.println("tearDown");
> }
> }
> {noformat}
> Some elements of the output are not redirected with JUNit47.
> {noformat}
> Concurrency config is parallel='none', perCoreThreadCount=true,
> threadCount=2, useUnlimitedThreads=false
> setUpBeforeClass
> Constructor
> Constructor
> tearDownAfterClass
> Running Test0
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.01 sec
> {noformat}
> While it's ok with with JUNit4:
> {noformat}
> ---
> T E S T S
> ---
> Running Test0
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.09 sec
> {noformat}
--
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:all-tabpanel ] Kristian Rosenvold closed SUREFIRE-827. --- Resolution: Fixed Fixed in r1364159 > 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
[jira] (SUREFIRE-800) redirectTestOutputToFile is not taken into account in all cases with JUnit47 provider
[
https://jira.codehaus.org/browse/SUREFIRE-800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Rosenvold reopened SUREFIRE-800:
-
Assignee: (was: Kristian Rosenvold)
> redirectTestOutputToFile is not taken into account in all cases with JUnit47
> provider
> -
>
> Key: SUREFIRE-800
> URL: https://jira.codehaus.org/browse/SUREFIRE-800
> Project: Maven Surefire
> Issue Type: Bug
> Components: Junit 4.7+ (parallel) support
>Affects Versions: 2.10
> Environment: all
>Reporter: nkeywal
> Fix For: 2.12
>
>
> With the following class:
> {noformat}
> public class Test0 {
> public Test0(){
> System.out.println("Constructor");
> }
> @Test
> public void testT0() throws Exception {
> System.out.println("testT0");
> }
> @Test
> public void testT1() throws Exception {
> System.out.println("testT1");
> }
> @BeforeClass
> public static void setUpBeforeClass() throws Exception {
> System.out.println("setUpBeforeClass");
> }
> @AfterClass
> public static void tearDownAfterClass() throws Exception {
> System.out.println("tearDownAfterClass");
> }
> @Before
> public void setUp() throws Exception {
> System.out.println("setUp");
> }
> @After
> public void tearDown() throws Exception {
> System.out.println("tearDown");
> }
> }
> {noformat}
> Some elements of the output are not redirected with JUNit47.
> {noformat}
> Concurrency config is parallel='none', perCoreThreadCount=true,
> threadCount=2, useUnlimitedThreads=false
> setUpBeforeClass
> Constructor
> Constructor
> tearDownAfterClass
> Running Test0
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.01 sec
> {noformat}
> While it's ok with with JUNit4:
> {noformat}
> ---
> T E S T S
> ---
> Running Test0
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.09 sec
> {noformat}
--
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
[ https://jira.codehaus.org/browse/SUREFIRE-847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold closed SUREFIRE-847. --- Resolution: Fixed Additional regression fixed in r1364144 > 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 >Assignee: Kristian Rosenvold >Priority: Blocker > Fix For: 2.13 > > Attachments: onlyFailedTest.log, onlyPassedTest.log, > 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] (MNG-5318) mvn.bat fail on TTC/LE when -Dkey=value parameters are not quoted
zart colwing created MNG-5318: - Summary: mvn.bat fail on TTC/LE when -Dkey=value parameters are not quoted Key: MNG-5318 URL: https://jira.codehaus.org/browse/MNG-5318 Project: Maven 2 & 3 Issue Type: Bug Components: Command Line Affects Versions: 3.0.4 Environment: windows-7, tccle.ex Reporter: zart colwing Attachments: mvn_bat.patch When the mvn command contains an unquoted -Dkey=value parameter then mvn fail with a: [ERROR] Unknown lifecycle phase "". You must specify a valid lifecycle phase or a goal in the format : or... The problem is that the bat file execute: set MAVEN_CMD_LINE_ARGS=%$ (on line 129) instead of set MAVEN_CMD_LINE_ARGS=%* (on line 124) when it detect TCC/LE (on line 121) from http://www.robvanderwoude.com/parameters.php %$ replace '=' by space unless they are part of a string in doublequotes. %* will leave all delimiters intact A possible fix is to use %* in both case. Another possible fix is to remove (or comment out) the TCC/LE detection on line 121 and let the script fall-through to the "Regular WinNT" case. -- 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-782) Properties defined in a child pom hide all the properties defined in the parent pom while performing release:prepare
[
https://jira.codehaus.org/browse/MRELEASE-782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=304239#comment-304239
]
Robert Scholte commented on MRELEASE-782:
-
One option is to copy this plugin to the pluginManagement of the parent-pom, so
you can remove the dependency in the child-pom.
> Properties defined in a child pom hide all the properties defined in the
> parent pom while performing release:prepare
>
>
> Key: MRELEASE-782
> URL: https://jira.codehaus.org/browse/MRELEASE-782
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
>Affects Versions: 2.3.2
> Environment: Any
>Reporter: Marius Dumitru Florea
>
> Suppose you have this two poms:
> {code:title=Parent POM}
> ...
>
> 1.6
>
> ...
> {code}
> {code:title=Child POM}
> ...
>
> ...
>
> ...
>
>
> ...
> ${my.version}
>
>
>
> ...
> {code}
> Running release:prepare on this works just fine. Now, if we add a
> {{properties}} section with any property to the child pom we get:
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-release-plugin:2.3.2:prepare (default-cli) on
> project XYZ: The version could not be updated: ${my.version} -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-release-plugin:2.3.2:prepare
> (default-cli) on project XYZ: The version could not be updated: ${my.version}
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
> 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:320)
> 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.MojoFailureException: The version could
> not be updated: ${commons.version}
> at
> org.apache.maven.plugins.release.PrepareReleaseMojo.prepareRelease(PrepareReleaseMojo.java:299)
> at
> org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareReleaseMojo.java:247)
> 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.ReleaseFailureException: The
> version could not be updated: ${my.version}
> at
> org.apache.maven.shared.release.phase.AbstractRewritePomsPhase.rewriteArtifactVersions(AbstractRewritePomsPhase.java:578)
> at
> org.apache.maven.shared.release.phase.AbstractRewritePomsPhase.transformDocument(AbstractRewritePomsPhase.java:298)
> at
> org.apache.maven.shared.release.phase.AbstractRewritePomsPhase.transformProject(AbstractRewritePomsPhase.java:220)
> at
> org.apache.maven.shared.release.phase.AbstractRewritePomsPhase.transform(AbstractRewritePomsPhase.java:126)
> at
> org.apache.maven.shared.release.phase.AbstractRewritePomsPhase.simulate(AbstractRewritePomsPhase.java:713)
> at
> org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:228)
> at
> org.apache.maven.shared.release.DefaultRele
