[GitHub] [maven-plugin-tools] slawekjaranowski commented on pull request #104: Bump plexus-utils from 3.0.2 to 3.0.16 in /maven-plugin-plugin/src/it/fix-maven-since-3.x
slawekjaranowski commented on PR #104: URL: https://github.com/apache/maven-plugin-tools/pull/104#issuecomment-1188640377 @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
[GitHub] [maven-plugin-tools] dependabot[bot] closed pull request #112: Bump plexus-utils from 3.0.1 to 3.0.16 in /maven-plugin-plugin/src/it/mplugin-372-annotation-with-inheritance-from-provided-deps
dependabot[bot] closed pull request #112: Bump plexus-utils from 3.0.1 to 3.0.16 in /maven-plugin-plugin/src/it/mplugin-372-annotation-with-inheritance-from-provided-deps URL: https://github.com/apache/maven-plugin-tools/pull/112 -- 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-plugin-tools] dependabot[bot] commented on pull request #112: Bump plexus-utils from 3.0.1 to 3.0.16 in /maven-plugin-plugin/src/it/mplugin-372-annotation-with-inheritance-from-provide
dependabot[bot] commented on PR #112: URL: https://github.com/apache/maven-plugin-tools/pull/112#issuecomment-1188636088 Looks like org.codehaus.plexus:plexus-utils 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-plugin-tools] dependabot[bot] closed pull request #107: Bump plexus-utils from 3.0.1 to 3.0.16 in /maven-plugin-plugin/src/it/java-basic-annotations
dependabot[bot] closed pull request #107: Bump plexus-utils from 3.0.1 to 3.0.16 in /maven-plugin-plugin/src/it/java-basic-annotations URL: https://github.com/apache/maven-plugin-tools/pull/107 -- 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-plugin-tools] dependabot[bot] closed pull request #115: Bump plexus-utils from 3.0.1 to 3.0.16 in /maven-plugin-plugin/src/it/java-basic-annotations-jdkcurrent
dependabot[bot] closed pull request #115: Bump plexus-utils from 3.0.1 to 3.0.16 in /maven-plugin-plugin/src/it/java-basic-annotations-jdkcurrent URL: https://github.com/apache/maven-plugin-tools/pull/115 -- 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-plugin-tools] dependabot[bot] closed pull request #111: Bump plexus-utils from 3.0.1 to 3.0.16 in /maven-plugin-plugin/src/it/mplugin-299_no-configuration
dependabot[bot] closed pull request #111: Bump plexus-utils from 3.0.1 to 3.0.16 in /maven-plugin-plugin/src/it/mplugin-299_no-configuration URL: https://github.com/apache/maven-plugin-tools/pull/111 -- 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-plugin-tools] dependabot[bot] closed pull request #109: Bump plexus-utils from 3.0.1 to 3.0.16 in /maven-plugin-plugin/src/it/help-package
dependabot[bot] closed pull request #109: Bump plexus-utils from 3.0.1 to 3.0.16 in /maven-plugin-plugin/src/it/help-package URL: https://github.com/apache/maven-plugin-tools/pull/109 -- 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-plugin-tools] dependabot[bot] closed pull request #105: Bump plexus-utils from 3.0.1 to 3.0.16 in /maven-plugin-plugin/src/it/help-basic
dependabot[bot] closed pull request #105: Bump plexus-utils from 3.0.1 to 3.0.16 in /maven-plugin-plugin/src/it/help-basic URL: https://github.com/apache/maven-plugin-tools/pull/105 -- 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-plugin-tools] dependabot[bot] closed pull request #110: Bump plexus-utils from 3.0.1 to 3.0.16 in /maven-plugin-plugin/src/it/help-basic-jdk11
dependabot[bot] closed pull request #110: Bump plexus-utils from 3.0.1 to 3.0.16 in /maven-plugin-plugin/src/it/help-basic-jdk11 URL: https://github.com/apache/maven-plugin-tools/pull/110 -- 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-plugin-tools] dependabot[bot] commented on pull request #107: Bump plexus-utils from 3.0.1 to 3.0.16 in /maven-plugin-plugin/src/it/java-basic-annotations
dependabot[bot] commented on PR #107: URL: https://github.com/apache/maven-plugin-tools/pull/107#issuecomment-1188636065 Looks like org.codehaus.plexus:plexus-utils 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-plugin-tools] dependabot[bot] commented on pull request #115: Bump plexus-utils from 3.0.1 to 3.0.16 in /maven-plugin-plugin/src/it/java-basic-annotations-jdkcurrent
dependabot[bot] commented on PR #115: URL: https://github.com/apache/maven-plugin-tools/pull/115#issuecomment-1188636058 Looks like org.codehaus.plexus:plexus-utils 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-plugin-tools] dependabot[bot] closed pull request #108: Bump plexus-utils from 3.0.1 to 3.0.16 in /maven-plugin-plugin/src/it/packaging-jar
dependabot[bot] closed pull request #108: Bump plexus-utils from 3.0.1 to 3.0.16 in /maven-plugin-plugin/src/it/packaging-jar URL: https://github.com/apache/maven-plugin-tools/pull/108 -- 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-plugin-tools] dependabot[bot] commented on pull request #109: Bump plexus-utils from 3.0.1 to 3.0.16 in /maven-plugin-plugin/src/it/help-package
dependabot[bot] commented on PR #109: URL: https://github.com/apache/maven-plugin-tools/pull/109#issuecomment-1188636040 Looks like org.codehaus.plexus:plexus-utils 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-plugin-tools] dependabot[bot] closed pull request #106: Bump plexus-utils from 3.0.1 to 3.0.16 in /maven-plugin-plugin/src/it/java-basic-annotations-jdk8
dependabot[bot] closed pull request #106: Bump plexus-utils from 3.0.1 to 3.0.16 in /maven-plugin-plugin/src/it/java-basic-annotations-jdk8 URL: https://github.com/apache/maven-plugin-tools/pull/106 -- 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-plugin-tools] dependabot[bot] commented on pull request #106: Bump plexus-utils from 3.0.1 to 3.0.16 in /maven-plugin-plugin/src/it/java-basic-annotations-jdk8
dependabot[bot] commented on PR #106: URL: https://github.com/apache/maven-plugin-tools/pull/106#issuecomment-1188636033 Looks like org.codehaus.plexus:plexus-utils 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-plugin-tools] dependabot[bot] commented on pull request #105: Bump plexus-utils from 3.0.1 to 3.0.16 in /maven-plugin-plugin/src/it/help-basic
dependabot[bot] commented on PR #105: URL: https://github.com/apache/maven-plugin-tools/pull/105#issuecomment-1188636043 Looks like org.codehaus.plexus:plexus-utils 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-plugin-tools] dependabot[bot] commented on pull request #111: Bump plexus-utils from 3.0.1 to 3.0.16 in /maven-plugin-plugin/src/it/mplugin-299_no-configuration
dependabot[bot] commented on PR #111: URL: https://github.com/apache/maven-plugin-tools/pull/111#issuecomment-1188636039 Looks like org.codehaus.plexus:plexus-utils 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-plugin-tools] dependabot[bot] commented on pull request #108: Bump plexus-utils from 3.0.1 to 3.0.16 in /maven-plugin-plugin/src/it/packaging-jar
dependabot[bot] commented on PR #108: URL: https://github.com/apache/maven-plugin-tools/pull/108#issuecomment-1188636032 Looks like org.codehaus.plexus:plexus-utils 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-plugin-tools] dependabot[bot] closed pull request #103: Bump plexus-utils from 3.0.1 to 3.0.16 in /maven-plugin-plugin/src/it/annotation-with-inheritance-from-deps
dependabot[bot] closed pull request #103: Bump plexus-utils from 3.0.1 to 3.0.16 in /maven-plugin-plugin/src/it/annotation-with-inheritance-from-deps URL: https://github.com/apache/maven-plugin-tools/pull/103 -- 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-plugin-tools] dependabot[bot] commented on pull request #110: Bump plexus-utils from 3.0.1 to 3.0.16 in /maven-plugin-plugin/src/it/help-basic-jdk11
dependabot[bot] commented on PR #110: URL: https://github.com/apache/maven-plugin-tools/pull/110#issuecomment-1188636036 Looks like org.codehaus.plexus:plexus-utils 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-plugin-tools] dependabot[bot] closed pull request #102: Bump plexus-utils from 3.0.1 to 3.0.16 in /maven-plugin-plugin/src/it/mplugin-324_javadoc
dependabot[bot] closed pull request #102: Bump plexus-utils from 3.0.1 to 3.0.16 in /maven-plugin-plugin/src/it/mplugin-324_javadoc URL: https://github.com/apache/maven-plugin-tools/pull/102 -- 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-plugin-tools] dependabot[bot] commented on pull request #103: Bump plexus-utils from 3.0.1 to 3.0.16 in /maven-plugin-plugin/src/it/annotation-with-inheritance-from-deps
dependabot[bot] commented on PR #103: URL: https://github.com/apache/maven-plugin-tools/pull/103#issuecomment-1188636016 Looks like org.codehaus.plexus:plexus-utils 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-plugin-tools] dependabot[bot] closed pull request #101: Bump plexus-utils from 3.0.1 to 3.0.16 in /maven-plugin-plugin/src/it/annotation-with-inheritance
dependabot[bot] closed pull request #101: Bump plexus-utils from 3.0.1 to 3.0.16 in /maven-plugin-plugin/src/it/annotation-with-inheritance URL: https://github.com/apache/maven-plugin-tools/pull/101 -- 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-plugin-tools] dependabot[bot] commented on pull request #102: Bump plexus-utils from 3.0.1 to 3.0.16 in /maven-plugin-plugin/src/it/mplugin-324_javadoc
dependabot[bot] commented on PR #102: URL: https://github.com/apache/maven-plugin-tools/pull/102#issuecomment-1188635980 Looks like org.codehaus.plexus:plexus-utils 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-plugin-tools] dependabot[bot] commented on pull request #101: Bump plexus-utils from 3.0.1 to 3.0.16 in /maven-plugin-plugin/src/it/annotation-with-inheritance
dependabot[bot] commented on PR #101: URL: https://github.com/apache/maven-plugin-tools/pull/101#issuecomment-1188635973 Looks like org.codehaus.plexus:plexus-utils 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-plugin-tools] slawekjaranowski merged pull request #121: Bump plexus-utils to 3.4.2
slawekjaranowski merged PR #121: URL: https://github.com/apache/maven-plugin-tools/pull/121 -- 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-7511) Ensure the degreeOfConcurrency is a positive number in MavenExecutionRequest
[
https://issues.apache.org/jira/browse/MNG-7511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17568332#comment-17568332
]
ASF GitHub Bot commented on MNG-7511:
-
kwart commented on PR #773:
URL: https://github.com/apache/maven/pull/773#issuecomment-1188622683
Thanks for the review, Michael.
> Ensure the degreeOfConcurrency is a positive number in MavenExecutionRequest
>
>
> Key: MNG-7511
> URL: https://issues.apache.org/jira/browse/MNG-7511
> Project: Maven
> Issue Type: Bug
> Components: Core
>Affects Versions: 3.8.6
>Reporter: Josef Cacek
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.9.0, 4.0.0-alpha-1, 4.0.0
>
>
> The {{degreeOfConcurrency}} should always be a positive number, otherwise
> builds might fail.
> In Hazelcast we build with threads set to {{-T 0.5C}} in
> [{{.mvn/maven.config}}|https://github.com/hazelcast/hazelcast/blob/v5.1.2/.mvn/maven.config].
> This is fine until we run the build on a single CPU machine. It fails then
> with {{IllegalArgumentException}} as the computed {{degreeOfConcurrency ==
> 0}}.
> Stacktrace from Maven 3.6.3:
> {code}
> [ERROR] IllegalArgumentException
> java.lang.IllegalArgumentException
> at java.util.concurrent.ThreadPoolExecutor.
> (ThreadPoolExecutor.java:1293)
> at java.util.concurrent.ThreadPoolExecutor.
> (ThreadPoolExecutor.java:1215)
> at java.util.concurrent.Executors.newFixedThreadPool (Executors.java:155)
> at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder.build
> (MultiThreadedBuilder.java:88)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:62)
> at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:566)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:282)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:225)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:406)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:347)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[GitHub] [maven] kwart commented on pull request #773: [MNG-7511] Ensure the degreeOfConcurrency is a positive number (3.9.x)
kwart commented on PR #773: URL: https://github.com/apache/maven/pull/773#issuecomment-1188622683 Thanks for the review, Michael. -- 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-enforcer] hyman-yin opened a new pull request, #172: [enforcer:enforcer fix] enable RequireSameVersions with plugins parameter
hyman-yin opened a new pull request, #172: URL: https://github.com/apache/maven-enforcer/pull/172 org.apache.maven.enforcer:enforcer:3.1.1-SNAPSHOT RequireSameVersions.java did not add [plugins] parameter to [buildPluings] and [reportPlugins] Copyright [hymanyin] [name of copyright owner] Licensed 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. -- 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-7516) Support CI-Friendly-Versions in parent pom references
[ https://issues.apache.org/jira/browse/MNG-7516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17568304#comment-17568304 ] Christoph Läubrich commented on MNG-7516: - DO you like to reference them here? > Support CI-Friendly-Versions in parent pom references > - > > Key: MNG-7516 > URL: https://issues.apache.org/jira/browse/MNG-7516 > Project: Maven > Issue Type: New Feature >Reporter: Christoph Läubrich >Priority: Major > > I just noticed that one could use CI-riendly versions in the version of the > project but not in the version of the parent. > Is there any reason for not supporting this? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-enforcer] hyman-yin closed pull request #171: [enforcer:enforcer fix] enable RequireSameVersions with plugins parameter
hyman-yin closed pull request #171: [enforcer:enforcer fix] enable RequireSameVersions with plugins parameter URL: https://github.com/apache/maven-enforcer/pull/171 -- 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-enforcer] hyman-yin opened a new pull request, #171: [enforcer:enforcer fix] enable RequireSameVersions with plugins parameter
hyman-yin opened a new pull request, #171: URL: https://github.com/apache/maven-enforcer/pull/171 org.apache.maven.enforcer:enforcer:3.1.1-SNAPSHOT RequireSameVersions.java did not add [plugins] parameter to [buildPluings] and [reportPlugins] Copyright [hymanyin] [name of copyright owner] Licensed 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. -- 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 merged pull request #774: Fix typos in code
michael-o merged PR #774: URL: https://github.com/apache/maven/pull/774 -- 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] marcwrobel commented on a diff in pull request #774: Fix typos in code
marcwrobel commented on code in PR #774: URL: https://github.com/apache/maven/pull/774#discussion_r923907258 ## maven-core/src/test/java/org/apache/maven/lifecycle/internal/stub/ProjectDependenciesResolverStub.java: ## @@ -62,7 +62,7 @@ public Set resolve( Collection projects, Colle public Set resolve( MavenProject project, Collection scopesToCollect, Collection scopesToResolve, MavenSession session, - Set ignoreableArtifacts ) + Set ignorableArtifacts) Review Comment: Fixed. -- 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-7516) Support CI-Friendly-Versions in parent pom references
[ https://issues.apache.org/jira/browse/MNG-7516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17568226#comment-17568226 ] Michael Osipov commented on MNG-7516: - There are other open issues similar to this. > Support CI-Friendly-Versions in parent pom references > - > > Key: MNG-7516 > URL: https://issues.apache.org/jira/browse/MNG-7516 > Project: Maven > Issue Type: New Feature >Reporter: Christoph Läubrich >Priority: Major > > I just noticed that one could use CI-riendly versions in the version of the > project but not in the version of the parent. > Is there any reason for not supporting this? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7511) Ensure the degreeOfConcurrency is a positive number in MavenExecutionRequest
[
https://issues.apache.org/jira/browse/MNG-7511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17568224#comment-17568224
]
Hudson commented on MNG-7511:
-
Build succeeded in Jenkins: Maven » Maven TLP » maven » maven-3.9.x #55
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/maven-3.9.x/55/
> Ensure the degreeOfConcurrency is a positive number in MavenExecutionRequest
>
>
> Key: MNG-7511
> URL: https://issues.apache.org/jira/browse/MNG-7511
> Project: Maven
> Issue Type: Bug
> Components: Core
>Affects Versions: 3.8.6
>Reporter: Josef Cacek
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.9.0, 4.0.0-alpha-1, 4.0.0
>
>
> The {{degreeOfConcurrency}} should always be a positive number, otherwise
> builds might fail.
> In Hazelcast we build with threads set to {{-T 0.5C}} in
> [{{.mvn/maven.config}}|https://github.com/hazelcast/hazelcast/blob/v5.1.2/.mvn/maven.config].
> This is fine until we run the build on a single CPU machine. It fails then
> with {{IllegalArgumentException}} as the computed {{degreeOfConcurrency ==
> 0}}.
> Stacktrace from Maven 3.6.3:
> {code}
> [ERROR] IllegalArgumentException
> java.lang.IllegalArgumentException
> at java.util.concurrent.ThreadPoolExecutor.
> (ThreadPoolExecutor.java:1293)
> at java.util.concurrent.ThreadPoolExecutor.
> (ThreadPoolExecutor.java:1215)
> at java.util.concurrent.Executors.newFixedThreadPool (Executors.java:155)
> at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder.build
> (MultiThreadedBuilder.java:88)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:62)
> at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:566)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:282)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:225)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:406)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:347)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[GitHub] [maven] michael-o commented on a diff in pull request #774: Fix typos in code
michael-o commented on code in PR #774: URL: https://github.com/apache/maven/pull/774#discussion_r923883197 ## maven-core/src/test/java/org/apache/maven/lifecycle/internal/stub/ProjectDependenciesResolverStub.java: ## @@ -62,7 +62,7 @@ public Set resolve( Collection projects, Colle public Set resolve( MavenProject project, Collection scopesToCollect, Collection scopesToResolve, MavenSession session, - Set ignoreableArtifacts ) + Set ignorableArtifacts) Review Comment: whitespace gone -- 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] (MNG-7511) Ensure the degreeOfConcurrency is a positive number in MavenExecutionRequest
[
https://issues.apache.org/jira/browse/MNG-7511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov reopened MNG-7511:
-
> Ensure the degreeOfConcurrency is a positive number in MavenExecutionRequest
>
>
> Key: MNG-7511
> URL: https://issues.apache.org/jira/browse/MNG-7511
> Project: Maven
> Issue Type: Bug
> Components: Core
>Affects Versions: 3.8.6
>Reporter: Josef Cacek
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.9.0-candidate, 4.0.0-alpha-1, 4.0.0
>
>
> The {{degreeOfConcurrency}} should always be a positive number, otherwise
> builds might fail.
> In Hazelcast we build with threads set to {{-T 0.5C}} in
> [{{.mvn/maven.config}}|https://github.com/hazelcast/hazelcast/blob/v5.1.2/.mvn/maven.config].
> This is fine until we run the build on a single CPU machine. It fails then
> with {{IllegalArgumentException}} as the computed {{degreeOfConcurrency ==
> 0}}.
> Stacktrace from Maven 3.6.3:
> {code}
> [ERROR] IllegalArgumentException
> java.lang.IllegalArgumentException
> at java.util.concurrent.ThreadPoolExecutor.
> (ThreadPoolExecutor.java:1293)
> at java.util.concurrent.ThreadPoolExecutor.
> (ThreadPoolExecutor.java:1215)
> at java.util.concurrent.Executors.newFixedThreadPool (Executors.java:155)
> at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder.build
> (MultiThreadedBuilder.java:88)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:62)
> at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:566)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:282)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:225)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:406)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:347)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (MNG-7511) Ensure the degreeOfConcurrency is a positive number in MavenExecutionRequest
[
https://issues.apache.org/jira/browse/MNG-7511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MNG-7511.
---
Fix Version/s: 3.9.0
(was: 3.9.0-candidate)
Resolution: Fixed
Fixed with
[e1e4f5bda02535f718785189082f4197037774f3|https://gitbox.apache.org/repos/asf?p=maven.git;a=commit;h=e1e4f5bda02535f718785189082f4197037774f3]
for {{maven-3.9.x}} branch.
> Ensure the degreeOfConcurrency is a positive number in MavenExecutionRequest
>
>
> Key: MNG-7511
> URL: https://issues.apache.org/jira/browse/MNG-7511
> Project: Maven
> Issue Type: Bug
> Components: Core
>Affects Versions: 3.8.6
>Reporter: Josef Cacek
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.9.0, 4.0.0-alpha-1, 4.0.0
>
>
> The {{degreeOfConcurrency}} should always be a positive number, otherwise
> builds might fail.
> In Hazelcast we build with threads set to {{-T 0.5C}} in
> [{{.mvn/maven.config}}|https://github.com/hazelcast/hazelcast/blob/v5.1.2/.mvn/maven.config].
> This is fine until we run the build on a single CPU machine. It fails then
> with {{IllegalArgumentException}} as the computed {{degreeOfConcurrency ==
> 0}}.
> Stacktrace from Maven 3.6.3:
> {code}
> [ERROR] IllegalArgumentException
> java.lang.IllegalArgumentException
> at java.util.concurrent.ThreadPoolExecutor.
> (ThreadPoolExecutor.java:1293)
> at java.util.concurrent.ThreadPoolExecutor.
> (ThreadPoolExecutor.java:1215)
> at java.util.concurrent.Executors.newFixedThreadPool (Executors.java:155)
> at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder.build
> (MultiThreadedBuilder.java:88)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:62)
> at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:566)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:282)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:225)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:406)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:347)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-7511) Ensure the degreeOfConcurrency is a positive number in MavenExecutionRequest
[
https://issues.apache.org/jira/browse/MNG-7511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17568220#comment-17568220
]
ASF GitHub Bot commented on MNG-7511:
-
asfgit merged PR #773:
URL: https://github.com/apache/maven/pull/773
> Ensure the degreeOfConcurrency is a positive number in MavenExecutionRequest
>
>
> Key: MNG-7511
> URL: https://issues.apache.org/jira/browse/MNG-7511
> Project: Maven
> Issue Type: Bug
> Components: Core
>Affects Versions: 3.8.6
>Reporter: Josef Cacek
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.9.0-candidate, 4.0.0-alpha-1, 4.0.0
>
>
> The {{degreeOfConcurrency}} should always be a positive number, otherwise
> builds might fail.
> In Hazelcast we build with threads set to {{-T 0.5C}} in
> [{{.mvn/maven.config}}|https://github.com/hazelcast/hazelcast/blob/v5.1.2/.mvn/maven.config].
> This is fine until we run the build on a single CPU machine. It fails then
> with {{IllegalArgumentException}} as the computed {{degreeOfConcurrency ==
> 0}}.
> Stacktrace from Maven 3.6.3:
> {code}
> [ERROR] IllegalArgumentException
> java.lang.IllegalArgumentException
> at java.util.concurrent.ThreadPoolExecutor.
> (ThreadPoolExecutor.java:1293)
> at java.util.concurrent.ThreadPoolExecutor.
> (ThreadPoolExecutor.java:1215)
> at java.util.concurrent.Executors.newFixedThreadPool (Executors.java:155)
> at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder.build
> (MultiThreadedBuilder.java:88)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:62)
> at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:566)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:282)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:225)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:406)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:347)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[GitHub] [maven] marcwrobel opened a new pull request, #774: Fix typos in code
marcwrobel opened a new pull request, #774: URL: https://github.com/apache/maven/pull/774 Fix minor typos in code : - test method names, - method parameter names, - variable names. Public API is not modified by this PR, so it should be safe to merge. 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. - [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 [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
[GitHub] [maven] asfgit merged pull request #773: [MNG-7511] Ensure the degreeOfConcurrency is a positive number (3.9.x)
asfgit merged PR #773: URL: https://github.com/apache/maven/pull/773 -- 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-7511) Ensure the degreeOfConcurrency is a positive number in MavenExecutionRequest
[
https://issues.apache.org/jira/browse/MNG-7511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17568207#comment-17568207
]
ASF GitHub Bot commented on MNG-7511:
-
michael-o commented on code in PR #773:
URL: https://github.com/apache/maven/pull/773#discussion_r923855612
##
maven-embedder/src/test/java/org/apache/maven/cli/MavenCliTest.java:
##
@@ -371,4 +375,20 @@ public void testVersionStringWithoutAnsi() throws Exception
assertEquals( MessageUtils.stripAnsiCodes( versionOut ), versionOut );
}
+class ConcurrencyCalculator implements ThrowingRunnable
Review Comment:
That's fine although Maven 3.9 is Java 8.
> Ensure the degreeOfConcurrency is a positive number in MavenExecutionRequest
>
>
> Key: MNG-7511
> URL: https://issues.apache.org/jira/browse/MNG-7511
> Project: Maven
> Issue Type: Bug
> Components: Core
>Affects Versions: 3.8.6
>Reporter: Josef Cacek
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.9.0-candidate, 4.0.0-alpha-1, 4.0.0
>
>
> The {{degreeOfConcurrency}} should always be a positive number, otherwise
> builds might fail.
> In Hazelcast we build with threads set to {{-T 0.5C}} in
> [{{.mvn/maven.config}}|https://github.com/hazelcast/hazelcast/blob/v5.1.2/.mvn/maven.config].
> This is fine until we run the build on a single CPU machine. It fails then
> with {{IllegalArgumentException}} as the computed {{degreeOfConcurrency ==
> 0}}.
> Stacktrace from Maven 3.6.3:
> {code}
> [ERROR] IllegalArgumentException
> java.lang.IllegalArgumentException
> at java.util.concurrent.ThreadPoolExecutor.
> (ThreadPoolExecutor.java:1293)
> at java.util.concurrent.ThreadPoolExecutor.
> (ThreadPoolExecutor.java:1215)
> at java.util.concurrent.Executors.newFixedThreadPool (Executors.java:155)
> at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder.build
> (MultiThreadedBuilder.java:88)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:62)
> at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:566)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:282)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:225)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:406)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:347)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[GitHub] [maven] michael-o commented on a diff in pull request #773: [MNG-7511] Ensure the degreeOfConcurrency is a positive number (3.9.x)
michael-o commented on code in PR #773: URL: https://github.com/apache/maven/pull/773#discussion_r923855612 ## maven-embedder/src/test/java/org/apache/maven/cli/MavenCliTest.java: ## @@ -371,4 +375,20 @@ public void testVersionStringWithoutAnsi() throws Exception assertEquals( MessageUtils.stripAnsiCodes( versionOut ), versionOut ); } +class ConcurrencyCalculator implements ThrowingRunnable Review Comment: That's fine although Maven 3.9 is Java 8. -- 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-7511) Ensure the degreeOfConcurrency is a positive number in MavenExecutionRequest
[
https://issues.apache.org/jira/browse/MNG-7511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17568205#comment-17568205
]
ASF GitHub Bot commented on MNG-7511:
-
kwart commented on code in PR #773:
URL: https://github.com/apache/maven/pull/773#discussion_r923854420
##
maven-embedder/src/test/java/org/apache/maven/cli/MavenCliTest.java:
##
@@ -371,4 +375,20 @@ public void testVersionStringWithoutAnsi() throws Exception
assertEquals( MessageUtils.stripAnsiCodes( versionOut ), versionOut );
}
+class ConcurrencyCalculator implements ThrowingRunnable
Review Comment:
I guess so if we stick to Java 1.7 code level. It seems to be cleaner than
anonymous classes used directly in the test method.
The signature of the assert method is: ` T
assertThrows(Class, ThrowingRunnable)`
> Ensure the degreeOfConcurrency is a positive number in MavenExecutionRequest
>
>
> Key: MNG-7511
> URL: https://issues.apache.org/jira/browse/MNG-7511
> Project: Maven
> Issue Type: Bug
> Components: Core
>Affects Versions: 3.8.6
>Reporter: Josef Cacek
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.9.0-candidate, 4.0.0-alpha-1, 4.0.0
>
>
> The {{degreeOfConcurrency}} should always be a positive number, otherwise
> builds might fail.
> In Hazelcast we build with threads set to {{-T 0.5C}} in
> [{{.mvn/maven.config}}|https://github.com/hazelcast/hazelcast/blob/v5.1.2/.mvn/maven.config].
> This is fine until we run the build on a single CPU machine. It fails then
> with {{IllegalArgumentException}} as the computed {{degreeOfConcurrency ==
> 0}}.
> Stacktrace from Maven 3.6.3:
> {code}
> [ERROR] IllegalArgumentException
> java.lang.IllegalArgumentException
> at java.util.concurrent.ThreadPoolExecutor.
> (ThreadPoolExecutor.java:1293)
> at java.util.concurrent.ThreadPoolExecutor.
> (ThreadPoolExecutor.java:1215)
> at java.util.concurrent.Executors.newFixedThreadPool (Executors.java:155)
> at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder.build
> (MultiThreadedBuilder.java:88)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:62)
> at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:566)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:282)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:225)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:406)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:347)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[GitHub] [maven] kwart commented on a diff in pull request #773: [MNG-7511] Ensure the degreeOfConcurrency is a positive number (3.9.x)
kwart commented on code in PR #773: URL: https://github.com/apache/maven/pull/773#discussion_r923854420 ## maven-embedder/src/test/java/org/apache/maven/cli/MavenCliTest.java: ## @@ -371,4 +375,20 @@ public void testVersionStringWithoutAnsi() throws Exception assertEquals( MessageUtils.stripAnsiCodes( versionOut ), versionOut ); } +class ConcurrencyCalculator implements ThrowingRunnable Review Comment: I guess so if we stick to Java 1.7 code level. It seems to be cleaner than anonymous classes used directly in the test method. The signature of the assert method is: ` T assertThrows(Class, ThrowingRunnable)` -- 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-7511) Ensure the degreeOfConcurrency is a positive number in MavenExecutionRequest
[
https://issues.apache.org/jira/browse/MNG-7511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17568198#comment-17568198
]
ASF GitHub Bot commented on MNG-7511:
-
michael-o commented on code in PR #773:
URL: https://github.com/apache/maven/pull/773#discussion_r923845420
##
maven-embedder/src/test/java/org/apache/maven/cli/MavenCliTest.java:
##
@@ -371,4 +375,20 @@ public void testVersionStringWithoutAnsi() throws Exception
assertEquals( MessageUtils.stripAnsiCodes( versionOut ), versionOut );
}
+class ConcurrencyCalculator implements ThrowingRunnable
Review Comment:
Is this a technical requirement from JUnit?
> Ensure the degreeOfConcurrency is a positive number in MavenExecutionRequest
>
>
> Key: MNG-7511
> URL: https://issues.apache.org/jira/browse/MNG-7511
> Project: Maven
> Issue Type: Bug
> Components: Core
>Affects Versions: 3.8.6
>Reporter: Josef Cacek
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.9.0-candidate, 4.0.0-alpha-1, 4.0.0
>
>
> The {{degreeOfConcurrency}} should always be a positive number, otherwise
> builds might fail.
> In Hazelcast we build with threads set to {{-T 0.5C}} in
> [{{.mvn/maven.config}}|https://github.com/hazelcast/hazelcast/blob/v5.1.2/.mvn/maven.config].
> This is fine until we run the build on a single CPU machine. It fails then
> with {{IllegalArgumentException}} as the computed {{degreeOfConcurrency ==
> 0}}.
> Stacktrace from Maven 3.6.3:
> {code}
> [ERROR] IllegalArgumentException
> java.lang.IllegalArgumentException
> at java.util.concurrent.ThreadPoolExecutor.
> (ThreadPoolExecutor.java:1293)
> at java.util.concurrent.ThreadPoolExecutor.
> (ThreadPoolExecutor.java:1215)
> at java.util.concurrent.Executors.newFixedThreadPool (Executors.java:155)
> at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder.build
> (MultiThreadedBuilder.java:88)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:62)
> at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:566)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:282)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:225)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:406)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:347)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[GitHub] [maven] michael-o commented on a diff in pull request #773: [MNG-7511] Ensure the degreeOfConcurrency is a positive number (3.9.x)
michael-o commented on code in PR #773: URL: https://github.com/apache/maven/pull/773#discussion_r923845420 ## maven-embedder/src/test/java/org/apache/maven/cli/MavenCliTest.java: ## @@ -371,4 +375,20 @@ public void testVersionStringWithoutAnsi() throws Exception assertEquals( MessageUtils.stripAnsiCodes( versionOut ), versionOut ); } +class ConcurrencyCalculator implements ThrowingRunnable Review Comment: Is this a technical requirement from JUnit? -- 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-7511) Ensure the degreeOfConcurrency is a positive number in MavenExecutionRequest
[
https://issues.apache.org/jira/browse/MNG-7511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17568195#comment-17568195
]
ASF GitHub Bot commented on MNG-7511:
-
kwart opened a new pull request, #773:
URL: https://github.com/apache/maven/pull/773
Backports #767 into the `3.9.x`.
JIRA: https://issues.apache.org/jira/browse/MNG-7511
This PR ensures the `degreeOfConcurrency` is a positive number. It resolves
issues when the computed value is `< 1`.
> Ensure the degreeOfConcurrency is a positive number in MavenExecutionRequest
>
>
> Key: MNG-7511
> URL: https://issues.apache.org/jira/browse/MNG-7511
> Project: Maven
> Issue Type: Bug
> Components: Core
>Affects Versions: 3.8.6
>Reporter: Josef Cacek
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.9.0-candidate, 4.0.0-alpha-1, 4.0.0
>
>
> The {{degreeOfConcurrency}} should always be a positive number, otherwise
> builds might fail.
> In Hazelcast we build with threads set to {{-T 0.5C}} in
> [{{.mvn/maven.config}}|https://github.com/hazelcast/hazelcast/blob/v5.1.2/.mvn/maven.config].
> This is fine until we run the build on a single CPU machine. It fails then
> with {{IllegalArgumentException}} as the computed {{degreeOfConcurrency ==
> 0}}.
> Stacktrace from Maven 3.6.3:
> {code}
> [ERROR] IllegalArgumentException
> java.lang.IllegalArgumentException
> at java.util.concurrent.ThreadPoolExecutor.
> (ThreadPoolExecutor.java:1293)
> at java.util.concurrent.ThreadPoolExecutor.
> (ThreadPoolExecutor.java:1215)
> at java.util.concurrent.Executors.newFixedThreadPool (Executors.java:155)
> at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder.build
> (MultiThreadedBuilder.java:88)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:62)
> at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:566)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:282)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:225)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:406)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:347)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[GitHub] [maven] kwart opened a new pull request, #773: [MNG-7511] Ensure the degreeOfConcurrency is a positive number (3.9.x)
kwart opened a new pull request, #773: URL: https://github.com/apache/maven/pull/773 Backports #767 into the `3.9.x`. JIRA: https://issues.apache.org/jira/browse/MNG-7511 This PR ensures the `degreeOfConcurrency` is a positive number. It resolves issues when the computed value is `< 1`. -- 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] (MPLUGIN-407) Remove duplicate code from PluginReport
[
https://issues.apache.org/jira/browse/MPLUGIN-407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17568187#comment-17568187
]
ASF GitHub Bot commented on MPLUGIN-407:
michael-o commented on PR #120:
URL:
https://github.com/apache/maven-plugin-tools/pull/120#issuecomment-1188264394
Please go ahead and merge this.
> Remove duplicate code from PluginReport
> ---
>
> Key: MPLUGIN-407
> URL: https://issues.apache.org/jira/browse/MPLUGIN-407
> Project: Maven Plugin Tools
> Issue Type: Task
>Reporter: Slawomir Jaranowski
>Assignee: Slawomir Jaranowski
>Priority: Major
>
> In {{PluginReport}} we try to read plugin descriptor if some problem occurs
> in this step we have copied code from {{AbstractGeneratorMojo}} which try to
> generate plugin descriptor again.
> Reports is skipped at all if {{plugin.xml}} doesn't exist ... so fallback
> will not be used ...
> {{plugin.xml}} is generated by {{descriptor}} goal so if we have code in sync
> - fallback will do the same.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[GitHub] [maven-plugin-tools] michael-o commented on pull request #120: [MPLUGIN-407] Remove duplicate code from PluginReport
michael-o commented on PR #120: URL: https://github.com/apache/maven-plugin-tools/pull/120#issuecomment-1188264394 Please go ahead and merge 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
[GitHub] [maven-plugin-tools] michael-o opened a new pull request, #123: Prepare for Doxia (Sitetools) 2.0.0
michael-o opened a new pull request, #123: URL: https://github.com/apache/maven-plugin-tools/pull/123 * Simplify Velocity context setup * Add/fix missing elements in site descriptors * Upgrade Maven Project Reports Plugin to 3.4.0 for ITs This closes #124 -- 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-7511) Ensure the degreeOfConcurrency is a positive number in MavenExecutionRequest
[
https://issues.apache.org/jira/browse/MNG-7511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNG-7511:
Fix Version/s: 3.9.0-candidate
> Ensure the degreeOfConcurrency is a positive number in MavenExecutionRequest
>
>
> Key: MNG-7511
> URL: https://issues.apache.org/jira/browse/MNG-7511
> Project: Maven
> Issue Type: Bug
> Components: Core
>Affects Versions: 3.8.6
>Reporter: Josef Cacek
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.9.0-candidate, 4.0.0-alpha-1, 4.0.0
>
>
> The {{degreeOfConcurrency}} should always be a positive number, otherwise
> builds might fail.
> In Hazelcast we build with threads set to {{-T 0.5C}} in
> [{{.mvn/maven.config}}|https://github.com/hazelcast/hazelcast/blob/v5.1.2/.mvn/maven.config].
> This is fine until we run the build on a single CPU machine. It fails then
> with {{IllegalArgumentException}} as the computed {{degreeOfConcurrency ==
> 0}}.
> Stacktrace from Maven 3.6.3:
> {code}
> [ERROR] IllegalArgumentException
> java.lang.IllegalArgumentException
> at java.util.concurrent.ThreadPoolExecutor.
> (ThreadPoolExecutor.java:1293)
> at java.util.concurrent.ThreadPoolExecutor.
> (ThreadPoolExecutor.java:1215)
> at java.util.concurrent.Executors.newFixedThreadPool (Executors.java:155)
> at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder.build
> (MultiThreadedBuilder.java:88)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:62)
> at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:566)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:282)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:225)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:406)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:347)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[GitHub] [maven] michael-o commented on pull request #772: Fix minor typos
michael-o commented on PR #772: URL: https://github.com/apache/maven/pull/772#issuecomment-1187993339 > Still failing with 3.8.6 (used for both building maven and running the Core IT tests). > > @michael-o, I'm not going to bother you more with this issue (I may look into it later). Thank you for your review and for your support. If you still experience issues, seek help on users@. -- 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] marcwrobel commented on pull request #772: Fix minor typos
marcwrobel commented on PR #772: URL: https://github.com/apache/maven/pull/772#issuecomment-1187991128 Still failing with 3.8.6 (used for both building maven and running the Core IT tests). @michael-o, I'm not going to bother you more with this issue (I may look into it later). Thank you for your review and for your support. -- 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-7373) Maven should not attempt to download the jar when pom
[
https://issues.apache.org/jira/browse/MNG-7373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17568145#comment-17568145
]
Michael Osipov commented on MNG-7373:
-
Please raise a PR.
> Maven should not attempt to download the jar when pom
>
>
> Key: MNG-7373
> URL: https://issues.apache.org/jira/browse/MNG-7373
> Project: Maven
> Issue Type: Improvement
>Reporter: S L
>Priority: Major
> Fix For: waiting-for-feedback, wontfix-candidate
>
>
> Hello,
> maybe a corner case of what exactly should be part of a "relocation pom"
> ([https://maven.apache.org/guides/mini/guide-relocation.html]), but I created
> a release just consisting of the relocation-info
> ([https://repo1.maven.org/maven2/pl/project13/maven/git-commit-id-plugin/4.9.9/git-commit-id-plugin-4.9.9.pom])
> as type `pom` (since I only wanted to publish the
> relocation information).
> Using this depdendency.e.g. via:
> {code}
>
>
>
> pl.project13.maven
> git-commit-id-plugin
> 4.9.9
>
>
>
> {code}
> yields in the incorrect attempt of downloading a JAR-File from the new
> repository location:
> {code}
> [INFO] Building Git Commit Id Plugin Maven Mojo Debugging 0.0.3-SNAPSHOT
> [1/3]
> [INFO] [ pom
> ]-
> Downloading from central-secure:
> https://repo.maven.apache.org/maven2/io/github/git-commit-id/git-commit-id-maven-plugin/4.9.9/git-commit-id-maven-plugin-4.9.9.pom
> [WARNING] The POM for
> io.github.git-commit-id:git-commit-id-maven-plugin:jar:4.9.9 is missing, no
> dependency information available
> Downloading from central-secure:
> https://repo.maven.apache.org/maven2/io/github/git-commit-id/git-commit-id-maven-plugin/4.9.9/git-commit-id-maven-plugin-4.9.9.jar
> [INFO]
>
> [INFO] Reactor Summary for Git Commit Id Plugin Maven Mojo Debugging
> 0.0.3-SNAPSHOT:
> [INFO]
> [INFO] Git Commit Id Plugin Maven Mojo Debugging .. FAILURE [ 0.850
> s]
> [INFO] submodule-one .. SKIPPED
> [INFO] submodule-two .. SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 1.000 s
> [INFO] Finished at: 2021-07-12T21:42:15+02:00
> [INFO]
>
> [ERROR] Plugin pl.project13.maven:git-commit-id-plugin:4.9.9 or one of its
> dependencies could not be resolved: Could not find artifact
> io.github.git-commit-id:git-commit-id-maven-plugin:jar:4.9.9 in
> central-secure (https://repo.maven.apache.org/maven2) -> [Help 1]
> {code}
> IMHO Maven should not even try to search for a jar when
> `pom`. Simply raise an error that the package was
> relocated. the new location is at least detected, since it tries to download
> the artifact from a new location.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-7373) Maven should not attempt to download the jar when pom
[
https://issues.apache.org/jira/browse/MNG-7373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17568143#comment-17568143
]
Michael Osipov commented on MNG-7373:
-
The guide is likely outdated. Documentation is hard. The expectation is that
the new POM is *identical*, but the relocation information and a new version.
*No* change in the packaging.
> Maven should not attempt to download the jar when pom
>
>
> Key: MNG-7373
> URL: https://issues.apache.org/jira/browse/MNG-7373
> Project: Maven
> Issue Type: Improvement
>Reporter: S L
>Priority: Major
> Fix For: waiting-for-feedback, wontfix-candidate
>
>
> Hello,
> maybe a corner case of what exactly should be part of a "relocation pom"
> ([https://maven.apache.org/guides/mini/guide-relocation.html]), but I created
> a release just consisting of the relocation-info
> ([https://repo1.maven.org/maven2/pl/project13/maven/git-commit-id-plugin/4.9.9/git-commit-id-plugin-4.9.9.pom])
> as type `pom` (since I only wanted to publish the
> relocation information).
> Using this depdendency.e.g. via:
> {code}
>
>
>
> pl.project13.maven
> git-commit-id-plugin
> 4.9.9
>
>
>
> {code}
> yields in the incorrect attempt of downloading a JAR-File from the new
> repository location:
> {code}
> [INFO] Building Git Commit Id Plugin Maven Mojo Debugging 0.0.3-SNAPSHOT
> [1/3]
> [INFO] [ pom
> ]-
> Downloading from central-secure:
> https://repo.maven.apache.org/maven2/io/github/git-commit-id/git-commit-id-maven-plugin/4.9.9/git-commit-id-maven-plugin-4.9.9.pom
> [WARNING] The POM for
> io.github.git-commit-id:git-commit-id-maven-plugin:jar:4.9.9 is missing, no
> dependency information available
> Downloading from central-secure:
> https://repo.maven.apache.org/maven2/io/github/git-commit-id/git-commit-id-maven-plugin/4.9.9/git-commit-id-maven-plugin-4.9.9.jar
> [INFO]
>
> [INFO] Reactor Summary for Git Commit Id Plugin Maven Mojo Debugging
> 0.0.3-SNAPSHOT:
> [INFO]
> [INFO] Git Commit Id Plugin Maven Mojo Debugging .. FAILURE [ 0.850
> s]
> [INFO] submodule-one .. SKIPPED
> [INFO] submodule-two .. SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 1.000 s
> [INFO] Finished at: 2021-07-12T21:42:15+02:00
> [INFO]
>
> [ERROR] Plugin pl.project13.maven:git-commit-id-plugin:4.9.9 or one of its
> dependencies could not be resolved: Could not find artifact
> io.github.git-commit-id:git-commit-id-maven-plugin:jar:4.9.9 in
> central-secure (https://repo.maven.apache.org/maven2) -> [Help 1]
> {code}
> IMHO Maven should not even try to search for a jar when
> `pom`. Simply raise an error that the package was
> relocated. the new location is at least detected, since it tries to download
> the artifact from a new location.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[GitHub] [maven] marcwrobel commented on pull request #772: Fix minor typos
marcwrobel commented on PR #772: URL: https://github.com/apache/maven/pull/772#issuecomment-1187924628 There is also another file, `./core-it-suite/target/test-classes/mng-6391-print-version/version-log.txt` and it looks good in this one : ``` $ find . -name version-log.txt ./core-it-suite/target/test-classes/mng-6391-print-version-aggregator/version-log.txt ./core-it-suite/target/test-classes/mng-6391-print-version/version-log.txt $ cat ./core-it-suite/target/test-classes/mng-6391-print-version/version-log.txt [INFO] Error stacktraces are turned on. [INFO] Scanning for projects... [INFO] -- [INFO] Reactor Build Order: [INFO] [INFO] base-project [pom] [INFO] module-1 [jar] [INFO] module-2 [jar] [INFO] module-3 [jar] [INFO] [INFO] -< mng-6352-print-version:base-project >-- [INFO] Building base-project 1.3.0-SNAPSHOT [1/4] [INFO] from pom.xml [INFO] -[ pom ]-- [WARNING] Version not locked for default bindings plugins [maven-clean-plugin], you should define versions in pluginManagement section of your pom.xml or parent [INFO] [INFO] --- maven-clean-plugin:3.1.0:clean (default-clean) @ base-project --- [INFO] [INFO] ---< mng-6352-print-version:module-1 > [INFO] Building module-1 1.3.0-SNAPSHOT [2/4] [INFO] from module-1/pom.xml [INFO] -[ jar ]-- [WARNING] Version not locked for default bindings plugins [maven-clean-plugin], you should define versions in pluginManagement section of your pom.xml or parent [INFO] [INFO] --- maven-clean-plugin:3.1.0:clean (default-clean) @ module-1 --- [INFO] [INFO] ---< mng-6352-print-version:module-2 > [INFO] Building module-2 1.3.0-SNAPSHOT [3/4] [INFO] from module-2/pom.xml [INFO] -[ jar ]-- [WARNING] Version not locked for default bindings plugins [maven-clean-plugin], you should define versions in pluginManagement section of your pom.xml or parent [INFO] [INFO] --- maven-clean-plugin:3.1.0:clean (default-clean) @ module-2 --- [INFO] [INFO] ---< mng-6352-print-version:module-3 > [INFO] Building module-3 1.3.0-SNAPSHOT [4/4] [INFO] from module-3/pom.xml [INFO] -[ jar ]-- [WARNING] Version not locked for default bindings plugins [maven-clean-plugin], you should define versions in pluginManagement section of your pom.xml or parent [INFO] [INFO] --- maven-clean-plugin:3.1.0:clean (default-clean) @ module-3 --- [INFO] -- [INFO] Reactor Summary for base-project 1.3.0-SNAPSHOT: [INFO] [INFO] base-project . SUCCESS [ 0.020 s] [INFO] module-1 . SUCCESS [ 0.001 s] [INFO] module-2 . SUCCESS [ 0.001 s] [INFO] module-3 . SUCCESS [ 0.000 s] [INFO] -
[GitHub] [maven] michael-o commented on pull request #772: Fix minor typos
michael-o commented on PR #772: URL: https://github.com/apache/maven/pull/772#issuecomment-1187919658 Retry with 3.8.6 -- 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] marcwrobel commented on pull request #772: Fix minor typos
marcwrobel commented on PR #772: URL: https://github.com/apache/maven/pull/772#issuecomment-1187916790 Just checked the test, it turns out the logs are written to a `version-log.txt` file. The file in question : ``` $ cat ./core-it-suite/target/test-classes/mng-6391-print-version-aggregator/version-log.txt [INFO] Error stacktraces are turned on. [INFO] Scanning for projects... [INFO] -- [INFO] Reactor Build Order: [INFO] [INFO] module-1 [jar] [INFO] module-2 [jar] [INFO] module-3 [jar] [INFO] base-project [pom] [INFO] [INFO] ---< mng-6352-print-version:module-1 > [INFO] Building module-1 1.2.7.43.RELEASE [1/4] [INFO] from module-1/pom.xml [INFO] -[ jar ]-- [WARNING] Version not locked for default bindings plugins [maven-clean-plugin], you should define versions in pluginManagement section of your pom.xml or parent [INFO] [INFO] --- maven-clean-plugin:3.1.0:clean (default-clean) @ module-1 --- [INFO] [INFO] ---< mng-6352-print-version:module-2 > [INFO] Building module-2 7.5-SNAPSHOT [2/4] [INFO] from module-2/pom.xml [INFO] -[ jar ]-- [WARNING] Version not locked for default bindings plugins [maven-clean-plugin], you should define versions in pluginManagement section of your pom.xml or parent [INFO] [INFO] --- maven-clean-plugin:3.1.0:clean (default-clean) @ module-2 --- [INFO] [INFO] ---< mng-6352-print-version:module-3 > [INFO] Building module-3 1-RC1 [3/4] [INFO] from module-3/pom.xml [INFO] -[ jar ]-- [WARNING] Version not locked for default bindings plugins [maven-clean-plugin], you should define versions in pluginManagement section of your pom.xml or parent [INFO] [INFO] --- maven-clean-plugin:3.1.0:clean (default-clean) @ module-3 --- [INFO] [INFO] -< mng-6352-print-version:base-project >-- [INFO] Building base-project 1.0.0-SNAPSHOT [4/4] [INFO] from pom.xml [INFO] -[ pom ]-- [WARNING] Version not locked for default bindings plugins [maven-clean-plugin], you should define versions in pluginManagement section of your pom.xml or parent [INFO] [INFO] --- maven-clean-plugin:3.1.0:clean (default-clean) @ base-project --- [INFO] -- [INFO] Reactor Summary: [INFO] [INFO] module-1 1.2.7.43.RELEASE SUCCESS [ 0.021 s] [INFO] module-2 7.5-SNAPSHOT SUCCESS [ 0.000 s] [INFO] module-3 1-RC1 ... SUCCESS [ 0.000 s] [INFO] base-project 1.0.0-SNAPSHOT .. SUCCESS [ 0.001 s] [INFO] -- [INFO] BUILD SUCCESS [INFO] -- [INFO] Total time: 0.027 s [INFO] Finished at: 2022-07-18T19:33:30+02:00
[GitHub] [maven] marcwrobel commented on pull request #772: Fix minor typos
marcwrobel commented on PR #772: URL: https://github.com/apache/maven/pull/772#issuecomment-1187907909 [Snippet](https://gist.github.com/marcwrobel/778947223bea86a2abff5fd1790d6bef) updated with full build.log. I did not see anything in those logs but maybe I missed something. FYI the tests were launched using : ``` $ mvn -v Apache Maven 3.8.5 (3599d3414f046de2324203b78ddcf9b5e4388aa0) Maven home: /home/mwrobel/.asdf/installs/maven/3.8.5 Java version: 1.8.0_332, vendor: Temurin, runtime: /home/mwrobel/.asdf/installs/java/temurin-8.0.332+9/jre Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "5.10.0-16-amd64", arch: "amd64", family: "unix" ``` -- 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 merged pull request #772: Fix minor typos
michael-o merged PR #772: URL: https://github.com/apache/maven/pull/772 -- 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 #772: Fix minor typos
michael-o commented on PR #772: URL: https://github.com/apache/maven/pull/772#issuecomment-1187837923 Share the build.log from the failing IT as well. -- 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] marcwrobel commented on pull request #772: Fix minor typos
marcwrobel commented on PR #772: URL: https://github.com/apache/maven/pull/772#issuecomment-1187826270 Marked this PR as ready : the Core IT tests succeeded on GitHub actions. -- 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] marcwrobel commented on pull request #772: Fix minor typos
marcwrobel commented on PR #772: URL: https://github.com/apache/maven/pull/772#issuecomment-1187820195 https://gist.github.com/marcwrobel/778947223bea86a2abff5fd1790d6bef -- 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-7515) Cannot see a dependency tree for apache-maven module
[
https://issues.apache.org/jira/browse/MNG-7515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17568124#comment-17568124
]
Hudson commented on MNG-7515:
-
Build succeeded in Jenkins: Maven » Maven TLP » maven » PR-769 #2
See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/PR-769/2/
> Cannot see a dependency tree for apache-maven module
>
>
> Key: MNG-7515
> URL: https://issues.apache.org/jira/browse/MNG-7515
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.8.6
>Reporter: Rafael Chaves
>Assignee: Michael Osipov
>Priority: Minor
> Fix For: 3.9.0, 4.0.0-alpha-1, 4.0.0
>
>
> The {{apache-maven}} module configures maven-dependency-plugin under the
> {{}} element, which prevents that plug-in from being used with custom
> configuration from the command-line.
>
> {noformat}
> mvn org.apache.maven.plugins:maven-dependency-plugin:3.3.0:list -f
> apache-maven
> [INFO] Scanning for projects...
> [INFO]
> [INFO] ---< org.apache.maven:apache-maven
> >
> [INFO] Building Apache Maven Distribution 3.6.3
> [INFO] [ pom
> ]-
> [INFO]
> [INFO] --- maven-dependency-plugin:3.3.0:list (default-cli) @ apache-maven ---
> [INFO]
> [INFO] The following files have been resolved:
> [INFO] org.fusesource.jansi:jansi:jar:1.17.1:compile -- module jansi (auto)
> [INFO]
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
>
> [INFO] Total time: 0.483 s
> [INFO] Finished at: 2022-07-14T16:55:57-03:00
> [INFO]
> {noformat}
> The `dependency:tree` goal under debug mode shows something interesting:
> {noformat}
> [DEBUG] + Filtering dependency tree by artifact include patterns:
> [META-INF/native/**]{noformat}
> Turns out the apache-maven module configures the dependency plugin in a way
> that prevents it from being used from the command-line:
>
> {noformat}
>
>
> org.apache.maven.plugins
> maven-dependency-plugin
>
> jansi
> META-INF/native/**
>
>
>
> unpack-jansi-native
>
> unpack-dependencies
>
>
>
> {noformat}
>
> Moving the configuration element to under the {{}} element avoids
> the issue:
> {noformat}
> mvn org.apache.maven.plugins:maven-dependency-plugin:3.3.0:list -f
> apache-maven
> [INFO] Scanning for projects...
> [INFO]
> [INFO] ---< org.apache.maven:apache-maven
> >
> [INFO] Building Apache Maven Distribution 3.6.3
> [INFO] [ pom
> ]-
> [INFO]
> [INFO] --- maven-dependency-plugin:3.3.0:list (default-cli) @ apache-maven ---
> [INFO]
> [INFO] The following files have been resolved:
> [INFO]org.apache.maven:maven-embedder:jar:3.6.3:compile -- module
> maven.embedder (auto)
> [INFO]org.apache.maven:maven-settings:jar:3.6.3:compile -- module
> maven.settings (auto)
> [INFO]org.apache.maven:maven-settings-builder:jar:3.6.3:compile -- module
> maven.settings.builder (auto)
> [INFO]org.apache.maven:maven-plugin-api:jar:3.6.3:compile -- module
> maven.plugin.api (auto)
> [INFO]org.apache.maven:maven-model:jar:3.6.3:compile -- module
> maven.model (auto)
> [INFO]org.apache.maven:maven-model-builder:jar:3.6.3:compile -- module
> maven.model.builder (auto)
> [INFO]org.apache.maven:maven-builder-support:jar:3.6.3:compile -- module
> maven.builder.support (auto)
> [INFO]org.apache.maven.resolver:maven-resolver-api:jar:1.4.1:compile --
> module org.apache.maven.resolver [auto]
> [INFO]org.apache.maven.resolver:maven-resolver-util:jar:1.4.1:compile --
> module org.apache.maven.resolver.util [auto]
> [INFO]org.apache.maven.shared:maven-shared-utils:jar:3.2.1:compile --
> module maven.shared.utils (auto)
> [INFO]commons-io:commons-io:jar:2.5:compile -- module commons.io (auto)
> [INFO]com.google.inject:guice:jar:no_aop:4.2.1:compile -- module
> com.google.guice [auto]
> [INFO]com.google.guava:guava:jar:25.1-android:compile -- module
> com.google.common [auto]
> [INFO]javax.inject:javax.inject:jar:1:compile -- module javax.inject
> (auto)
> [INFO]javax.annotation:jsr250-api:jar:1.0:compile -- module jsr250.api
> (auto)
> [INFO]org.codehaus.plexus:plexus-utils:jar:3.2.1:compile -- module
> plexus.utils (auto)
> [INFO]org.codehaus.plexus:plexus-classworlds:jar:2.6.0:compile -- module
> plexus.classworlds (auto)
> [I
[jira] [Commented] (MNG-7511) Ensure the degreeOfConcurrency is a positive number in MavenExecutionRequest
[
https://issues.apache.org/jira/browse/MNG-7511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17568122#comment-17568122
]
Hudson commented on MNG-7511:
-
Build succeeded in Jenkins: Maven » Maven TLP » maven » PR-769 #2
See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/PR-769/2/
> Ensure the degreeOfConcurrency is a positive number in MavenExecutionRequest
>
>
> Key: MNG-7511
> URL: https://issues.apache.org/jira/browse/MNG-7511
> Project: Maven
> Issue Type: Bug
> Components: Core
>Affects Versions: 3.8.6
>Reporter: Josef Cacek
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 4.0.0-alpha-1, 4.0.0
>
>
> The {{degreeOfConcurrency}} should always be a positive number, otherwise
> builds might fail.
> In Hazelcast we build with threads set to {{-T 0.5C}} in
> [{{.mvn/maven.config}}|https://github.com/hazelcast/hazelcast/blob/v5.1.2/.mvn/maven.config].
> This is fine until we run the build on a single CPU machine. It fails then
> with {{IllegalArgumentException}} as the computed {{degreeOfConcurrency ==
> 0}}.
> Stacktrace from Maven 3.6.3:
> {code}
> [ERROR] IllegalArgumentException
> java.lang.IllegalArgumentException
> at java.util.concurrent.ThreadPoolExecutor.
> (ThreadPoolExecutor.java:1293)
> at java.util.concurrent.ThreadPoolExecutor.
> (ThreadPoolExecutor.java:1215)
> at java.util.concurrent.Executors.newFixedThreadPool (Executors.java:155)
> at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder.build
> (MultiThreadedBuilder.java:88)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:62)
> at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:566)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:282)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:225)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:406)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:347)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-7513) Address commons-io_commons-io vulnerability found in maven latest version
[ https://issues.apache.org/jira/browse/MNG-7513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17568123#comment-17568123 ] Hudson commented on MNG-7513: - Build succeeded in Jenkins: Maven » Maven TLP » maven » PR-769 #2 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/PR-769/2/ > Address commons-io_commons-io vulnerability found in maven latest version > - > > Key: MNG-7513 > URL: https://issues.apache.org/jira/browse/MNG-7513 > Project: Maven > Issue Type: Task >Affects Versions: 3.8.6 >Reporter: Polu Ram Charan Teja >Assignee: Michael Osipov >Priority: Major > Fix For: 3.9.0, 4.0.0-alpha-1, 4.0.0 > > > In the maven latest version 3.8.6 one dependency is identified with known > vulnerabilities in commons-io-2.6.jar CVE-2021-29425. so please suggest if > you have plan to upgrade commons-io to latest version as we are getting > impacted due to security checks -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven] michael-o commented on pull request #772: Fix minor typos
michael-o commented on PR #772: URL: https://github.com/apache/maven/pull/772#issuecomment-1187784332 Share a gist with the failure. -- 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] marcwrobel commented on pull request #772: Fix minor typos
marcwrobel commented on PR #772: URL: https://github.com/apache/maven/pull/772#issuecomment-1187766946 @michael-o, I am currently trying to figure out why the Core IT tests fail on org.apache.maven.it.MavenITmng6391PrintVersionTest#testitShouldPrintVersionAtTopAndAtBottom on my laptop (both for this branch and for the main branch). -- 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] marcwrobel commented on a diff in pull request #772: Fix minor typos
marcwrobel commented on code in PR #772: URL: https://github.com/apache/maven/pull/772#discussion_r923598424 ## maven-core/src/main/java/org/apache/maven/lifecycle/internal/ProjectSegment.java: ## @@ -26,7 +26,7 @@ import java.util.List; /** - * A build context that matches a mavenproject to a given tasksegment, and the session to be used. + * A build context that matches a maven project to a given task segment, and the session to be used. Review Comment: Fixed. -- 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 a diff in pull request #772: Fix minor typos
michael-o commented on code in PR #772: URL: https://github.com/apache/maven/pull/772#discussion_r923589663 ## maven-repository-metadata/src/site/apt/index.apt: ## @@ -44,7 +44,7 @@ Maven Repository Metadata Model gives data about available versions (<<>>, <<>>, <<>> list and <<>>), [[3]] in a "groupId/artifactId/version" snapshot artifact directory: metadata describes <<>>, <<>>, <<>> (base version, i.e. ending in <<<-SNAPSHOT>>>) and - <<>> element that gives data about snaphot (<<>>, <<>> and <<>> list). Notice that a + <<>> element that gives data about snapshot (<<>>, <<>> and <<>> list). Notice that a Review Comment: Snap it while it's hot! ## maven-core/src/main/java/org/apache/maven/lifecycle/internal/ProjectSegment.java: ## @@ -26,7 +26,7 @@ import java.util.List; /** - * A build context that matches a mavenproject to a given tasksegment, and the session to be used. + * A build context that matches a maven project to a given task segment, and the session to be used. Review Comment: Maven project -- 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-7515) Cannot see a dependency tree for apache-maven module
[
https://issues.apache.org/jira/browse/MNG-7515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17568108#comment-17568108
]
Hudson commented on MNG-7515:
-
Build failed in Jenkins: Maven » Maven TLP » maven » master #69
See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/master/69/
> Cannot see a dependency tree for apache-maven module
>
>
> Key: MNG-7515
> URL: https://issues.apache.org/jira/browse/MNG-7515
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.8.6
>Reporter: Rafael Chaves
>Assignee: Michael Osipov
>Priority: Minor
> Fix For: 3.9.0, 4.0.0-alpha-1, 4.0.0
>
>
> The {{apache-maven}} module configures maven-dependency-plugin under the
> {{}} element, which prevents that plug-in from being used with custom
> configuration from the command-line.
>
> {noformat}
> mvn org.apache.maven.plugins:maven-dependency-plugin:3.3.0:list -f
> apache-maven
> [INFO] Scanning for projects...
> [INFO]
> [INFO] ---< org.apache.maven:apache-maven
> >
> [INFO] Building Apache Maven Distribution 3.6.3
> [INFO] [ pom
> ]-
> [INFO]
> [INFO] --- maven-dependency-plugin:3.3.0:list (default-cli) @ apache-maven ---
> [INFO]
> [INFO] The following files have been resolved:
> [INFO] org.fusesource.jansi:jansi:jar:1.17.1:compile -- module jansi (auto)
> [INFO]
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
>
> [INFO] Total time: 0.483 s
> [INFO] Finished at: 2022-07-14T16:55:57-03:00
> [INFO]
> {noformat}
> The `dependency:tree` goal under debug mode shows something interesting:
> {noformat}
> [DEBUG] + Filtering dependency tree by artifact include patterns:
> [META-INF/native/**]{noformat}
> Turns out the apache-maven module configures the dependency plugin in a way
> that prevents it from being used from the command-line:
>
> {noformat}
>
>
> org.apache.maven.plugins
> maven-dependency-plugin
>
> jansi
> META-INF/native/**
>
>
>
> unpack-jansi-native
>
> unpack-dependencies
>
>
>
> {noformat}
>
> Moving the configuration element to under the {{}} element avoids
> the issue:
> {noformat}
> mvn org.apache.maven.plugins:maven-dependency-plugin:3.3.0:list -f
> apache-maven
> [INFO] Scanning for projects...
> [INFO]
> [INFO] ---< org.apache.maven:apache-maven
> >
> [INFO] Building Apache Maven Distribution 3.6.3
> [INFO] [ pom
> ]-
> [INFO]
> [INFO] --- maven-dependency-plugin:3.3.0:list (default-cli) @ apache-maven ---
> [INFO]
> [INFO] The following files have been resolved:
> [INFO]org.apache.maven:maven-embedder:jar:3.6.3:compile -- module
> maven.embedder (auto)
> [INFO]org.apache.maven:maven-settings:jar:3.6.3:compile -- module
> maven.settings (auto)
> [INFO]org.apache.maven:maven-settings-builder:jar:3.6.3:compile -- module
> maven.settings.builder (auto)
> [INFO]org.apache.maven:maven-plugin-api:jar:3.6.3:compile -- module
> maven.plugin.api (auto)
> [INFO]org.apache.maven:maven-model:jar:3.6.3:compile -- module
> maven.model (auto)
> [INFO]org.apache.maven:maven-model-builder:jar:3.6.3:compile -- module
> maven.model.builder (auto)
> [INFO]org.apache.maven:maven-builder-support:jar:3.6.3:compile -- module
> maven.builder.support (auto)
> [INFO]org.apache.maven.resolver:maven-resolver-api:jar:1.4.1:compile --
> module org.apache.maven.resolver [auto]
> [INFO]org.apache.maven.resolver:maven-resolver-util:jar:1.4.1:compile --
> module org.apache.maven.resolver.util [auto]
> [INFO]org.apache.maven.shared:maven-shared-utils:jar:3.2.1:compile --
> module maven.shared.utils (auto)
> [INFO]commons-io:commons-io:jar:2.5:compile -- module commons.io (auto)
> [INFO]com.google.inject:guice:jar:no_aop:4.2.1:compile -- module
> com.google.guice [auto]
> [INFO]com.google.guava:guava:jar:25.1-android:compile -- module
> com.google.common [auto]
> [INFO]javax.inject:javax.inject:jar:1:compile -- module javax.inject
> (auto)
> [INFO]javax.annotation:jsr250-api:jar:1.0:compile -- module jsr250.api
> (auto)
> [INFO]org.codehaus.plexus:plexus-utils:jar:3.2.1:compile -- module
> plexus.utils (auto)
> [INFO]org.codehaus.plexus:plexus-classworlds:jar:2.6.0:compile -- module
> plexus.classworlds (auto)
> [IN
[jira] [Commented] (MNG-7515) Cannot see a dependency tree for apache-maven module
[
https://issues.apache.org/jira/browse/MNG-7515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17568105#comment-17568105
]
Hudson commented on MNG-7515:
-
Build succeeded in Jenkins: Maven » Maven TLP » maven » PR-770 #2
See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/PR-770/2/
> Cannot see a dependency tree for apache-maven module
>
>
> Key: MNG-7515
> URL: https://issues.apache.org/jira/browse/MNG-7515
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.8.6
>Reporter: Rafael Chaves
>Assignee: Michael Osipov
>Priority: Minor
> Fix For: 3.9.0, 4.0.0-alpha-1, 4.0.0
>
>
> The {{apache-maven}} module configures maven-dependency-plugin under the
> {{}} element, which prevents that plug-in from being used with custom
> configuration from the command-line.
>
> {noformat}
> mvn org.apache.maven.plugins:maven-dependency-plugin:3.3.0:list -f
> apache-maven
> [INFO] Scanning for projects...
> [INFO]
> [INFO] ---< org.apache.maven:apache-maven
> >
> [INFO] Building Apache Maven Distribution 3.6.3
> [INFO] [ pom
> ]-
> [INFO]
> [INFO] --- maven-dependency-plugin:3.3.0:list (default-cli) @ apache-maven ---
> [INFO]
> [INFO] The following files have been resolved:
> [INFO] org.fusesource.jansi:jansi:jar:1.17.1:compile -- module jansi (auto)
> [INFO]
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
>
> [INFO] Total time: 0.483 s
> [INFO] Finished at: 2022-07-14T16:55:57-03:00
> [INFO]
> {noformat}
> The `dependency:tree` goal under debug mode shows something interesting:
> {noformat}
> [DEBUG] + Filtering dependency tree by artifact include patterns:
> [META-INF/native/**]{noformat}
> Turns out the apache-maven module configures the dependency plugin in a way
> that prevents it from being used from the command-line:
>
> {noformat}
>
>
> org.apache.maven.plugins
> maven-dependency-plugin
>
> jansi
> META-INF/native/**
>
>
>
> unpack-jansi-native
>
> unpack-dependencies
>
>
>
> {noformat}
>
> Moving the configuration element to under the {{}} element avoids
> the issue:
> {noformat}
> mvn org.apache.maven.plugins:maven-dependency-plugin:3.3.0:list -f
> apache-maven
> [INFO] Scanning for projects...
> [INFO]
> [INFO] ---< org.apache.maven:apache-maven
> >
> [INFO] Building Apache Maven Distribution 3.6.3
> [INFO] [ pom
> ]-
> [INFO]
> [INFO] --- maven-dependency-plugin:3.3.0:list (default-cli) @ apache-maven ---
> [INFO]
> [INFO] The following files have been resolved:
> [INFO]org.apache.maven:maven-embedder:jar:3.6.3:compile -- module
> maven.embedder (auto)
> [INFO]org.apache.maven:maven-settings:jar:3.6.3:compile -- module
> maven.settings (auto)
> [INFO]org.apache.maven:maven-settings-builder:jar:3.6.3:compile -- module
> maven.settings.builder (auto)
> [INFO]org.apache.maven:maven-plugin-api:jar:3.6.3:compile -- module
> maven.plugin.api (auto)
> [INFO]org.apache.maven:maven-model:jar:3.6.3:compile -- module
> maven.model (auto)
> [INFO]org.apache.maven:maven-model-builder:jar:3.6.3:compile -- module
> maven.model.builder (auto)
> [INFO]org.apache.maven:maven-builder-support:jar:3.6.3:compile -- module
> maven.builder.support (auto)
> [INFO]org.apache.maven.resolver:maven-resolver-api:jar:1.4.1:compile --
> module org.apache.maven.resolver [auto]
> [INFO]org.apache.maven.resolver:maven-resolver-util:jar:1.4.1:compile --
> module org.apache.maven.resolver.util [auto]
> [INFO]org.apache.maven.shared:maven-shared-utils:jar:3.2.1:compile --
> module maven.shared.utils (auto)
> [INFO]commons-io:commons-io:jar:2.5:compile -- module commons.io (auto)
> [INFO]com.google.inject:guice:jar:no_aop:4.2.1:compile -- module
> com.google.guice [auto]
> [INFO]com.google.guava:guava:jar:25.1-android:compile -- module
> com.google.common [auto]
> [INFO]javax.inject:javax.inject:jar:1:compile -- module javax.inject
> (auto)
> [INFO]javax.annotation:jsr250-api:jar:1.0:compile -- module jsr250.api
> (auto)
> [INFO]org.codehaus.plexus:plexus-utils:jar:3.2.1:compile -- module
> plexus.utils (auto)
> [INFO]org.codehaus.plexus:plexus-classworlds:jar:2.6.0:compile -- module
> plexus.classworlds (auto)
> [I
[jira] [Commented] (MNG-7513) Address commons-io_commons-io vulnerability found in maven latest version
[ https://issues.apache.org/jira/browse/MNG-7513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17568104#comment-17568104 ] Hudson commented on MNG-7513: - Build succeeded in Jenkins: Maven » Maven TLP » maven » PR-770 #2 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/PR-770/2/ > Address commons-io_commons-io vulnerability found in maven latest version > - > > Key: MNG-7513 > URL: https://issues.apache.org/jira/browse/MNG-7513 > Project: Maven > Issue Type: Task >Affects Versions: 3.8.6 >Reporter: Polu Ram Charan Teja >Assignee: Michael Osipov >Priority: Major > Fix For: 3.9.0, 4.0.0-alpha-1, 4.0.0 > > > In the maven latest version 3.8.6 one dependency is identified with known > vulnerabilities in commons-io-2.6.jar CVE-2021-29425. so please suggest if > you have plan to upgrade commons-io to latest version as we are getting > impacted due to security checks -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7513) Address commons-io_commons-io vulnerability found in maven latest version
[ https://issues.apache.org/jira/browse/MNG-7513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17568103#comment-17568103 ] Hudson commented on MNG-7513: - Build succeeded in Jenkins: Maven » Maven TLP » maven » master #68 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/master/68/ > Address commons-io_commons-io vulnerability found in maven latest version > - > > Key: MNG-7513 > URL: https://issues.apache.org/jira/browse/MNG-7513 > Project: Maven > Issue Type: Task >Affects Versions: 3.8.6 >Reporter: Polu Ram Charan Teja >Assignee: Michael Osipov >Priority: Major > Fix For: 3.9.0, 4.0.0-alpha-1, 4.0.0 > > > In the maven latest version 3.8.6 one dependency is identified with known > vulnerabilities in commons-io-2.6.jar CVE-2021-29425. so please suggest if > you have plan to upgrade commons-io to latest version as we are getting > impacted due to security checks -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7515) Cannot see a dependency tree for apache-maven module
[
https://issues.apache.org/jira/browse/MNG-7515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17568099#comment-17568099
]
Hudson commented on MNG-7515:
-
Build failed in Jenkins: Maven » Maven TLP » maven » maven-3.9.x #54
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/maven-3.9.x/54/
> Cannot see a dependency tree for apache-maven module
>
>
> Key: MNG-7515
> URL: https://issues.apache.org/jira/browse/MNG-7515
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.8.6
>Reporter: Rafael Chaves
>Assignee: Michael Osipov
>Priority: Minor
> Fix For: 3.9.0, 4.0.0-alpha-1, 4.0.0
>
>
> The {{apache-maven}} module configures maven-dependency-plugin under the
> {{}} element, which prevents that plug-in from being used with custom
> configuration from the command-line.
>
> {noformat}
> mvn org.apache.maven.plugins:maven-dependency-plugin:3.3.0:list -f
> apache-maven
> [INFO] Scanning for projects...
> [INFO]
> [INFO] ---< org.apache.maven:apache-maven
> >
> [INFO] Building Apache Maven Distribution 3.6.3
> [INFO] [ pom
> ]-
> [INFO]
> [INFO] --- maven-dependency-plugin:3.3.0:list (default-cli) @ apache-maven ---
> [INFO]
> [INFO] The following files have been resolved:
> [INFO] org.fusesource.jansi:jansi:jar:1.17.1:compile -- module jansi (auto)
> [INFO]
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
>
> [INFO] Total time: 0.483 s
> [INFO] Finished at: 2022-07-14T16:55:57-03:00
> [INFO]
> {noformat}
> The `dependency:tree` goal under debug mode shows something interesting:
> {noformat}
> [DEBUG] + Filtering dependency tree by artifact include patterns:
> [META-INF/native/**]{noformat}
> Turns out the apache-maven module configures the dependency plugin in a way
> that prevents it from being used from the command-line:
>
> {noformat}
>
>
> org.apache.maven.plugins
> maven-dependency-plugin
>
> jansi
> META-INF/native/**
>
>
>
> unpack-jansi-native
>
> unpack-dependencies
>
>
>
> {noformat}
>
> Moving the configuration element to under the {{}} element avoids
> the issue:
> {noformat}
> mvn org.apache.maven.plugins:maven-dependency-plugin:3.3.0:list -f
> apache-maven
> [INFO] Scanning for projects...
> [INFO]
> [INFO] ---< org.apache.maven:apache-maven
> >
> [INFO] Building Apache Maven Distribution 3.6.3
> [INFO] [ pom
> ]-
> [INFO]
> [INFO] --- maven-dependency-plugin:3.3.0:list (default-cli) @ apache-maven ---
> [INFO]
> [INFO] The following files have been resolved:
> [INFO]org.apache.maven:maven-embedder:jar:3.6.3:compile -- module
> maven.embedder (auto)
> [INFO]org.apache.maven:maven-settings:jar:3.6.3:compile -- module
> maven.settings (auto)
> [INFO]org.apache.maven:maven-settings-builder:jar:3.6.3:compile -- module
> maven.settings.builder (auto)
> [INFO]org.apache.maven:maven-plugin-api:jar:3.6.3:compile -- module
> maven.plugin.api (auto)
> [INFO]org.apache.maven:maven-model:jar:3.6.3:compile -- module
> maven.model (auto)
> [INFO]org.apache.maven:maven-model-builder:jar:3.6.3:compile -- module
> maven.model.builder (auto)
> [INFO]org.apache.maven:maven-builder-support:jar:3.6.3:compile -- module
> maven.builder.support (auto)
> [INFO]org.apache.maven.resolver:maven-resolver-api:jar:1.4.1:compile --
> module org.apache.maven.resolver [auto]
> [INFO]org.apache.maven.resolver:maven-resolver-util:jar:1.4.1:compile --
> module org.apache.maven.resolver.util [auto]
> [INFO]org.apache.maven.shared:maven-shared-utils:jar:3.2.1:compile --
> module maven.shared.utils (auto)
> [INFO]commons-io:commons-io:jar:2.5:compile -- module commons.io (auto)
> [INFO]com.google.inject:guice:jar:no_aop:4.2.1:compile -- module
> com.google.guice [auto]
> [INFO]com.google.guava:guava:jar:25.1-android:compile -- module
> com.google.common [auto]
> [INFO]javax.inject:javax.inject:jar:1:compile -- module javax.inject
> (auto)
> [INFO]javax.annotation:jsr250-api:jar:1.0:compile -- module jsr250.api
> (auto)
> [INFO]org.codehaus.plexus:plexus-utils:jar:3.2.1:compile -- module
> plexus.utils (auto)
> [INFO]org.codehaus.plexus:plexus-classworlds:jar:2.6.0:compile -- module
> plexus.classworlds (
[jira] [Commented] (MNG-7360) Can't parse project that has tag in plugin configuration
[
https://issues.apache.org/jira/browse/MNG-7360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17568095#comment-17568095
]
Hudson commented on MNG-7360:
-
Build succeeded in Jenkins: Maven » Maven TLP » maven » maven-3.9.x #53
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/maven-3.9.x/53/
> Can't parse project that has tag in plugin configuration
> -
>
> Key: MNG-7360
> URL: https://issues.apache.org/jira/browse/MNG-7360
> Project: Maven
> Issue Type: Bug
> Components: build/consumer
>Affects Versions: 4.0.x-candidate
> Environment: Apache Maven 4.0.0-alpha-1-SNAPSHOT
> (3a06530dbce82e2054afa3cc4c81631910474bd0)
> Maven home:
> /usr/local/Cellar/maven-snapshot/4.0.0-alpha-1-SNAPSHOT_290/libexec
> Java version: 17.0.1, vendor: Eclipse Adoptium, runtime:
> /Library/Java/JavaVirtualMachines/temurin-17.jdk/Contents/Home
> Default locale: en_GB, platform encoding: UTF-8
> OS name: "mac os x", version: "11.5", arch: "x86_64", family: "mac"
>Reporter: Maarten Mulders
>Assignee: Guillaume Nodet
>Priority: Major
> Fix For: 4.0.0-alpha-1, 4.0.0
>
> Attachments: Screenshot 2021-12-13 at 13.45.01.png
>
>
> The Apache Camel project has the following snippet in their root POM:
> {code:xml}
>
> org.codehaus.mojo
> flatten-maven-plugin
> 1.2.5
>
>
> default-cli
> process-resources
>
> flatten
>
>
>
>
>
> expand
>
>
>
>
>
>
> {code}
> With Maven 4's "Build Consumer" feature enabled, parsing this plugin
> definition breaks with
> {code:none}
> [INFO] BuildTimeEventSpy is registered.
> [INFO] Scanning for projects...
> [ERROR] [ERROR] Some problems were encountered while processing the POMs:
> [FATAL] Unable to transform pom
> [ERROR] The build could not read 1 project -> [Help 1]
> [ERROR]
> [ERROR] The project (/Users/maarten/Code/open-source/camel/pom.xml) has 1
> error
> [ERROR] Unable to transform pom: Not a regular file:
> /Users/maarten/Code/open-source/pom.xml
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the '-e'
> switch
> [ERROR] Re-run Maven using the '-X' switch to enable verbose output
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
> {code}
> I suspect that the {{}} tag is the culprit. It seems to me that it
> causes the {{ParentXMLFilter}} to think it needs to do its work. The attached
> screenshot shows the stacktrace that brought me to this idea. As the
> {{BufferingParser}} class processes its buffer of events, it encounters a
> situation of an "end {{parent}} tag". But that {{parent}} tag did not have
> child elements {{version}} and {{relativePath}} and so, it decides it needs
> to resolve the parent as {{../pom.xml}} against the project path
> ({{/Users/maarten/Code/open-source/camel/}} in my case), leading to the
> non-existing path of {{/Users/maarten/Code/open-source/pom.xml}}.
> I think the bug here is not that it resolves to a non-existing path (it's
> good to check that before actually reading the file). I think the bug is that
> the {{ParentXMLFilter}} is acting on the {{parent}} tag inside the plugin
> configuration.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-7504) Warning about unknown reportPlugins parameters for m-site-p are always generated
[
https://issues.apache.org/jira/browse/MNG-7504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17568096#comment-17568096
]
Hudson commented on MNG-7504:
-
Build succeeded in Jenkins: Maven » Maven TLP » maven » maven-3.9.x #53
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/maven-3.9.x/53/
> Warning about unknown reportPlugins parameters for m-site-p are always
> generated
>
>
> Key: MNG-7504
> URL: https://issues.apache.org/jira/browse/MNG-7504
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.9.0, 4.0.0
>Reporter: Slawomir Jaranowski
>Assignee: Slawomir Jaranowski
>Priority: Major
> Fix For: 3.9.0
>
>
> In {{m-site-p 3.7}} configuration parameter {{reportPlugins}} was removed
> MSITE-792
> After MNG-7468 unknown parameter is detected and warning is generated.
> We have service {{org.apache.maven.model.plugin.DefaultReportingConverter}}
> which always add configuration for m-site-p with unsupported parameter
> {{reportPlugins}}.
> Configuration is added when project contains reporting sections.
> Possible solution
> - drop service - easy to implement but with impact on m-site-p < 3.7
> - detect m-site-p version in project - complicated
> - don't print warning about {{reportPlugins}} for {{m-site-p}} - easy but
> workaround
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-7513) Address commons-io_commons-io vulnerability found in maven latest version
[ https://issues.apache.org/jira/browse/MNG-7513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17568094#comment-17568094 ] Hudson commented on MNG-7513: - Build succeeded in Jenkins: Maven » Maven TLP » maven » maven-3.9.x #53 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/maven-3.9.x/53/ > Address commons-io_commons-io vulnerability found in maven latest version > - > > Key: MNG-7513 > URL: https://issues.apache.org/jira/browse/MNG-7513 > Project: Maven > Issue Type: Task >Affects Versions: 3.8.6 >Reporter: Polu Ram Charan Teja >Assignee: Michael Osipov >Priority: Major > Fix For: 3.9.0, 4.0.0-alpha-1, 4.0.0 > > > In the maven latest version 3.8.6 one dependency is identified with known > vulnerabilities in commons-io-2.6.jar CVE-2021-29425. so please suggest if > you have plan to upgrade commons-io to latest version as we are getting > impacted due to security checks -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MINSTALL-160) generatePom=true with 3.0.0-M1 does not generate minimal POM but copies existing one
[
https://issues.apache.org/jira/browse/MINSTALL-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17568093#comment-17568093
]
Václav Haisman commented on MINSTALL-160:
-
Works for me.
!https://github.githubassets.com/images/icons/emoji/unicode/1f44d.png|width=20,height=20!
> generatePom=true with 3.0.0-M1 does not generate minimal POM but copies
> existing one
>
>
> Key: MINSTALL-160
> URL: https://issues.apache.org/jira/browse/MINSTALL-160
> Project: Maven Install Plugin
> Issue Type: Bug
> Components: install:install-file
>Affects Versions: 3.0.0-M1, 3.0.0, 3.0.0-M2
>Reporter: Václav Haisman
>Assignee: Tamás Cservenák
>Priority: Major
> Fix For: 3.0.1
>
>
> I am using install:install-file with generatePom=true to install JAR with
> minimal POM file. This has stopped working with 3.0.0-M1. With 3.0.0-M1, it
> copeis existing project pom.xml instead of generating a minimal one.
>
> This is easily reproducible with minimal project:
> {code:java}
>
> http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/xsd/maven-4.0.0.xsd";>
> 4.0.0
> maven.install.plugin.issue
> maven.install.plugin.issue
> 1.0-SNAPSHOT
> jar
> maven.install.plugin.issue
>
> 1.6
> 1.6
>
>
>
>
>
> maven-install-plugin
>
> 3.0.0-M1
>
>
>
>
>
>
> maven-install-plugin
>
>
> default-install
> none
> install
>
>
> custom-install
> install
>
> install-file
>
>
>
> ${project.build.directory}/${project.artifactId}-${project.version}.${project.packaging}
> true
>
>
>
>
>
>
>
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[GitHub] [maven-install-plugin] wilx commented on pull request #36: [MINSTALL-160] Generated POM is not installed if original POM exists
wilx commented on PR #36: URL: https://github.com/apache/maven-install-plugin/pull/36#issuecomment-1187703708 Works for me. :+1: -- 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] marcwrobel opened a new pull request, #772: Fix minor typos
marcwrobel opened a new pull request, #772: URL: https://github.com/apache/maven/pull/772 Fix various minor typos in : - project documentations, - javadoc and comments, - test files. 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. - [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. - [ ] 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-7515) Cannot see a dependency tree for apache-maven module
[
https://issues.apache.org/jira/browse/MNG-7515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17568083#comment-17568083
]
ASF GitHub Bot commented on MNG-7515:
-
asfgit merged PR #770:
URL: https://github.com/apache/maven/pull/770
> Cannot see a dependency tree for apache-maven module
>
>
> Key: MNG-7515
> URL: https://issues.apache.org/jira/browse/MNG-7515
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.8.6
>Reporter: Rafael Chaves
>Assignee: Michael Osipov
>Priority: Minor
> Fix For: 3.9.0, 4.0.0-alpha-1, 4.0.0
>
>
> The {{apache-maven}} module configures maven-dependency-plugin under the
> {{}} element, which prevents that plug-in from being used with custom
> configuration from the command-line.
>
> {noformat}
> mvn org.apache.maven.plugins:maven-dependency-plugin:3.3.0:list -f
> apache-maven
> [INFO] Scanning for projects...
> [INFO]
> [INFO] ---< org.apache.maven:apache-maven
> >
> [INFO] Building Apache Maven Distribution 3.6.3
> [INFO] [ pom
> ]-
> [INFO]
> [INFO] --- maven-dependency-plugin:3.3.0:list (default-cli) @ apache-maven ---
> [INFO]
> [INFO] The following files have been resolved:
> [INFO] org.fusesource.jansi:jansi:jar:1.17.1:compile -- module jansi (auto)
> [INFO]
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
>
> [INFO] Total time: 0.483 s
> [INFO] Finished at: 2022-07-14T16:55:57-03:00
> [INFO]
> {noformat}
> The `dependency:tree` goal under debug mode shows something interesting:
> {noformat}
> [DEBUG] + Filtering dependency tree by artifact include patterns:
> [META-INF/native/**]{noformat}
> Turns out the apache-maven module configures the dependency plugin in a way
> that prevents it from being used from the command-line:
>
> {noformat}
>
>
> org.apache.maven.plugins
> maven-dependency-plugin
>
> jansi
> META-INF/native/**
>
>
>
> unpack-jansi-native
>
> unpack-dependencies
>
>
>
> {noformat}
>
> Moving the configuration element to under the {{}} element avoids
> the issue:
> {noformat}
> mvn org.apache.maven.plugins:maven-dependency-plugin:3.3.0:list -f
> apache-maven
> [INFO] Scanning for projects...
> [INFO]
> [INFO] ---< org.apache.maven:apache-maven
> >
> [INFO] Building Apache Maven Distribution 3.6.3
> [INFO] [ pom
> ]-
> [INFO]
> [INFO] --- maven-dependency-plugin:3.3.0:list (default-cli) @ apache-maven ---
> [INFO]
> [INFO] The following files have been resolved:
> [INFO]org.apache.maven:maven-embedder:jar:3.6.3:compile -- module
> maven.embedder (auto)
> [INFO]org.apache.maven:maven-settings:jar:3.6.3:compile -- module
> maven.settings (auto)
> [INFO]org.apache.maven:maven-settings-builder:jar:3.6.3:compile -- module
> maven.settings.builder (auto)
> [INFO]org.apache.maven:maven-plugin-api:jar:3.6.3:compile -- module
> maven.plugin.api (auto)
> [INFO]org.apache.maven:maven-model:jar:3.6.3:compile -- module
> maven.model (auto)
> [INFO]org.apache.maven:maven-model-builder:jar:3.6.3:compile -- module
> maven.model.builder (auto)
> [INFO]org.apache.maven:maven-builder-support:jar:3.6.3:compile -- module
> maven.builder.support (auto)
> [INFO]org.apache.maven.resolver:maven-resolver-api:jar:1.4.1:compile --
> module org.apache.maven.resolver [auto]
> [INFO]org.apache.maven.resolver:maven-resolver-util:jar:1.4.1:compile --
> module org.apache.maven.resolver.util [auto]
> [INFO]org.apache.maven.shared:maven-shared-utils:jar:3.2.1:compile --
> module maven.shared.utils (auto)
> [INFO]commons-io:commons-io:jar:2.5:compile -- module commons.io (auto)
> [INFO]com.google.inject:guice:jar:no_aop:4.2.1:compile -- module
> com.google.guice [auto]
> [INFO]com.google.guava:guava:jar:25.1-android:compile -- module
> com.google.common [auto]
> [INFO]javax.inject:javax.inject:jar:1:compile -- module javax.inject
> (auto)
> [INFO]javax.annotation:jsr250-api:jar:1.0:compile -- module jsr250.api
> (auto)
> [INFO]org.codehaus.plexus:plexus-utils:jar:3.2.1:compile -- module
> plexus.utils (auto)
> [INFO]org.codehaus.plexus:plexus-classworlds:jar:2.6.0:compile -- module
> plexus.classworlds (auto)
> [INFO]org.sonatype.plexus:plexus-sec-dispatcher:jar:1.4:c
[jira] [Closed] (MNG-7515) Cannot see a dependency tree for apache-maven module
[
https://issues.apache.org/jira/browse/MNG-7515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MNG-7515.
---
Resolution: Fixed
Fixed with
[8ff8ebcaeadab54190581a6e4cdadbd80f872d9f|https://gitbox.apache.org/repos/asf?p=maven.git;a=commit;h=8ff8ebcaeadab54190581a6e4cdadbd80f872d9f]
and with
[eaac5f345828d4b7b846dcc6da21a5f77822bfaa|https://gitbox.apache.org/repos/asf?p=maven.git;a=commit;h=eaac5f345828d4b7b846dcc6da21a5f77822bfaa]
for {{maven-3.9.x}} branch.
> Cannot see a dependency tree for apache-maven module
>
>
> Key: MNG-7515
> URL: https://issues.apache.org/jira/browse/MNG-7515
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.8.6
>Reporter: Rafael Chaves
>Assignee: Michael Osipov
>Priority: Minor
> Fix For: 3.9.0, 4.0.0-alpha-1, 4.0.0
>
>
> The {{apache-maven}} module configures maven-dependency-plugin under the
> {{}} element, which prevents that plug-in from being used with custom
> configuration from the command-line.
>
> {noformat}
> mvn org.apache.maven.plugins:maven-dependency-plugin:3.3.0:list -f
> apache-maven
> [INFO] Scanning for projects...
> [INFO]
> [INFO] ---< org.apache.maven:apache-maven
> >
> [INFO] Building Apache Maven Distribution 3.6.3
> [INFO] [ pom
> ]-
> [INFO]
> [INFO] --- maven-dependency-plugin:3.3.0:list (default-cli) @ apache-maven ---
> [INFO]
> [INFO] The following files have been resolved:
> [INFO] org.fusesource.jansi:jansi:jar:1.17.1:compile -- module jansi (auto)
> [INFO]
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
>
> [INFO] Total time: 0.483 s
> [INFO] Finished at: 2022-07-14T16:55:57-03:00
> [INFO]
> {noformat}
> The `dependency:tree` goal under debug mode shows something interesting:
> {noformat}
> [DEBUG] + Filtering dependency tree by artifact include patterns:
> [META-INF/native/**]{noformat}
> Turns out the apache-maven module configures the dependency plugin in a way
> that prevents it from being used from the command-line:
>
> {noformat}
>
>
> org.apache.maven.plugins
> maven-dependency-plugin
>
> jansi
> META-INF/native/**
>
>
>
> unpack-jansi-native
>
> unpack-dependencies
>
>
>
> {noformat}
>
> Moving the configuration element to under the {{}} element avoids
> the issue:
> {noformat}
> mvn org.apache.maven.plugins:maven-dependency-plugin:3.3.0:list -f
> apache-maven
> [INFO] Scanning for projects...
> [INFO]
> [INFO] ---< org.apache.maven:apache-maven
> >
> [INFO] Building Apache Maven Distribution 3.6.3
> [INFO] [ pom
> ]-
> [INFO]
> [INFO] --- maven-dependency-plugin:3.3.0:list (default-cli) @ apache-maven ---
> [INFO]
> [INFO] The following files have been resolved:
> [INFO]org.apache.maven:maven-embedder:jar:3.6.3:compile -- module
> maven.embedder (auto)
> [INFO]org.apache.maven:maven-settings:jar:3.6.3:compile -- module
> maven.settings (auto)
> [INFO]org.apache.maven:maven-settings-builder:jar:3.6.3:compile -- module
> maven.settings.builder (auto)
> [INFO]org.apache.maven:maven-plugin-api:jar:3.6.3:compile -- module
> maven.plugin.api (auto)
> [INFO]org.apache.maven:maven-model:jar:3.6.3:compile -- module
> maven.model (auto)
> [INFO]org.apache.maven:maven-model-builder:jar:3.6.3:compile -- module
> maven.model.builder (auto)
> [INFO]org.apache.maven:maven-builder-support:jar:3.6.3:compile -- module
> maven.builder.support (auto)
> [INFO]org.apache.maven.resolver:maven-resolver-api:jar:1.4.1:compile --
> module org.apache.maven.resolver [auto]
> [INFO]org.apache.maven.resolver:maven-resolver-util:jar:1.4.1:compile --
> module org.apache.maven.resolver.util [auto]
> [INFO]org.apache.maven.shared:maven-shared-utils:jar:3.2.1:compile --
> module maven.shared.utils (auto)
> [INFO]commons-io:commons-io:jar:2.5:compile -- module commons.io (auto)
> [INFO]com.google.inject:guice:jar:no_aop:4.2.1:compile -- module
> com.google.guice [auto]
> [INFO]com.google.guava:guava:jar:25.1-android:compile -- module
> com.google.common [auto]
> [INFO]javax.inject:javax.inject:jar:1:compile -- module javax.inject
> (auto)
> [INFO]javax.annotation:jsr250-api:jar:1.0:compile -- module jsr250.api
> (auto)
> [INFO]org.codehaus.plexus:plexus
[GitHub] [maven] asfgit merged pull request #770: [MNG-7515] Cannot see a dependency tree for apache-maven module
asfgit merged PR #770: URL: https://github.com/apache/maven/pull/770 -- 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-7513) Address commons-io_commons-io vulnerability found in maven latest version
[ https://issues.apache.org/jira/browse/MNG-7513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17568076#comment-17568076 ] ASF GitHub Bot commented on MNG-7513: - asfgit closed pull request #771: [MNG-7513] Address commons-io_commons-io vulnerability found in maven… URL: https://github.com/apache/maven/pull/771 > Address commons-io_commons-io vulnerability found in maven latest version > - > > Key: MNG-7513 > URL: https://issues.apache.org/jira/browse/MNG-7513 > Project: Maven > Issue Type: Task >Affects Versions: 3.8.6 >Reporter: Polu Ram Charan Teja >Assignee: Michael Osipov >Priority: Major > Fix For: 3.9.0, 4.0.0-alpha-1, 4.0.0 > > > In the maven latest version 3.8.6 one dependency is identified with known > vulnerabilities in commons-io-2.6.jar CVE-2021-29425. so please suggest if > you have plan to upgrade commons-io to latest version as we are getting > impacted due to security checks -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MNG-7513) Address commons-io_commons-io vulnerability found in maven latest version
[
https://issues.apache.org/jira/browse/MNG-7513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MNG-7513.
---
Resolution: Fixed
Fixed with
[efa9f0c67888c0d88e6611560994c8c00ca92491|https://gitbox.apache.org/repos/asf?p=maven.git;a=commit;h=efa9f0c67888c0d88e6611560994c8c00ca92491]
and with with
[f164ab5f89c85657f6f5d8a6c05978e60c87dcc5|https://gitbox.apache.org/repos/asf?p=maven.git;a=commit;h=f164ab5f89c85657f6f5d8a6c05978e60c87dcc5]
for {{maven-3.9.x}} branch.
> Address commons-io_commons-io vulnerability found in maven latest version
> -
>
> Key: MNG-7513
> URL: https://issues.apache.org/jira/browse/MNG-7513
> Project: Maven
> Issue Type: Task
>Affects Versions: 3.8.6
>Reporter: Polu Ram Charan Teja
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.9.0, 4.0.0-alpha-1, 4.0.0
>
>
> In the maven latest version 3.8.6 one dependency is identified with known
> vulnerabilities in commons-io-2.6.jar CVE-2021-29425. so please suggest if
> you have plan to upgrade commons-io to latest version as we are getting
> impacted due to security checks
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[GitHub] [maven] asfgit closed pull request #771: [MNG-7513] Address commons-io_commons-io vulnerability found in maven…
asfgit closed pull request #771: [MNG-7513] Address commons-io_commons-io vulnerability found in maven… URL: https://github.com/apache/maven/pull/771 -- 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-7513) Address commons-io_commons-io vulnerability found in maven latest version
[ https://issues.apache.org/jira/browse/MNG-7513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17568075#comment-17568075 ] Hudson commented on MNG-7513: - Build succeeded in Jenkins: Maven » Maven TLP » maven » PR-771 #2 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/PR-771/2/ > Address commons-io_commons-io vulnerability found in maven latest version > - > > Key: MNG-7513 > URL: https://issues.apache.org/jira/browse/MNG-7513 > Project: Maven > Issue Type: Task >Affects Versions: 3.8.6 >Reporter: Polu Ram Charan Teja >Assignee: Michael Osipov >Priority: Major > Fix For: 3.9.0, 4.0.0-alpha-1, 4.0.0 > > > In the maven latest version 3.8.6 one dependency is identified with known > vulnerabilities in commons-io-2.6.jar CVE-2021-29425. so please suggest if > you have plan to upgrade commons-io to latest version as we are getting > impacted due to security checks -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MNG-7513) Address commons-io_commons-io vulnerability found in maven latest version
[ https://issues.apache.org/jira/browse/MNG-7513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MNG-7513: Fix Version/s: 3.9.0 4.0.0-alpha-1 4.0.0 > Address commons-io_commons-io vulnerability found in maven latest version > - > > Key: MNG-7513 > URL: https://issues.apache.org/jira/browse/MNG-7513 > Project: Maven > Issue Type: Task >Affects Versions: 3.8.6 >Reporter: Polu Ram Charan Teja >Assignee: Michael Osipov >Priority: Major > Fix For: 3.9.0, 4.0.0-alpha-1, 4.0.0 > > > In the maven latest version 3.8.6 one dependency is identified with known > vulnerabilities in commons-io-2.6.jar CVE-2021-29425. so please suggest if > you have plan to upgrade commons-io to latest version as we are getting > impacted due to security checks -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MNG-7513) Address commons-io_commons-io vulnerability found in maven latest version
[ https://issues.apache.org/jira/browse/MNG-7513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov reassigned MNG-7513: --- Assignee: Michael Osipov > Address commons-io_commons-io vulnerability found in maven latest version > - > > Key: MNG-7513 > URL: https://issues.apache.org/jira/browse/MNG-7513 > Project: Maven > Issue Type: Task >Affects Versions: 3.8.6 >Reporter: Polu Ram Charan Teja >Assignee: Michael Osipov >Priority: Major > > In the maven latest version 3.8.6 one dependency is identified with known > vulnerabilities in commons-io-2.6.jar CVE-2021-29425. so please suggest if > you have plan to upgrade commons-io to latest version as we are getting > impacted due to security checks -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-site] fkleedorfer opened a new pull request, #311: Update guide-attached-tests.apt
fkleedorfer opened a new pull request, #311: URL: https://github.com/apache/maven-site/pull/311 The guide is incomplete. Surefire does not pick up the tess in the attached jar on its own, it has to be configured to to so, and its provider autodetection does not work with attached jars, so it has to be nudged. With this change, the guide would have saved me an hour. -- 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-7515) Cannot see a dependency tree for apache-maven module
[
https://issues.apache.org/jira/browse/MNG-7515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17568036#comment-17568036
]
ASF GitHub Bot commented on MNG-7515:
-
abstratt commented on PR #770:
URL: https://github.com/apache/maven/pull/770#issuecomment-1187586973
Thanks, @michael-o, worked for me!
> Cannot see a dependency tree for apache-maven module
>
>
> Key: MNG-7515
> URL: https://issues.apache.org/jira/browse/MNG-7515
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.8.6
>Reporter: Rafael Chaves
>Assignee: Michael Osipov
>Priority: Minor
> Fix For: 3.9.0, 4.0.0-alpha-1, 4.0.0
>
>
> The {{apache-maven}} module configures maven-dependency-plugin under the
> {{}} element, which prevents that plug-in from being used with custom
> configuration from the command-line.
>
> {noformat}
> mvn org.apache.maven.plugins:maven-dependency-plugin:3.3.0:list -f
> apache-maven
> [INFO] Scanning for projects...
> [INFO]
> [INFO] ---< org.apache.maven:apache-maven
> >
> [INFO] Building Apache Maven Distribution 3.6.3
> [INFO] [ pom
> ]-
> [INFO]
> [INFO] --- maven-dependency-plugin:3.3.0:list (default-cli) @ apache-maven ---
> [INFO]
> [INFO] The following files have been resolved:
> [INFO] org.fusesource.jansi:jansi:jar:1.17.1:compile -- module jansi (auto)
> [INFO]
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
>
> [INFO] Total time: 0.483 s
> [INFO] Finished at: 2022-07-14T16:55:57-03:00
> [INFO]
> {noformat}
> The `dependency:tree` goal under debug mode shows something interesting:
> {noformat}
> [DEBUG] + Filtering dependency tree by artifact include patterns:
> [META-INF/native/**]{noformat}
> Turns out the apache-maven module configures the dependency plugin in a way
> that prevents it from being used from the command-line:
>
> {noformat}
>
>
> org.apache.maven.plugins
> maven-dependency-plugin
>
> jansi
> META-INF/native/**
>
>
>
> unpack-jansi-native
>
> unpack-dependencies
>
>
>
> {noformat}
>
> Moving the configuration element to under the {{}} element avoids
> the issue:
> {noformat}
> mvn org.apache.maven.plugins:maven-dependency-plugin:3.3.0:list -f
> apache-maven
> [INFO] Scanning for projects...
> [INFO]
> [INFO] ---< org.apache.maven:apache-maven
> >
> [INFO] Building Apache Maven Distribution 3.6.3
> [INFO] [ pom
> ]-
> [INFO]
> [INFO] --- maven-dependency-plugin:3.3.0:list (default-cli) @ apache-maven ---
> [INFO]
> [INFO] The following files have been resolved:
> [INFO]org.apache.maven:maven-embedder:jar:3.6.3:compile -- module
> maven.embedder (auto)
> [INFO]org.apache.maven:maven-settings:jar:3.6.3:compile -- module
> maven.settings (auto)
> [INFO]org.apache.maven:maven-settings-builder:jar:3.6.3:compile -- module
> maven.settings.builder (auto)
> [INFO]org.apache.maven:maven-plugin-api:jar:3.6.3:compile -- module
> maven.plugin.api (auto)
> [INFO]org.apache.maven:maven-model:jar:3.6.3:compile -- module
> maven.model (auto)
> [INFO]org.apache.maven:maven-model-builder:jar:3.6.3:compile -- module
> maven.model.builder (auto)
> [INFO]org.apache.maven:maven-builder-support:jar:3.6.3:compile -- module
> maven.builder.support (auto)
> [INFO]org.apache.maven.resolver:maven-resolver-api:jar:1.4.1:compile --
> module org.apache.maven.resolver [auto]
> [INFO]org.apache.maven.resolver:maven-resolver-util:jar:1.4.1:compile --
> module org.apache.maven.resolver.util [auto]
> [INFO]org.apache.maven.shared:maven-shared-utils:jar:3.2.1:compile --
> module maven.shared.utils (auto)
> [INFO]commons-io:commons-io:jar:2.5:compile -- module commons.io (auto)
> [INFO]com.google.inject:guice:jar:no_aop:4.2.1:compile -- module
> com.google.guice [auto]
> [INFO]com.google.guava:guava:jar:25.1-android:compile -- module
> com.google.common [auto]
> [INFO]javax.inject:javax.inject:jar:1:compile -- module javax.inject
> (auto)
> [INFO]javax.annotation:jsr250-api:jar:1.0:compile -- module jsr250.api
> (auto)
> [INFO]org.codehaus.plexus:plexus-utils:jar:3.2.1:compile -- module
> plexus.utils (auto)
> [INFO]org.codehaus.plexus:plexus-classworlds:jar:2.6.0:compile -- module
> plexus.classworlds
[GitHub] [maven] abstratt commented on pull request #770: [MNG-7515] Cannot see a dependency tree for apache-maven module
abstratt commented on PR #770: URL: https://github.com/apache/maven/pull/770#issuecomment-1187586973 Thanks, @michael-o, worked for me! -- 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-7513) Address commons-io_commons-io vulnerability found in maven latest version
[ https://issues.apache.org/jira/browse/MNG-7513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17568020#comment-17568020 ] ASF GitHub Bot commented on MNG-7513: - michael-o commented on code in PR #771: URL: https://github.com/apache/maven/pull/771#discussion_r923419579 ## pom.xml: ## @@ -300,6 +301,13 @@ under the License. org.apache.maven.shared maven-shared-utils Review Comment: No, not yet. All coloring is in m-s-u. > Address commons-io_commons-io vulnerability found in maven latest version > - > > Key: MNG-7513 > URL: https://issues.apache.org/jira/browse/MNG-7513 > Project: Maven > Issue Type: Task >Affects Versions: 3.8.6 >Reporter: Polu Ram Charan Teja >Priority: Major > > In the maven latest version 3.8.6 one dependency is identified with known > vulnerabilities in commons-io-2.6.jar CVE-2021-29425. so please suggest if > you have plan to upgrade commons-io to latest version as we are getting > impacted due to security checks -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven] michael-o commented on a diff in pull request #771: [MNG-7513] Address commons-io_commons-io vulnerability found in maven…
michael-o commented on code in PR #771: URL: https://github.com/apache/maven/pull/771#discussion_r923419579 ## pom.xml: ## @@ -300,6 +301,13 @@ under the License. org.apache.maven.shared maven-shared-utils Review Comment: No, not yet. All coloring is in m-s-u. -- 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-7513) Address commons-io_commons-io vulnerability found in maven latest version
[ https://issues.apache.org/jira/browse/MNG-7513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17568013#comment-17568013 ] ASF GitHub Bot commented on MNG-7513: - cstamas commented on code in PR #771: URL: https://github.com/apache/maven/pull/771#discussion_r923411425 ## pom.xml: ## @@ -300,6 +301,13 @@ under the License. org.apache.maven.shared maven-shared-utils Review Comment: could we get rid of m-shared-u? > Address commons-io_commons-io vulnerability found in maven latest version > - > > Key: MNG-7513 > URL: https://issues.apache.org/jira/browse/MNG-7513 > Project: Maven > Issue Type: Task >Affects Versions: 3.8.6 >Reporter: Polu Ram Charan Teja >Priority: Major > > In the maven latest version 3.8.6 one dependency is identified with known > vulnerabilities in commons-io-2.6.jar CVE-2021-29425. so please suggest if > you have plan to upgrade commons-io to latest version as we are getting > impacted due to security checks -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven] cstamas commented on a diff in pull request #771: [MNG-7513] Address commons-io_commons-io vulnerability found in maven…
cstamas commented on code in PR #771: URL: https://github.com/apache/maven/pull/771#discussion_r923411425 ## pom.xml: ## @@ -300,6 +301,13 @@ under the License. org.apache.maven.shared maven-shared-utils Review Comment: could we get rid of m-shared-u? -- 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
