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

Omar Allauddin updated MRELEASE-786:
------------------------------------
    Comment: was deleted

(was: [~snowmanchu] 
I have added -T with release:clean and release:prepare. As far I can tell the 
release plugin it is not officially thread safe. I got warning this during the 
build.
{code:java}
[INFO] --------------------------------[ pom ]---------------------------------
[WARNING] *****************************************************************
[WARNING] * Your build is requesting parallel execution, but project *
[WARNING] * contains the following plugin(s) that have goals not marked *
[WARNING] * as @threadSafe to support parallel building. *
[WARNING] * While this /may/ work fine, please look for plugin updates *
[WARNING] * and/or request plugins be made thread-safe. *
[WARNING] * If reporting an issue, report it against the plugin in *
[WARNING] * question, not against maven-core *
[WARNING] *****************************************************************
[WARNING] The following plugins are not marked @threadSafe in dpas-bom:
[WARNING] org.apache.maven.plugins:maven-release-plugin:2.5.3
[WARNING] Enable debug to see more precisely which goals are not marked 
@threadSafe.
[WARNING] *****************************************************************
{code}

)

> -Darguments doesn't allow -T to be passed to forked builds for multi threading
> ------------------------------------------------------------------------------
>
>                 Key: MRELEASE-786
>                 URL: https://issues.apache.org/jira/browse/MRELEASE-786
>             Project: Maven Release Plugin
>          Issue Type: Bug
>          Components: prepare
>    Affects Versions: 2.3.2
>            Reporter: Tom Clark
>            Assignee: Robert Scholte
>            Priority: Major
>             Fix For: 2.4
>
>
> I would like to be able to use -T with the release plugin for the compiling 
> phase, as the plugin is thread safe, which would allow for about half the 
> release time.
> I've tried:
> {code}
> -Darguments='-T 3'
> {code}
> which doesn't throw an error but doesn't actually trigger multi threading.
> also:
> {code}
> -Darguments='-T3'
> -Darguments='"-T 3"'
> {code}
> Both throws an error saying that -T isn't parsable
> {code}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-release-plugin:2.3.2:prepare (default-cli) on 
> project parent: Failed to re-parse additional arguments for Maven invocation. 
> Unrecognized option: -T -> [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 parent: Failed to re-parse additional arguments for 
> Maven invocation.
>       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: Failed to re-parse 
> additional arguments for Maven invocation.
>       at 
> org.apache.maven.plugins.release.PrepareReleaseMojo.prepareRelease(PrepareReleaseMojo.java:295)
>       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.ReleaseExecutionException: Failed 
> to re-parse additional arguments for Maven invocation.
>       at 
> org.apache.maven.shared.release.phase.AbstractRunGoalsPhase.execute(AbstractRunGoalsPhase.java:89)
>       at 
> org.apache.maven.shared.release.phase.RunPrepareGoalsPhase.execute(RunPrepareGoalsPhase.java:44)
>       at 
> org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:234)
>       at 
> org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:169)
>       at 
> org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:146)
>       at 
> org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:107)
>       at 
> org.apache.maven.plugins.release.PrepareReleaseMojo.prepareRelease(PrepareReleaseMojo.java:291)
>       ... 22 more
> Caused by: org.apache.maven.shared.release.exec.MavenExecutorException: 
> Failed to re-parse additional arguments for Maven invocation.
>       at 
> org.apache.maven.shared.release.exec.InvokerMavenExecutor.setupRequest(InvokerMavenExecutor.java:335)
>       at 
> org.apache.maven.shared.release.exec.InvokerMavenExecutor.executeGoals(InvokerMavenExecutor.java:394)
>       at 
> org.apache.maven.shared.release.exec.AbstractMavenExecutor.executeGoals(AbstractMavenExecutor.java:85)
>       at 
> org.apache.maven.shared.release.phase.AbstractRunGoalsPhase.execute(AbstractRunGoalsPhase.java:81)
>       ... 28 more
> Caused by: org.apache.commons.cli.UnrecognizedOptionException: Unrecognized 
> option: -T
>       at org.apache.commons.cli.Parser.processOption(Parser.java:253)
>       at org.apache.commons.cli.Parser.parse(Parser.java:170)
>       at org.apache.commons.cli.Parser.parse(Parser.java:114)
>       at 
> org.apache.maven.shared.release.exec.InvokerMavenExecutor.setupRequest(InvokerMavenExecutor.java:176)
>       ... 31 more
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to