[jira] [Commented] (MNGSITE-407) Delete CI page

[ https://issues.apache.org/jira/browse/MNGSITE-407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17104976#comment-17104976 ] Hudson commented on MNGSITE-407: Build succeeded in Jenkins: Maven TLP » maven-site » elharo-patch-5 #3

[jira] [Commented] (ARCHETYPE-584) Resulting root pom.xml from archetype generation has additional newlines with JDK11

[ https://issues.apache.org/jira/browse/ARCHETYPE-584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17104951#comment-17104951 ] Ruwen Reddig commented on ARCHETYPE-584: Hello, since this issue just passed its 6 month, I

[jira] [Commented] (MDEP-480) There should be an option to prevent files overwrite for unpack-dependencies and unpack

[ https://issues.apache.org/jira/browse/MDEP-480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17104887#comment-17104887 ] Benson Margulies commented on MDEP-480: --- Jonathan Volfson and I are working on this. I wanted to

[jira] [Updated] (MDEP-480) There should be an option to prevent files overwrite for unpack-dependencies and unpack

[ https://issues.apache.org/jira/browse/MDEP-480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies updated MDEP-480: -- Labels: (was: close-pending) > There should be an option to prevent files overwrite for

[jira] [Updated] (MDEP-694) Include import-scoped dependency in the output of the dependency plugin goals (e.g. `analyze`, `resolve`, `tree`, `list`, ...)

[ https://issues.apache.org/jira/browse/MDEP-694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Wu updated MDEP-694: - Description: * Currently, there is no way to include/show an import-scoped dependency in the output of

[jira] [Updated] (MDEP-694) Include import-scoped dependency in the output of the dependency plugin goals (e.g. `analyze`, `resolve`, `tree`, `list`, ...)

[ https://issues.apache.org/jira/browse/MDEP-694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Wu updated MDEP-694: - Attachment: hello-model.pom.xml hello-bom.pom.xml > Include import-scoped dependency in the output

[jira] [Created] (MDEP-694) Include import-scoped dependency in the output of the dependency plugin goals (e.g. `analyze`, `resolve`, `tree`, `list`, ...)

John Wu created MDEP-694: Summary: Include import-scoped dependency in the output of the dependency plugin goals (e.g. `analyze`, `resolve`, `tree`, `list`, ...) Key: MDEP-694 URL:

[jira] [Assigned] (SCM-941) Remove/replace ScmTest.assertPath

[ https://issues.apache.org/jira/browse/SCM-941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elliotte Rusty Harold reassigned SCM-941: - Assignee: Elliotte Rusty Harold > Remove/replace ScmTest.assertPath >

[jira] [Created] (SCM-941) Remove/replace ScmTest.assertPath

Elliotte Rusty Harold created SCM-941: - Summary: Remove/replace ScmTest.assertPath Key: SCM-941 URL: https://issues.apache.org/jira/browse/SCM-941 Project: Maven SCM Issue Type: Bug

[jira] [Commented] (SCM-938) TagMojoTest is flaky on Windows

[ https://issues.apache.org/jira/browse/SCM-938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17104710#comment-17104710 ] Michael Osipov commented on SCM-938: Please create an INFRA ticket. They must create

[jira] [Commented] (SCM-938) TagMojoTest is flaky on Windows

[ https://issues.apache.org/jira/browse/SCM-938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17104712#comment-17104712 ] Michael Osipov commented on SCM-938:

[jira] [Comment Edited] (SCM-939) Assume SCM is present

[ https://issues.apache.org/jira/browse/SCM-939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17104459#comment-17104459 ] Michael Osipov edited comment on SCM-939 at 5/11/20, 5:41 PM: -- Problem is

[jira] [Commented] (SCM-939) Assume SCM is present

[ https://issues.apache.org/jira/browse/SCM-939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17104700#comment-17104700 ] Elliotte Rusty Harold commented on SCM-939: --- It's possible we don't need to extend PlexusTestCase

[jira] [Assigned] (SCM-940) ScmTestCase.getModule should be abstract

[ https://issues.apache.org/jira/browse/SCM-940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elliotte Rusty Harold reassigned SCM-940: - Assignee: Elliotte Rusty Harold > ScmTestCase.getModule should be abstract >

[jira] [Commented] (SCM-939) Assume SCM is present

[ https://issues.apache.org/jira/browse/SCM-939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17104696#comment-17104696 ] Elliotte Rusty Harold commented on SCM-939: --- appears to be fixed in latest PlexusTestCase. We need

[jira] [Commented] (SCM-939) Assume SCM is present

[ https://issues.apache.org/jira/browse/SCM-939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17104459#comment-17104459 ] Elliotte Rusty Harold commented on SCM-939: --- Problem is PlexusTestCase.setUp catches

[jira] [Commented] (SCM-939) Assume SCM is present

[ https://issues.apache.org/jira/browse/SCM-939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17104457#comment-17104457 ] Elliotte Rusty Harold commented on SCM-939: --- This is tricky because Maven incorrectly treats an

[jira] [Created] (SCM-940) ScmTestCase.getModule should be abstract

Elliotte Rusty Harold created SCM-940: - Summary: ScmTestCase.getModule should be abstract Key: SCM-940 URL: https://issues.apache.org/jira/browse/SCM-940 Project: Maven SCM Issue Type:

[jira] [Comment Edited] (WAGON-590) Maven 3.5.0+ don't seem to send credentials after 301/302 http redirect

[ https://issues.apache.org/jira/browse/WAGON-590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17104410#comment-17104410 ] Michael Osipov edited comment on WAGON-590 at 5/11/20, 12:41 PM: - There is

[jira] [Comment Edited] (WAGON-590) Maven 3.5.0+ don't seem to send credentials after 301/302 http redirect

[ https://issues.apache.org/jira/browse/WAGON-590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17104410#comment-17104410 ] Michael Osipov edited comment on WAGON-590 at 5/11/20, 12:40 PM: - There is

[jira] [Commented] (WAGON-590) Maven 3.5.0+ don't seem to send credentials after 301/302 http redirect

[ https://issues.apache.org/jira/browse/WAGON-590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17104410#comment-17104410 ] Michael Osipov commented on WAGON-590: -- There is nothing from your end and there is little you can

[GitHub] [maven-wagon] elharo commented on pull request #66: [SCM-930] update plexus-utils

elharo commented on pull request #66: URL: https://github.com/apache/maven-wagon/pull/66#issuecomment-626673893 Jenkins passes. This is an automated message from the Apache Git Service. To respond to the message, please log

[GitHub] [maven-wagon] elharo opened a new pull request #66: [SCM-930] update plexus-utils

elharo opened a new pull request #66: URL: https://github.com/apache/maven-wagon/pull/66 @michael-o This syncs the version with Maven core head which already has 3.3.0 This is an automated message from the Apache Git

[GitHub] [maven-scm] elharo commented on a change in pull request #102: [SCM-936] extract common code

elharo commented on a change in pull request #102: URL: https://github.com/apache/maven-scm/pull/102#discussion_r422992708 ## File path: maven-scm-plugin/src/test/java/org/apache/maven/scm/plugin/TagMojoTest.java ## @@ -63,32 +62,29 @@ protected void setUp()

[GitHub] [maven-scm] elharo commented on a change in pull request #102: [SCM-936] extract common code

elharo commented on a change in pull request #102: URL: https://github.com/apache/maven-scm/pull/102#discussion_r422983147 ## File path: maven-scm-plugin/src/test/java/org/apache/maven/scm/plugin/TagMojoTest.java ## @@ -63,32 +62,29 @@ protected void setUp()

[GitHub] [maven-scm] michael-o commented on pull request #101: [SCM-937] replace deprecated methods

michael-o commented on pull request #101: URL: https://github.com/apache/maven-scm/pull/101#issuecomment-626649562 > > > If it's the Temp directory that's at fault, there might be a way to avoid that. What is your proposal then?

[GitHub] [maven-scm] michael-o commented on a change in pull request #102: [SCM-936] extract common code

michael-o commented on a change in pull request #102: URL: https://github.com/apache/maven-scm/pull/102#discussion_r422978204 ## File path: maven-scm-plugin/src/test/java/org/apache/maven/scm/plugin/TagMojoTest.java ## @@ -63,32 +62,29 @@ protected void setUp()

[GitHub] [maven-scm] elharo commented on a change in pull request #102: [SCM-936] extract common code

elharo commented on a change in pull request #102: URL: https://github.com/apache/maven-scm/pull/102#discussion_r422975447 ## File path: maven-scm-plugin/src/test/java/org/apache/maven/scm/plugin/TagMojoTest.java ## @@ -63,32 +62,29 @@ protected void setUp()

[GitHub] [maven-scm] michael-o commented on pull request #101: [SCM-937] replace deprecated methods

michael-o commented on pull request #101: URL: https://github.com/apache/maven-scm/pull/101#issuecomment-626641175 > > > #99 to update Plexus didn't flake, so possibly the plexus-utils update there fixes this? I don't think. It might be node specific that `Temp` does exist.

[GitHub] [maven-scm] michael-o commented on a change in pull request #102: [SCM-936] extract common code

michael-o commented on a change in pull request #102: URL: https://github.com/apache/maven-scm/pull/102#discussion_r422967796 ## File path: maven-scm-plugin/src/test/java/org/apache/maven/scm/plugin/TagMojoTest.java ## @@ -63,32 +62,29 @@ protected void setUp()

[GitHub] [maven-scm] elharo opened a new pull request #102: [SCM-936] extract common code

elharo opened a new pull request #102: URL: https://github.com/apache/maven-scm/pull/102 @michael-o Let's see if the test still flakes. This is an automated message from the Apache Git Service. To respond to the message,

[jira] [Created] (SCM-939) Assume SCM is present

Elliotte Rusty Harold created SCM-939: - Summary: Assume SCM is present Key: SCM-939 URL: https://issues.apache.org/jira/browse/SCM-939 Project: Maven SCM Issue Type: Bug

[GitHub] [maven-scm] michael-o edited a comment on pull request #101: [SCM-937] replace deprecated methods

michael-o edited a comment on pull request #101: URL: https://github.com/apache/maven-scm/pull/101#issuecomment-626623296 This cannot be real: C:\Windows\system32\config\systemprofile\AppData\Local\Temp\maven-scm-173513893.commit Writing into `C:\Windows` is just wrong. I have this

[GitHub] [maven-scm] michael-o edited a comment on pull request #101: [SCM-937] replace deprecated methods

michael-o edited a comment on pull request #101: URL: https://github.com/apache/maven-scm/pull/101#issuecomment-626623296 This cannot be real: C:\Windows\system32\config\systemprofile\AppData\Local\Temp\maven-scm-173513893.commit Writing into `C:\Windows` is just wrong. I have this

[GitHub] [maven-scm] michael-o edited a comment on pull request #101: [SCM-937] replace deprecated methods

michael-o edited a comment on pull request #101: URL: https://github.com/apache/maven-scm/pull/101#issuecomment-626623296 This cannot be real: C:\Windows\system32\config\systemprofile\AppData\Local\Temp\maven-scm-173513893.commit Writing into `C:\Windows` is just wrong. I have this

[GitHub] [maven-scm] michael-o commented on a change in pull request #101: [SCM-937] replace deprecated methods

michael-o commented on a change in pull request #101: URL: https://github.com/apache/maven-scm/pull/101#discussion_r422948794 ## File path:

[jira] [Created] (SCM-938) TagMojoTest is flaky on Windows

Elliotte Rusty Harold created SCM-938: - Summary: TagMojoTest is flaky on Windows Key: SCM-938 URL: https://issues.apache.org/jira/browse/SCM-938 Project: Maven SCM Issue Type: Bug

[jira] [Closed] (MNGSITE-409) TagMojoTest is flaky on Windows

[ https://issues.apache.org/jira/browse/MNGSITE-409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elliotte Rusty Harold closed MNGSITE-409. - > TagMojoTest is flaky on Windows > --- > >

[jira] [Resolved] (MNGSITE-409) TagMojoTest is flaky on Windows

[ https://issues.apache.org/jira/browse/MNGSITE-409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elliotte Rusty Harold resolved MNGSITE-409. --- Resolution: Invalid > TagMojoTest is flaky on Windows >

[GitHub] [maven-scm] michael-o commented on pull request #101: [SCM-937] replace deprecated methods

michael-o commented on pull request #101: URL: https://github.com/apache/maven-scm/pull/101#issuecomment-626623296 This cannot be real: C:\Windows\system32\config\systemprofile\AppData\Local\Temp\maven-scm-173513893.commit Writing into `C:\Windows` is just wrong. I have this dir on

[jira] [Created] (MNGSITE-409) TagMojoTest is flaky on Windows

Elliotte Rusty Harold created MNGSITE-409: - Summary: TagMojoTest is flaky on Windows Key: MNGSITE-409 URL: https://issues.apache.org/jira/browse/MNGSITE-409 Project: Maven Project Web Site

[GitHub] [maven-scm] elharo commented on pull request #101: [SCM-937] replace deprecated methods

elharo commented on pull request #101: URL: https://github.com/apache/maven-scm/pull/101#issuecomment-626622170 Seeing some flakiness in our windows builds for this plugin in multiple PRs: Error Message Command failed.The svn tag command failed. Stacktrace

[GitHub] [maven-scm] elharo commented on a change in pull request #101: [SCM-937] replace deprecated methods

elharo commented on a change in pull request #101: URL: https://github.com/apache/maven-scm/pull/101#discussion_r422946097 ## File path:

[jira] [Closed] (MNGSITE-407) Delete CI page

[ https://issues.apache.org/jira/browse/MNGSITE-407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elliotte Rusty Harold closed MNGSITE-407. - > Delete CI page > -- > > Key: MNGSITE-407 >

[jira] [Resolved] (MNGSITE-407) Delete CI page

[ https://issues.apache.org/jira/browse/MNGSITE-407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elliotte Rusty Harold resolved MNGSITE-407. --- Resolution: Fixed > Delete CI page > -- > >

[GitHub] [maven-enforcer] svenlange commented on a change in pull request #35: [MENFORCER-304] Improve dependency resolving in multiple modules project

svenlange commented on a change in pull request #35: URL: https://github.com/apache/maven-enforcer/pull/35#discussion_r422942540 ## File path: enforcer-rules/src/main/java/org/apache/maven/plugins/enforcer/AbstractBanDependencies.java ## @@ -191,4 +207,19 @@ public void

[jira] [Commented] (MSHARED-856) Require Maven 3.1 or later

[ https://issues.apache.org/jira/browse/MSHARED-856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17104296#comment-17104296 ] Michael Osipov commented on MSHARED-856: This sounds like a good plan. > Require Maven 3.1 or

[jira] [Commented] (MSHARED-856) Require Maven 3.1 or later

[ https://issues.apache.org/jira/browse/MSHARED-856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17104293#comment-17104293 ] Karl Heinz Marbaise commented on MSHARED-856: - At the moment we don't change the component

[GitHub] [maven-scm] michael-o commented on a change in pull request #101: [SCM-937] replace deprecated methods

michael-o commented on a change in pull request #101: URL: https://github.com/apache/maven-scm/pull/101#discussion_r422930910 ## File path:

[jira] [Commented] (MSHARED-856) Require Maven 3.1 or later

[ https://issues.apache.org/jira/browse/MSHARED-856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17104288#comment-17104288 ] Michael Osipov commented on MSHARED-856: [~slachiewicz], at least [~khmarbaise] did recently a

[jira] [Commented] (MRESOLVER-90) HTML content in POM: Maven should validate content before storing in local repo

[ https://issues.apache.org/jira/browse/MRESOLVER-90?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17104287#comment-17104287 ] Michael Osipov commented on MRESOLVER-90: - I expect that we use checksums to detect transport

[jira] [Commented] (MNG-6902) not storing/getting artifacts in/from local repository

[ https://issues.apache.org/jira/browse/MNG-6902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17104282#comment-17104282 ] Enrique commented on MNG-6902: -- [~nhoj.patrick] thanks a lot. Yes I did, let me explain you what I found

[GitHub] [maven-surefire] Tibor17 commented on pull request #290: [SUREFIRE-1787] Support multiple runners (JUnit4, TestNG, other) and their API in JUnit5 Provider

Tibor17 commented on pull request #290: URL: https://github.com/apache/maven-surefire/pull/290#issuecomment-626598963 already squashed except Jenkinsfile and pushed to gitbox This is an automated message from the Apache Git

[jira] [Closed] (SUREFIRE-1787) Support multiple runners (JUnit4, TestNG, other) and their API in JUnit5 Provider

[ https://issues.apache.org/jira/browse/SUREFIRE-1787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana closed SUREFIRE-1787. -- Resolution: Fixed