[jira] [Updated] (MDEPLOY-297) [REGRESSION] deploy-file no longer honor 'packaging' parameter

[ https://issues.apache.org/jira/browse/MDEPLOY-297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Tran updated MDEPLOY-297: - Summary: [REGRESSION] deploy-file no longer honor 'packaging' parameter (was: [REGRESSION] deploy-file

[jira] [Updated] (MDEPLOY-297) [REGRESSION] deploy-file not longer honor 'packaging' parameter

[ https://issues.apache.org/jira/browse/MDEPLOY-297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Tran updated MDEPLOY-297: - Summary: [REGRESSION] deploy-file not longer honor 'packaging' parameter (was: [REGRESSION]

[jira] [Created] (MDEPLOY-297) [REGRESSION] deploy-file not long honor 'packaging' parameter

Dan Tran created MDEPLOY-297: Summary: [REGRESSION] deploy-file not long honor 'packaging' parameter Key: MDEPLOY-297 URL: https://issues.apache.org/jira/browse/MDEPLOY-297 Project: Maven Deploy Plugin

[jira] [Commented] (MWRAPPER-68) MVNW_REPOURL improperly formed distributionUrl

[ https://issues.apache.org/jira/browse/MWRAPPER-68?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17553503#comment-17553503 ] Dan Tran commented on MWRAPPER-68: -- I am facing same issue after upgrading to 3.1.1 > MVNW_REPOURL

[jira] [Comment Edited] (MNG-7433) [REGRESSION] Multiple maven instances working on same source tree can lock each other

[ https://issues.apache.org/jira/browse/MNG-7433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17523970#comment-17523970 ] Dan Tran edited comment on MNG-7433 at 4/19/22 1:16 AM: Actually, I firmly believe

[jira] [Comment Edited] (MNG-7433) [REGRESSION] Multiple maven instances working on same source tree can lock each other

[ https://issues.apache.org/jira/browse/MNG-7433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17523970#comment-17523970 ] Dan Tran edited comment on MNG-7433 at 4/19/22 1:15 AM: Actually, I firmly believe

[jira] [Commented] (MNG-7433) [REGRESSION] Multiple maven instances working on same source tree can lock each other

[ https://issues.apache.org/jira/browse/MNG-7433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17523970#comment-17523970 ] Dan Tran commented on MNG-7433: --- Actually, I firmly believe it has something to do with one of my reactor

[jira] [Commented] (MNG-7433) [REGRESSION] Multiple maven instances working on same source tree can lock each other

[ https://issues.apache.org/jira/browse/MNG-7433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17523616#comment-17523616 ] Dan Tran commented on MNG-7433: --- basically, all running mojo executions in a reactor multi-thread build must

[jira] [Commented] (MNG-7433) [REGRESSION] Multiple maven instances working on same source tree can lock each other

[ https://issues.apache.org/jira/browse/MNG-7433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17523538#comment-17523538 ] Dan Tran commented on MNG-7433: --- I will proceed to update all our internal mojos to non-aggregate, and

[jira] [Commented] (MNG-7433) [REGRESSION] Multiple maven instances working on same source tree can lock each other

[ https://issues.apache.org/jira/browse/MNG-7433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17521340#comment-17521340 ] Dan Tran commented on MNG-7433: --- buildnumber:create-metadate is used since it has a feature we need to dump

[jira] [Comment Edited] (MNG-7433) [REGRESSION] Multiple maven instances working on same source tree can lock each other

[ https://issues.apache.org/jira/browse/MNG-7433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17520123#comment-17520123 ] Dan Tran edited comment on MNG-7433 at 4/10/22 8:58 AM: per my finding, i updated

[jira] [Commented] (MNG-7433) [REGRESSION] Multiple maven instances working on same source tree can lock each other

[ https://issues.apache.org/jira/browse/MNG-7433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17520123#comment-17520123 ] Dan Tran commented on MNG-7433: --- per my finding, i updated my mdev:sonar ( the one that spins another mvn,

[jira] [Commented] (MNG-7433) [REGRESSION] Multiple maven instances working on same source tree can lock each other

[ https://issues.apache.org/jira/browse/MNG-7433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17520061#comment-17520061 ] Dan Tran commented on MNG-7433: --- [~cstamas] from your explanation, can I assume that all 'aggregating' mojo

[jira] (MNG-7433) [REGRESSION] Multiple maven instances working on same source tree can lock each other

[ https://issues.apache.org/jira/browse/MNG-7433 ] Dan Tran deleted comment on MNG-7433: --- was (Author: dantran): further testing and debugging show that all mojo, with 'aggregator = true' set at @Mojo, executions are serialized in multi-thread

[jira] [Commented] (MNG-7433) [REGRESSION] Multiple maven instances working on same source tree can lock each other

[ https://issues.apache.org/jira/browse/MNG-7433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17520058#comment-17520058 ] Dan Tran commented on MNG-7433: --- further testing and debugging show that all mojo, with 'aggregator = true'

[jira] [Comment Edited] (MNG-7433) [REGRESSION] Multiple maven instances working on same source tree can lock each other

[ https://issues.apache.org/jira/browse/MNG-7433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17519781#comment-17519781 ] Dan Tran edited comment on MNG-7433 at 4/8/22 9:39 PM: --- Thanks for the suggestion

[jira] [Comment Edited] (MNG-7433) [REGRESSION] Multiple maven instances working on same source tree can lock each other

[ https://issues.apache.org/jira/browse/MNG-7433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17519781#comment-17519781 ] Dan Tran edited comment on MNG-7433 at 4/8/22 8:21 PM: --- Thanks for the suggestion

[jira] [Commented] (MNG-7433) [REGRESSION] Multiple maven instances working on same source tree can lock each other

[ https://issues.apache.org/jira/browse/MNG-7433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17519781#comment-17519781 ] Dan Tran commented on MNG-7433: --- Thanks for the suggestion regarding 'aggregating mojo', I found the

[jira] [Comment Edited] (MNG-7433) [REGRESSION] Multiple maven instances working on same source tree can lock each other

[ https://issues.apache.org/jira/browse/MNG-7433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17519165#comment-17519165 ] Dan Tran edited comment on MNG-7433 at 4/8/22 3:18 AM: --- here is a brief just to

[jira] [Commented] (MNG-7433) [REGRESSION] Multiple maven instances working on same source tree can lock each other

[ https://issues.apache.org/jira/browse/MNG-7433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17519165#comment-17519165 ] Dan Tran commented on MNG-7433: --- here is a brief just to visualize the issue and its steps {code:java}

[jira] [Commented] (MNG-7433) [REGRESSION] Multiple maven instances working on same source tree can lock each other

[ https://issues.apache.org/jira/browse/MNG-7433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17519031#comment-17519031 ] Dan Tran commented on MNG-7433: --- my .mvn/extensions.xml does have {code:java} io.takari.maven

[jira] [Commented] (MNG-7433) [REGRESSION] Multiple maven instances working on same source tree can lock each other

[ https://issues.apache.org/jira/browse/MNG-7433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17518656#comment-17518656 ] Dan Tran commented on MNG-7433: --- [~cstamas] thanks for the advice. In my use case i have 2 MVN each of

[jira] [Comment Edited] (MNG-7433) Multiple maven instances working on same source tree can lock each other

[ https://issues.apache.org/jira/browse/MNG-7433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17508424#comment-17508424 ] Dan Tran edited comment on MNG-7433 at 3/20/22, 7:49 PM: - I also tried: *

[jira] [Comment Edited] (MNG-7433) Multiple maven instances working on same source tree can lock each other

[ https://issues.apache.org/jira/browse/MNG-7433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17508563#comment-17508563 ] Dan Tran edited comment on MNG-7433 at 3/20/22, 7:49 AM: - The below comment block

[jira] [Commented] (MNG-7433) Multiple maven instances working on same source tree can lock each other

[ https://issues.apache.org/jira/browse/MNG-7433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17509393#comment-17509393 ] Dan Tran commented on MNG-7433: --- [~gnodet] please advice > Multiple maven instances working on same source

[jira] [Updated] (MNG-7433) Multiple maven instances working on same source tree can lock each other

[ https://issues.apache.org/jira/browse/MNG-7433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Tran updated MNG-7433: -- Summary: Multiple maven instances working on same source tree can lock each other (was: multiple maven

[jira] [Comment Edited] (MNG-7433) multiple maven instances working same source tree can lock each other

[ https://issues.apache.org/jira/browse/MNG-7433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17508424#comment-17508424 ] Dan Tran edited comment on MNG-7433 at 3/20/22, 3:35 AM: - I also tried: *

[jira] [Comment Edited] (MNG-7433) multiple maven instances working same source tree can lock each other

[ https://issues.apache.org/jira/browse/MNG-7433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17508424#comment-17508424 ] Dan Tran edited comment on MNG-7433 at 3/20/22, 2:27 AM: - I also tried: *

[jira] [Comment Edited] (MNG-7433) multiple maven instances working same source tree can lock each other

[ https://issues.apache.org/jira/browse/MNG-7433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17508424#comment-17508424 ] Dan Tran edited comment on MNG-7433 at 3/20/22, 2:26 AM: - I also tried: *

[jira] [Commented] (MNG-7433) multiple maven instances working same source tree can lock each other

[ https://issues.apache.org/jira/browse/MNG-7433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17508563#comment-17508563 ] Dan Tran commented on MNG-7433: --- The below comment block in interesting {code:java} /** *

[jira] [Comment Edited] (MNG-7433) multiple maven instances working same source tree can lock each other

[ https://issues.apache.org/jira/browse/MNG-7433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17508424#comment-17508424 ] Dan Tran edited comment on MNG-7433 at 3/18/22, 3:21 AM: - I also tried: *

[jira] [Comment Edited] (MNG-7433) multiple maven instances working same source tree can lock each other

[ https://issues.apache.org/jira/browse/MNG-7433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17508424#comment-17508424 ] Dan Tran edited comment on MNG-7433 at 3/17/22, 8:50 PM: - I also tried: *

[jira] [Commented] (MNG-7433) multiple maven instances working same source tree can lock each other

[ https://issues.apache.org/jira/browse/MNG-7433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17508424#comment-17508424 ] Dan Tran commented on MNG-7433: --- I also tried: * replicate local repo to dedicate for sonar:sonar

[jira] [Updated] (MNG-7433) multiple maven instances working same source tree can lock each other

[ https://issues.apache.org/jira/browse/MNG-7433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Tran updated MNG-7433: -- Description: I have a large multi modules java maven build where: * phase 1 - basic build + unit tests +

[jira] [Updated] (MNG-7433) multiple maven instances working same source tree can lock each other

[ https://issues.apache.org/jira/browse/MNG-7433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Tran updated MNG-7433: -- Description: I have a large multi modules java maven build where: * phase 1 - basic build + unit tests - 40

[jira] [Updated] (MNG-7433) multiple maven instances working same source tree can lock each other

[ https://issues.apache.org/jira/browse/MNG-7433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Tran updated MNG-7433: -- Description: I have a large multi modules java maven build where: * phase 1 - basic build + unit tests - 40

[jira] [Created] (MNG-7433) multiple maven instances working same source tree can lock each other

Dan Tran created MNG-7433: - Summary: multiple maven instances working same source tree can lock each other Key: MNG-7433 URL: https://issues.apache.org/jira/browse/MNG-7433 Project: Maven Issue

[jira] (SUREFIRE-2033) Regression: 3.0.0-M5 misidentifies JUnit 5 configuration as JUnit 4

[ https://issues.apache.org/jira/browse/SUREFIRE-2033 ] Dan Tran deleted comment on SUREFIRE-2033: was (Author: dantran): I do agree with [~roxspring] this is a regression compared with M4. with M6, i now have to manually add provider ( in my

[jira] [Commented] (SUREFIRE-2033) Regression: 3.0.0-M5 misidentifies JUnit 5 configuration as JUnit 4

[ https://issues.apache.org/jira/browse/SUREFIRE-2033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17505302#comment-17505302 ] Dan Tran commented on SUREFIRE-2033: I do agree with [~roxspring] this is a regression compared

[jira] [Comment Edited] (MRESOLVER-123) Provide a global locking sync context by default

[ https://issues.apache.org/jira/browse/MRESOLVER-123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17174068#comment-17174068 ] Dan Tran edited comment on MRESOLVER-123 at 8/10/20, 4:21 AM: -- some thing

[jira] [Commented] (MRESOLVER-123) Provide a global locking sync context by default

[ https://issues.apache.org/jira/browse/MRESOLVER-123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17174068#comment-17174068 ] Dan Tran commented on MRESOLVER-123: some thing like below {code:java} [ERROR] Failed to execute

[jira] [Commented] (MRESOLVER-123) Provide a global locking sync context by default

[ https://issues.apache.org/jira/browse/MRESOLVER-123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17173401#comment-17173401 ] Dan Tran commented on MRESOLVER-123: I do have random compilation failures. The error sounds like

[jira] [Commented] (MRESOLVER-123) Provide a global locking sync context by default

[ https://issues.apache.org/jira/browse/MRESOLVER-123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17173329#comment-17173329 ] Dan Tran commented on MRESOLVER-123: w/o smart build, no issue with Resolver 1.4.2 but

[jira] [Commented] (MRESOLVER-123) Provide a global locking sync context by default

[ https://issues.apache.org/jira/browse/MRESOLVER-123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17173017#comment-17173017 ] Dan Tran commented on MRESOLVER-123: my 350 modules build without tests + Takari 4 thread smart

[jira] [Commented] (MRESOLVER-123) Provide a global locking sync context by default

[ https://issues.apache.org/jira/browse/MRESOLVER-123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17172965#comment-17172965 ] Dan Tran commented on MRESOLVER-123: I rebuilt maven 3.6.3 with apache-resolver-1.5.1-SNAPSHOT and

[jira] [Comment Edited] (MNG-6604) Intermittent failures while downloading GAVs from Nexus

[ https://issues.apache.org/jira/browse/MNG-6604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16814886#comment-16814886 ] Dan Tran edited comment on MNG-6604 at 4/10/19 9:41 PM: This is very strange, I am

[jira] [Commented] (MNG-6604) Intermittent failures while downloading GAVs from Nexus

[ https://issues.apache.org/jira/browse/MNG-6604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16814886#comment-16814886 ] Dan Tran commented on MNG-6604: --- This is very strange, I am very sure there are a lot of us successfully

[jira] [Commented] (SUREFIRE-1585) Align JUnit Platform version at runtime

[ https://issues.apache.org/jira/browse/SUREFIRE-1585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16782257#comment-16782257 ] Dan Tran commented on SUREFIRE-1585: [~tibor17] could you deploy a new snaphost for

[jira] [Comment Edited] (SUREFIRE-1546) JUnit 5 runner does not honor JUnit 5 display names

[ https://issues.apache.org/jira/browse/SUREFIRE-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16763744#comment-16763744 ] Dan Tran edited comment on SUREFIRE-1546 at 2/8/19 4:35 PM: Yes, we can

[jira] [Commented] (SUREFIRE-1546) JUnit 5 runner does not honor JUnit 5 display names

[ https://issues.apache.org/jira/browse/SUREFIRE-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16763744#comment-16763744 ] Dan Tran commented on SUREFIRE-1546: Yes, we can consume the snapshot directly. Since this is

[jira] [Comment Edited] (SUREFIRE-1546) JUnit 5 runner does not honor JUnit 5 display names

[ https://issues.apache.org/jira/browse/SUREFIRE-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16763134#comment-16763134 ] Dan Tran edited comment on SUREFIRE-1546 at 2/7/19 10:29 PM: - "By default,

[jira] [Commented] (SUREFIRE-1546) JUnit 5 runner does not honor JUnit 5 display names

[ https://issues.apache.org/jira/browse/SUREFIRE-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16763134#comment-16763134 ] Dan Tran commented on SUREFIRE-1546: "By default, there would be current behavior." this is good

[jira] [Comment Edited] (SUREFIRE-1546) JUnit 5 runner does not honor JUnit 5 display names

[ https://issues.apache.org/jira/browse/SUREFIRE-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16758909#comment-16758909 ] Dan Tran edited comment on SUREFIRE-1546 at 2/2/19 6:53 AM: what is the

[jira] [Commented] (SUREFIRE-1546) JUnit 5 runner does not honor JUnit 5 display names

[ https://issues.apache.org/jira/browse/SUREFIRE-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16758909#comment-16758909 ] Dan Tran commented on SUREFIRE-1546: what is the final verdict? what is the format of adding

[jira] [Commented] (SUREFIRE-1546) JUnit 5 runner does not honor JUnit 5 display names

[ https://issues.apache.org/jira/browse/SUREFIRE-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16758478#comment-16758478 ] Dan Tran commented on SUREFIRE-1546: correction, we are not parsing the content of display name

[jira] [Comment Edited] (SUREFIRE-1546) JUnit 5 runner does not honor JUnit 5 display names

[ https://issues.apache.org/jira/browse/SUREFIRE-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16758382#comment-16758382 ] Dan Tran edited comment on SUREFIRE-1546 at 2/1/19 2:59 PM: For reporting

[jira] [Commented] (SUREFIRE-1546) JUnit 5 runner does not honor JUnit 5 display names

[ https://issues.apache.org/jira/browse/SUREFIRE-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16758382#comment-16758382 ] Dan Tran commented on SUREFIRE-1546: For reporting purpose. We parse TEST-*.xml under

[jira] [Commented] (SUREFIRE-1546) JUnit 5 runner does not honor JUnit 5 display names

[ https://issues.apache.org/jira/browse/SUREFIRE-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16755320#comment-16755320 ] Dan Tran commented on SUREFIRE-1546: tested 3.0.0-M4-SNAPSHOT, looking forward to M4 release. Many

[jira] [Commented] (SUREFIRE-1546) JUnit 5 runner does not honor JUnit 5 display names

[ https://issues.apache.org/jira/browse/SUREFIRE-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16753392#comment-16753392 ] Dan Tran commented on SUREFIRE-1546: @Tibor please deploy new snapshot at

[jira] [Commented] (WAGON-544) Work around JSch issue #122

[ https://issues.apache.org/jira/browse/WAGON-544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16732805#comment-16732805 ] Dan Tran commented on WAGON-544: the branch looks good, I integrated WAGON-544 branch with maven

[jira] [Commented] (WAGON-543) wagon-ssh download hangs

[ https://issues.apache.org/jira/browse/WAGON-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16732297#comment-16732297 ] Dan Tran commented on WAGON-543: Let's go with that option > wagon-ssh download hangs >

[jira] [Commented] (WAGON-543) wagon-ssh download hangs

[ https://issues.apache.org/jira/browse/WAGON-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16730905#comment-16730905 ] Dan Tran commented on WAGON-543: Looks like new changes at AbstractWagon's transfer method requires NIO

[jira] [Comment Edited] (WAGON-543) wagon-ssh download hangs

[ https://issues.apache.org/jira/browse/WAGON-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16730860#comment-16730860 ] Dan Tran edited comment on WAGON-543 at 12/30/18 1:04 AM: -- To help with debugging

[jira] [Commented] (WAGON-543) wagon-ssh download hangs

[ https://issues.apache.org/jira/browse/WAGON-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16730860#comment-16730860 ] Dan Tran commented on WAGON-543: To help with debugging this issue, I cooked up a sshshell wrapper of

[jira] [Comment Edited] (WAGON-543) wagon-ssh download hangs

[ https://issues.apache.org/jira/browse/WAGON-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16730845#comment-16730845 ] Dan Tran edited comment on WAGON-543 at 12/29/18 10:55 PM: --- it passes b/c you

[jira] [Commented] (WAGON-543) wagon-ssh download hangs

[ https://issues.apache.org/jira/browse/WAGON-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16730845#comment-16730845 ] Dan Tran commented on WAGON-543: it passes b/c you have wagon-provider-api-3.2.0.jar under your maven's

[jira] [Commented] (WAGON-537) Maven transfer speed of large artifacts is slow due to unsuitable buffer strategy

[ https://issues.apache.org/jira/browse/WAGON-537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16730818#comment-16730818 ] Dan Tran commented on WAGON-537: To test wagon 3.3.0 download speed, I build maven-3.6.1-snapshot with the

[jira] [Updated] (WAGON-543) wagon-ssh download hangs

[ https://issues.apache.org/jira/browse/WAGON-543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Tran updated WAGON-543: --- Description: To reproduce this issue 1. checkout https://github.com/mojohaus/wagon-maven-plugin.git 2.

[jira] [Commented] (WAGON-537) Maven transfer speed of large artifacts is slow due to unsuitable buffer strategy

[ https://issues.apache.org/jira/browse/WAGON-537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16730513#comment-16730513 ] Dan Tran commented on WAGON-537: I see no gain in my download. Basic single download test with curl curl

[jira] [Updated] (WAGON-543) wagon-ssh download hangs

[ https://issues.apache.org/jira/browse/WAGON-543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Tran updated WAGON-543: --- Description: To reproduce this issue 1. checkout https://github.com/mojohaus/wagon-maven-plugin.git 2.

[jira] [Updated] (WAGON-543) wagon-ssh download hangs

[ https://issues.apache.org/jira/browse/WAGON-543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Tran updated WAGON-543: --- Description: To reproduce this issue 1. checkout https://github.com/mojohaus/wagon-maven-plugin.git 2.

[jira] [Updated] (WAGON-543) wagon-ssh download hangs

[ https://issues.apache.org/jira/browse/WAGON-543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Tran updated WAGON-543: --- Description: To reproduce this issue 1. checkout https://github.com/mojohaus/wagon-maven-plugin.git 2.

[jira] [Updated] (WAGON-543) wagon-ssh download hangs

[ https://issues.apache.org/jira/browse/WAGON-543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Tran updated WAGON-543: --- Description: To reproduce this issue 1. checkout https://github.com/mojohaus/wagon-maven-plugin.git 2.

[jira] [Updated] (WAGON-543) wagon-ssh download hangs

[ https://issues.apache.org/jira/browse/WAGON-543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Tran updated WAGON-543: --- Description: To reproduce this issue 1. checkout https://github.com/mojohaus/wagon-maven-plugin.git 2.

[jira] [Updated] (WAGON-543) wagon-ssh download hangs

[ https://issues.apache.org/jira/browse/WAGON-543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Tran updated WAGON-543: --- Description: To reproduce this issue 1. checkout https://github.com/mojohaus/wagon-maven-plugin.git 2.

[jira] [Updated] (WAGON-543) wagon-ssh download hangs

[ https://issues.apache.org/jira/browse/WAGON-543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Tran updated WAGON-543: --- Description: To reproduce this issue 1. checkout https://github.com/mojohaus/wagon-maven-plugin.git 2.

[jira] [Created] (WAGON-543) wagon-ssh download hangs

Dan Tran created WAGON-543: -- Summary: wagon-ssh download hangs Key: WAGON-543 URL: https://issues.apache.org/jira/browse/WAGON-543 Project: Maven Wagon Issue Type: Bug Components:

[jira] [Commented] (WAGON-537) Maven transfer speed of large artifacts is slow due to unsuitable buffer strategy

[ https://issues.apache.org/jira/browse/WAGON-537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16729902#comment-16729902 ] Dan Tran commented on WAGON-537: Tested with latest maven 3.6.1-SNAPSHOT with both latest wagon snapshot

[jira] [Commented] (WAGON-537) Maven transfer speed of large artifacts is slow due to unsuitable buffer strategy

[ https://issues.apache.org/jira/browse/WAGON-537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16729287#comment-16729287 ] Dan Tran commented on WAGON-537: sorry about the noise, I am able to cook up a multi SCM freeslyle job to

[jira] [Commented] (WAGON-537) Maven transfer speed of large artifacts is slow due to unsuitable buffer strategy

[ https://issues.apache.org/jira/browse/WAGON-537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16729276#comment-16729276 ] Dan Tran commented on WAGON-537: Could you deploy latest wagon snapshot to repository.apache.org? This is

[jira] [Commented] (WAGON-537) Maven transfer speed of large artifacts is slow due to unsuitable buffer strategy

[ https://issues.apache.org/jira/browse/WAGON-537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16728872#comment-16728872 ] Dan Tran commented on WAGON-537: I think not able to use dependency as snapshot is a setback. but i am

[jira] [Commented] (WAGON-537) Maven transfer speed of large artifacts is slow due to unsuitable buffer strategy

[ https://issues.apache.org/jira/browse/WAGON-537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16728837#comment-16728837 ] Dan Tran commented on WAGON-537: [~michael-o] could you hook up latest wagon snapshot with maven

[jira] [Commented] (MASSEMBLY-766) OOM with 1CPU

[ https://issues.apache.org/jira/browse/MASSEMBLY-766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16728087#comment-16728087 ] Dan Tran commented on MASSEMBLY-766: Let's close this ticket since it is no longer practical >

[jira] [Commented] (MRESOLVER-64) restore setLoggerFactory(...) API deleted from version 1.3.0

[ https://issues.apache.org/jira/browse/MRESOLVER-64?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16718504#comment-16718504 ] Dan Tran commented on MRESOLVER-64: --- Are we all set?  > restore setLoggerFactory(...) API deleted

[jira] [Commented] (SUREFIRE-1546) JUnit 5 runner does not honor JUnit 5 display names

[ https://issues.apache.org/jira/browse/SUREFIRE-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16716519#comment-16716519 ] Dan Tran commented on SUREFIRE-1546: is this scheduled for 3.0 surefire? > JUnit 5 runner does

[jira] [Comment Edited] (MRESOLVER-64) restore setLoggerFactory(...) API deleted from version 1.3.0

[ https://issues.apache.org/jira/browse/MRESOLVER-64?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16714222#comment-16714222 ] Dan Tran edited comment on MRESOLVER-64 at 12/10/18 4:03 AM: - I am able to

[jira] [Commented] (MRESOLVER-64) restore setLoggerFactory(...) API deleted from version 1.3.0

[ https://issues.apache.org/jira/browse/MRESOLVER-64?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16714222#comment-16714222 ] Dan Tran commented on MRESOLVER-64: --- I am able to reproduce this issue with instructions from

[jira] [Commented] (MRESOLVER-64) restore setLoggerFactory(...) API deleted from version 1.3.0

[ https://issues.apache.org/jira/browse/MRESOLVER-64?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16714161#comment-16714161 ] Dan Tran commented on MRESOLVER-64: --- [~slachiewicz] Could you help to give it a try. I totally new

[jira] [Commented] (MRESOLVER-64) restore setLoggerFactory(...) API deleted from version 1.3.0

[ https://issues.apache.org/jira/browse/MRESOLVER-64?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16713887#comment-16713887 ] Dan Tran commented on MRESOLVER-64: --- I think we should hook this up with Maven 3.6.1-SNAPSHOT and

[jira] [Commented] (WAGON-537) Maven transfer speed of large artifacts is slow due to unsuitable buffer strategy

[ https://issues.apache.org/jira/browse/WAGON-537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16682745#comment-16682745 ] Dan Tran commented on WAGON-537: This is Xmas present ... early. Many thanks > Maven transfer speed of

[jira] [Commented] (SUREFIRE-1359) Corrupted stdin stream in forked JVM 1. See the dump file

[ https://issues.apache.org/jira/browse/SUREFIRE-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16674259#comment-16674259 ] Dan Tran commented on SUREFIRE-1359: [~MattNelson] I am experiencing the same issue. maven 3.6

[jira] [Commented] (MNG-6412) Exceeding project discovery time when using CI friendly versions

[ https://issues.apache.org/jira/browse/MNG-6412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1555#comment-1555 ] Dan Tran commented on MNG-6412: --- oh mine!! this is fixed on my 300+ maven modules project using maven 3.6.

[jira] [Closed] (SUREFIRE-1567) Surefire Plugin should evaluate Junit 5 @DisplayName

[ https://issues.apache.org/jira/browse/SUREFIRE-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Tran closed SUREFIRE-1567. -- Resolution: Duplicate > Surefire Plugin should evaluate Junit 5 @DisplayName >

[jira] [Updated] (SUREFIRE-1567) Surefire Plugin should evaluate Junit 5 @DisplayName

[ https://issues.apache.org/jira/browse/SUREFIRE-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Tran updated SUREFIRE-1567: --- Description: Details discussed at https://github.com/junit-team/junit5/issues/990 Per junit5

[jira] [Created] (SUREFIRE-1567) Surefire Plugin should evaluate Junit 5 @DisplayName

Dan Tran created SUREFIRE-1567: -- Summary: Surefire Plugin should evaluate Junit 5 @DisplayName Key: SUREFIRE-1567 URL: https://issues.apache.org/jira/browse/SUREFIRE-1567 Project: Maven Surefire

[jira] [Commented] (SUREFIRE-1527) Surefire does not discover junit5 test case when testng is in the classpath

[ https://issues.apache.org/jira/browse/SUREFIRE-1527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16529343#comment-16529343 ] Dan Tran commented on SUREFIRE-1527: Ouch, my simple naive solution breaks any TestNG test cases

[jira] [Comment Edited] (SUREFIRE-1527) Surefire does not discover junit5 test case when testng is in the classpath

[ https://issues.apache.org/jira/browse/SUREFIRE-1527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16529019#comment-16529019 ] Dan Tran edited comment on SUREFIRE-1527 at 7/1/18 4:51 PM: Here is

[jira] [Comment Edited] (SUREFIRE-1527) Surefire does not discover junit5 test case when testng is in the classpath

[ https://issues.apache.org/jira/browse/SUREFIRE-1527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16529019#comment-16529019 ] Dan Tran edited comment on SUREFIRE-1527 at 7/1/18 9:05 AM: Here is

[jira] [Comment Edited] (SUREFIRE-1527) Surefire does not discover junit5 test case when testng is in the classpath

[ https://issues.apache.org/jira/browse/SUREFIRE-1527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16529019#comment-16529019 ] Dan Tran edited comment on SUREFIRE-1527 at 7/1/18 9:04 AM: Here is

[jira] [Comment Edited] (SUREFIRE-1527) Surefire does not discover junit5 test case when testng is in the classpath

[ https://issues.apache.org/jira/browse/SUREFIRE-1527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16529019#comment-16529019 ] Dan Tran edited comment on SUREFIRE-1527 at 7/1/18 9:04 AM: Here is

  1   2   3   4   5   6   7   8   9   >