[jira] [Commented] (MSHADE-357) Upgrade asm to 8.0

[ https://issues.apache.org/jira/browse/MSHADE-357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17071342#comment-17071342 ] Hudson commented on MSHADE-357: --- Build succeeded in Jenkins: Maven TLP » maven-shade-plugin » master #72

[jira] [Closed] (MSHADE-357) Upgrade asm to 8.0

[ https://issues.apache.org/jira/browse/MSHADE-357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MSHADE-357. -- Resolution: Done > Upgrade asm to 8.0 > -- > > Key:

[jira] [Commented] (MSHADE-357) Upgrade asm to 8.0

[ https://issues.apache.org/jira/browse/MSHADE-357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17071338#comment-17071338 ] Karl Heinz Marbaise commented on MSHADE-357: Done in

[GitHub] [maven-resolver] dependabot[bot] commented on issue #40: Bump jettyVersion from 9.2.26.v20180806 to 9.4.22.v20191022 in /maven-resolver-transport-http

dependabot[bot] commented on issue #40: Bump jettyVersion from 9.2.26.v20180806 to 9.4.22.v20191022 in /maven-resolver-transport-http URL: https://github.com/apache/maven-resolver/pull/40#issuecomment-606313264 OK, I won't notify you again about this release, but will get in touch when a

[GitHub] [maven-resolver] asfgit closed pull request #40: Bump jettyVersion from 9.2.26.v20180806 to 9.4.22.v20191022 in /maven-resolver-transport-http

asfgit closed pull request #40: Bump jettyVersion from 9.2.26.v20180806 to 9.4.22.v20191022 in /maven-resolver-transport-http URL: https://github.com/apache/maven-resolver/pull/40 This is an automated message from the

[jira] [Comment Edited] (ARCHETYPE-561) Plugin picks 1.0 version of archetype when versionId not specified

[ https://issues.apache.org/jira/browse/ARCHETYPE-561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16811615#comment-16811615 ] Bruno Borges edited comment on ARCHETYPE-561 at 3/30/20, 11:03 PM: ---

[jira] [Commented] (MSHADE-355) Java 15 Compatibility - JDependecny/ASM Upgrade

[ https://issues.apache.org/jira/browse/MSHADE-355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17071315#comment-17071315 ] Hudson commented on MSHADE-355: --- Build succeeded in Jenkins: Maven TLP » maven-shade-plugin » master #70

[jira] [Closed] (MSHADE-355) Java 15 Compatibility - JDependecny/ASM Upgrade

[ https://issues.apache.org/jira/browse/MSHADE-355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz closed MSHADE-355. --- Resolution: Fixed > Java 15 Compatibility - JDependecny/ASM Upgrade >

[jira] [Commented] (MSHADE-355) Java 15 Compatibility - JDependecny/ASM Upgrade

[ https://issues.apache.org/jira/browse/MSHADE-355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17071314#comment-17071314 ] Sylwester Lachiewicz commented on MSHADE-355: - Upgraded JDependency to 2.4.0 (with ASM 8.0)

[jira] [Commented] (SUREFIRE-1339) Forked JVM hangs in FreeBSD when reuseForks=true

[ https://issues.apache.org/jira/browse/SUREFIRE-1339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17071308#comment-17071308 ] Michael Osipov commented on SUREFIRE-1339: -- [~tibordigana], how can I reproduce this issue?

[jira] [Closed] (MRELEASE-1039) Custom search broken on pages rendered using Fluido Skin 1.7

[ https://issues.apache.org/jira/browse/MRELEASE-1039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MRELEASE-1039. Resolution: Fixed Fixed in

[jira] [Commented] (MRELEASE-1040) release-prepare: Required class missing org/eclipse/aether/util/version/GenericVersionScheme

[ https://issues.apache.org/jira/browse/MRELEASE-1040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17071293#comment-17071293 ] Hudson commented on MRELEASE-1040: -- Build succeeded in Jenkins: Maven TLP » maven-release » master

[jira] [Closed] (MRELEASE-1040) release-prepare: Required class missing org/eclipse/aether/util/version/GenericVersionScheme

[ https://issues.apache.org/jira/browse/MRELEASE-1040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MRELEASE-1040. Fix Version/s: 3.0.0 Resolution: Fixed Fixed in

[jira] [Closed] (MNG-6880) Maven creates `?/m2` dir in pwd if run in Docker image with custom UID

[ https://issues.apache.org/jira/browse/MNG-6880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MNG-6880. --- Resolution: Invalid > Maven creates `?/m2` dir in pwd if run in Docker image with custom UID >

[jira] [Commented] (MNG-6880) Maven creates `?/m2` dir in pwd if run in Docker image with custom UID

[ https://issues.apache.org/jira/browse/MNG-6880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17071279#comment-17071279 ] Michael Osipov commented on MNG-6880: - The code you are referencing is the wrong one. The spots are:

[jira] [Assigned] (MRELEASE-1039) Custom search broken on pages rendered using Fluido Skin 1.7

[ https://issues.apache.org/jira/browse/MRELEASE-1039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte reassigned MRELEASE-1039: Assignee: Robert Scholte > Custom search broken on pages rendered using Fluido

[jira] [Commented] (SUREFIRE-1766) Surefire does not display TestNG data provider values on command line

[ https://issues.apache.org/jira/browse/SUREFIRE-1766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17071175#comment-17071175 ] Simon Levermann commented on SUREFIRE-1766: ---   {code:java} [INFO] ---

[jira] [Commented] (SUREFIRE-1766) Surefire does not display TestNG data provider values on command line

[ https://issues.apache.org/jira/browse/SUREFIRE-1766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17071167#comment-17071167 ] Tibor Digana commented on SUREFIRE-1766: How the console looks like? > Surefire does not

[jira] [Commented] (MNG-6880) Maven creates `?/m2` dir in pwd if run in Docker image with custom UID

[ https://issues.apache.org/jira/browse/MNG-6880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17071166#comment-17071166 ] Florian Wilhelm commented on MNG-6880: -- I've looked for it in the jvm source code (open jdk 8), but

[jira] [Commented] (SUREFIRE-1765) target/test-classes should not be added to classpath when tests run on modulepath using patch-module

[ https://issues.apache.org/jira/browse/SUREFIRE-1765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17071163#comment-17071163 ] Tibor Digana commented on SUREFIRE-1765: [~tomdw] We have another Jira ticket for the same

[GitHub] [maven-dependency-plugin] elharo opened a new pull request #42: update to collections4

elharo opened a new pull request #42: update to collections4 URL: https://github.com/apache/maven-dependency-plugin/pull/42 @michael-o 4.2 is lats version that supports Java 7 This is an automated message from the

[GitHub] [maven-dependency-plugin] elharo merged pull request #40: update commons-lang

elharo merged pull request #40: update commons-lang URL: https://github.com/apache/maven-dependency-plugin/pull/40 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub

[GitHub] [maven-dependency-plugin] elharo merged pull request #41: remove debugging code

elharo merged pull request #41: remove debugging code URL: https://github.com/apache/maven-dependency-plugin/pull/41 This is an automated message from the Apache Git Service. To respond to the message, please log on to

[jira] [Created] (MPMD-300) Unable to format output with custom renderer (CodeClimateRenderer)

João Taborda created MPMD-300: - Summary: Unable to format output with custom renderer (CodeClimateRenderer) Key: MPMD-300 URL: https://issues.apache.org/jira/browse/MPMD-300 Project: Maven PMD Plugin

[GitHub] [maven-javadoc-plugin] elharo commented on a change in pull request #27: MJAVADOC-617 Normalize module path so that '..' in the path are resolved

elharo commented on a change in pull request #27: MJAVADOC-617 Normalize module path so that '..' in the path are resolved URL: https://github.com/apache/maven-javadoc-plugin/pull/27#discussion_r400288981 ## File path:

[GitHub] [maven-javadoc-plugin] elharo commented on a change in pull request #27: MJAVADOC-617 Normalize module path so that '..' in the path are resolved

elharo commented on a change in pull request #27: MJAVADOC-617 Normalize module path so that '..' in the path are resolved URL: https://github.com/apache/maven-javadoc-plugin/pull/27#discussion_r400289549 ## File path:

[GitHub] [maven-javadoc-plugin] elharo commented on a change in pull request #27: MJAVADOC-617 Normalize module path so that '..' in the path are resolved

elharo commented on a change in pull request #27: MJAVADOC-617 Normalize module path so that '..' in the path are resolved URL: https://github.com/apache/maven-javadoc-plugin/pull/27#discussion_r400287916 ## File path:

[GitHub] [maven-javadoc-plugin] elharo commented on a change in pull request #27: MJAVADOC-617 Normalize module path so that '..' in the path are resolved

elharo commented on a change in pull request #27: MJAVADOC-617 Normalize module path so that '..' in the path are resolved URL: https://github.com/apache/maven-javadoc-plugin/pull/27#discussion_r400288663 ## File path:

[GitHub] [maven-javadoc-plugin] elharo commented on a change in pull request #27: MJAVADOC-617 Normalize module path so that '..' in the path are resolved

elharo commented on a change in pull request #27: MJAVADOC-617 Normalize module path so that '..' in the path are resolved URL: https://github.com/apache/maven-javadoc-plugin/pull/27#discussion_r400291134 ## File path:

[GitHub] [maven-javadoc-plugin] elharo commented on a change in pull request #27: MJAVADOC-617 Normalize module path so that '..' in the path are resolved

elharo commented on a change in pull request #27: MJAVADOC-617 Normalize module path so that '..' in the path are resolved URL: https://github.com/apache/maven-javadoc-plugin/pull/27#discussion_r400291687 ## File path:

[GitHub] [maven-javadoc-plugin] elharo commented on a change in pull request #27: MJAVADOC-617 Normalize module path so that '..' in the path are resolved

elharo commented on a change in pull request #27: MJAVADOC-617 Normalize module path so that '..' in the path are resolved URL: https://github.com/apache/maven-javadoc-plugin/pull/27#discussion_r400289418 ## File path:

[GitHub] [maven-javadoc-plugin] elharo commented on a change in pull request #27: MJAVADOC-617 Normalize module path so that '..' in the path are resolved

elharo commented on a change in pull request #27: MJAVADOC-617 Normalize module path so that '..' in the path are resolved URL: https://github.com/apache/maven-javadoc-plugin/pull/27#discussion_r400290634 ## File path:

[GitHub] [maven-javadoc-plugin] elharo commented on a change in pull request #27: MJAVADOC-617 Normalize module path so that '..' in the path are resolved

elharo commented on a change in pull request #27: MJAVADOC-617 Normalize module path so that '..' in the path are resolved URL: https://github.com/apache/maven-javadoc-plugin/pull/27#discussion_r400290038 ## File path:

[GitHub] [maven-javadoc-plugin] elharo commented on a change in pull request #27: MJAVADOC-617 Normalize module path so that '..' in the path are resolved

elharo commented on a change in pull request #27: MJAVADOC-617 Normalize module path so that '..' in the path are resolved URL: https://github.com/apache/maven-javadoc-plugin/pull/27#discussion_r400287007 ## File path:

[GitHub] [maven-javadoc-plugin] weissreto commented on a change in pull request #27: MJAVADOC-617 Normalize module path so that '..' in the path are resolved

weissreto commented on a change in pull request #27: MJAVADOC-617 Normalize module path so that '..' in the path are resolved URL: https://github.com/apache/maven-javadoc-plugin/pull/27#discussion_r400278728 ## File path:

[GitHub] [maven-dependency-plugin] elharo commented on issue #41: remove debugging code

elharo commented on issue #41: remove debugging code URL: https://github.com/apache/maven-dependency-plugin/pull/41#issuecomment-606064534 Haven't dived into the history of this file, but I suspect someone threw this in there when they were first implementing the model class or seeking

[jira] [Created] (SUREFIRE-1766) Surefire does not display TestNG data provider values on command line

Simon Levermann created SUREFIRE-1766: - Summary: Surefire does not display TestNG data provider values on command line Key: SUREFIRE-1766 URL: https://issues.apache.org/jira/browse/SUREFIRE-1766

[jira] [Updated] (SUREFIRE-1766) Surefire does not display TestNG data provider values on command line

[ https://issues.apache.org/jira/browse/SUREFIRE-1766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Levermann updated SUREFIRE-1766: -- Description: When using Surefire's DataProvider annotation, TestNG also exposes the

[GitHub] [maven-dependency-plugin] michael-o commented on issue #41: remove debugging code

michael-o commented on issue #41: remove debugging code URL: https://github.com/apache/maven-dependency-plugin/pull/41#issuecomment-605985557 I guess they are visible with `-X`? This is an automated message from the Apache

[jira] [Commented] (SUREFIRE-1765) target/test-classes should not be added to classpath when tests run on modulepath using patch-module

[ https://issues.apache.org/jira/browse/SUREFIRE-1765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17070934#comment-17070934 ] Tom De Wolf commented on SUREFIRE-1765: --- [~tibordigana] I added a small maven project in the

[jira] [Updated] (SUREFIRE-1765) target/test-classes should not be added to classpath when tests run on modulepath using patch-module

[ https://issues.apache.org/jira/browse/SUREFIRE-1765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom De Wolf updated SUREFIRE-1765: -- Attachment: reproduce-xxxAnnotation-jdk-bug.zip > target/test-classes should not be added

[jira] [Commented] (SUREFIRE-1765) target/test-classes should not be added to classpath when tests run on modulepath using patch-module

[ https://issues.apache.org/jira/browse/SUREFIRE-1765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17070920#comment-17070920 ] Michael Rasmussen commented on SUREFIRE-1765: - You might want to do proper whitebox

[jira] [Commented] (SUREFIRE-1765) target/test-classes should not be added to classpath when tests run on modulepath using patch-module

[ https://issues.apache.org/jira/browse/SUREFIRE-1765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17070909#comment-17070909 ] Tom De Wolf commented on SUREFIRE-1765: --- [~tibordigana] for this issue that is only an example

[GitHub] [maven-dependency-plugin] elharo opened a new pull request #41: remove debugging code

elharo opened a new pull request #41: remove debugging code URL: https://github.com/apache/maven-dependency-plugin/pull/41 @michael-o This is an automated message from the Apache Git Service. To respond to the message,

[jira] [Commented] (MRESOURCES-236) Copying of files with permissions broken

[ https://issues.apache.org/jira/browse/MRESOURCES-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17070889#comment-17070889 ] Magnus Reftel commented on MRESOURCES-236: -- Bug still present in Maven Resource Plugin

[GitHub] [maven-dependency-plugin] elharo commented on issue #40: update commons-lang

elharo commented on issue #40: update commons-lang URL: https://github.com/apache/maven-dependency-plugin/pull/40#issuecomment-605934953 Hmm, looks like they did change the package? So how are the tests passing?

[jira] [Commented] (SUREFIRE-1765) target/test-classes should not be added to classpath when tests run on modulepath using patch-module

[ https://issues.apache.org/jira/browse/SUREFIRE-1765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17070865#comment-17070865 ] Tibor Digana commented on SUREFIRE-1765: We have supposed that the modularity in

[jira] [Comment Edited] (SUREFIRE-1765) target/test-classes should not be added to classpath when tests run on modulepath using patch-module

[ https://issues.apache.org/jira/browse/SUREFIRE-1765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17070865#comment-17070865 ] Tibor Digana edited comment on SUREFIRE-1765 at 3/30/20, 10:38 AM: ---

[jira] [Updated] (SUREFIRE-1765) target/test-classes should not be added to classpath when tests run on modulepath using patch-module

[ https://issues.apache.org/jira/browse/SUREFIRE-1765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom De Wolf updated SUREFIRE-1765: -- Affects Version/s: 2.22.1 > target/test-classes should not be added to classpath when tests

[jira] [Updated] (SUREFIRE-1765) target/test-classes should not be added to classpath when tests run on modulepath using patch-module

[ https://issues.apache.org/jira/browse/SUREFIRE-1765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom De Wolf updated SUREFIRE-1765: -- Affects Version/s: 2.22.2 > target/test-classes should not be added to classpath when tests

[jira] [Created] (SUREFIRE-1765) target/test-classes should not be added to classpath when tests run on modulepath using patch-module

Tom De Wolf created SUREFIRE-1765: - Summary: target/test-classes should not be added to classpath when tests run on modulepath using patch-module Key: SUREFIRE-1765 URL:

[jira] [Closed] (WAGON-585) maven.wagon.http.ssl features documentation is incomplete

[ https://issues.apache.org/jira/browse/WAGON-585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed WAGON-585. Fix Version/s: 3.4.0 Resolution: Fixed Fixed with

[GitHub] [maven-wagon] asfgit closed pull request #64: WAGON-585 maven.wagon.http.ssl features documentation is incomplete

asfgit closed pull request #64: WAGON-585 maven.wagon.http.ssl features documentation is incomplete URL: https://github.com/apache/maven-wagon/pull/64 This is an automated message from the Apache Git Service. To respond to

[jira] [Commented] (MINVOKER-260) Option 'streamLogs' does not work properly for logs from intepreter

[ https://issues.apache.org/jira/browse/MINVOKER-260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17070731#comment-17070731 ] Leonid Gorshkov commented on MINVOKER-260: -- [~slawekjaranowski], thank you for your reply.