[
https://issues.apache.org/jira/browse/MDEPLOY-206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamas Cservenak updated MDEPLOY-206:
------------------------------------
Description:
When deploying at end with a large reactor the deployment process can take some
time. If the DeployMojo was updated to support a configuration value for the
amount of parallelism the deployment could be speed up substantially.
The change in m-deploy-p is nearly trivial (create one DeployRequest with
everything), but once MRESOLVER-319 in place (planned to be part of Maven
3.9.1), parallel deploy w/ deployAtEnd will be handled by resolver.
was:
When deploying at end with a large reactor the deployment process can take some
time. If the DeployMojo was updated to support a configuration value for the
amount of parallelism the deployment could be speed up substantially.
The change in m-deploy-p is nearly trivial (create one DeployRequest with
everything), but once
> Support parallel deployment at end (needs resolver changes as well)
> -------------------------------------------------------------------
>
> Key: MDEPLOY-206
> URL: https://issues.apache.org/jira/browse/MDEPLOY-206
> Project: Maven Deploy Plugin
> Issue Type: New Feature
> Components: deploy:deploy
> Reporter: Matt Nelson
> Assignee: Slawomir Jaranowski
> Priority: Major
> Fix For: 3.1.0
>
>
> When deploying at end with a large reactor the deployment process can take
> some time. If the DeployMojo was updated to support a configuration value for
> the amount of parallelism the deployment could be speed up substantially.
> The change in m-deploy-p is nearly trivial (create one DeployRequest with
> everything), but once MRESOLVER-319 in place (planned to be part of Maven
> 3.9.1), parallel deploy w/ deployAtEnd will be handled by resolver.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
