You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Tamas Cservenak (Jira)" <ji...@apache.org> on 2023/03/21 16:30:00 UTC

[jira] [Comment Edited] (MDEPLOY-307) [REGRESSION] Longer deploy times

    [ https://issues.apache.org/jira/browse/MDEPLOY-307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17703285#comment-17703285 ] 

Tamas Cservenak edited comment on MDEPLOY-307 at 3/21/23 4:29 PM:
------------------------------------------------------------------

Hm, that is strange. What transport you use (ie. Do you force wagon or just leave to Maven to sort it out)? Can you show me some concrete numbers? (Times with 3.8 maven vs 3.9.1?)


was (Author: cstamas):
Hm, that us strange. What transport you use (ie. Do you force wagon or just leave to Maven to sort it out)? Can you show me some concrete numbers? (Times with 3.8 maven vs 3.9.1?)

> [REGRESSION] Longer deploy times
> --------------------------------
>
>                 Key: MDEPLOY-307
>                 URL: https://issues.apache.org/jira/browse/MDEPLOY-307
>             Project: Maven Deploy Plugin
>          Issue Type: Bug
>          Components: deploy:deploy
>    Affects Versions: 3.1.0
>            Reporter: Delany
>            Priority: Major
>
> On Windows OS, a 500 module build takes half an hour to deploy when using deployAtEnd.
> I was expecting an improvement in build time with this version of the plugin.
> Maven 3.9.0



--
This message was sent by Atlassian Jira
(v8.20.10#820010)