[jira] [Created] (MPMD-353) An API incompatibility was encountered while executing org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd
Piotr Zygielo created MPMD-353:
--
Summary: An API incompatibility was encountered while executing
org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd
Key: MPMD-353
URL: https://issues.apache.org/jira/browse/MPMD-353
Project: Maven PMD Plugin
Issue Type: Bug
Components: PMD
Affects Versions: 3.18.0
Reporter: Piotr Zygielo
{code:bash}
Error: Failed to execute goal
org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd (pmd) on project
UnnecessaryFullyQualifiedName: Execution pmd of goal
org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd failed: An API
incompatibility was encountered while executing
org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd:
java.lang.NoSuchMethodError:
org.fusesource.jansi.AnsiConsole.out()Lorg/fusesource/jansi/AnsiPrintStream;
Error: -
Error: realm = plugin>org.apache.maven.plugins:maven-pmd-plugin:3.18.0
Error: strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
Error: urls[0] =
file:/home/runner/.m2/repository/org/apache/maven/plugins/maven-pmd-plugin/3.18.0/maven-pmd-plugin-3.18.0.jar
Error: urls[1] =
file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-core/6.48.0/pmd-core-6.48.0.jar
Error: urls[2] =
file:/home/runner/.m2/repository/org/antlr/antlr4-runtime/4.7.2/antlr4-runtime-4.7.2.jar
Error: urls[3] =
file:/home/runner/.m2/repository/com/beust/jcommander/1.48/jcommander-1.48.jar
Error: urls[4] =
file:/home/runner/.m2/repository/net/sourceforge/saxon/saxon/9.1.0.8/saxon-9.1.0.8.jar
Error: urls[5] =
file:/home/runner/.m2/repository/org/ow2/asm/asm/9.3/asm-9.3.jar
Error: urls[6] =
file:/home/runner/.m2/repository/com/google/code/gson/gson/2.8.9/gson-2.8.9.jar
Error: urls[7] =
file:/home/runner/.m2/repository/net/sourceforge/saxon/saxon/9.1.0.8/saxon-9.1.0.8-dom.jar
Error: urls[8] =
file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-java/6.48.0/pmd-java-6.48.0.jar
Error: urls[9] =
file:/home/runner/.m2/repository/org/apache/maven/shared/maven-artifact-transfer/0.13.1/maven-artifact-transfer-0.13.1.jar
Error: urls[10] =
file:/home/runner/.m2/repository/org/sonatype/aether/aether-util/1.7/aether-util-1.7.jar
Error: urls[11] =
file:/home/runner/.m2/repository/org/sonatype/sisu/sisu-inject-bean/1.4.2/sisu-inject-bean-1.4.2.jar
Error: urls[12] =
file:/home/runner/.m2/repository/org/sonatype/sisu/sisu-guice/2.1.7/sisu-guice-2.1.7-noaop.jar
Error: urls[13] =
file:/home/runner/.m2/repository/org/codehaus/plexus/plexus-interpolation/1.14/plexus-interpolation-1.14.jar
Error: urls[14] =
file:/home/runner/.m2/repository/org/sonatype/plexus/plexus-sec-dispatcher/1.3/plexus-sec-dispatcher-1.3.jar
Error: urls[15] =
file:/home/runner/.m2/repository/org/sonatype/plexus/plexus-cipher/1.4/plexus-cipher-1.4.jar
Error: urls[16] =
file:/home/runner/.m2/repository/org/codehaus/plexus/plexus-component-annotations/2.1.1/plexus-component-annotations-2.1.1.jar
Error: urls[17] =
file:/home/runner/.m2/repository/org/apache/maven/shared/maven-common-artifact-filters/3.3.1/maven-common-artifact-filters-3.3.1.jar
Error: urls[18] =
file:/home/runner/.m2/repository/commons-io/commons-io/2.11.0/commons-io-2.11.0.jar
Error: urls[19] =
file:/home/runner/.m2/repository/org/apache/commons/commons-lang3/3.12.0/commons-lang3-3.12.0.jar
Error: urls[20] =
file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-javascript/6.48.0/pmd-javascript-6.48.0.jar
Error: urls[21] =
file:/home/runner/.m2/repository/org/mozilla/rhino/1.7.14/rhino-1.7.14.jar
Error: urls[22] =
file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-jsp/6.48.0/pmd-jsp-6.48.0.jar
Error: urls[23] =
file:/home/runner/.m2/repository/org/slf4j/jul-to-slf4j/1.7.36/jul-to-slf4j-1.7.36.jar
Error: urls[24] =
file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-sink-api/1.11.1/doxia-sink-api-1.11.1.jar
Error: urls[25] =
file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-logging-api/1.11.1/doxia-logging-api-1.11.1.jar
Error: urls[26] =
file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-decoration-model/1.11.1/doxia-decoration-model-1.11.1.jar
Error: urls[27] =
file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-site-renderer/1.11.1/doxia-site-renderer-1.11.1.jar
Error: urls[28] =
file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-core/1.11.1/doxia-core-1.11.1.jar
Error: urls[29] =
file:/home/runner/.m2/repository/org/apache/commons/commons-text/1.3/commons-text-1.3.jar
Error: urls[30] =
file:/home/runner/.m2/repository/org/apache/httpcomponents/httpcore/4.4.14/httpcore-4.4.14.jar
Error: urls[31] =
file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-skin-model/1.11.1/doxia-skin-model-1.11.1.jar
Error: urls[32] =
file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-module-xhtml/1.11.1/doxia-module-xhtml-1.11.1.jar
Error: urls[33] =
file:/home
[jira] [Closed] (MPMD-353) An API incompatibility was encountered while executing org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd
[
https://issues.apache.org/jira/browse/MPMD-353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MPMD-353.
---
Resolution: Information Provided
Please read:
https://www.mail-archive.com/dev@maven.apache.org/msg127729.html
> An API incompatibility was encountered while executing
> org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd
> ---
>
> Key: MPMD-353
> URL: https://issues.apache.org/jira/browse/MPMD-353
> Project: Maven PMD Plugin
> Issue Type: Bug
> Components: PMD
>Affects Versions: 3.18.0
>Reporter: Piotr Zygielo
>Priority: Major
>
> {code:bash}
> Error: Failed to execute goal
> org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd (pmd) on project
> UnnecessaryFullyQualifiedName: Execution pmd of goal
> org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd failed: An API
> incompatibility was encountered while executing
> org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd:
> java.lang.NoSuchMethodError:
> org.fusesource.jansi.AnsiConsole.out()Lorg/fusesource/jansi/AnsiPrintStream;
> Error: -
> Error: realm = plugin>org.apache.maven.plugins:maven-pmd-plugin:3.18.0
> Error: strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> Error: urls[0] =
> file:/home/runner/.m2/repository/org/apache/maven/plugins/maven-pmd-plugin/3.18.0/maven-pmd-plugin-3.18.0.jar
> Error: urls[1] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-core/6.48.0/pmd-core-6.48.0.jar
> Error: urls[2] =
> file:/home/runner/.m2/repository/org/antlr/antlr4-runtime/4.7.2/antlr4-runtime-4.7.2.jar
> Error: urls[3] =
> file:/home/runner/.m2/repository/com/beust/jcommander/1.48/jcommander-1.48.jar
> Error: urls[4] =
> file:/home/runner/.m2/repository/net/sourceforge/saxon/saxon/9.1.0.8/saxon-9.1.0.8.jar
> Error: urls[5] =
> file:/home/runner/.m2/repository/org/ow2/asm/asm/9.3/asm-9.3.jar
> Error: urls[6] =
> file:/home/runner/.m2/repository/com/google/code/gson/gson/2.8.9/gson-2.8.9.jar
> Error: urls[7] =
> file:/home/runner/.m2/repository/net/sourceforge/saxon/saxon/9.1.0.8/saxon-9.1.0.8-dom.jar
> Error: urls[8] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-java/6.48.0/pmd-java-6.48.0.jar
> Error: urls[9] =
> file:/home/runner/.m2/repository/org/apache/maven/shared/maven-artifact-transfer/0.13.1/maven-artifact-transfer-0.13.1.jar
> Error: urls[10] =
> file:/home/runner/.m2/repository/org/sonatype/aether/aether-util/1.7/aether-util-1.7.jar
> Error: urls[11] =
> file:/home/runner/.m2/repository/org/sonatype/sisu/sisu-inject-bean/1.4.2/sisu-inject-bean-1.4.2.jar
> Error: urls[12] =
> file:/home/runner/.m2/repository/org/sonatype/sisu/sisu-guice/2.1.7/sisu-guice-2.1.7-noaop.jar
> Error: urls[13] =
> file:/home/runner/.m2/repository/org/codehaus/plexus/plexus-interpolation/1.14/plexus-interpolation-1.14.jar
> Error: urls[14] =
> file:/home/runner/.m2/repository/org/sonatype/plexus/plexus-sec-dispatcher/1.3/plexus-sec-dispatcher-1.3.jar
> Error: urls[15] =
> file:/home/runner/.m2/repository/org/sonatype/plexus/plexus-cipher/1.4/plexus-cipher-1.4.jar
> Error: urls[16] =
> file:/home/runner/.m2/repository/org/codehaus/plexus/plexus-component-annotations/2.1.1/plexus-component-annotations-2.1.1.jar
> Error: urls[17] =
> file:/home/runner/.m2/repository/org/apache/maven/shared/maven-common-artifact-filters/3.3.1/maven-common-artifact-filters-3.3.1.jar
> Error: urls[18] =
> file:/home/runner/.m2/repository/commons-io/commons-io/2.11.0/commons-io-2.11.0.jar
> Error: urls[19] =
> file:/home/runner/.m2/repository/org/apache/commons/commons-lang3/3.12.0/commons-lang3-3.12.0.jar
> Error: urls[20] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-javascript/6.48.0/pmd-javascript-6.48.0.jar
> Error: urls[21] =
> file:/home/runner/.m2/repository/org/mozilla/rhino/1.7.14/rhino-1.7.14.jar
> Error: urls[22] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-jsp/6.48.0/pmd-jsp-6.48.0.jar
> Error: urls[23] =
> file:/home/runner/.m2/repository/org/slf4j/jul-to-slf4j/1.7.36/jul-to-slf4j-1.7.36.jar
> Error: urls[24] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-sink-api/1.11.1/doxia-sink-api-1.11.1.jar
> Error: urls[25] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-logging-api/1.11.1/doxia-logging-api-1.11.1.jar
> Error: urls[26] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-decoration-model/1.11.1/doxia-decoration-model-1.11.1.jar
> Error: urls[27] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-site-renderer/1.11.1/doxia-site-renderer-1.11.1.jar
> Error: urls[28] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-core/1.11.1/doxia-core-1.11.1.jar
[jira] [Commented] (MPMD-353) An API incompatibility was encountered while executing org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd
[
https://issues.apache.org/jira/browse/MPMD-353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584056#comment-17584056
]
Piotr Zygielo commented on MPMD-353:
Outdated wrapped maven on my side (3.6.3). Works fine with current 3.8.6.
Please close this issue.
> An API incompatibility was encountered while executing
> org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd
> ---
>
> Key: MPMD-353
> URL: https://issues.apache.org/jira/browse/MPMD-353
> Project: Maven PMD Plugin
> Issue Type: Bug
> Components: PMD
>Affects Versions: 3.18.0
>Reporter: Piotr Zygielo
>Priority: Major
>
> {code:bash}
> Error: Failed to execute goal
> org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd (pmd) on project
> UnnecessaryFullyQualifiedName: Execution pmd of goal
> org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd failed: An API
> incompatibility was encountered while executing
> org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd:
> java.lang.NoSuchMethodError:
> org.fusesource.jansi.AnsiConsole.out()Lorg/fusesource/jansi/AnsiPrintStream;
> Error: -
> Error: realm = plugin>org.apache.maven.plugins:maven-pmd-plugin:3.18.0
> Error: strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> Error: urls[0] =
> file:/home/runner/.m2/repository/org/apache/maven/plugins/maven-pmd-plugin/3.18.0/maven-pmd-plugin-3.18.0.jar
> Error: urls[1] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-core/6.48.0/pmd-core-6.48.0.jar
> Error: urls[2] =
> file:/home/runner/.m2/repository/org/antlr/antlr4-runtime/4.7.2/antlr4-runtime-4.7.2.jar
> Error: urls[3] =
> file:/home/runner/.m2/repository/com/beust/jcommander/1.48/jcommander-1.48.jar
> Error: urls[4] =
> file:/home/runner/.m2/repository/net/sourceforge/saxon/saxon/9.1.0.8/saxon-9.1.0.8.jar
> Error: urls[5] =
> file:/home/runner/.m2/repository/org/ow2/asm/asm/9.3/asm-9.3.jar
> Error: urls[6] =
> file:/home/runner/.m2/repository/com/google/code/gson/gson/2.8.9/gson-2.8.9.jar
> Error: urls[7] =
> file:/home/runner/.m2/repository/net/sourceforge/saxon/saxon/9.1.0.8/saxon-9.1.0.8-dom.jar
> Error: urls[8] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-java/6.48.0/pmd-java-6.48.0.jar
> Error: urls[9] =
> file:/home/runner/.m2/repository/org/apache/maven/shared/maven-artifact-transfer/0.13.1/maven-artifact-transfer-0.13.1.jar
> Error: urls[10] =
> file:/home/runner/.m2/repository/org/sonatype/aether/aether-util/1.7/aether-util-1.7.jar
> Error: urls[11] =
> file:/home/runner/.m2/repository/org/sonatype/sisu/sisu-inject-bean/1.4.2/sisu-inject-bean-1.4.2.jar
> Error: urls[12] =
> file:/home/runner/.m2/repository/org/sonatype/sisu/sisu-guice/2.1.7/sisu-guice-2.1.7-noaop.jar
> Error: urls[13] =
> file:/home/runner/.m2/repository/org/codehaus/plexus/plexus-interpolation/1.14/plexus-interpolation-1.14.jar
> Error: urls[14] =
> file:/home/runner/.m2/repository/org/sonatype/plexus/plexus-sec-dispatcher/1.3/plexus-sec-dispatcher-1.3.jar
> Error: urls[15] =
> file:/home/runner/.m2/repository/org/sonatype/plexus/plexus-cipher/1.4/plexus-cipher-1.4.jar
> Error: urls[16] =
> file:/home/runner/.m2/repository/org/codehaus/plexus/plexus-component-annotations/2.1.1/plexus-component-annotations-2.1.1.jar
> Error: urls[17] =
> file:/home/runner/.m2/repository/org/apache/maven/shared/maven-common-artifact-filters/3.3.1/maven-common-artifact-filters-3.3.1.jar
> Error: urls[18] =
> file:/home/runner/.m2/repository/commons-io/commons-io/2.11.0/commons-io-2.11.0.jar
> Error: urls[19] =
> file:/home/runner/.m2/repository/org/apache/commons/commons-lang3/3.12.0/commons-lang3-3.12.0.jar
> Error: urls[20] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-javascript/6.48.0/pmd-javascript-6.48.0.jar
> Error: urls[21] =
> file:/home/runner/.m2/repository/org/mozilla/rhino/1.7.14/rhino-1.7.14.jar
> Error: urls[22] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-jsp/6.48.0/pmd-jsp-6.48.0.jar
> Error: urls[23] =
> file:/home/runner/.m2/repository/org/slf4j/jul-to-slf4j/1.7.36/jul-to-slf4j-1.7.36.jar
> Error: urls[24] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-sink-api/1.11.1/doxia-sink-api-1.11.1.jar
> Error: urls[25] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-logging-api/1.11.1/doxia-logging-api-1.11.1.jar
> Error: urls[26] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-decoration-model/1.11.1/doxia-decoration-model-1.11.1.jar
> Error: urls[27] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-site-renderer/1.11.1/doxia-site-renderer-1.11.1.jar
> Error: urls[28] =
> file:/home/runner/.m2/repository/org/apache/maven/doxi
[jira] [Created] (MJAR-291) Upgrade Parent to 37
Jorge Solórzano created MJAR-291: Summary: Upgrade Parent to 37 Key: MJAR-291 URL: https://issues.apache.org/jira/browse/MJAR-291 Project: Maven JAR Plugin Issue Type: Dependency upgrade Reporter: Jorge Solórzano -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven] michael-o commented on pull request #793: [MNG-7532] Log shouldn't have been deprecated so ensure it is not
michael-o commented on PR #793: URL: https://github.com/apache/maven/pull/793#issuecomment-1225364928 I still don't understand why we need a wrapper around a facade... -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MNG-7532) Revert MNG-6931 deprecation since list shows no consensus on that
[ https://issues.apache.org/jira/browse/MNG-7532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584113#comment-17584113 ] ASF GitHub Bot commented on MNG-7532: - michael-o commented on PR #793: URL: https://github.com/apache/maven/pull/793#issuecomment-1225364928 I still don't understand why we need a wrapper around a facade... > Revert MNG-6931 deprecation since list shows no consensus on that > - > > Key: MNG-7532 > URL: https://issues.apache.org/jira/browse/MNG-7532 > Project: Maven > Issue Type: Task >Reporter: Romain Manni-Bucau >Priority: Major > > There are several threads on the dev list asking for the drop of slf4j and at > least keeping a logging abstraction for not internal dev (= core can use > slf4j but not mojo/extensions). > Work is being done to abstract plugin api so let's keep the > deprecation/replacement of our Log API in this track and keep it the official > way for now. > one of the multiple refs: > https://www.mail-archive.com/dev@maven.apache.org/msg123452.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven] rmannibucau commented on pull request #793: [MNG-7532] Log shouldn't have been deprecated so ensure it is not
rmannibucau commented on PR #793: URL: https://github.com/apache/maven/pull/793#issuecomment-1225374475 @michael-o I don't have all the threads handy but we have several dev@ threads explaining it has several technical pitfalls (the way the API loads the impl - v1 or v2) and that we don't want to bind ourselves to an implementation we can't sustain in time. This PR just avoids to have to redefine yet another package and API for plugin (work Guillaume is doing) since we already have it and can enhance it with `Supplier` or alike for formatter like features - more efficient as of today. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MNG-7532) Revert MNG-6931 deprecation since list shows no consensus on that
[ https://issues.apache.org/jira/browse/MNG-7532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584120#comment-17584120 ] ASF GitHub Bot commented on MNG-7532: - rmannibucau commented on PR #793: URL: https://github.com/apache/maven/pull/793#issuecomment-1225374475 @michael-o I don't have all the threads handy but we have several dev@ threads explaining it has several technical pitfalls (the way the API loads the impl - v1 or v2) and that we don't want to bind ourselves to an implementation we can't sustain in time. This PR just avoids to have to redefine yet another package and API for plugin (work Guillaume is doing) since we already have it and can enhance it with `Supplier` or alike for formatter like features - more efficient as of today. > Revert MNG-6931 deprecation since list shows no consensus on that > - > > Key: MNG-7532 > URL: https://issues.apache.org/jira/browse/MNG-7532 > Project: Maven > Issue Type: Task >Reporter: Romain Manni-Bucau >Priority: Major > > There are several threads on the dev list asking for the drop of slf4j and at > least keeping a logging abstraction for not internal dev (= core can use > slf4j but not mojo/extensions). > Work is being done to abstract plugin api so let's keep the > deprecation/replacement of our Log API in this track and keep it the official > way for now. > one of the multiple refs: > https://www.mail-archive.com/dev@maven.apache.org/msg123452.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven] michael-o commented on pull request #793: [MNG-7532] Log shouldn't have been deprecated so ensure it is not
michael-o commented on PR #793: URL: https://github.com/apache/maven/pull/793#issuecomment-1225385847 > @michael-o I don't have all the threads handy but we have several dev@ threads explaining it has several technical pitfalls (the way the API loads the impl - v1 or v2) and that we don't want to bind ourselves to an implementation we can't sustain in time. This PR just avoids to have to redefine yet another package and API for plugin (work Guillaume is doing) since we already have it and can enhance it with `Supplier` or alike for formatter like features - more efficient as of today. I see, what I would like to avoid is to add features to this wrapper which will duplicate SLF4J at the end. We have this: Plexus Logging. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MNG-7532) Revert MNG-6931 deprecation since list shows no consensus on that
[ https://issues.apache.org/jira/browse/MNG-7532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584123#comment-17584123 ] ASF GitHub Bot commented on MNG-7532: - michael-o commented on PR #793: URL: https://github.com/apache/maven/pull/793#issuecomment-1225385847 > @michael-o I don't have all the threads handy but we have several dev@ threads explaining it has several technical pitfalls (the way the API loads the impl - v1 or v2) and that we don't want to bind ourselves to an implementation we can't sustain in time. This PR just avoids to have to redefine yet another package and API for plugin (work Guillaume is doing) since we already have it and can enhance it with `Supplier` or alike for formatter like features - more efficient as of today. I see, what I would like to avoid is to add features to this wrapper which will duplicate SLF4J at the end. We have this: Plexus Logging. > Revert MNG-6931 deprecation since list shows no consensus on that > - > > Key: MNG-7532 > URL: https://issues.apache.org/jira/browse/MNG-7532 > Project: Maven > Issue Type: Task >Reporter: Romain Manni-Bucau >Priority: Major > > There are several threads on the dev list asking for the drop of slf4j and at > least keeping a logging abstraction for not internal dev (= core can use > slf4j but not mojo/extensions). > Work is being done to abstract plugin api so let's keep the > deprecation/replacement of our Log API in this track and keep it the official > way for now. > one of the multiple refs: > https://www.mail-archive.com/dev@maven.apache.org/msg123452.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-integration-testing] michael-o commented on pull request #190: [MNG-7353] Add missing dependencies to bootstrap.txt
michael-o commented on PR #190: URL: https://github.com/apache/maven-integration-testing/pull/190#issuecomment-1225390060 I am trying to reproduce the problem here... -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven] rmannibucau commented on pull request #793: [MNG-7532] Log shouldn't have been deprecated so ensure it is not
rmannibucau commented on PR #793: URL: https://github.com/apache/maven/pull/793#issuecomment-1225399117 @michael-o right but it is not clear what we do of plexus - we are between being based on it and dropping it. Personally I tend to think we should rely on the abstraction we want to expose long term in a very stable way so either JUL (which can be used as an abstraction) or an org.apache.maven.somethingLogging but if we import plexus @asf it sounds like another valid option. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MNG-7532) Revert MNG-6931 deprecation since list shows no consensus on that
[ https://issues.apache.org/jira/browse/MNG-7532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584127#comment-17584127 ] ASF GitHub Bot commented on MNG-7532: - rmannibucau commented on PR #793: URL: https://github.com/apache/maven/pull/793#issuecomment-1225399117 @michael-o right but it is not clear what we do of plexus - we are between being based on it and dropping it. Personally I tend to think we should rely on the abstraction we want to expose long term in a very stable way so either JUL (which can be used as an abstraction) or an org.apache.maven.somethingLogging but if we import plexus @asf it sounds like another valid option. > Revert MNG-6931 deprecation since list shows no consensus on that > - > > Key: MNG-7532 > URL: https://issues.apache.org/jira/browse/MNG-7532 > Project: Maven > Issue Type: Task >Reporter: Romain Manni-Bucau >Priority: Major > > There are several threads on the dev list asking for the drop of slf4j and at > least keeping a logging abstraction for not internal dev (= core can use > slf4j but not mojo/extensions). > Work is being done to abstract plugin api so let's keep the > deprecation/replacement of our Log API in this track and keep it the official > way for now. > one of the multiple refs: > https://www.mail-archive.com/dev@maven.apache.org/msg123452.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-integration-testing] michael-o commented on pull request #190: [MNG-7353] Add missing dependencies to bootstrap.txt
michael-o commented on PR #190: URL: https://github.com/apache/maven-integration-testing/pull/190#issuecomment-1225441418 @hgschmie Can you share the error output you see? I cannot reproduce the failure. It works for me with an empty repo. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-integration-testing] slawekjaranowski commented on pull request #190: [MNG-7353] Add missing dependencies to bootstrap.txt
slawekjaranowski commented on PR #190: URL: https://github.com/apache/maven-integration-testing/pull/190#issuecomment-1225441963 @michael-o look this: https://github.com/apache/maven/actions/workflows/maven.yml more of build failed of missing m-clean-p -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-integration-testing] slawekjaranowski commented on pull request #190: [MNG-7353] Add missing dependencies to bootstrap.txt
slawekjaranowski commented on PR #190: URL: https://github.com/apache/maven-integration-testing/pull/190#issuecomment-1225447166 locally with Maven from master I have the same ``` [INFO] --< org.apache.maven.its.mng7443:consistent-logging-of-optional-projects-and-profiles-selectors >-- [INFO] Building consistent-logging-of-optional-projects-and-profiles-selectors 1.0 [INFO] from pom.xml [INFO] [ jar ]- [INFO] Downloading from central: file:target/null/org/apache/maven/plugins/maven-clean-plugin/3.1.0/maven-clean-plugin-3.1.0.pom [WARNING] The POM for org.apache.maven.plugins:maven-clean-plugin:jar:3.1.0 is missing, no dependency information available [INFO] Downloading from central: file:target/null/org/apache/maven/plugins/maven-clean-plugin/3.1.0/maven-clean-plugin-3.1.0.jar [INFO] ... [ERROR] Plugin org.apache.maven.plugins:maven-clean-plugin:3.1.0 or one of its dependencies could not be resolved: Could not find artifact org.apache.maven.plugins:maven-clean-plugin:jar:3.1.0 in central (file:target/null) -> [Help 1] org.apache.maven.plugin.PluginResolutionException: Plugin org.apache.maven.plugins:maven-clean-plugin:3.1.0 or one of its dependencies could not be resolved: Could not find artifact org.apache.maven.plugins:maven-clean-plugin:jar:3.1.0 in central (file:target/null) ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-jar-plugin] jorsol opened a new pull request, #50: [MJAR-291] - Upgrade Parent to 37
jorsol opened a new pull request, #50: URL: https://github.com/apache/maven-jar-plugin/pull/50 Following this checklist to help us incorporate your contribution quickly and easily: - [X] Make sure there is a [JIRA issue](https://issues.apache.org/jira/browse/MJAR) filed for the change (usually before you start working on it). Trivial changes like typos do not require a JIRA issue. Your pull request should address just this issue, without pulling in other changes. - [X] Each commit in the pull request should have a meaningful subject line and body. - [X] Format the pull request title like `[MJAR-XXX] - Fixes bug in ApproximateQuantiles`, where you replace `MJAR-XXX` with the appropriate JIRA issue. Best practice is to use the JIRA issue title in the pull request title and in the first line of the commit message. - [X] Write a pull request description that is detailed enough to understand what the pull request does, how, and why. - [X] Run `mvn clean verify` to make sure basic checks pass. A more thorough check will be performed on your pull request automatically. - [X] You have run the integration tests successfully (`mvn -Prun-its clean verify`). If your pull request is about ~20 lines of code you don't need to sign an [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf) if you are unsure please ask on the developers list. To make clear that you license your contribution under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0) you have to acknowledge this by using the following check-box. - [X] I hereby declare this contribution to be licenced under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0) - [X] In any other case, please file an [Apache Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-integration-testing] michael-o commented on pull request #190: [MNG-7353] Add missing dependencies to bootstrap.txt
michael-o commented on PR #190: URL: https://github.com/apache/maven-integration-testing/pull/190#issuecomment-1225467688 > locally with Maven from master I have the same > > ``` > [INFO] --< org.apache.maven.its.mng7443:consistent-logging-of-optional-projects-and-profiles-selectors >-- > [INFO] Building consistent-logging-of-optional-projects-and-profiles-selectors 1.0 > [INFO] from pom.xml > [INFO] [ jar ]- > [INFO] Downloading from central: file:target/null/org/apache/maven/plugins/maven-clean-plugin/3.1.0/maven-clean-plugin-3.1.0.pom > [WARNING] The POM for org.apache.maven.plugins:maven-clean-plugin:jar:3.1.0 is missing, no dependency information available > [INFO] Downloading from central: file:target/null/org/apache/maven/plugins/maven-clean-plugin/3.1.0/maven-clean-plugin-3.1.0.jar > [INFO] > ... > [ERROR] Plugin org.apache.maven.plugins:maven-clean-plugin:3.1.0 or one of its dependencies could not be resolved: Could not find artifact org.apache.maven.plugins:maven-clean-plugin:jar:3.1.0 in central (file:target/null) -> [Help 1] > org.apache.maven.plugin.PluginResolutionException: Plugin org.apache.maven.plugins:maven-clean-plugin:3.1.0 or one of its dependencies could not be resolved: Could not find artifact org.apache.maven.plugins:maven-clean-plugin:jar:3.1.0 in central (file:target/null) > ``` Weird why it does not fail for me with two setups. I agree for the clean plugin, but what's with dependency plugin? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-integration-testing] slawekjaranowski commented on pull request #190: [MNG-7353] Add missing dependencies to bootstrap.txt
slawekjaranowski commented on PR #190: URL: https://github.com/apache/maven-integration-testing/pull/190#issuecomment-1225549241 m-dependency-p - versions from test was added to bootstrap -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-jar-plugin] slawekjaranowski commented on a diff in pull request #50: [MJAR-291] - Upgrade Parent to 37
slawekjaranowski commented on code in PR #50: URL: https://github.com/apache/maven-jar-plugin/pull/50#discussion_r953643266 ## src/it/MJAR-162/pom.xml: ## @@ -32,12 +32,17 @@ junit junit - 3.8.1 + 4.13.2 test + +org.apache.maven.plugins +maven-resources-plugin +3.3.0 + Review Comment: Is it needed for parent pom upgrade? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Comment Edited] (MSITE-773) The evaluation of the within the settings.xml does not work
[
https://issues.apache.org/jira/browse/MSITE-773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584189#comment-17584189
]
Elliotte Rusty Harold edited comment on MSITE-773 at 8/24/22 11:18 AM:
---
The default is that issues are still issues until there's reason to believe
otherwise. Reporters shouldn't have to constantly comment on and refile bugs to
keep them open. Time does not fix bugs.
was (Author: elharo):
The default is that issues are still issues until there's reason to believe
otherwise. Reporters shouldn't have to constantly comment on and refile bugs to
keep them open.
> The evaluation of the within the settings.xml does not work
> ---
>
> Key: MSITE-773
> URL: https://issues.apache.org/jira/browse/MSITE-773
> Project: Maven Site Plugin
> Issue Type: Bug
> Components: site:deploy
>Affects Versions: 3.5
>Reporter: Konrad Windszus
>Priority: Major
> Fix For: waiting-for-feedback
>
>
> Although the m-s-p evaluates the configuration within the settings.xml it
> does not correctly evaluate the {{wagonProvider}} element in the settings.xml
> (https://maven.apache.org/guides/mini/guide-wagon-providers.html).
> Using it leads to exceptions like this
> {code}
> Unable to configure Wagon: 'dav': While configuring wagon for 'nexus': Unable
> to apply wagon configuration. Cannot find 'wagonProvider' in class
> org.apache.maven.wagon.providers.webdav.WebDavWagon
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MSITE-773) The evaluation of the within the settings.xml does not work
[
https://issues.apache.org/jira/browse/MSITE-773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584189#comment-17584189
]
Elliotte Rusty Harold commented on MSITE-773:
-
The default is that issues are still issues until there's reason to believe
otherwise. Reporters shouldn't have to constantly comment on and refile bugs to
keep them open.
> The evaluation of the within the settings.xml does not work
> ---
>
> Key: MSITE-773
> URL: https://issues.apache.org/jira/browse/MSITE-773
> Project: Maven Site Plugin
> Issue Type: Bug
> Components: site:deploy
>Affects Versions: 3.5
>Reporter: Konrad Windszus
>Priority: Major
> Fix For: waiting-for-feedback
>
>
> Although the m-s-p evaluates the configuration within the settings.xml it
> does not correctly evaluate the {{wagonProvider}} element in the settings.xml
> (https://maven.apache.org/guides/mini/guide-wagon-providers.html).
> Using it leads to exceptions like this
> {code}
> Unable to configure Wagon: 'dav': While configuring wagon for 'nexus': Unable
> to apply wagon configuration. Cannot find 'wagonProvider' in class
> org.apache.maven.wagon.providers.webdav.WebDavWagon
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[GitHub] [maven] michael-o commented on pull request #793: [MNG-7532] Log shouldn't have been deprecated so ensure it is not
michael-o commented on PR #793: URL: https://github.com/apache/maven/pull/793#issuecomment-1225589776 > @michael-o right but it is not clear what we do of plexus - we are between being based on it and dropping it. Personally I tend to think we should rely on the abstraction we want to expose long term in a very stable way so either JUL (which can be used as an abstraction) or an org.apache.maven.somethingLogging but if we import plexus @asf it sounds like another valid option. Do you expect SLF4J 2.x not to live 10 years? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven] michael-o commented on pull request #793: [MNG-7532] Log shouldn't have been deprecated so ensure it is not
michael-o commented on PR #793: URL: https://github.com/apache/maven/pull/793#issuecomment-1225590071 I'd be interested to head @ceki's opinion on this. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MNG-7532) Revert MNG-6931 deprecation since list shows no consensus on that
[ https://issues.apache.org/jira/browse/MNG-7532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584198#comment-17584198 ] ASF GitHub Bot commented on MNG-7532: - michael-o commented on PR #793: URL: https://github.com/apache/maven/pull/793#issuecomment-1225590071 I'd be interested to head @ceki's opinion on this. > Revert MNG-6931 deprecation since list shows no consensus on that > - > > Key: MNG-7532 > URL: https://issues.apache.org/jira/browse/MNG-7532 > Project: Maven > Issue Type: Task >Reporter: Romain Manni-Bucau >Priority: Major > > There are several threads on the dev list asking for the drop of slf4j and at > least keeping a logging abstraction for not internal dev (= core can use > slf4j but not mojo/extensions). > Work is being done to abstract plugin api so let's keep the > deprecation/replacement of our Log API in this track and keep it the official > way for now. > one of the multiple refs: > https://www.mail-archive.com/dev@maven.apache.org/msg123452.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7532) Revert MNG-6931 deprecation since list shows no consensus on that
[ https://issues.apache.org/jira/browse/MNG-7532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584196#comment-17584196 ] ASF GitHub Bot commented on MNG-7532: - michael-o commented on PR #793: URL: https://github.com/apache/maven/pull/793#issuecomment-1225589776 > @michael-o right but it is not clear what we do of plexus - we are between being based on it and dropping it. Personally I tend to think we should rely on the abstraction we want to expose long term in a very stable way so either JUL (which can be used as an abstraction) or an org.apache.maven.somethingLogging but if we import plexus @asf it sounds like another valid option. Do you expect SLF4J 2.x not to live 10 years? > Revert MNG-6931 deprecation since list shows no consensus on that > - > > Key: MNG-7532 > URL: https://issues.apache.org/jira/browse/MNG-7532 > Project: Maven > Issue Type: Task >Reporter: Romain Manni-Bucau >Priority: Major > > There are several threads on the dev list asking for the drop of slf4j and at > least keeping a logging abstraction for not internal dev (= core can use > slf4j but not mojo/extensions). > Work is being done to abstract plugin api so let's keep the > deprecation/replacement of our Log API in this track and keep it the official > way for now. > one of the multiple refs: > https://www.mail-archive.com/dev@maven.apache.org/msg123452.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-jar-plugin] jorsol commented on a diff in pull request #50: [MJAR-291] - Upgrade Parent to 37
jorsol commented on code in PR #50: URL: https://github.com/apache/maven-jar-plugin/pull/50#discussion_r953676232 ## src/it/MJAR-162/pom.xml: ## @@ -32,12 +32,17 @@ junit junit - 3.8.1 + 4.13.2 test + +org.apache.maven.plugins +maven-resources-plugin +3.3.0 + Review Comment: it's needed as the empty test jar is not filtering the .gitignore file with the defaults. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-jar-plugin] jorsol commented on a diff in pull request #50: [MJAR-291] - Upgrade Parent to 37
jorsol commented on code in PR #50: URL: https://github.com/apache/maven-jar-plugin/pull/50#discussion_r953676232 ## src/it/MJAR-162/pom.xml: ## @@ -32,12 +32,17 @@ junit junit - 3.8.1 + 4.13.2 test + +org.apache.maven.plugins +maven-resources-plugin +3.3.0 + Review Comment: it's needed as the empty test jar is not filtering the .gitignore file with the defaults. Or in other words, the default resource plugin copies the .gitignore into the jar and the test fails as the jar is not supposed to be created. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven] rmannibucau commented on pull request #793: [MNG-7532] Log shouldn't have been deprecated so ensure it is not
rmannibucau commented on PR #793: URL: https://github.com/apache/maven/pull/793#issuecomment-1225612530 > Do you expect SLF4J 2.x not to live 10 years? I expect it to not be usable within 5 years at least due to the current usage of 1.x and SLF4J is a good example of why we shouldnt rely on a 3rd party for our own API (once again, point is used by *users*), it broke several times and we can't help. Only facade we can leverage would be Java Util Logging if you really want to kill our existing logging abstraction and use something existing IMHO. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MNG-7532) Revert MNG-6931 deprecation since list shows no consensus on that
[ https://issues.apache.org/jira/browse/MNG-7532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584209#comment-17584209 ] ASF GitHub Bot commented on MNG-7532: - rmannibucau commented on PR #793: URL: https://github.com/apache/maven/pull/793#issuecomment-1225612530 > Do you expect SLF4J 2.x not to live 10 years? I expect it to not be usable within 5 years at least due to the current usage of 1.x and SLF4J is a good example of why we shouldnt rely on a 3rd party for our own API (once again, point is used by *users*), it broke several times and we can't help. Only facade we can leverage would be Java Util Logging if you really want to kill our existing logging abstraction and use something existing IMHO. > Revert MNG-6931 deprecation since list shows no consensus on that > - > > Key: MNG-7532 > URL: https://issues.apache.org/jira/browse/MNG-7532 > Project: Maven > Issue Type: Task >Reporter: Romain Manni-Bucau >Priority: Major > > There are several threads on the dev list asking for the drop of slf4j and at > least keeping a logging abstraction for not internal dev (= core can use > slf4j but not mojo/extensions). > Work is being done to abstract plugin api so let's keep the > deprecation/replacement of our Log API in this track and keep it the official > way for now. > one of the multiple refs: > https://www.mail-archive.com/dev@maven.apache.org/msg123452.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-dist-tool] dependabot[bot] commented on pull request #9: Bump jsoup from 1.13.1 to 1.15.2
dependabot[bot] commented on PR #9: URL: https://github.com/apache/maven-dist-tool/pull/9#issuecomment-1225626745 Superseded by #20. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-dist-tool] dependabot[bot] opened a new pull request, #20: Bump jsoup from 1.13.1 to 1.15.3
dependabot[bot] opened a new pull request, #20: URL: https://github.com/apache/maven-dist-tool/pull/20 Bumps [jsoup](https://github.com/jhy/jsoup) from 1.13.1 to 1.15.3. Release notes Sourced from https://github.com/jhy/jsoup/releases";>jsoup's releases. jsoup 1.15.3 jsoup 1.15.3 is out now, and includes a security fix for potential XSS attacks, along with other bug fixes and improvements, including more descriptive validation error messages. Details: https://github.com/jhy/jsoup/security/advisories/GHSA-gp7f-rwcx-9369";>Security advisory https://jsoup.org/news/release-1.15.3";>Release notes https://jsoup.org/download";>Download jsoup 1.15.2 is out now with a bunch of https://jsoup.org/news/release-1.15.2";>improvements and bug fixes. jsoup 1.15.1 is out now with a bunch of https://jsoup.org/news/release-1.15.1";>improvements and bug fixes. jsoup 1.14.3 jsoup 1.14.3 is out now, adding native XPath selector support, improved \ support, and also includes a bunch of bug fixes, improvements, and performance enhancements. See the https://jsoup.org/news/release-1.14.3";>release announcement for the full changelog. jsoup 1.14.2 Caught by the fuzz! jsoup 1.14.2 is out now, and includes a set of parser bug fixes and improvements for handling rough HTML and XML, as identified by the Jazzer JVM fuzzer. This release also includes other fixes and improvements. See the https://jsoup.org/news/release-1.14.2";>release announcement for the full changelog. jsoup 1.14.1 jsoup 1.14.1 is out now, with simple request session management, increased parse robustness, and a ton of other improvements, speed-ups, and bug fixes. See the full https://jsoup.org/news/release-1.14.1";>announcement for all the details on what's changed. Changelog Sourced from https://github.com/jhy/jsoup/blob/master/CHANGES";>jsoup's changelog. jsoup changelog Release 1.15.3 [2022-Aug-24] Security: fixed an issue where the jsoup cleaner may incorrectly sanitize crafted XSS attempts if SafeList.preserveRelativeLinks is enabled. https://github.com/jhy/jsoup/security/advisories/GHSA-gp7f-rwcx-9369";>https://github.com/jhy/jsoup/security/advisories/GHSA-gp7f-rwcx-9369 Improvement: the Cleaner will preserve the source position of cleaned elements, if source tracking is enabled in the original parse. Improvement: the error messages output from Validate are more descriptive. Exceptions are now ValidationExceptions (extending IllegalArgumentException). Stack traces do not include the Validate class, to make it simpler to see where the exception originated. Common validation errors including malformed URLs and empty selector results have more explicit error messages. Bugfix: the DataUtil would incorrectly read from InputStreams that emitted reads less than the requested size. This lead to incorrect results when parsing from chunked server responses, for e.g. https://github-redirect.dependabot.com/jhy/jsoup/issues/1807";>jhy/jsoup#1807 Build Improvement: added implementation version and related fields to the jar manifest. https://github-redirect.dependabot.com/jhy/jsoup/issues/1809";>jhy/jsoup#1809 *** Release 1.15.2 [2022-Jul-04] Improvement: added the ability to track the position (line, column, index) in the original input source from where a given node was parsed. Accessible via Node.sourceRange() and Element.endSourceRange(). https://github-redirect.dependabot.com/jhy/jsoup/pull/1790";>jhy/jsoup#1790 Improvement: added Element.firstElementChild(), Element.lastElementChild(), Node.firstChild(), Node.lastChild(), as convenient accessors to those child nodes and elements. Improvement: added Element.expectFirst(cssQuery), which is just like Element.selectFirst(), but instead of returning a null if there is no match, will throw an IllegalArgumentException. This is useful if you want to simply abort processing if an expected match is not found. Improvement: when pretty-printing HTML, doctypes are emitted on a newline if there is a preceding comment. https://github-redirect.dependabot.com/jhy/jsoup/pull/1664";>jhy/jsoup#1664 Improvement: when pretty-printing, trim the leading and trailing spaces of textnodes in block tags when possible, so that they are indented correctly. https://github-redirect.dependabot.com/jhy/jsoup/issues/1798";>jhy/jsoup#1798 Improvement: in Element#selectXpath(), disable namespace awareness. This makes it possible to always select elements by their simple local name, regardless of whether an xmlns attribute was set. https://github-redirect.dependabot.com/jhy/jsoup/issues/1801";>jhy/jsoup#1801 Bugfix: when using the readToByteBuffer method, such as in Connection.Response.body(), if the document has no
[GitHub] [maven-dist-tool] dependabot[bot] closed pull request #9: Bump jsoup from 1.13.1 to 1.15.2
dependabot[bot] closed pull request #9: Bump jsoup from 1.13.1 to 1.15.2 URL: https://github.com/apache/maven-dist-tool/pull/9 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (SUREFIRE-2114) Surefire is going to kill self fork JVM. The exit has elapsed 30 seconds after System.exit(0).
[
https://issues.apache.org/jira/browse/SUREFIRE-2114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kamalpreet updated SUREFIRE-2114:
-
Description:
Hi Team,
I'm using maven surefire plugin to execute tests on two testing frameworks
(e.g, jUnit, jBehave).
Have tried to implement parallelisation by spawning couple of Threads which in
turn create processes to execute surefire jar (taking it from
{code:java}
ManagementFactory.getRuntimeMXBean().getSystemProperties().get("sun.java.command"){code}
Code snippet to show process creation -
{code:java}
ProcessBuilder processBuilder = new ProcessBuilder(commandArray);
Map environment = processBuilder.environment();
environment.put("platformIndex", String.valueOf(platformIndex));
try {
processBuilder.inheritIO();
Process p = processBuilder.start();
LOGGER.info("Is Alive {} {}", p.isAlive(), LocalTime.now());
int statusCode = p.waitFor();
} catch (Exception e) {
e.printStackTrace();
} {code}
And then calling *System.exit.*
*After running two or sometimes three processes in corresponding Threads, the
process execution got stuck on p.waitFor();*
Then the process exits after 30 secs and with error message *"Surefire is going
to kill self fork JVM. The exit has elapsed 30 seconds after System.exit(0)."*
resulting in Build Failure though the tests have passed in their respective
processes.
Seems like surefire execution is stuck in some processes. Could you please let
me know what can be the possible reasons for it and how to mitigate this? Tried
extending the ForkedProcessTimeoutInSeconds to few minutes.
Thanks.
was:
Hi Team,
I'm using maven surefire plugin to execute tests on two testing frameworks
(e.g, jUnit, jBehave).
Have tried to implement parallelisation by spawning couple of Threads which in
turn create processes to execute surefire jar (taking it from
{code:java}
ManagementFactory.getRuntimeMXBean().getSystemProperties().get("sun.java.command"){code}
Code snippet to show process creation -
{code:java}
ProcessBuilder processBuilder = new ProcessBuilder(commandArray);
Map environment = processBuilder.environment();
environment.put("platformIndex", String.valueOf(platformIndex));
try {
processBuilder.inheritIO();
Process p = processBuilder.start();
LOGGER.info("Is Alive {} {}", p.isAlive(), LocalTime.now());
int statusCode = p.waitFor();
} catch (Exception e) {
e.printStackTrace();
} {code}
And then calling *System.exit.*
*After running two or sometimes three processes in corresponding Threads, the
process execution got stuck on p.waitFor();*
Then the process exits after 30 secs and with error message *"Surefire is going
to kill self fork JVM. The exit has elapsed 30 seconds after System.exit(0)."*
resulting in Build Failure though the tests have passed in their respective
processes.
Seems like surefire execution is stuck in some processes. Could you please let
me know what can be the possible reasons for it and how to mitigate this? Tried
extending the ForkedProcessTimeoutInSeconds to few minutes.
Thanks.
> Surefire is going to kill self fork JVM. The exit has elapsed 30 seconds
> after System.exit(0).
> ---
>
> Key: SUREFIRE-2114
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2114
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Reporter: Kamalpreet
>Priority: Critical
>
> Hi Team,
> I'm using maven surefire plugin to execute tests on two testing frameworks
> (e.g, jUnit, jBehave).
> Have tried to implement parallelisation by spawning couple of Threads which
> in turn create processes to execute surefire jar (taking it from
>
> {code:java}
> ManagementFactory.getRuntimeMXBean().getSystemProperties().get("sun.java.command"){code}
> Code snippet to show process creation -
> {code:java}
> ProcessBuilder processBuilder = new ProcessBuilder(commandArray);
> Map environment = processBuilder.environment();
> environment.put("platformIndex", String.valueOf(platformIndex));
> try {
> processBuilder.inheritIO();
> Process p = processBuilder.start();
> LOGGER.info("Is Alive {} {}", p.isAlive(), LocalTime.now());
> int statusCode = p.waitFor();
> } catch (Exception e) {
> e.printStackTrace();
> } {code}
> And then calling *System.exit.*
>
> *After running two or sometimes three processes in corresponding Threads, the
> process execution got stuck on p.waitFor();*
> Then the process exits after 30 secs and with error message *"Surefire is
> going to kill self fork JVM. The exit has elapsed 30 seconds after
> System.exit(0)."* resulting in Build Failure though the tests have passed in
> their respective processes.
> Seems like surefire execution is stuck in some pro
[jira] [Created] (SUREFIRE-2114) Surefire is going to kill self fork JVM. The exit has elapsed 30 seconds after System.exit(0).
Kamalpreet created SUREFIRE-2114:
Summary: Surefire is going to kill self fork JVM. The exit has
elapsed 30 seconds after System.exit(0).
Key: SUREFIRE-2114
URL: https://issues.apache.org/jira/browse/SUREFIRE-2114
Project: Maven Surefire
Issue Type: Bug
Components: Maven Surefire Plugin
Reporter: Kamalpreet
Hi Team,
I'm using maven surefire plugin to execute tests on two testing frameworks
(e.g, jUnit, jBehave).
Have tried to implement parallelisation by spawning couple of Threads which in
turn create processes to execute surefire jar (taking it from
{code:java}
ManagementFactory.getRuntimeMXBean().getSystemProperties().get("sun.java.command"){code}
Code snippet to show process creation -
{code:java}
ProcessBuilder processBuilder = new ProcessBuilder(commandArray);
Map environment = processBuilder.environment();
environment.put("platformIndex", String.valueOf(platformIndex));
try {
processBuilder.inheritIO();
Process p = processBuilder.start();
LOGGER.info("Is Alive {} {}", p.isAlive(), LocalTime.now());
int statusCode = p.waitFor();
} catch (Exception e) {
e.printStackTrace();
} {code}
And then calling *System.exit.*
*After running two or sometimes three processes in corresponding Threads, the
process execution got stuck on p.waitFor();*
Then the process exits after 30 secs and with error message *"Surefire is going
to kill self fork JVM. The exit has elapsed 30 seconds after System.exit(0)."*
resulting in Build Failure though the tests have passed in their respective
processes.
Seems like surefire execution is stuck in some processes. Could you please let
me know what can be the possible reasons for it and how to mitigate this? Tried
extending the ForkedProcessTimeoutInSeconds to few minutes.
Thanks.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (SUREFIRE-2114) Surefire is going to kill self fork JVM. The exit has elapsed 30 seconds after System.exit(0).
[
https://issues.apache.org/jira/browse/SUREFIRE-2114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kamalpreet updated SUREFIRE-2114:
-
Description:
Hi Team,
I'm using maven surefire plugin to execute tests on two testing frameworks
(e.g, jUnit, jBehave).
Have tried to implement parallelisation by spawning couple of Threads which in
turn create processes to execute surefire jar (taking it from
{code:java}
ManagementFactory.getRuntimeMXBean().getSystemProperties().get("sun.java.command"){code}
Code snippet to show process creation -
{code:java}
ProcessBuilder processBuilder = new ProcessBuilder(commandArray);
Map environment = processBuilder.environment();
environment.put("platformIndex", String.valueOf(platformIndex));
try {
processBuilder.inheritIO();
Process p = processBuilder.start();
LOGGER.info("Is Alive {} {}", p.isAlive(), LocalTime.now());
int statusCode = p.waitFor();
} catch (Exception e) {
e.printStackTrace();
} {code}
And then calling *System.exit.*
*After running two or sometimes three processes in corresponding Threads, the
process execution got stuck on p.waitFor();*
Then the process exits after 30 secs and with error message *"Surefire is going
to kill self fork JVM. The exit has elapsed 30 seconds after System.exit(0)."*
resulting in Build Failure though the tests have passed in their respective
processes.
Seems like surefire execution is stuck in some processes. Could you please let
me know what can be the possible reasons for it and how to mitigate this? Tried
extending the ForkedProcessTimeoutInSeconds to few minutes.
Thanks.
was:
Hi Team,
I'm using maven surefire plugin to execute tests on two testing frameworks
(e.g, jUnit, jBehave).
Have tried to implement parallelisation by spawning couple of Threads which in
turn create processes to execute surefire jar (taking it from
{code:java}
ManagementFactory.getRuntimeMXBean().getSystemProperties().get("sun.java.command"){code}
Code snippet to show process creation -
{code:java}
ProcessBuilder processBuilder = new ProcessBuilder(commandArray);
Map environment = processBuilder.environment();
environment.put("platformIndex", String.valueOf(platformIndex));
try {
processBuilder.inheritIO();
Process p = processBuilder.start();
LOGGER.info("Is Alive {} {}", p.isAlive(), LocalTime.now());
int statusCode = p.waitFor();
} catch (Exception e) {
e.printStackTrace();
} {code}
And then calling *System.exit.*
*After running two or sometimes three processes in corresponding Threads, the
process execution got stuck on p.waitFor();*
Then the process exits after 30 secs and with error message *"Surefire is going
to kill self fork JVM. The exit has elapsed 30 seconds after System.exit(0)."*
resulting in Build Failure though the tests have passed in their respective
processes.
Seems like surefire execution is stuck in some processes. Could you please let
me know what can be the possible reasons for it and how to mitigate this? Tried
extending the ForkedProcessTimeoutInSeconds to few minutes.
Thanks.
> Surefire is going to kill self fork JVM. The exit has elapsed 30 seconds
> after System.exit(0).
> ---
>
> Key: SUREFIRE-2114
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2114
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Reporter: Kamalpreet
>Priority: Critical
>
> Hi Team,
> I'm using maven surefire plugin to execute tests on two testing frameworks
> (e.g, jUnit, jBehave).
> Have tried to implement parallelisation by spawning couple of Threads which
> in turn create processes to execute surefire jar (taking it from
>
> {code:java}
> ManagementFactory.getRuntimeMXBean().getSystemProperties().get("sun.java.command"){code}
> Code snippet to show process creation -
> {code:java}
> ProcessBuilder processBuilder = new ProcessBuilder(commandArray);
> Map environment = processBuilder.environment();
> environment.put("platformIndex", String.valueOf(platformIndex));
> try {
> processBuilder.inheritIO();
> Process p = processBuilder.start();
> LOGGER.info("Is Alive {} {}", p.isAlive(), LocalTime.now());
> int statusCode = p.waitFor();
> } catch (Exception e) {
> e.printStackTrace();
> } {code}
> And then calling *System.exit.*
>
> *After running two or sometimes three processes in corresponding Threads, the
> process execution got stuck on p.waitFor();*
> Then the process exits after 30 secs and with error message *"Surefire is
> going to kill self fork JVM. The exit has elapsed 30 seconds after
> System.exit(0)."* resulting in Build Failure though the tests have passed in
> their respective processes.
> Seems like surefire execution is stuck in some processes
[jira] [Updated] (SUREFIRE-2114) Surefire is going to kill self fork JVM. The exit has elapsed 30 seconds after System.exit(0).
[
https://issues.apache.org/jira/browse/SUREFIRE-2114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kamalpreet updated SUREFIRE-2114:
-
Description:
Hi Team,
I'm using maven surefire plugin (LTS Version) to execute tests on two testing
frameworks (e.g, jUnit, jBehave).
Have tried to implement parallelisation by spawning couple of Threads which in
turn create processes to execute surefire jar, taking it from -
{code:java}
ManagementFactory.getRuntimeMXBean().getSystemProperties().get("sun.java.command"){code}
Code snippet to show process creation -
{code:java}
ProcessBuilder processBuilder = new ProcessBuilder(commandArray);
Map environment = processBuilder.environment();
environment.put("platformIndex", String.valueOf(platformIndex));
try {
processBuilder.inheritIO();
Process p = processBuilder.start();
LOGGER.info("Is Alive {} {}", p.isAlive(), LocalTime.now());
int statusCode = p.waitFor();
} catch (Exception e) {
e.printStackTrace();
} {code}
And then calling *System.exit.*
*After running two or sometimes three processes in corresponding Threads, the
process execution got stuck on p.waitFor();*
Then the process exits after 30 secs and with error message *"Surefire is going
to kill self fork JVM. The exit has elapsed 30 seconds after System.exit(0)."*
resulting in Build Failure though the tests have passed in their respective
processes.
Seems like surefire execution is stuck in some processes. Could you please let
me know what can be the possible reasons for it and how to mitigate this? Tried
extending the ForkedProcessTimeoutInSeconds to few minutes.
Thanks.
was:
Hi Team,
I'm using maven surefire plugin to execute tests on two testing frameworks
(e.g, jUnit, jBehave).
Have tried to implement parallelisation by spawning couple of Threads which in
turn create processes to execute surefire jar (taking it from
{code:java}
ManagementFactory.getRuntimeMXBean().getSystemProperties().get("sun.java.command"){code}
Code snippet to show process creation -
{code:java}
ProcessBuilder processBuilder = new ProcessBuilder(commandArray);
Map environment = processBuilder.environment();
environment.put("platformIndex", String.valueOf(platformIndex));
try {
processBuilder.inheritIO();
Process p = processBuilder.start();
LOGGER.info("Is Alive {} {}", p.isAlive(), LocalTime.now());
int statusCode = p.waitFor();
} catch (Exception e) {
e.printStackTrace();
} {code}
And then calling *System.exit.*
*After running two or sometimes three processes in corresponding Threads, the
process execution got stuck on p.waitFor();*
Then the process exits after 30 secs and with error message *"Surefire is going
to kill self fork JVM. The exit has elapsed 30 seconds after System.exit(0)."*
resulting in Build Failure though the tests have passed in their respective
processes.
Seems like surefire execution is stuck in some processes. Could you please let
me know what can be the possible reasons for it and how to mitigate this? Tried
extending the ForkedProcessTimeoutInSeconds to few minutes.
Thanks.
> Surefire is going to kill self fork JVM. The exit has elapsed 30 seconds
> after System.exit(0).
> ---
>
> Key: SUREFIRE-2114
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2114
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Reporter: Kamalpreet
>Priority: Critical
>
> Hi Team,
> I'm using maven surefire plugin (LTS Version) to execute tests on two testing
> frameworks (e.g, jUnit, jBehave).
> Have tried to implement parallelisation by spawning couple of Threads which
> in turn create processes to execute surefire jar, taking it from -
> {code:java}
> ManagementFactory.getRuntimeMXBean().getSystemProperties().get("sun.java.command"){code}
> Code snippet to show process creation -
> {code:java}
> ProcessBuilder processBuilder = new ProcessBuilder(commandArray);
> Map environment = processBuilder.environment();
> environment.put("platformIndex", String.valueOf(platformIndex));
> try {
> processBuilder.inheritIO();
> Process p = processBuilder.start();
> LOGGER.info("Is Alive {} {}", p.isAlive(), LocalTime.now());
> int statusCode = p.waitFor();
> } catch (Exception e) {
> e.printStackTrace();
> } {code}
> And then calling *System.exit.*
>
> *After running two or sometimes three processes in corresponding Threads, the
> process execution got stuck on p.waitFor();*
> Then the process exits after 30 secs and with error message *"Surefire is
> going to kill self fork JVM. The exit has elapsed 30 seconds after
> System.exit(0)."* resulting in Build Failure though the tests have passed in
> their respective processes.
> Seems like surefire execution is s
[jira] [Updated] (SUREFIRE-2114) Surefire is going to kill self fork JVM. The exit has elapsed 30 seconds after System.exit(0).
[
https://issues.apache.org/jira/browse/SUREFIRE-2114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kamalpreet updated SUREFIRE-2114:
-
Labels: Issue (was: )
> Surefire is going to kill self fork JVM. The exit has elapsed 30 seconds
> after System.exit(0).
> ---
>
> Key: SUREFIRE-2114
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2114
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Reporter: Kamalpreet
>Priority: Critical
> Labels: Issue
>
> Hi Team,
> I'm using maven surefire plugin (LTS Version) to execute tests on two testing
> frameworks (e.g, jUnit, jBehave).
> Have tried to implement parallelisation by spawning couple of Threads which
> in turn create processes to execute surefire jar, taking it from -
> {code:java}
> ManagementFactory.getRuntimeMXBean().getSystemProperties().get("sun.java.command"){code}
> Code snippet to show process creation -
> {code:java}
> ProcessBuilder processBuilder = new ProcessBuilder(commandArray);
> Map environment = processBuilder.environment();
> environment.put("platformIndex", String.valueOf(platformIndex));
> try {
> processBuilder.inheritIO();
> Process p = processBuilder.start();
> LOGGER.info("Is Alive {} {}", p.isAlive(), LocalTime.now());
> int statusCode = p.waitFor();
> } catch (Exception e) {
> e.printStackTrace();
> } {code}
> And then calling *System.exit.*
>
> *After running two or sometimes three processes in corresponding Threads, the
> process execution got stuck on p.waitFor();*
> Then the process exits after 30 secs and with error message *"Surefire is
> going to kill self fork JVM. The exit has elapsed 30 seconds after
> System.exit(0)."* resulting in Build Failure though the tests have passed in
> their respective processes.
> Seems like surefire execution is stuck in some processes. Could you please
> let me know what can be the possible reasons for it and how to mitigate this?
> Tried extending the ForkedProcessTimeoutInSeconds to few minutes.
> Thanks.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (SUREFIRE-2114) Surefire is going to kill self fork JVM. The exit has elapsed 30 seconds after System.exit(0).
[
https://issues.apache.org/jira/browse/SUREFIRE-2114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kamalpreet updated SUREFIRE-2114:
-
Labels: Issue process (was: Issue)
> Surefire is going to kill self fork JVM. The exit has elapsed 30 seconds
> after System.exit(0).
> ---
>
> Key: SUREFIRE-2114
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2114
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Reporter: Kamalpreet
>Priority: Critical
> Labels: Issue, process
>
> Hi Team,
> I'm using maven surefire plugin (LTS Version) to execute tests on two testing
> frameworks (e.g, jUnit, jBehave).
> Have tried to implement parallelisation by spawning couple of Threads which
> in turn create processes to execute surefire jar, taking it from -
> {code:java}
> ManagementFactory.getRuntimeMXBean().getSystemProperties().get("sun.java.command"){code}
> Code snippet to show process creation -
> {code:java}
> ProcessBuilder processBuilder = new ProcessBuilder(commandArray);
> Map environment = processBuilder.environment();
> environment.put("platformIndex", String.valueOf(platformIndex));
> try {
> processBuilder.inheritIO();
> Process p = processBuilder.start();
> LOGGER.info("Is Alive {} {}", p.isAlive(), LocalTime.now());
> int statusCode = p.waitFor();
> } catch (Exception e) {
> e.printStackTrace();
> } {code}
> And then calling *System.exit.*
>
> *After running two or sometimes three processes in corresponding Threads, the
> process execution got stuck on p.waitFor();*
> Then the process exits after 30 secs and with error message *"Surefire is
> going to kill self fork JVM. The exit has elapsed 30 seconds after
> System.exit(0)."* resulting in Build Failure though the tests have passed in
> their respective processes.
> Seems like surefire execution is stuck in some processes. Could you please
> let me know what can be the possible reasons for it and how to mitigate this?
> Tried extending the ForkedProcessTimeoutInSeconds to few minutes.
> Thanks.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MWRAPPER-48) Error "}" was unexpected at this time (Windows 10)
[
https://issues.apache.org/jira/browse/MWRAPPER-48?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584240#comment-17584240
]
Svein commented on MWRAPPER-48:
---
I think a better way is to use:
@setlocal EnableDelayedExpansion and !WRAPPER_JAR!
{code:java}
@setlocal EnableDelayedExpansion
powershell -Command "&{"^
"$webclient = new-object System.Net.WebClient;"^
"if (-not ([string]::IsNullOrEmpty('%MVNW_USERNAME%') -and
[string]::IsNullOrEmpty('%MVNW_PASSWORD%'))) {"^
"$webclient.Credentials = new-object
System.Net.NetworkCredential('%MVNW_USERNAME%', '%MVNW_PASSWORD%');"^
"}"^
"[Net.ServicePointManager]::SecurityProtocol =
[Net.SecurityProtocolType]::Tls12; $webclient.DownloadFile('%DOWNLOAD_URL%',
'!WRAPPER_JAR!')"^
"}"
@endlocal
{code}
> Error "}" was unexpected at this time (Windows 10)
> --
>
> Key: MWRAPPER-48
> URL: https://issues.apache.org/jira/browse/MWRAPPER-48
> Project: Maven Wrapper
> Issue Type: Bug
> Components: Maven Wrapper Scripts
>Affects Versions: 0.5.6
>Reporter: Valentin Despa
>Priority: Major
> Labels: waiting-for-feedback
> Fix For: 3.1.0
>
> Attachments: 2022-08-23_16-25-17.png, demo.zip,
> image-2022-02-06-14-14-42-220.png, not-working.png, working.png
>
>
> I have generated a simple project using the Spring Initializr. If I try to
> run the Maven wrapper from a workspace folder within Jenkins, the following
> error occurs:
> {{"}" was unexpected at this time}}
> If I copy the project folder and run it from a different location, it works
> with no issues.
> A similar issue has been reported on Stackoverflow as well:
> [https://stackoverflow.com/q/62028432/766177]
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (MWRAPPER-48) Error "}" was unexpected at this time (Windows 10)
[
https://issues.apache.org/jira/browse/MWRAPPER-48?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584240#comment-17584240
]
Svein edited comment on MWRAPPER-48 at 8/24/22 1:22 PM:
I think a better way is to use:
@setlocal EnableDelayedExpansion and !WRAPPER_JAR!.
{code:java}
@setlocal EnableDelayedExpansion
powershell -Command "&{"^
"$webclient = new-object System.Net.WebClient;"^
"if (-not ([string]::IsNullOrEmpty('%MVNW_USERNAME%') -and
[string]::IsNullOrEmpty('%MVNW_PASSWORD%'))) {"^
"$webclient.Credentials = new-object
System.Net.NetworkCredential('%MVNW_USERNAME%', '%MVNW_PASSWORD%');"^
"}"^
"[Net.ServicePointManager]::SecurityProtocol =
[Net.SecurityProtocolType]::Tls12; $webclient.DownloadFile('%DOWNLOAD_URL%',
'!WRAPPER_JAR!')"^
"}"
@endlocal
{code}
was (Author: svein):
I think a better way is to use:
@setlocal EnableDelayedExpansion and !WRAPPER_JAR!
{code:java}
@setlocal EnableDelayedExpansion
powershell -Command "&{"^
"$webclient = new-object System.Net.WebClient;"^
"if (-not ([string]::IsNullOrEmpty('%MVNW_USERNAME%') -and
[string]::IsNullOrEmpty('%MVNW_PASSWORD%'))) {"^
"$webclient.Credentials = new-object
System.Net.NetworkCredential('%MVNW_USERNAME%', '%MVNW_PASSWORD%');"^
"}"^
"[Net.ServicePointManager]::SecurityProtocol =
[Net.SecurityProtocolType]::Tls12; $webclient.DownloadFile('%DOWNLOAD_URL%',
'!WRAPPER_JAR!')"^
"}"
@endlocal
{code}
> Error "}" was unexpected at this time (Windows 10)
> --
>
> Key: MWRAPPER-48
> URL: https://issues.apache.org/jira/browse/MWRAPPER-48
> Project: Maven Wrapper
> Issue Type: Bug
> Components: Maven Wrapper Scripts
>Affects Versions: 0.5.6
>Reporter: Valentin Despa
>Priority: Major
> Labels: waiting-for-feedback
> Fix For: 3.1.0
>
> Attachments: 2022-08-23_16-25-17.png, demo.zip,
> image-2022-02-06-14-14-42-220.png, not-working.png, working.png
>
>
> I have generated a simple project using the Spring Initializr. If I try to
> run the Maven wrapper from a workspace folder within Jenkins, the following
> error occurs:
> {{"}" was unexpected at this time}}
> If I copy the project folder and run it from a different location, it works
> with no issues.
> A similar issue has been reported on Stackoverflow as well:
> [https://stackoverflow.com/q/62028432/766177]
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (MWRAPPER-76) Error "{6}" was unexpected at this time (Windows 10)
Svein created MWRAPPER-76:
-
Summary: Error "{6}" was unexpected at this time (Windows 10)
Key: MWRAPPER-76
URL: https://issues.apache.org/jira/browse/MWRAPPER-76
Project: Maven Wrapper
Issue Type: Bug
Components: Maven Wrapper Scripts
Affects Versions: 3.1.1
Reporter: Svein
{color:#00}Testes and i worked on this path: C:\tmp\New (2)\{6}
folder\my-app57(2). The problem is the ')' character.{color}
{color:#00}My solution is:{color}
{color:#00}@setlocal EnableDelayedExpansion and !WRAPPER_JAR!.{color}
{code:java}
@setlocal EnableDelayedExpansion
powershell -Command "&{"^
"$webclient = new-object System.Net.WebClient;"^
"if (-not ([string]::IsNullOrEmpty('%MVNW_USERNAME%') -and
[string]::IsNullOrEmpty('%MVNW_PASSWORD%'))) {"^
"$webclient.Credentials = new-object
System.Net.NetworkCredential('%MVNW_USERNAME%', '%MVNW_PASSWORD%');"^
"}"^
"[Net.ServicePointManager]::SecurityProtocol =
[Net.SecurityProtocolType]::Tls12; $webclient.DownloadFile('%DOWNLOAD_URL%',
'!WRAPPER_JAR!')"^
"}"
@endlocal
{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MPMD-353) An API incompatibility was encountered while executing org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd
[
https://issues.apache.org/jira/browse/MPMD-353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584255#comment-17584255
]
Slawomir Jaranowski commented on MPMD-353:
--
[~michael-o]
Does this means that {{pmd:3.18.0}} will not work with Maven older than 3.8.2.
Adding jansi 2.4.0 to plugin dependencies has no effect - jansi is exported by
Maven.
> An API incompatibility was encountered while executing
> org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd
> ---
>
> Key: MPMD-353
> URL: https://issues.apache.org/jira/browse/MPMD-353
> Project: Maven PMD Plugin
> Issue Type: Bug
> Components: PMD
>Affects Versions: 3.18.0
>Reporter: Piotr Zygielo
>Priority: Major
>
> {code:bash}
> Error: Failed to execute goal
> org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd (pmd) on project
> UnnecessaryFullyQualifiedName: Execution pmd of goal
> org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd failed: An API
> incompatibility was encountered while executing
> org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd:
> java.lang.NoSuchMethodError:
> org.fusesource.jansi.AnsiConsole.out()Lorg/fusesource/jansi/AnsiPrintStream;
> Error: -
> Error: realm = plugin>org.apache.maven.plugins:maven-pmd-plugin:3.18.0
> Error: strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> Error: urls[0] =
> file:/home/runner/.m2/repository/org/apache/maven/plugins/maven-pmd-plugin/3.18.0/maven-pmd-plugin-3.18.0.jar
> Error: urls[1] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-core/6.48.0/pmd-core-6.48.0.jar
> Error: urls[2] =
> file:/home/runner/.m2/repository/org/antlr/antlr4-runtime/4.7.2/antlr4-runtime-4.7.2.jar
> Error: urls[3] =
> file:/home/runner/.m2/repository/com/beust/jcommander/1.48/jcommander-1.48.jar
> Error: urls[4] =
> file:/home/runner/.m2/repository/net/sourceforge/saxon/saxon/9.1.0.8/saxon-9.1.0.8.jar
> Error: urls[5] =
> file:/home/runner/.m2/repository/org/ow2/asm/asm/9.3/asm-9.3.jar
> Error: urls[6] =
> file:/home/runner/.m2/repository/com/google/code/gson/gson/2.8.9/gson-2.8.9.jar
> Error: urls[7] =
> file:/home/runner/.m2/repository/net/sourceforge/saxon/saxon/9.1.0.8/saxon-9.1.0.8-dom.jar
> Error: urls[8] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-java/6.48.0/pmd-java-6.48.0.jar
> Error: urls[9] =
> file:/home/runner/.m2/repository/org/apache/maven/shared/maven-artifact-transfer/0.13.1/maven-artifact-transfer-0.13.1.jar
> Error: urls[10] =
> file:/home/runner/.m2/repository/org/sonatype/aether/aether-util/1.7/aether-util-1.7.jar
> Error: urls[11] =
> file:/home/runner/.m2/repository/org/sonatype/sisu/sisu-inject-bean/1.4.2/sisu-inject-bean-1.4.2.jar
> Error: urls[12] =
> file:/home/runner/.m2/repository/org/sonatype/sisu/sisu-guice/2.1.7/sisu-guice-2.1.7-noaop.jar
> Error: urls[13] =
> file:/home/runner/.m2/repository/org/codehaus/plexus/plexus-interpolation/1.14/plexus-interpolation-1.14.jar
> Error: urls[14] =
> file:/home/runner/.m2/repository/org/sonatype/plexus/plexus-sec-dispatcher/1.3/plexus-sec-dispatcher-1.3.jar
> Error: urls[15] =
> file:/home/runner/.m2/repository/org/sonatype/plexus/plexus-cipher/1.4/plexus-cipher-1.4.jar
> Error: urls[16] =
> file:/home/runner/.m2/repository/org/codehaus/plexus/plexus-component-annotations/2.1.1/plexus-component-annotations-2.1.1.jar
> Error: urls[17] =
> file:/home/runner/.m2/repository/org/apache/maven/shared/maven-common-artifact-filters/3.3.1/maven-common-artifact-filters-3.3.1.jar
> Error: urls[18] =
> file:/home/runner/.m2/repository/commons-io/commons-io/2.11.0/commons-io-2.11.0.jar
> Error: urls[19] =
> file:/home/runner/.m2/repository/org/apache/commons/commons-lang3/3.12.0/commons-lang3-3.12.0.jar
> Error: urls[20] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-javascript/6.48.0/pmd-javascript-6.48.0.jar
> Error: urls[21] =
> file:/home/runner/.m2/repository/org/mozilla/rhino/1.7.14/rhino-1.7.14.jar
> Error: urls[22] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-jsp/6.48.0/pmd-jsp-6.48.0.jar
> Error: urls[23] =
> file:/home/runner/.m2/repository/org/slf4j/jul-to-slf4j/1.7.36/jul-to-slf4j-1.7.36.jar
> Error: urls[24] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-sink-api/1.11.1/doxia-sink-api-1.11.1.jar
> Error: urls[25] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-logging-api/1.11.1/doxia-logging-api-1.11.1.jar
> Error: urls[26] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-decoration-model/1.11.1/doxia-decoration-model-1.11.1.jar
> Error: urls[27] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-site-renderer/1.11.1/doxia-site-rend
[jira] [Updated] (SUREFIRE-2114) Surefire is going to kill self fork JVM. The exit has elapsed 30 seconds after System.exit(0).
[
https://issues.apache.org/jira/browse/SUREFIRE-2114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kamalpreet updated SUREFIRE-2114:
-
Description:
Hi Team,
I'm using maven surefire plugin (LTS Version) to execute tests on two testing
frameworks (e.g, jUnit, jBehave).
Have tried to implement parallelisation by spawning couple of Threads which in
turn create processes to execute surefire jar, taking it from -
{code:java}
ManagementFactory.getRuntimeMXBean().getSystemProperties().get("sun.java.command"){code}
Code snippet to show process creation -
{code:java}
ProcessBuilder processBuilder = new ProcessBuilder(commandArray);
Map environment = processBuilder.environment();
environment.put("platformIndex", String.valueOf(platformIndex));
try {
processBuilder.inheritIO();
Process p = processBuilder.start();
LOGGER.info("Is Alive {} {}", p.isAlive(), LocalTime.now());
int statusCode = p.waitFor();
} catch (Exception e) {
e.printStackTrace();
} {code}
And then calling *System.exit.*
*After running two or sometimes three processes in corresponding Threads, the
process execution got stuck on p.waitFor();*
Then the process exits after 30 secs and with error message *"Surefire is going
to kill self fork JVM. The exit has elapsed 30 seconds after System.exit(0)."*
resulting in Build Failure (sometimes it doesn't) though the tests have passed
in their respective processes.
Seems like surefire execution is stuck in some processes. Could you please let
me know what can be the possible reasons for it and how to mitigate this? Tried
extending the ForkedProcessTimeoutInSeconds to few minutes.
Thanks.
was:
Hi Team,
I'm using maven surefire plugin (LTS Version) to execute tests on two testing
frameworks (e.g, jUnit, jBehave).
Have tried to implement parallelisation by spawning couple of Threads which in
turn create processes to execute surefire jar, taking it from -
{code:java}
ManagementFactory.getRuntimeMXBean().getSystemProperties().get("sun.java.command"){code}
Code snippet to show process creation -
{code:java}
ProcessBuilder processBuilder = new ProcessBuilder(commandArray);
Map environment = processBuilder.environment();
environment.put("platformIndex", String.valueOf(platformIndex));
try {
processBuilder.inheritIO();
Process p = processBuilder.start();
LOGGER.info("Is Alive {} {}", p.isAlive(), LocalTime.now());
int statusCode = p.waitFor();
} catch (Exception e) {
e.printStackTrace();
} {code}
And then calling *System.exit.*
*After running two or sometimes three processes in corresponding Threads, the
process execution got stuck on p.waitFor();*
Then the process exits after 30 secs and with error message *"Surefire is going
to kill self fork JVM. The exit has elapsed 30 seconds after System.exit(0)."*
resulting in Build Failure though the tests have passed in their respective
processes.
Seems like surefire execution is stuck in some processes. Could you please let
me know what can be the possible reasons for it and how to mitigate this? Tried
extending the ForkedProcessTimeoutInSeconds to few minutes.
Thanks.
> Surefire is going to kill self fork JVM. The exit has elapsed 30 seconds
> after System.exit(0).
> ---
>
> Key: SUREFIRE-2114
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2114
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Reporter: Kamalpreet
>Priority: Critical
> Labels: Issue, process
>
> Hi Team,
> I'm using maven surefire plugin (LTS Version) to execute tests on two testing
> frameworks (e.g, jUnit, jBehave).
> Have tried to implement parallelisation by spawning couple of Threads which
> in turn create processes to execute surefire jar, taking it from -
> {code:java}
> ManagementFactory.getRuntimeMXBean().getSystemProperties().get("sun.java.command"){code}
> Code snippet to show process creation -
> {code:java}
> ProcessBuilder processBuilder = new ProcessBuilder(commandArray);
> Map environment = processBuilder.environment();
> environment.put("platformIndex", String.valueOf(platformIndex));
> try {
> processBuilder.inheritIO();
> Process p = processBuilder.start();
> LOGGER.info("Is Alive {} {}", p.isAlive(), LocalTime.now());
> int statusCode = p.waitFor();
> } catch (Exception e) {
> e.printStackTrace();
> } {code}
> And then calling *System.exit.*
>
> *After running two or sometimes three processes in corresponding Threads, the
> process execution got stuck on p.waitFor();*
> Then the process exits after 30 secs and with error message *"Surefire is
> going to kill self fork JVM. The exit has elapsed 30 seconds after
> System.exit(0)."* resulting in Build Failure (sometimes it doesn't) th
[jira] [Commented] (MPMD-353) An API incompatibility was encountered while executing org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd
[
https://issues.apache.org/jira/browse/MPMD-353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584266#comment-17584266
]
Michael Osipov commented on MPMD-353:
-
It does, but not out of the box. We likely need to analyze who else uses Maven
Shared Utils 3.3.4 and check.
> Adding jansi 2.4.0 to plugin dependencies has no effect - jansi is exported
> by Maven.
I cannot reproduce that. I did and it worked for me. It is a missing method,
that's it. Can you retry? After my local change all ITs passed.
> An API incompatibility was encountered while executing
> org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd
> ---
>
> Key: MPMD-353
> URL: https://issues.apache.org/jira/browse/MPMD-353
> Project: Maven PMD Plugin
> Issue Type: Bug
> Components: PMD
>Affects Versions: 3.18.0
>Reporter: Piotr Zygielo
>Priority: Major
>
> {code:bash}
> Error: Failed to execute goal
> org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd (pmd) on project
> UnnecessaryFullyQualifiedName: Execution pmd of goal
> org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd failed: An API
> incompatibility was encountered while executing
> org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd:
> java.lang.NoSuchMethodError:
> org.fusesource.jansi.AnsiConsole.out()Lorg/fusesource/jansi/AnsiPrintStream;
> Error: -
> Error: realm = plugin>org.apache.maven.plugins:maven-pmd-plugin:3.18.0
> Error: strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> Error: urls[0] =
> file:/home/runner/.m2/repository/org/apache/maven/plugins/maven-pmd-plugin/3.18.0/maven-pmd-plugin-3.18.0.jar
> Error: urls[1] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-core/6.48.0/pmd-core-6.48.0.jar
> Error: urls[2] =
> file:/home/runner/.m2/repository/org/antlr/antlr4-runtime/4.7.2/antlr4-runtime-4.7.2.jar
> Error: urls[3] =
> file:/home/runner/.m2/repository/com/beust/jcommander/1.48/jcommander-1.48.jar
> Error: urls[4] =
> file:/home/runner/.m2/repository/net/sourceforge/saxon/saxon/9.1.0.8/saxon-9.1.0.8.jar
> Error: urls[5] =
> file:/home/runner/.m2/repository/org/ow2/asm/asm/9.3/asm-9.3.jar
> Error: urls[6] =
> file:/home/runner/.m2/repository/com/google/code/gson/gson/2.8.9/gson-2.8.9.jar
> Error: urls[7] =
> file:/home/runner/.m2/repository/net/sourceforge/saxon/saxon/9.1.0.8/saxon-9.1.0.8-dom.jar
> Error: urls[8] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-java/6.48.0/pmd-java-6.48.0.jar
> Error: urls[9] =
> file:/home/runner/.m2/repository/org/apache/maven/shared/maven-artifact-transfer/0.13.1/maven-artifact-transfer-0.13.1.jar
> Error: urls[10] =
> file:/home/runner/.m2/repository/org/sonatype/aether/aether-util/1.7/aether-util-1.7.jar
> Error: urls[11] =
> file:/home/runner/.m2/repository/org/sonatype/sisu/sisu-inject-bean/1.4.2/sisu-inject-bean-1.4.2.jar
> Error: urls[12] =
> file:/home/runner/.m2/repository/org/sonatype/sisu/sisu-guice/2.1.7/sisu-guice-2.1.7-noaop.jar
> Error: urls[13] =
> file:/home/runner/.m2/repository/org/codehaus/plexus/plexus-interpolation/1.14/plexus-interpolation-1.14.jar
> Error: urls[14] =
> file:/home/runner/.m2/repository/org/sonatype/plexus/plexus-sec-dispatcher/1.3/plexus-sec-dispatcher-1.3.jar
> Error: urls[15] =
> file:/home/runner/.m2/repository/org/sonatype/plexus/plexus-cipher/1.4/plexus-cipher-1.4.jar
> Error: urls[16] =
> file:/home/runner/.m2/repository/org/codehaus/plexus/plexus-component-annotations/2.1.1/plexus-component-annotations-2.1.1.jar
> Error: urls[17] =
> file:/home/runner/.m2/repository/org/apache/maven/shared/maven-common-artifact-filters/3.3.1/maven-common-artifact-filters-3.3.1.jar
> Error: urls[18] =
> file:/home/runner/.m2/repository/commons-io/commons-io/2.11.0/commons-io-2.11.0.jar
> Error: urls[19] =
> file:/home/runner/.m2/repository/org/apache/commons/commons-lang3/3.12.0/commons-lang3-3.12.0.jar
> Error: urls[20] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-javascript/6.48.0/pmd-javascript-6.48.0.jar
> Error: urls[21] =
> file:/home/runner/.m2/repository/org/mozilla/rhino/1.7.14/rhino-1.7.14.jar
> Error: urls[22] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-jsp/6.48.0/pmd-jsp-6.48.0.jar
> Error: urls[23] =
> file:/home/runner/.m2/repository/org/slf4j/jul-to-slf4j/1.7.36/jul-to-slf4j-1.7.36.jar
> Error: urls[24] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-sink-api/1.11.1/doxia-sink-api-1.11.1.jar
> Error: urls[25] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-logging-api/1.11.1/doxia-logging-api-1.11.1.jar
> Error: urls[26] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-decoration-model/1.11.1/d
[GitHub] [maven] ceki commented on pull request #793: [MNG-7532] Log shouldn't have been deprecated so ensure it is not
ceki commented on PR #793: URL: https://github.com/apache/maven/pull/793#issuecomment-1225793381 The client facing API of SLF4J is stable and has been stable since version 1.0. You can compile an application using the API in SLF4J 1.0 (released in 2005) and it will run just fine with SLF4J version 2.0 on the classpath. As for Maven creating its own logging API, there is a [FAQ entry](https://www.slf4j.org/faq.html#optional_dependency) treating this question. Anyway, thank you all for your awesome work on Maven. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MNG-7532) Revert MNG-6931 deprecation since list shows no consensus on that
[ https://issues.apache.org/jira/browse/MNG-7532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584273#comment-17584273 ] ASF GitHub Bot commented on MNG-7532: - ceki commented on PR #793: URL: https://github.com/apache/maven/pull/793#issuecomment-1225793381 The client facing API of SLF4J is stable and has been stable since version 1.0. You can compile an application using the API in SLF4J 1.0 (released in 2005) and it will run just fine with SLF4J version 2.0 on the classpath. As for Maven creating its own logging API, there is a [FAQ entry](https://www.slf4j.org/faq.html#optional_dependency) treating this question. Anyway, thank you all for your awesome work on Maven. > Revert MNG-6931 deprecation since list shows no consensus on that > - > > Key: MNG-7532 > URL: https://issues.apache.org/jira/browse/MNG-7532 > Project: Maven > Issue Type: Task >Reporter: Romain Manni-Bucau >Priority: Major > > There are several threads on the dev list asking for the drop of slf4j and at > least keeping a logging abstraction for not internal dev (= core can use > slf4j but not mojo/extensions). > Work is being done to abstract plugin api so let's keep the > deprecation/replacement of our Log API in this track and keep it the official > way for now. > one of the multiple refs: > https://www.mail-archive.com/dev@maven.apache.org/msg123452.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MPMD-353) An API incompatibility was encountered while executing org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd
[
https://issues.apache.org/jira/browse/MPMD-353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584283#comment-17584283
]
Michael Osipov commented on MPMD-353:
-
I think alternatively, one can downgrade m-s-u.
> An API incompatibility was encountered while executing
> org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd
> ---
>
> Key: MPMD-353
> URL: https://issues.apache.org/jira/browse/MPMD-353
> Project: Maven PMD Plugin
> Issue Type: Bug
> Components: PMD
>Affects Versions: 3.18.0
>Reporter: Piotr Zygielo
>Priority: Major
>
> {code:bash}
> Error: Failed to execute goal
> org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd (pmd) on project
> UnnecessaryFullyQualifiedName: Execution pmd of goal
> org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd failed: An API
> incompatibility was encountered while executing
> org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd:
> java.lang.NoSuchMethodError:
> org.fusesource.jansi.AnsiConsole.out()Lorg/fusesource/jansi/AnsiPrintStream;
> Error: -
> Error: realm = plugin>org.apache.maven.plugins:maven-pmd-plugin:3.18.0
> Error: strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> Error: urls[0] =
> file:/home/runner/.m2/repository/org/apache/maven/plugins/maven-pmd-plugin/3.18.0/maven-pmd-plugin-3.18.0.jar
> Error: urls[1] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-core/6.48.0/pmd-core-6.48.0.jar
> Error: urls[2] =
> file:/home/runner/.m2/repository/org/antlr/antlr4-runtime/4.7.2/antlr4-runtime-4.7.2.jar
> Error: urls[3] =
> file:/home/runner/.m2/repository/com/beust/jcommander/1.48/jcommander-1.48.jar
> Error: urls[4] =
> file:/home/runner/.m2/repository/net/sourceforge/saxon/saxon/9.1.0.8/saxon-9.1.0.8.jar
> Error: urls[5] =
> file:/home/runner/.m2/repository/org/ow2/asm/asm/9.3/asm-9.3.jar
> Error: urls[6] =
> file:/home/runner/.m2/repository/com/google/code/gson/gson/2.8.9/gson-2.8.9.jar
> Error: urls[7] =
> file:/home/runner/.m2/repository/net/sourceforge/saxon/saxon/9.1.0.8/saxon-9.1.0.8-dom.jar
> Error: urls[8] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-java/6.48.0/pmd-java-6.48.0.jar
> Error: urls[9] =
> file:/home/runner/.m2/repository/org/apache/maven/shared/maven-artifact-transfer/0.13.1/maven-artifact-transfer-0.13.1.jar
> Error: urls[10] =
> file:/home/runner/.m2/repository/org/sonatype/aether/aether-util/1.7/aether-util-1.7.jar
> Error: urls[11] =
> file:/home/runner/.m2/repository/org/sonatype/sisu/sisu-inject-bean/1.4.2/sisu-inject-bean-1.4.2.jar
> Error: urls[12] =
> file:/home/runner/.m2/repository/org/sonatype/sisu/sisu-guice/2.1.7/sisu-guice-2.1.7-noaop.jar
> Error: urls[13] =
> file:/home/runner/.m2/repository/org/codehaus/plexus/plexus-interpolation/1.14/plexus-interpolation-1.14.jar
> Error: urls[14] =
> file:/home/runner/.m2/repository/org/sonatype/plexus/plexus-sec-dispatcher/1.3/plexus-sec-dispatcher-1.3.jar
> Error: urls[15] =
> file:/home/runner/.m2/repository/org/sonatype/plexus/plexus-cipher/1.4/plexus-cipher-1.4.jar
> Error: urls[16] =
> file:/home/runner/.m2/repository/org/codehaus/plexus/plexus-component-annotations/2.1.1/plexus-component-annotations-2.1.1.jar
> Error: urls[17] =
> file:/home/runner/.m2/repository/org/apache/maven/shared/maven-common-artifact-filters/3.3.1/maven-common-artifact-filters-3.3.1.jar
> Error: urls[18] =
> file:/home/runner/.m2/repository/commons-io/commons-io/2.11.0/commons-io-2.11.0.jar
> Error: urls[19] =
> file:/home/runner/.m2/repository/org/apache/commons/commons-lang3/3.12.0/commons-lang3-3.12.0.jar
> Error: urls[20] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-javascript/6.48.0/pmd-javascript-6.48.0.jar
> Error: urls[21] =
> file:/home/runner/.m2/repository/org/mozilla/rhino/1.7.14/rhino-1.7.14.jar
> Error: urls[22] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-jsp/6.48.0/pmd-jsp-6.48.0.jar
> Error: urls[23] =
> file:/home/runner/.m2/repository/org/slf4j/jul-to-slf4j/1.7.36/jul-to-slf4j-1.7.36.jar
> Error: urls[24] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-sink-api/1.11.1/doxia-sink-api-1.11.1.jar
> Error: urls[25] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-logging-api/1.11.1/doxia-logging-api-1.11.1.jar
> Error: urls[26] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-decoration-model/1.11.1/doxia-decoration-model-1.11.1.jar
> Error: urls[27] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-site-renderer/1.11.1/doxia-site-renderer-1.11.1.jar
> Error: urls[28] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-core/1.11.1/doxia-core-1.11.1.jar
> Error:
[GitHub] [maven] rmannibucau commented on pull request #793: [MNG-7532] Log shouldn't have been deprecated so ensure it is not
rmannibucau commented on PR #793: URL: https://github.com/apache/maven/pull/793#issuecomment-1225848083 > The client facing API of SLF4J is stable and has been stable since version 1.0. Not really 1.5->1.6 were not compat for ex (LocationAwareLogger#log, MessageFormatter, etc...). It hurt several apps already. So even I agree it is generally stable, it is not something we can assume for our *api*. It also increase the work needed to stay compatible since we have our own binding. It is really not "is slf4j bad" topic - in particular since it is fine to use it in @apache/maven core modules - but simply a design issue (we could workaround technical details if we would like to use it on a pure technical side), we should own our API to ensure mojo and extensions are reliable in time and not highly unstable (like gradle had been and was forced to introduce the wrapper to workaround it). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MNG-7532) Revert MNG-6931 deprecation since list shows no consensus on that
[ https://issues.apache.org/jira/browse/MNG-7532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584306#comment-17584306 ] ASF GitHub Bot commented on MNG-7532: - rmannibucau commented on PR #793: URL: https://github.com/apache/maven/pull/793#issuecomment-1225848083 > The client facing API of SLF4J is stable and has been stable since version 1.0. Not really 1.5->1.6 were not compat for ex (LocationAwareLogger#log, MessageFormatter, etc...). It hurt several apps already. So even I agree it is generally stable, it is not something we can assume for our *api*. It also increase the work needed to stay compatible since we have our own binding. It is really not "is slf4j bad" topic - in particular since it is fine to use it in @apache/maven core modules - but simply a design issue (we could workaround technical details if we would like to use it on a pure technical side), we should own our API to ensure mojo and extensions are reliable in time and not highly unstable (like gradle had been and was forced to introduce the wrapper to workaround it). > Revert MNG-6931 deprecation since list shows no consensus on that > - > > Key: MNG-7532 > URL: https://issues.apache.org/jira/browse/MNG-7532 > Project: Maven > Issue Type: Task >Reporter: Romain Manni-Bucau >Priority: Major > > There are several threads on the dev list asking for the drop of slf4j and at > least keeping a logging abstraction for not internal dev (= core can use > slf4j but not mojo/extensions). > Work is being done to abstract plugin api so let's keep the > deprecation/replacement of our Log API in this track and keep it the official > way for now. > one of the multiple refs: > https://www.mail-archive.com/dev@maven.apache.org/msg123452.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven] ceki commented on pull request #793: [MNG-7532] Log shouldn't have been deprecated so ensure it is not
ceki commented on PR #793: URL: https://github.com/apache/maven/pull/793#issuecomment-1225892740 @rmannibucau Since you mention `LocationAwareLogger`, the person who has been been publicly and loudly complaining about `LocationAwareLogger` for the last 12 years is the same person who asked for that breaking change in the first place. I am sure that is a bit hard to believe but please have a look at [SLF4J-118](https://jira.qos.ch/browse/SLF4J-118). The ticket is rather short and quite informative in its own right. As for stability, perhaps Maven has a higher standard regarding API compatibility than SLF4J, as Maven really shines in that regard. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MNG-7532) Revert MNG-6931 deprecation since list shows no consensus on that
[ https://issues.apache.org/jira/browse/MNG-7532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584321#comment-17584321 ] ASF GitHub Bot commented on MNG-7532: - ceki commented on PR #793: URL: https://github.com/apache/maven/pull/793#issuecomment-1225892740 @rmannibucau Since you mention `LocationAwareLogger`, the person who has been been publicly and loudly complaining about `LocationAwareLogger` for the last 12 years is the same person who asked for that breaking change in the first place. I am sure that is a bit hard to believe but please have a look at [SLF4J-118](https://jira.qos.ch/browse/SLF4J-118). The ticket is rather short and quite informative in its own right. As for stability, perhaps Maven has a higher standard regarding API compatibility than SLF4J, as Maven really shines in that regard. > Revert MNG-6931 deprecation since list shows no consensus on that > - > > Key: MNG-7532 > URL: https://issues.apache.org/jira/browse/MNG-7532 > Project: Maven > Issue Type: Task >Reporter: Romain Manni-Bucau >Priority: Major > > There are several threads on the dev list asking for the drop of slf4j and at > least keeping a logging abstraction for not internal dev (= core can use > slf4j but not mojo/extensions). > Work is being done to abstract plugin api so let's keep the > deprecation/replacement of our Log API in this track and keep it the official > way for now. > one of the multiple refs: > https://www.mail-archive.com/dev@maven.apache.org/msg123452.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven] michael-o commented on pull request #793: [MNG-7532] Log shouldn't have been deprecated so ensure it is not
michael-o commented on PR #793: URL: https://github.com/apache/maven/pull/793#issuecomment-1225894024 > > The client facing API of SLF4J is stable and has been stable since version 1.0. > > Not really 1.5->1.6 were not compat for ex (LocationAwareLogger#log, MessageFormatter, etc...). It hurt several apps already. So even I agree it is generally stable, it is not something we can assume for our _api_. It also increase the work needed to stay compatible since we have our own binding. > > It is really not "is slf4j bad" topic - in particular since it is fine to use it in @apache/maven core modules - but simply a design issue (we could workaround technical details if we would like to use it on a pure technical side), we should own our API to ensure mojo and extensions are reliable in time and not highly unstable (like gradle had been and was forced to introduce the wrapper to workaround it). You are mostly talking about impl, not API not. For the plugin dev.SLF4J simply works. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MNG-7532) Revert MNG-6931 deprecation since list shows no consensus on that
[ https://issues.apache.org/jira/browse/MNG-7532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584322#comment-17584322 ] ASF GitHub Bot commented on MNG-7532: - michael-o commented on PR #793: URL: https://github.com/apache/maven/pull/793#issuecomment-1225894024 > > The client facing API of SLF4J is stable and has been stable since version 1.0. > > Not really 1.5->1.6 were not compat for ex (LocationAwareLogger#log, MessageFormatter, etc...). It hurt several apps already. So even I agree it is generally stable, it is not something we can assume for our _api_. It also increase the work needed to stay compatible since we have our own binding. > > It is really not "is slf4j bad" topic - in particular since it is fine to use it in @apache/maven core modules - but simply a design issue (we could workaround technical details if we would like to use it on a pure technical side), we should own our API to ensure mojo and extensions are reliable in time and not highly unstable (like gradle had been and was forced to introduce the wrapper to workaround it). You are mostly talking about impl, not API not. For the plugin dev.SLF4J simply works. > Revert MNG-6931 deprecation since list shows no consensus on that > - > > Key: MNG-7532 > URL: https://issues.apache.org/jira/browse/MNG-7532 > Project: Maven > Issue Type: Task >Reporter: Romain Manni-Bucau >Priority: Major > > There are several threads on the dev list asking for the drop of slf4j and at > least keeping a logging abstraction for not internal dev (= core can use > slf4j but not mojo/extensions). > Work is being done to abstract plugin api so let's keep the > deprecation/replacement of our Log API in this track and keep it the official > way for now. > one of the multiple refs: > https://www.mail-archive.com/dev@maven.apache.org/msg123452.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-integration-testing] slawekjaranowski merged pull request #190: [MNG-7353] Add missing dependencies to bootstrap.txt
slawekjaranowski merged PR #190: URL: https://github.com/apache/maven-integration-testing/pull/190 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MNG-7527) Resolving inter-module dependencies does not work like expected
[
https://issues.apache.org/jira/browse/MNG-7527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584340#comment-17584340
]
Maarten Mulders commented on MNG-7527:
--
I believe it should even work with an initial {{mvn compile}} (rather than
{{mvn package}}. If the modules actually do contain code, a {{target/classes/}}
folder will get generated and Maven will pick that one up when compiling
{{dep1}} or {{dep2}}. This works as expected, as far as I can tell.
When there's no code (as in your example), you indeed need {{mvn package}} for
a {{target/}} folder to be generated. But a module without code would usually
have type {{pom}}. Out of curiosity, what is your use case for "empty" modules
as a dependency?
> Resolving inter-module dependencies does not work like expected
> ---
>
> Key: MNG-7527
> URL: https://issues.apache.org/jira/browse/MNG-7527
> Project: Maven
> Issue Type: Bug
> Components: Core
>Affects Versions: 4.0.0-alpha-1
>Reporter: Andrey Panfilov
>Assignee: Maarten Mulders
>Priority: Major
> Attachments: MNG-7527.zip
>
>
> After resolving MNG-4660 ReactorReader picks up packaged main artifact only
> and ignores supplemental artifacts:
>
>
> {code:java}
> private Artifact findMatchingArtifact( MavenProject project, Artifact
> requestedArtifact )
> {
> String requestedRepositoryConflictId = ArtifactIdUtils.toVersionlessId(
> requestedArtifact );
> Artifact mainArtifact = RepositoryUtils.toArtifact( project.getArtifact()
> );
> if ( requestedRepositoryConflictId.equals(
> ArtifactIdUtils.toVersionlessId( mainArtifact ) ) )
> {
> return mainArtifact;
> }
>
> /*
> * if module is not a part of "build reactor",
> project.getAttachedArtifacts() always
> * returns empty list, it seems that it is plugins' responsibility to
> populate attached artifacts
> * however it seems no corresponding API has been introduced, which would
> allow to gather information
> * about supplemental artifacts without building module
> */
> return RepositoryUtils.toArtifacts( project.getAttachedArtifacts()
> ).stream()
> .filter( isRequestedArtifact( requestedArtifact ) )
> .findFirst()
> .orElse( null );
> } {code}
>
>
> {code:java}
> private File determinePreviouslyPackagedArtifactFile( MavenProject project,
> Artifact artifact )
> {
> if ( artifact == null )
>
> { return null; }
> /*
> * the implementation/signature of this method looks bit confusing: it
> accepts any artifact descriptor
> * but returns main artifact only, I do believe in some cases (if
> supplemental artifact got discovered)
> * it may return wrong file
> */
> String fileName = String.format( "%s.%s",
> project.getBuild().getFinalName(), artifact.getExtension() );
> return new File( project.getBuild().getDirectory(), fileName );
> } {code}
>
> That new behaviour causes following issues:
> * if extension of main artifact differs from classifier's (e.g. war/classes)
> ReactorReader fails to pick up artifact (gh link to demo project:
> [https://github.com/andreybpanfilov/MNG-7527])
> * if extension of main artifact does not differ from classifier's
> ReactorReader picks up wrong artifact
>
> I have discovered another issue - the `mvn package clean package` command
> might look insane, however, I do believe it reveals there are some issues
> with internal state of artifacts/dependencies:
>
> {code:java}
> MNG-7527 % ~/app/maven/4.0/bin/mvn package clean package -f mng7527-dep2
> [INFO] Building jar:
> MNG-7527/mng7527-dep2/target/mng7527-dep2-0.0.1-SNAPSHOT.jar
> [INFO]
> --
> [INFO] BUILD FAILURE
> [INFO]
> --
> [INFO] Total time: 1.063 s
> [INFO] Finished at: 2022-08-08T21:05:18+10:00
> [INFO]
> --
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-jar-plugin:3.2.0:jar (default-jar) on project
> mng7527-dep2: You have to use a classifier to attach supplemental artifacts
> to the project instead of replacing them. -> [Help 1]
> [ERROR] {code}
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MPMD-353) An API incompatibility was encountered while executing org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd
[
https://issues.apache.org/jira/browse/MPMD-353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584342#comment-17584342
]
Piotr Zygielo commented on MPMD-353:
> Adding jansi 2.4.0 to plugin dependencies has no effect
I observe the same - adding org.fusesource.jansi:jansi:2.4.0 to plugin's
dependencies does not help when building with maven 3.6.3 in my project.
> An API incompatibility was encountered while executing
> org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd
> ---
>
> Key: MPMD-353
> URL: https://issues.apache.org/jira/browse/MPMD-353
> Project: Maven PMD Plugin
> Issue Type: Bug
> Components: PMD
>Affects Versions: 3.18.0
>Reporter: Piotr Zygielo
>Priority: Major
>
> {code:bash}
> Error: Failed to execute goal
> org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd (pmd) on project
> UnnecessaryFullyQualifiedName: Execution pmd of goal
> org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd failed: An API
> incompatibility was encountered while executing
> org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd:
> java.lang.NoSuchMethodError:
> org.fusesource.jansi.AnsiConsole.out()Lorg/fusesource/jansi/AnsiPrintStream;
> Error: -
> Error: realm = plugin>org.apache.maven.plugins:maven-pmd-plugin:3.18.0
> Error: strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> Error: urls[0] =
> file:/home/runner/.m2/repository/org/apache/maven/plugins/maven-pmd-plugin/3.18.0/maven-pmd-plugin-3.18.0.jar
> Error: urls[1] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-core/6.48.0/pmd-core-6.48.0.jar
> Error: urls[2] =
> file:/home/runner/.m2/repository/org/antlr/antlr4-runtime/4.7.2/antlr4-runtime-4.7.2.jar
> Error: urls[3] =
> file:/home/runner/.m2/repository/com/beust/jcommander/1.48/jcommander-1.48.jar
> Error: urls[4] =
> file:/home/runner/.m2/repository/net/sourceforge/saxon/saxon/9.1.0.8/saxon-9.1.0.8.jar
> Error: urls[5] =
> file:/home/runner/.m2/repository/org/ow2/asm/asm/9.3/asm-9.3.jar
> Error: urls[6] =
> file:/home/runner/.m2/repository/com/google/code/gson/gson/2.8.9/gson-2.8.9.jar
> Error: urls[7] =
> file:/home/runner/.m2/repository/net/sourceforge/saxon/saxon/9.1.0.8/saxon-9.1.0.8-dom.jar
> Error: urls[8] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-java/6.48.0/pmd-java-6.48.0.jar
> Error: urls[9] =
> file:/home/runner/.m2/repository/org/apache/maven/shared/maven-artifact-transfer/0.13.1/maven-artifact-transfer-0.13.1.jar
> Error: urls[10] =
> file:/home/runner/.m2/repository/org/sonatype/aether/aether-util/1.7/aether-util-1.7.jar
> Error: urls[11] =
> file:/home/runner/.m2/repository/org/sonatype/sisu/sisu-inject-bean/1.4.2/sisu-inject-bean-1.4.2.jar
> Error: urls[12] =
> file:/home/runner/.m2/repository/org/sonatype/sisu/sisu-guice/2.1.7/sisu-guice-2.1.7-noaop.jar
> Error: urls[13] =
> file:/home/runner/.m2/repository/org/codehaus/plexus/plexus-interpolation/1.14/plexus-interpolation-1.14.jar
> Error: urls[14] =
> file:/home/runner/.m2/repository/org/sonatype/plexus/plexus-sec-dispatcher/1.3/plexus-sec-dispatcher-1.3.jar
> Error: urls[15] =
> file:/home/runner/.m2/repository/org/sonatype/plexus/plexus-cipher/1.4/plexus-cipher-1.4.jar
> Error: urls[16] =
> file:/home/runner/.m2/repository/org/codehaus/plexus/plexus-component-annotations/2.1.1/plexus-component-annotations-2.1.1.jar
> Error: urls[17] =
> file:/home/runner/.m2/repository/org/apache/maven/shared/maven-common-artifact-filters/3.3.1/maven-common-artifact-filters-3.3.1.jar
> Error: urls[18] =
> file:/home/runner/.m2/repository/commons-io/commons-io/2.11.0/commons-io-2.11.0.jar
> Error: urls[19] =
> file:/home/runner/.m2/repository/org/apache/commons/commons-lang3/3.12.0/commons-lang3-3.12.0.jar
> Error: urls[20] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-javascript/6.48.0/pmd-javascript-6.48.0.jar
> Error: urls[21] =
> file:/home/runner/.m2/repository/org/mozilla/rhino/1.7.14/rhino-1.7.14.jar
> Error: urls[22] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-jsp/6.48.0/pmd-jsp-6.48.0.jar
> Error: urls[23] =
> file:/home/runner/.m2/repository/org/slf4j/jul-to-slf4j/1.7.36/jul-to-slf4j-1.7.36.jar
> Error: urls[24] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-sink-api/1.11.1/doxia-sink-api-1.11.1.jar
> Error: urls[25] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-logging-api/1.11.1/doxia-logging-api-1.11.1.jar
> Error: urls[26] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-decoration-model/1.11.1/doxia-decoration-model-1.11.1.jar
> Error: urls[27] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-site-renderer/1.11.1/d
[GitHub] [maven] rmannibucau commented on pull request #793: [MNG-7532] Log shouldn't have been deprecated so ensure it is not
rmannibucau commented on PR #793: URL: https://github.com/apache/maven/pull/793#issuecomment-1225954621 > You are mostly talking about impl, not API not. For the plugin dev.SLF4J simply works. No @michael-o this is 100% the API sadly. We went through that several times on several apache projects as mentionned and as mentionned it is not only due to slf4j quality but also our own design so let's just do our homework and align on the dev@ discussion our code. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MNG-7532) Revert MNG-6931 deprecation since list shows no consensus on that
[ https://issues.apache.org/jira/browse/MNG-7532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584358#comment-17584358 ] ASF GitHub Bot commented on MNG-7532: - rmannibucau commented on PR #793: URL: https://github.com/apache/maven/pull/793#issuecomment-1225954621 > You are mostly talking about impl, not API not. For the plugin dev.SLF4J simply works. No @michael-o this is 100% the API sadly. We went through that several times on several apache projects as mentionned and as mentionned it is not only due to slf4j quality but also our own design so let's just do our homework and align on the dev@ discussion our code. > Revert MNG-6931 deprecation since list shows no consensus on that > - > > Key: MNG-7532 > URL: https://issues.apache.org/jira/browse/MNG-7532 > Project: Maven > Issue Type: Task >Reporter: Romain Manni-Bucau >Priority: Major > > There are several threads on the dev list asking for the drop of slf4j and at > least keeping a logging abstraction for not internal dev (= core can use > slf4j but not mojo/extensions). > Work is being done to abstract plugin api so let's keep the > deprecation/replacement of our Log API in this track and keep it the official > way for now. > one of the multiple refs: > https://www.mail-archive.com/dev@maven.apache.org/msg123452.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-jar-plugin] slawekjaranowski merged pull request #50: [MJAR-291] - Upgrade Parent to 37
slawekjaranowski merged PR #50: URL: https://github.com/apache/maven-jar-plugin/pull/50 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Closed] (MJAR-291) Upgrade Parent to 37
[ https://issues.apache.org/jira/browse/MJAR-291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Slawomir Jaranowski closed MJAR-291. Fix Version/s: 3.3.0 Assignee: Slawomir Jaranowski Resolution: Fixed > Upgrade Parent to 37 > > > Key: MJAR-291 > URL: https://issues.apache.org/jira/browse/MJAR-291 > Project: Maven JAR Plugin > Issue Type: Dependency upgrade >Reporter: Jorge Solórzano >Assignee: Slawomir Jaranowski >Priority: Trivial > Fix For: 3.3.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-jar-plugin] slawekjaranowski commented on pull request #46: Bump maven-plugins from 36 to 37
slawekjaranowski commented on PR #46: URL: https://github.com/apache/maven-jar-plugin/pull/46#issuecomment-1225965995 @dependabot rebase -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MJAR-291) Upgrade Parent to 37
[ https://issues.apache.org/jira/browse/MJAR-291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584362#comment-17584362 ] Hudson commented on MJAR-291: - Build succeeded in Jenkins: Maven » Maven TLP » maven-jar-plugin » master #23 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-jar-plugin/job/master/23/ > Upgrade Parent to 37 > > > Key: MJAR-291 > URL: https://issues.apache.org/jira/browse/MJAR-291 > Project: Maven JAR Plugin > Issue Type: Dependency upgrade >Reporter: Jorge Solórzano >Assignee: Slawomir Jaranowski >Priority: Trivial > Fix For: 3.3.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-jar-plugin] dependabot[bot] commented on pull request #46: Bump maven-plugins from 36 to 37
dependabot[bot] commented on PR #46: URL: https://github.com/apache/maven-jar-plugin/pull/46#issuecomment-1225966810 Looks like org.apache.maven.plugins:maven-plugins is up-to-date now, so this is no longer needed. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-jar-plugin] dependabot[bot] closed pull request #46: Bump maven-plugins from 36 to 37
dependabot[bot] closed pull request #46: Bump maven-plugins from 36 to 37 URL: https://github.com/apache/maven-jar-plugin/pull/46 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MPMD-353) An API incompatibility was encountered while executing org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd
[
https://issues.apache.org/jira/browse/MPMD-353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584364#comment-17584364
]
Michael Osipov commented on MPMD-353:
-
I will check again.
> An API incompatibility was encountered while executing
> org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd
> ---
>
> Key: MPMD-353
> URL: https://issues.apache.org/jira/browse/MPMD-353
> Project: Maven PMD Plugin
> Issue Type: Bug
> Components: PMD
>Affects Versions: 3.18.0
>Reporter: Piotr Zygielo
>Priority: Major
>
> {code:bash}
> Error: Failed to execute goal
> org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd (pmd) on project
> UnnecessaryFullyQualifiedName: Execution pmd of goal
> org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd failed: An API
> incompatibility was encountered while executing
> org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd:
> java.lang.NoSuchMethodError:
> org.fusesource.jansi.AnsiConsole.out()Lorg/fusesource/jansi/AnsiPrintStream;
> Error: -
> Error: realm = plugin>org.apache.maven.plugins:maven-pmd-plugin:3.18.0
> Error: strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> Error: urls[0] =
> file:/home/runner/.m2/repository/org/apache/maven/plugins/maven-pmd-plugin/3.18.0/maven-pmd-plugin-3.18.0.jar
> Error: urls[1] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-core/6.48.0/pmd-core-6.48.0.jar
> Error: urls[2] =
> file:/home/runner/.m2/repository/org/antlr/antlr4-runtime/4.7.2/antlr4-runtime-4.7.2.jar
> Error: urls[3] =
> file:/home/runner/.m2/repository/com/beust/jcommander/1.48/jcommander-1.48.jar
> Error: urls[4] =
> file:/home/runner/.m2/repository/net/sourceforge/saxon/saxon/9.1.0.8/saxon-9.1.0.8.jar
> Error: urls[5] =
> file:/home/runner/.m2/repository/org/ow2/asm/asm/9.3/asm-9.3.jar
> Error: urls[6] =
> file:/home/runner/.m2/repository/com/google/code/gson/gson/2.8.9/gson-2.8.9.jar
> Error: urls[7] =
> file:/home/runner/.m2/repository/net/sourceforge/saxon/saxon/9.1.0.8/saxon-9.1.0.8-dom.jar
> Error: urls[8] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-java/6.48.0/pmd-java-6.48.0.jar
> Error: urls[9] =
> file:/home/runner/.m2/repository/org/apache/maven/shared/maven-artifact-transfer/0.13.1/maven-artifact-transfer-0.13.1.jar
> Error: urls[10] =
> file:/home/runner/.m2/repository/org/sonatype/aether/aether-util/1.7/aether-util-1.7.jar
> Error: urls[11] =
> file:/home/runner/.m2/repository/org/sonatype/sisu/sisu-inject-bean/1.4.2/sisu-inject-bean-1.4.2.jar
> Error: urls[12] =
> file:/home/runner/.m2/repository/org/sonatype/sisu/sisu-guice/2.1.7/sisu-guice-2.1.7-noaop.jar
> Error: urls[13] =
> file:/home/runner/.m2/repository/org/codehaus/plexus/plexus-interpolation/1.14/plexus-interpolation-1.14.jar
> Error: urls[14] =
> file:/home/runner/.m2/repository/org/sonatype/plexus/plexus-sec-dispatcher/1.3/plexus-sec-dispatcher-1.3.jar
> Error: urls[15] =
> file:/home/runner/.m2/repository/org/sonatype/plexus/plexus-cipher/1.4/plexus-cipher-1.4.jar
> Error: urls[16] =
> file:/home/runner/.m2/repository/org/codehaus/plexus/plexus-component-annotations/2.1.1/plexus-component-annotations-2.1.1.jar
> Error: urls[17] =
> file:/home/runner/.m2/repository/org/apache/maven/shared/maven-common-artifact-filters/3.3.1/maven-common-artifact-filters-3.3.1.jar
> Error: urls[18] =
> file:/home/runner/.m2/repository/commons-io/commons-io/2.11.0/commons-io-2.11.0.jar
> Error: urls[19] =
> file:/home/runner/.m2/repository/org/apache/commons/commons-lang3/3.12.0/commons-lang3-3.12.0.jar
> Error: urls[20] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-javascript/6.48.0/pmd-javascript-6.48.0.jar
> Error: urls[21] =
> file:/home/runner/.m2/repository/org/mozilla/rhino/1.7.14/rhino-1.7.14.jar
> Error: urls[22] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-jsp/6.48.0/pmd-jsp-6.48.0.jar
> Error: urls[23] =
> file:/home/runner/.m2/repository/org/slf4j/jul-to-slf4j/1.7.36/jul-to-slf4j-1.7.36.jar
> Error: urls[24] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-sink-api/1.11.1/doxia-sink-api-1.11.1.jar
> Error: urls[25] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-logging-api/1.11.1/doxia-logging-api-1.11.1.jar
> Error: urls[26] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-decoration-model/1.11.1/doxia-decoration-model-1.11.1.jar
> Error: urls[27] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-site-renderer/1.11.1/doxia-site-renderer-1.11.1.jar
> Error: urls[28] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-core/1.11.1/doxia-core-1.11.1.jar
> Error: urls[29] =
> file:/home/ru
[GitHub] [maven-pmd-plugin] adangel merged pull request #86: Bump release-drafter/release-drafter from 5.20.0 to 5.20.1
adangel merged PR #86: URL: https://github.com/apache/maven-pmd-plugin/pull/86 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-jar-plugin] jorsol commented on pull request #48: [MJAR-290] - Update Plexus Utils to 3.4.2
jorsol commented on PR #48: URL: https://github.com/apache/maven-jar-plugin/pull/48#issuecomment-1225978954 @slawekjaranowski any comment on this? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Reopened] (MPMD-353) An API incompatibility was encountered while executing org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd
[
https://issues.apache.org/jira/browse/MPMD-353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Slawomir Jaranowski reopened MPMD-353:
--
> An API incompatibility was encountered while executing
> org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd
> ---
>
> Key: MPMD-353
> URL: https://issues.apache.org/jira/browse/MPMD-353
> Project: Maven PMD Plugin
> Issue Type: Bug
> Components: PMD
>Affects Versions: 3.18.0
>Reporter: Piotr Zygielo
>Priority: Major
>
> {code:bash}
> Error: Failed to execute goal
> org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd (pmd) on project
> UnnecessaryFullyQualifiedName: Execution pmd of goal
> org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd failed: An API
> incompatibility was encountered while executing
> org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd:
> java.lang.NoSuchMethodError:
> org.fusesource.jansi.AnsiConsole.out()Lorg/fusesource/jansi/AnsiPrintStream;
> Error: -
> Error: realm = plugin>org.apache.maven.plugins:maven-pmd-plugin:3.18.0
> Error: strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> Error: urls[0] =
> file:/home/runner/.m2/repository/org/apache/maven/plugins/maven-pmd-plugin/3.18.0/maven-pmd-plugin-3.18.0.jar
> Error: urls[1] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-core/6.48.0/pmd-core-6.48.0.jar
> Error: urls[2] =
> file:/home/runner/.m2/repository/org/antlr/antlr4-runtime/4.7.2/antlr4-runtime-4.7.2.jar
> Error: urls[3] =
> file:/home/runner/.m2/repository/com/beust/jcommander/1.48/jcommander-1.48.jar
> Error: urls[4] =
> file:/home/runner/.m2/repository/net/sourceforge/saxon/saxon/9.1.0.8/saxon-9.1.0.8.jar
> Error: urls[5] =
> file:/home/runner/.m2/repository/org/ow2/asm/asm/9.3/asm-9.3.jar
> Error: urls[6] =
> file:/home/runner/.m2/repository/com/google/code/gson/gson/2.8.9/gson-2.8.9.jar
> Error: urls[7] =
> file:/home/runner/.m2/repository/net/sourceforge/saxon/saxon/9.1.0.8/saxon-9.1.0.8-dom.jar
> Error: urls[8] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-java/6.48.0/pmd-java-6.48.0.jar
> Error: urls[9] =
> file:/home/runner/.m2/repository/org/apache/maven/shared/maven-artifact-transfer/0.13.1/maven-artifact-transfer-0.13.1.jar
> Error: urls[10] =
> file:/home/runner/.m2/repository/org/sonatype/aether/aether-util/1.7/aether-util-1.7.jar
> Error: urls[11] =
> file:/home/runner/.m2/repository/org/sonatype/sisu/sisu-inject-bean/1.4.2/sisu-inject-bean-1.4.2.jar
> Error: urls[12] =
> file:/home/runner/.m2/repository/org/sonatype/sisu/sisu-guice/2.1.7/sisu-guice-2.1.7-noaop.jar
> Error: urls[13] =
> file:/home/runner/.m2/repository/org/codehaus/plexus/plexus-interpolation/1.14/plexus-interpolation-1.14.jar
> Error: urls[14] =
> file:/home/runner/.m2/repository/org/sonatype/plexus/plexus-sec-dispatcher/1.3/plexus-sec-dispatcher-1.3.jar
> Error: urls[15] =
> file:/home/runner/.m2/repository/org/sonatype/plexus/plexus-cipher/1.4/plexus-cipher-1.4.jar
> Error: urls[16] =
> file:/home/runner/.m2/repository/org/codehaus/plexus/plexus-component-annotations/2.1.1/plexus-component-annotations-2.1.1.jar
> Error: urls[17] =
> file:/home/runner/.m2/repository/org/apache/maven/shared/maven-common-artifact-filters/3.3.1/maven-common-artifact-filters-3.3.1.jar
> Error: urls[18] =
> file:/home/runner/.m2/repository/commons-io/commons-io/2.11.0/commons-io-2.11.0.jar
> Error: urls[19] =
> file:/home/runner/.m2/repository/org/apache/commons/commons-lang3/3.12.0/commons-lang3-3.12.0.jar
> Error: urls[20] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-javascript/6.48.0/pmd-javascript-6.48.0.jar
> Error: urls[21] =
> file:/home/runner/.m2/repository/org/mozilla/rhino/1.7.14/rhino-1.7.14.jar
> Error: urls[22] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-jsp/6.48.0/pmd-jsp-6.48.0.jar
> Error: urls[23] =
> file:/home/runner/.m2/repository/org/slf4j/jul-to-slf4j/1.7.36/jul-to-slf4j-1.7.36.jar
> Error: urls[24] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-sink-api/1.11.1/doxia-sink-api-1.11.1.jar
> Error: urls[25] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-logging-api/1.11.1/doxia-logging-api-1.11.1.jar
> Error: urls[26] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-decoration-model/1.11.1/doxia-decoration-model-1.11.1.jar
> Error: urls[27] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-site-renderer/1.11.1/doxia-site-renderer-1.11.1.jar
> Error: urls[28] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-core/1.11.1/doxia-core-1.11.1.jar
> Error: urls[29] =
> file:/home/runner/.m2/repository/org/apache/commons/commons-text/1.3/commons-te
[jira] [Commented] (MPMD-353) An API incompatibility was encountered while executing org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd
[
https://issues.apache.org/jira/browse/MPMD-353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584382#comment-17584382
]
Slawomir Jaranowski commented on MPMD-353:
--
Maybe not call method {{MessageUtils.setColorEnabled}} from pmd?
[~adangel] what do you think?
> An API incompatibility was encountered while executing
> org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd
> ---
>
> Key: MPMD-353
> URL: https://issues.apache.org/jira/browse/MPMD-353
> Project: Maven PMD Plugin
> Issue Type: Bug
> Components: PMD
>Affects Versions: 3.18.0
>Reporter: Piotr Zygielo
>Priority: Major
>
> {code:bash}
> Error: Failed to execute goal
> org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd (pmd) on project
> UnnecessaryFullyQualifiedName: Execution pmd of goal
> org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd failed: An API
> incompatibility was encountered while executing
> org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd:
> java.lang.NoSuchMethodError:
> org.fusesource.jansi.AnsiConsole.out()Lorg/fusesource/jansi/AnsiPrintStream;
> Error: -
> Error: realm = plugin>org.apache.maven.plugins:maven-pmd-plugin:3.18.0
> Error: strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> Error: urls[0] =
> file:/home/runner/.m2/repository/org/apache/maven/plugins/maven-pmd-plugin/3.18.0/maven-pmd-plugin-3.18.0.jar
> Error: urls[1] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-core/6.48.0/pmd-core-6.48.0.jar
> Error: urls[2] =
> file:/home/runner/.m2/repository/org/antlr/antlr4-runtime/4.7.2/antlr4-runtime-4.7.2.jar
> Error: urls[3] =
> file:/home/runner/.m2/repository/com/beust/jcommander/1.48/jcommander-1.48.jar
> Error: urls[4] =
> file:/home/runner/.m2/repository/net/sourceforge/saxon/saxon/9.1.0.8/saxon-9.1.0.8.jar
> Error: urls[5] =
> file:/home/runner/.m2/repository/org/ow2/asm/asm/9.3/asm-9.3.jar
> Error: urls[6] =
> file:/home/runner/.m2/repository/com/google/code/gson/gson/2.8.9/gson-2.8.9.jar
> Error: urls[7] =
> file:/home/runner/.m2/repository/net/sourceforge/saxon/saxon/9.1.0.8/saxon-9.1.0.8-dom.jar
> Error: urls[8] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-java/6.48.0/pmd-java-6.48.0.jar
> Error: urls[9] =
> file:/home/runner/.m2/repository/org/apache/maven/shared/maven-artifact-transfer/0.13.1/maven-artifact-transfer-0.13.1.jar
> Error: urls[10] =
> file:/home/runner/.m2/repository/org/sonatype/aether/aether-util/1.7/aether-util-1.7.jar
> Error: urls[11] =
> file:/home/runner/.m2/repository/org/sonatype/sisu/sisu-inject-bean/1.4.2/sisu-inject-bean-1.4.2.jar
> Error: urls[12] =
> file:/home/runner/.m2/repository/org/sonatype/sisu/sisu-guice/2.1.7/sisu-guice-2.1.7-noaop.jar
> Error: urls[13] =
> file:/home/runner/.m2/repository/org/codehaus/plexus/plexus-interpolation/1.14/plexus-interpolation-1.14.jar
> Error: urls[14] =
> file:/home/runner/.m2/repository/org/sonatype/plexus/plexus-sec-dispatcher/1.3/plexus-sec-dispatcher-1.3.jar
> Error: urls[15] =
> file:/home/runner/.m2/repository/org/sonatype/plexus/plexus-cipher/1.4/plexus-cipher-1.4.jar
> Error: urls[16] =
> file:/home/runner/.m2/repository/org/codehaus/plexus/plexus-component-annotations/2.1.1/plexus-component-annotations-2.1.1.jar
> Error: urls[17] =
> file:/home/runner/.m2/repository/org/apache/maven/shared/maven-common-artifact-filters/3.3.1/maven-common-artifact-filters-3.3.1.jar
> Error: urls[18] =
> file:/home/runner/.m2/repository/commons-io/commons-io/2.11.0/commons-io-2.11.0.jar
> Error: urls[19] =
> file:/home/runner/.m2/repository/org/apache/commons/commons-lang3/3.12.0/commons-lang3-3.12.0.jar
> Error: urls[20] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-javascript/6.48.0/pmd-javascript-6.48.0.jar
> Error: urls[21] =
> file:/home/runner/.m2/repository/org/mozilla/rhino/1.7.14/rhino-1.7.14.jar
> Error: urls[22] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-jsp/6.48.0/pmd-jsp-6.48.0.jar
> Error: urls[23] =
> file:/home/runner/.m2/repository/org/slf4j/jul-to-slf4j/1.7.36/jul-to-slf4j-1.7.36.jar
> Error: urls[24] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-sink-api/1.11.1/doxia-sink-api-1.11.1.jar
> Error: urls[25] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-logging-api/1.11.1/doxia-logging-api-1.11.1.jar
> Error: urls[26] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-decoration-model/1.11.1/doxia-decoration-model-1.11.1.jar
> Error: urls[27] =
> file:/home/runner/.m2/repository/org/apache/maven/doxia/doxia-site-renderer/1.11.1/doxia-site-renderer-1.11.1.jar
> Error: urls[28] =
> file:/home/runner/.m2/repository/org/apache
[GitHub] [maven] slawekjaranowski commented on a diff in pull request #703: New API with immutable model
slawekjaranowski commented on code in PR #703: URL: https://github.com/apache/maven/pull/703#discussion_r954070936 ## api/maven-api-core/src/main/java/org/apache/maven/api/plugin/Log.java: ## @@ -0,0 +1,166 @@ +package org.apache.maven.api.plugin; + +/* + * Licensed to the Apache Software Foundation (ASF) under one + * or more contributor license agreements. See the NOTICE file + * distributed with this work for additional information + * regarding copyright ownership. The ASF licenses this file + * to you under the Apache License, Version 2.0 (the + * "License"); you may not use this file except in compliance + * with the License. You may obtain a copy of the License at + * + * http://www.apache.org/licenses/LICENSE-2.0 + * + * Unless required by applicable law or agreed to in writing, + * software distributed under the License is distributed on an + * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY + * KIND, either express or implied. See the License for the + * specific language governing permissions and limitations + * under the License. + */ + +import java.util.function.Supplier; + +/** + * This interface supplies the API for providing feedback to the user from the Mojo, using standard + * Maven channels. + * There should be no big surprises here, although you may notice that the methods accept + * java.lang.CharSequence rather than java.lang.String. This is provided mainly as a + * convenience, to enable developers to pass things like java.lang.StringBuffer directly into the logger, + * rather than formatting first by calling toString(). + */ +public interface Log Review Comment: What do you think about stuff of colorized messages from: https://maven.apache.org/shared/maven-shared-utils/apidocs/org/apache/maven/shared/utils/logging/MessageBuilder.html -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-jar-plugin] slawekjaranowski merged pull request #48: [MJAR-290] - Update Plexus Utils to 3.4.2
slawekjaranowski merged PR #48: URL: https://github.com/apache/maven-jar-plugin/pull/48 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Closed] (MJAR-290) Update Plexus Utils to 3.4.2
[ https://issues.apache.org/jira/browse/MJAR-290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Slawomir Jaranowski closed MJAR-290. Fix Version/s: 3.3.0 Assignee: Slawomir Jaranowski Resolution: Fixed > Update Plexus Utils to 3.4.2 > > > Key: MJAR-290 > URL: https://issues.apache.org/jira/browse/MJAR-290 > Project: Maven JAR Plugin > Issue Type: Dependency upgrade >Reporter: Jorge Solórzano >Assignee: Slawomir Jaranowski >Priority: Major > Labels: pull-request-available > Fix For: 3.3.0 > > > The current master branch pulls plexus-utils:jar:3.3.0 from > maven-core:jar:3.2.5. > Since Maven Jar Plugin moved to Java 8, we can use plexus-utils:jar:3.4.2 > that is already used in maven-archiver:jar:3.6.0. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MJAR-290) Update Plexus Utils to 3.4.2
[ https://issues.apache.org/jira/browse/MJAR-290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584384#comment-17584384 ] Hudson commented on MJAR-290: - Build succeeded in Jenkins: Maven » Maven TLP » maven-jar-plugin » master #24 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-jar-plugin/job/master/24/ > Update Plexus Utils to 3.4.2 > > > Key: MJAR-290 > URL: https://issues.apache.org/jira/browse/MJAR-290 > Project: Maven JAR Plugin > Issue Type: Dependency upgrade >Reporter: Jorge Solórzano >Assignee: Slawomir Jaranowski >Priority: Major > Labels: pull-request-available > Fix For: 3.3.0 > > > The current master branch pulls plexus-utils:jar:3.3.0 from > maven-core:jar:3.2.5. > Since Maven Jar Plugin moved to Java 8, we can use plexus-utils:jar:3.4.2 > that is already used in maven-archiver:jar:3.6.0. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7530) Upgrade Apache Maven parent POM to version 37
[ https://issues.apache.org/jira/browse/MNG-7530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584385#comment-17584385 ] ASF GitHub Bot commented on MNG-7530: - slawekjaranowski merged PR #792: URL: https://github.com/apache/maven/pull/792 > Upgrade Apache Maven parent POM to version 37 > - > > Key: MNG-7530 > URL: https://issues.apache.org/jira/browse/MNG-7530 > Project: Maven > Issue Type: Task >Reporter: Sylwester Lachiewicz >Assignee: Slawomir Jaranowski >Priority: Minor > Fix For: 3.9.0-candidate > > > Upgrade from maven-parent 36 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MNG-7530) Upgrade Apache Maven parent POM to version 37
[ https://issues.apache.org/jira/browse/MNG-7530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Slawomir Jaranowski updated MNG-7530: - Fix Version/s: 4.0.0 > Upgrade Apache Maven parent POM to version 37 > - > > Key: MNG-7530 > URL: https://issues.apache.org/jira/browse/MNG-7530 > Project: Maven > Issue Type: Task >Reporter: Sylwester Lachiewicz >Assignee: Slawomir Jaranowski >Priority: Minor > Fix For: 3.9.0-candidate, 4.0.0 > > > Upgrade from maven-parent 36 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven] slawekjaranowski merged pull request #792: [MNG-7530] Upgrade Apache Maven parent POM to version 37
slawekjaranowski merged PR #792: URL: https://github.com/apache/maven/pull/792 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (MNG-7530) Upgrade Apache Maven parent POM to version 37
[ https://issues.apache.org/jira/browse/MNG-7530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Slawomir Jaranowski updated MNG-7530: - Fix Version/s: 4.0.0-alpha-1 > Upgrade Apache Maven parent POM to version 37 > - > > Key: MNG-7530 > URL: https://issues.apache.org/jira/browse/MNG-7530 > Project: Maven > Issue Type: Task >Reporter: Sylwester Lachiewicz >Assignee: Slawomir Jaranowski >Priority: Minor > Fix For: 3.9.0-candidate, 4.0.0-alpha-1, 4.0.0 > > > Upgrade from maven-parent 36 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7353) Add support for "mvn pluginPrefix:version:goal"
[
https://issues.apache.org/jira/browse/MNG-7353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584407#comment-17584407
]
Hudson commented on MNG-7353:
-
Build succeeded in Jenkins: Maven » Maven TLP » maven » master #82
See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/master/82/
> Add support for "mvn pluginPrefix:version:goal"
> ---
>
> Key: MNG-7353
> URL: https://issues.apache.org/jira/browse/MNG-7353
> Project: Maven
> Issue Type: New Feature
> Components: Command Line
>Affects Versions: 3.8.4
>Reporter: Herve Boutemy
>Assignee: Herve Boutemy
>Priority: Major
> Fix For: 3.9.0, 4.0.0-alpha-1, 4.0.0
>
>
> currently, we can run a simplified 2 parts form {noformat}mvn
> wrapper:wrapper{noformat}
> but if we want to specify a version, we need to switch to full 4 prts form:
> {noformat}mvn
> org.apache.maven.plugins:maven-wrapper-plugin:3.1.0-SNAPSHOT:wrapper{noformat}
> it would be nice to be able to write 3 parts simplified {noformat}mvn
> wrapper:3.1.0-SNAPSHOT:wrapper{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-7530) Upgrade Apache Maven parent POM to version 37
[ https://issues.apache.org/jira/browse/MNG-7530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584406#comment-17584406 ] Hudson commented on MNG-7530: - Build succeeded in Jenkins: Maven » Maven TLP » maven » master #82 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/master/82/ > Upgrade Apache Maven parent POM to version 37 > - > > Key: MNG-7530 > URL: https://issues.apache.org/jira/browse/MNG-7530 > Project: Maven > Issue Type: Task >Reporter: Sylwester Lachiewicz >Assignee: Slawomir Jaranowski >Priority: Minor > Fix For: 3.9.0-candidate, 4.0.0-alpha-1, 4.0.0 > > > Upgrade from maven-parent 36 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MPMD-353) An API incompatibility was encountered while executing org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd
[
https://issues.apache.org/jira/browse/MPMD-353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584412#comment-17584412
]
Andreas Dangel commented on MPMD-353:
-
I added that in case PMD is executed via toolchain - then it's executed in a
separate process and I tried to setup the logging as before. Not calling
{{MessageUtils.setColorEnabled}} would only result in monochrome log output
when running PMD with a configured toolchain... only an aesthetic issue.
The problem appears only with maven 3.6.3 - this ships with jansi 1.17.1.
Maven Shared Utils 3.3.4 is compiled against jansi 2.2.0 (as an optional
dependency).
Would it be an option to catch this MethodNotFoundError and ignore it? As
described above, it should only have the effect, that logging from PMD might be
monochrome - but would only affect maven 3.6.x users...
> An API incompatibility was encountered while executing
> org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd
> ---
>
> Key: MPMD-353
> URL: https://issues.apache.org/jira/browse/MPMD-353
> Project: Maven PMD Plugin
> Issue Type: Bug
> Components: PMD
>Affects Versions: 3.18.0
>Reporter: Piotr Zygielo
>Priority: Major
>
> {code:bash}
> Error: Failed to execute goal
> org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd (pmd) on project
> UnnecessaryFullyQualifiedName: Execution pmd of goal
> org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd failed: An API
> incompatibility was encountered while executing
> org.apache.maven.plugins:maven-pmd-plugin:3.18.0:pmd:
> java.lang.NoSuchMethodError:
> org.fusesource.jansi.AnsiConsole.out()Lorg/fusesource/jansi/AnsiPrintStream;
> Error: -
> Error: realm = plugin>org.apache.maven.plugins:maven-pmd-plugin:3.18.0
> Error: strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> Error: urls[0] =
> file:/home/runner/.m2/repository/org/apache/maven/plugins/maven-pmd-plugin/3.18.0/maven-pmd-plugin-3.18.0.jar
> Error: urls[1] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-core/6.48.0/pmd-core-6.48.0.jar
> Error: urls[2] =
> file:/home/runner/.m2/repository/org/antlr/antlr4-runtime/4.7.2/antlr4-runtime-4.7.2.jar
> Error: urls[3] =
> file:/home/runner/.m2/repository/com/beust/jcommander/1.48/jcommander-1.48.jar
> Error: urls[4] =
> file:/home/runner/.m2/repository/net/sourceforge/saxon/saxon/9.1.0.8/saxon-9.1.0.8.jar
> Error: urls[5] =
> file:/home/runner/.m2/repository/org/ow2/asm/asm/9.3/asm-9.3.jar
> Error: urls[6] =
> file:/home/runner/.m2/repository/com/google/code/gson/gson/2.8.9/gson-2.8.9.jar
> Error: urls[7] =
> file:/home/runner/.m2/repository/net/sourceforge/saxon/saxon/9.1.0.8/saxon-9.1.0.8-dom.jar
> Error: urls[8] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-java/6.48.0/pmd-java-6.48.0.jar
> Error: urls[9] =
> file:/home/runner/.m2/repository/org/apache/maven/shared/maven-artifact-transfer/0.13.1/maven-artifact-transfer-0.13.1.jar
> Error: urls[10] =
> file:/home/runner/.m2/repository/org/sonatype/aether/aether-util/1.7/aether-util-1.7.jar
> Error: urls[11] =
> file:/home/runner/.m2/repository/org/sonatype/sisu/sisu-inject-bean/1.4.2/sisu-inject-bean-1.4.2.jar
> Error: urls[12] =
> file:/home/runner/.m2/repository/org/sonatype/sisu/sisu-guice/2.1.7/sisu-guice-2.1.7-noaop.jar
> Error: urls[13] =
> file:/home/runner/.m2/repository/org/codehaus/plexus/plexus-interpolation/1.14/plexus-interpolation-1.14.jar
> Error: urls[14] =
> file:/home/runner/.m2/repository/org/sonatype/plexus/plexus-sec-dispatcher/1.3/plexus-sec-dispatcher-1.3.jar
> Error: urls[15] =
> file:/home/runner/.m2/repository/org/sonatype/plexus/plexus-cipher/1.4/plexus-cipher-1.4.jar
> Error: urls[16] =
> file:/home/runner/.m2/repository/org/codehaus/plexus/plexus-component-annotations/2.1.1/plexus-component-annotations-2.1.1.jar
> Error: urls[17] =
> file:/home/runner/.m2/repository/org/apache/maven/shared/maven-common-artifact-filters/3.3.1/maven-common-artifact-filters-3.3.1.jar
> Error: urls[18] =
> file:/home/runner/.m2/repository/commons-io/commons-io/2.11.0/commons-io-2.11.0.jar
> Error: urls[19] =
> file:/home/runner/.m2/repository/org/apache/commons/commons-lang3/3.12.0/commons-lang3-3.12.0.jar
> Error: urls[20] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-javascript/6.48.0/pmd-javascript-6.48.0.jar
> Error: urls[21] =
> file:/home/runner/.m2/repository/org/mozilla/rhino/1.7.14/rhino-1.7.14.jar
> Error: urls[22] =
> file:/home/runner/.m2/repository/net/sourceforge/pmd/pmd-jsp/6.48.0/pmd-jsp-6.48.0.jar
> Error: urls[23] =
> file:/home/runner/.m2/repository/org/slf4j/jul-to-slf4j/1.7.36/jul-to-slf4j-1.7.36.jar
> Error: urls[24] =
> file:/home/run
[GitHub] [maven-wrapper] timtebeek opened a new pull request, #61: Switch to JUnit Jupiter
timtebeek opened a new pull request, #61: URL: https://github.com/apache/maven-wrapper/pull/61 Via mvn -U org.openrewrite.maven:rewrite-maven-plugin:4.32.0:run -Drewrite.recipeArtifactCoordinates=org.openrewrite.recipe:rewrite-testing-frameworks:1.26.1 -DactiveRecipes=org.openrewrite.java.testing.junit5.JUnit5BestPractices - [x] I hereby declare this contribution to be licenced under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-wrapper] jorsol commented on pull request #61: Switch to JUnit Jupiter
jorsol commented on PR #61: URL: https://github.com/apache/maven-wrapper/pull/61#issuecomment-1226111255 This project uses Java 7, so I expect that this will not be compatible. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-wrapper] timtebeek commented on pull request #61: Switch to JUnit Jupiter
timtebeek commented on PR #61: URL: https://github.com/apache/maven-wrapper/pull/61#issuecomment-1226115339 > This project uses Java 7, so I expect that this will not be compatible. Ah hadn't thought of that; [you're right](https://junit.org/junit5/docs/current/user-guide/#overview-java-versions). > JUnit 5 requires Java 8 (or higher) at runtime. However, you can still test code that has been compiled with previous versions of the JDK. Unless we want to bring in toolchains to [test on a different Java version](https://vladmihalcea.com/different-java-main-test-maven/), I guess this is blocked for now. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven] rmannibucau commented on a diff in pull request #703: New API with immutable model
rmannibucau commented on code in PR #703: URL: https://github.com/apache/maven/pull/703#discussion_r954217444 ## api/maven-api-core/src/main/java/org/apache/maven/api/plugin/Log.java: ## @@ -0,0 +1,166 @@ +package org.apache.maven.api.plugin; + +/* + * Licensed to the Apache Software Foundation (ASF) under one + * or more contributor license agreements. See the NOTICE file + * distributed with this work for additional information + * regarding copyright ownership. The ASF licenses this file + * to you under the Apache License, Version 2.0 (the + * "License"); you may not use this file except in compliance + * with the License. You may obtain a copy of the License at + * + * http://www.apache.org/licenses/LICENSE-2.0 + * + * Unless required by applicable law or agreed to in writing, + * software distributed under the License is distributed on an + * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY + * KIND, either express or implied. See the License for the + * specific language governing permissions and limitations + * under the License. + */ + +import java.util.function.Supplier; + +/** + * This interface supplies the API for providing feedback to the user from the Mojo, using standard + * Maven channels. + * There should be no big surprises here, although you may notice that the methods accept + * java.lang.CharSequence rather than java.lang.String. This is provided mainly as a + * convenience, to enable developers to pass things like java.lang.StringBuffer directly into the logger, + * rather than formatting first by calling toString(). + */ +public interface Log Review Comment: What about enhancing it after this one is merged (and before it rewrites all maven code in branches ;)) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-wrapper] timtebeek commented on pull request #61: Switch to JUnit Jupiter
timtebeek commented on PR #61: URL: https://github.com/apache/maven-wrapper/pull/61#issuecomment-1226322968 Good suggestion; applied just now, although it's not immediately clear to me whether this has any chance of getting merged (soon-ish), and/or what would be required to get it in a mergeable state. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven] gnodet commented on a diff in pull request #703: New API with immutable model
gnodet commented on code in PR #703: URL: https://github.com/apache/maven/pull/703#discussion_r954328145 ## api/maven-api-core/src/main/java/org/apache/maven/api/plugin/Log.java: ## @@ -0,0 +1,166 @@ +package org.apache.maven.api.plugin; + +/* + * Licensed to the Apache Software Foundation (ASF) under one + * or more contributor license agreements. See the NOTICE file + * distributed with this work for additional information + * regarding copyright ownership. The ASF licenses this file + * to you under the Apache License, Version 2.0 (the + * "License"); you may not use this file except in compliance + * with the License. You may obtain a copy of the License at + * + * http://www.apache.org/licenses/LICENSE-2.0 + * + * Unless required by applicable law or agreed to in writing, + * software distributed under the License is distributed on an + * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY + * KIND, either express or implied. See the License for the + * specific language governing permissions and limitations + * under the License. + */ + +import java.util.function.Supplier; + +/** + * This interface supplies the API for providing feedback to the user from the Mojo, using standard + * Maven channels. + * There should be no big surprises here, although you may notice that the methods accept + * java.lang.CharSequence rather than java.lang.String. This is provided mainly as a + * convenience, to enable developers to pass things like java.lang.StringBuffer directly into the logger, + * rather than formatting first by calling toString(). + */ +public interface Log Review Comment: A [`MessageBuilderFactory`](https://github.com/apache/maven/blob/bf4995e7f4c8ae473b441539824bf3712f82a553/api/maven-api-core/src/main/java/org/apache/maven/api/services/MessageBuilderFactory.java) is available from the `Session` to support those use cases. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven] slawekjaranowski opened a new pull request, #794: [MNG-7530] Upgrade Apache Maven parent POM to version 37
slawekjaranowski opened a new pull request, #794: URL: https://github.com/apache/maven/pull/794 (cherry picked from commit 750e1e3e71194644acda437cefbd73c8bd408f5d) Following this checklist to help us incorporate your contribution quickly and easily: - [x] Make sure there is a [JIRA issue](https://issues.apache.org/jira/browse/MNG) filed for the change (usually before you start working on it). Trivial changes like typos do not require a JIRA issue. Your pull request should address just this issue, without pulling in other changes. - [x] Each commit in the pull request should have a meaningful subject line and body. - [x] Format the pull request title like `[MNG-XXX] SUMMARY`, where you replace `MNG-XXX` and `SUMMARY` with the appropriate JIRA issue. Best practice is to use the JIRA issue title in the pull request title and in the first line of the commit message. - [ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why. - [x] Run `mvn clean verify` to make sure basic checks pass. A more thorough check will be performed on your pull request automatically. - [x] You have run the [Core IT][core-its] successfully. If your pull request is about ~20 lines of code you don't need to sign an [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf) if you are unsure please ask on the developers list. To make clear that you license your contribution under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0) you have to acknowledge this by using the following check-box. - [x] I hereby declare this contribution to be licenced under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0) - [x] In any other case, please file an [Apache Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf). [core-its]: https://maven.apache.org/core-its/core-it-suite/ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MNG-7530) Upgrade Apache Maven parent POM to version 37
[ https://issues.apache.org/jira/browse/MNG-7530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584482#comment-17584482 ] ASF GitHub Bot commented on MNG-7530: - slawekjaranowski opened a new pull request, #794: URL: https://github.com/apache/maven/pull/794 (cherry picked from commit 750e1e3e71194644acda437cefbd73c8bd408f5d) Following this checklist to help us incorporate your contribution quickly and easily: - [x] Make sure there is a [JIRA issue](https://issues.apache.org/jira/browse/MNG) filed for the change (usually before you start working on it). Trivial changes like typos do not require a JIRA issue. Your pull request should address just this issue, without pulling in other changes. - [x] Each commit in the pull request should have a meaningful subject line and body. - [x] Format the pull request title like `[MNG-XXX] SUMMARY`, where you replace `MNG-XXX` and `SUMMARY` with the appropriate JIRA issue. Best practice is to use the JIRA issue title in the pull request title and in the first line of the commit message. - [ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why. - [x] Run `mvn clean verify` to make sure basic checks pass. A more thorough check will be performed on your pull request automatically. - [x] You have run the [Core IT][core-its] successfully. If your pull request is about ~20 lines of code you don't need to sign an [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf) if you are unsure please ask on the developers list. To make clear that you license your contribution under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0) you have to acknowledge this by using the following check-box. - [x] I hereby declare this contribution to be licenced under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0) - [x] In any other case, please file an [Apache Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf). [core-its]: https://maven.apache.org/core-its/core-it-suite/ > Upgrade Apache Maven parent POM to version 37 > - > > Key: MNG-7530 > URL: https://issues.apache.org/jira/browse/MNG-7530 > Project: Maven > Issue Type: Task >Reporter: Sylwester Lachiewicz >Assignee: Slawomir Jaranowski >Priority: Minor > Fix For: 3.9.0-candidate, 4.0.0-alpha-1, 4.0.0 > > > Upgrade from maven-parent 36 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7527) Resolving inter-module dependencies does not work like expected
[
https://issues.apache.org/jira/browse/MNG-7527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584528#comment-17584528
]
Andrey Panfilov commented on MNG-7527:
--
[~mthmulders]
The purpose of demo project provided is to demonstrate the issue: maven fails
to discover packaged supplemental artifacts while they do exist in project
workspace. Adding sources doesn't make sense: maven still fails to discover
packaged supplemental artifacts however in that case in returns output
directory instead of the packaged artifact, that might be helpful for
compiling, but totally unusable for other scenarios.
> Resolving inter-module dependencies does not work like expected
> ---
>
> Key: MNG-7527
> URL: https://issues.apache.org/jira/browse/MNG-7527
> Project: Maven
> Issue Type: Bug
> Components: Core
>Affects Versions: 4.0.0-alpha-1
>Reporter: Andrey Panfilov
>Assignee: Maarten Mulders
>Priority: Major
> Attachments: MNG-7527.zip
>
>
> After resolving MNG-4660 ReactorReader picks up packaged main artifact only
> and ignores supplemental artifacts:
>
>
> {code:java}
> private Artifact findMatchingArtifact( MavenProject project, Artifact
> requestedArtifact )
> {
> String requestedRepositoryConflictId = ArtifactIdUtils.toVersionlessId(
> requestedArtifact );
> Artifact mainArtifact = RepositoryUtils.toArtifact( project.getArtifact()
> );
> if ( requestedRepositoryConflictId.equals(
> ArtifactIdUtils.toVersionlessId( mainArtifact ) ) )
> {
> return mainArtifact;
> }
>
> /*
> * if module is not a part of "build reactor",
> project.getAttachedArtifacts() always
> * returns empty list, it seems that it is plugins' responsibility to
> populate attached artifacts
> * however it seems no corresponding API has been introduced, which would
> allow to gather information
> * about supplemental artifacts without building module
> */
> return RepositoryUtils.toArtifacts( project.getAttachedArtifacts()
> ).stream()
> .filter( isRequestedArtifact( requestedArtifact ) )
> .findFirst()
> .orElse( null );
> } {code}
>
>
> {code:java}
> private File determinePreviouslyPackagedArtifactFile( MavenProject project,
> Artifact artifact )
> {
> if ( artifact == null )
>
> { return null; }
> /*
> * the implementation/signature of this method looks bit confusing: it
> accepts any artifact descriptor
> * but returns main artifact only, I do believe in some cases (if
> supplemental artifact got discovered)
> * it may return wrong file
> */
> String fileName = String.format( "%s.%s",
> project.getBuild().getFinalName(), artifact.getExtension() );
> return new File( project.getBuild().getDirectory(), fileName );
> } {code}
>
> That new behaviour causes following issues:
> * if extension of main artifact differs from classifier's (e.g. war/classes)
> ReactorReader fails to pick up artifact (gh link to demo project:
> [https://github.com/andreybpanfilov/MNG-7527])
> * if extension of main artifact does not differ from classifier's
> ReactorReader picks up wrong artifact
>
> I have discovered another issue - the `mvn package clean package` command
> might look insane, however, I do believe it reveals there are some issues
> with internal state of artifacts/dependencies:
>
> {code:java}
> MNG-7527 % ~/app/maven/4.0/bin/mvn package clean package -f mng7527-dep2
> [INFO] Building jar:
> MNG-7527/mng7527-dep2/target/mng7527-dep2-0.0.1-SNAPSHOT.jar
> [INFO]
> --
> [INFO] BUILD FAILURE
> [INFO]
> --
> [INFO] Total time: 1.063 s
> [INFO] Finished at: 2022-08-08T21:05:18+10:00
> [INFO]
> --
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-jar-plugin:3.2.0:jar (default-jar) on project
> mng7527-dep2: You have to use a classifier to attach supplemental artifacts
> to the project instead of replacing them. -> [Help 1]
> [ERROR] {code}
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[GitHub] [maven] hgschmie merged pull request #787: [MNG-7529] Maven resolver makes bad repository choices
hgschmie merged PR #787: URL: https://github.com/apache/maven/pull/787 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven] hgschmie merged pull request #786: [MNG-7529] Maven resolver makes bad repository choices
hgschmie merged PR #786: URL: https://github.com/apache/maven/pull/786 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MNG-7529) Maven resolver makes bad repository choices when resolving version ranges
[ https://issues.apache.org/jira/browse/MNG-7529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584595#comment-17584595 ] ASF GitHub Bot commented on MNG-7529: - hgschmie merged PR #787: URL: https://github.com/apache/maven/pull/787 > Maven resolver makes bad repository choices when resolving version ranges > - > > Key: MNG-7529 > URL: https://issues.apache.org/jira/browse/MNG-7529 > Project: Maven > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 3.8.6 >Reporter: Henning Schmiedehausen >Priority: Major > Fix For: 3.8.x-candidate > > > This is the same problem as MRESOLVER-270. The problem is actually in the > maven core, not in the resolver. See the description there. > > This bug is a placeholder for the fix PR. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7529) Maven resolver makes bad repository choices when resolving version ranges
[ https://issues.apache.org/jira/browse/MNG-7529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584596#comment-17584596 ] ASF GitHub Bot commented on MNG-7529: - hgschmie merged PR #786: URL: https://github.com/apache/maven/pull/786 > Maven resolver makes bad repository choices when resolving version ranges > - > > Key: MNG-7529 > URL: https://issues.apache.org/jira/browse/MNG-7529 > Project: Maven > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 3.8.6 >Reporter: Henning Schmiedehausen >Priority: Major > Fix For: 3.8.x-candidate > > > This is the same problem as MRESOLVER-270. The problem is actually in the > maven core, not in the resolver. See the description there. > > This bug is a placeholder for the fix PR. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven] michael-o commented on pull request #786: [MNG-7529] Maven resolver makes bad repository choices
michael-o commented on PR #786: URL: https://github.com/apache/maven/pull/786#issuecomment-1226775885 Mmmm, just like that. Shove it in... -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MNG-7529) Maven resolver makes bad repository choices when resolving version ranges
[ https://issues.apache.org/jira/browse/MNG-7529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584608#comment-17584608 ] ASF GitHub Bot commented on MNG-7529: - michael-o commented on PR #786: URL: https://github.com/apache/maven/pull/786#issuecomment-1226775885 Mmmm, just like that. Shove it in... > Maven resolver makes bad repository choices when resolving version ranges > - > > Key: MNG-7529 > URL: https://issues.apache.org/jira/browse/MNG-7529 > Project: Maven > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 3.8.6 >Reporter: Henning Schmiedehausen >Priority: Major > Fix For: 3.8.x-candidate > > > This is the same problem as MRESOLVER-270. The problem is actually in the > maven core, not in the resolver. See the description there. > > This bug is a placeholder for the fix PR. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7529) Maven resolver makes bad repository choices when resolving version ranges
[ https://issues.apache.org/jira/browse/MNG-7529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584609#comment-17584609 ] Hudson commented on MNG-7529: - Build succeeded in Jenkins: Maven » Maven TLP » maven » maven-3.9.x #63 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/maven-3.9.x/63/ > Maven resolver makes bad repository choices when resolving version ranges > - > > Key: MNG-7529 > URL: https://issues.apache.org/jira/browse/MNG-7529 > Project: Maven > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 3.8.6 >Reporter: Henning Schmiedehausen >Priority: Major > Fix For: 3.8.x-candidate > > > This is the same problem as MRESOLVER-270. The problem is actually in the > maven core, not in the resolver. See the description there. > > This bug is a placeholder for the fix PR. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7353) Add support for "mvn pluginPrefix:version:goal"
[
https://issues.apache.org/jira/browse/MNG-7353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584610#comment-17584610
]
Hudson commented on MNG-7353:
-
Build succeeded in Jenkins: Maven » Maven TLP » maven » maven-3.9.x #63
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/maven-3.9.x/63/
> Add support for "mvn pluginPrefix:version:goal"
> ---
>
> Key: MNG-7353
> URL: https://issues.apache.org/jira/browse/MNG-7353
> Project: Maven
> Issue Type: New Feature
> Components: Command Line
>Affects Versions: 3.8.4
>Reporter: Herve Boutemy
>Assignee: Herve Boutemy
>Priority: Major
> Fix For: 3.9.0, 4.0.0-alpha-1, 4.0.0
>
>
> currently, we can run a simplified 2 parts form {noformat}mvn
> wrapper:wrapper{noformat}
> but if we want to specify a version, we need to switch to full 4 prts form:
> {noformat}mvn
> org.apache.maven.plugins:maven-wrapper-plugin:3.1.0-SNAPSHOT:wrapper{noformat}
> it would be nice to be able to write 3 parts simplified {noformat}mvn
> wrapper:3.1.0-SNAPSHOT:wrapper{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-7529) Maven resolver makes bad repository choices when resolving version ranges
[ https://issues.apache.org/jira/browse/MNG-7529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584611#comment-17584611 ] Hudson commented on MNG-7529: - Build succeeded in Jenkins: Maven » Maven TLP » maven » master #83 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/master/83/ > Maven resolver makes bad repository choices when resolving version ranges > - > > Key: MNG-7529 > URL: https://issues.apache.org/jira/browse/MNG-7529 > Project: Maven > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 3.8.6 >Reporter: Henning Schmiedehausen >Priority: Major > Fix For: 3.8.x-candidate > > > This is the same problem as MRESOLVER-270. The problem is actually in the > maven core, not in the resolver. See the description there. > > This bug is a placeholder for the fix PR. -- This message was sent by Atlassian Jira (v8.20.10#820010)
