[jira] [Commented] (MDEP-751) Publish `maven-dependency-plugin:3.2.0` artifacts to the Central Maven repository
[
https://issues.apache.org/jira/browse/MDEP-751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17359418#comment-17359418
]
Sergey Vyacheslavovich Brunov commented on MDEP-751:
Hi, [~mthmulders]!
Thank you very much for the prompt reply!
Best regards,
Sergey Vyacheslavovich Brunov.
> Publish `maven-dependency-plugin:3.2.0` artifacts to the Central Maven
> repository
> -
>
> Key: MDEP-751
> URL: https://issues.apache.org/jira/browse/MDEP-751
> Project: Maven Dependency Plugin
> Issue Type: Improvement
>Reporter: Sergey Vyacheslavovich Brunov
>Priority: Minor
>
> To whom it may concern,
> It seems the {{maven-dependency-plugin:3.2.0}} artifacts have not been
> published to the Central Maven repository.
> But, at the same time, the development of a new version seems to have
> started: note {{3.2.1-SNAPSHOT}} in the
> [pom.xml|https://github.com/apache/maven-dependency-plugin/blob/1ac708df7ccf0245f8c91a6f57db9468670f11a1/pom.xml].
> Therefore, could you please publish `maven-dependency-plugin:3.2.0` artifacts
> to the Central Maven repository?
> Best regards,
> Sergey Vyacheslavovich Brunov.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MDEP-693) `dependency:analyze-only` goal fails on OpenJDK 14
[
https://issues.apache.org/jira/browse/MDEP-693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17362457#comment-17362457
]
Sergey Vyacheslavovich Brunov commented on MDEP-693:
Just for the record.
The Maven artifact that contains the changes — the {{3.2.0}} version — has been
published to the Central Maven repository.
Best regards,
Sergey Vyacheslavovich Brunov.
> `dependency:analyze-only` goal fails on OpenJDK 14
> --
>
> Key: MDEP-693
> URL: https://issues.apache.org/jira/browse/MDEP-693
> Project: Maven Dependency Plugin
> Issue Type: Bug
>Affects Versions: 3.1.2
> Environment: OpenJDK Runtime Environment (build 14.0.1+7-Debian-1)
> Apache Maven 3.6.3
> Maven Dependency Plugin 3.1.2
>Reporter: Sergey Vyacheslavovich Brunov
>Assignee: Sylwester Lachiewicz
>Priority: Major
> Fix For: 3.2.0
>
>
> h1. Environment
> h2. Java
> {code}
> $ java -version
> openjdk version "14.0.1" 2020-04-14
> OpenJDK Runtime Environment (build 14.0.1+7-Debian-1)
> OpenJDK 64-Bit Server VM (build 14.0.1+7-Debian-1, mixed mode, sharing)
> {code}
> h2. Maven
> {code}
> $ mvn --version
> Apache Maven 3.6.3
> Maven home: /usr/share/maven
> Java version: 14.0.1, vendor: Debian, runtime:
> /usr/lib/jvm/java-14-openjdk-amd64
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "5.6.0-1-amd64", arch: "amd64", family: "unix"
> {code}
> h2. Maven Dependency Plugin
> {code:xml}
>
> org.apache.maven.plugins
> maven-dependency-plugin
> 3.1.2
>
>
> analyze
>
> analyze-only
>
>
> true
> true
>
>
>
>
> {code}
> h1. Problem
> When running the {{dependency:analyze-only}} goal on a JDK 14 project that
> uses the «Java Records» feature ([JEP 359: Records
> (Preview)|https://openjdk.java.net/jeps/359]), the goal fails with the
> following error:
> {code}
> $ mvn clean install -X
> <...>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-dependency-plugin:3.1.2:analyze-only (analyze)
> on project the-maven-project: Execution analyze of goal
> org.apache.maven.plugins:maven-dependency-plugin:3.1.2:analyze-only failed:
> This feature requires ASM8_EXPERIMENTAL -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-dependency-plugin:3.1.2:analyze-only
> (analyze) on project the-maven-project: Execution analyze of goal
> org.apache.maven.plugins:maven-dependency-plugin:3.1.2:analyze-only failed:
> This feature requires ASM8_EXPERIMENTAL
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:215)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:156)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:148)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:56)
> 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:564)
> 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)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
> analyze of goal
> org.apache.maven.plugins:maven-dependency-plugin:3.1.2:analyze-only failed:
> This feature requires ASM8_EXPERIMENTAL
> at org.apac
[jira] [Comment Edited] (MDEP-693) `dependency:analyze-only` goal fails on OpenJDK 14
[
https://issues.apache.org/jira/browse/MDEP-693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17304025#comment-17304025
]
Sergey Vyacheslavovich Brunov edited comment on MDEP-693 at 6/12/21, 11:35 PM:
---
h1. Solution
1. Upgrade the {{org.ow2.asm:asm}} Maven dependency version to at least 9.0.
Upgraded to the 9.1 version that as per [its release
notes|https://asm.ow2.io/versions.html] introduced the JDK 17 support.
2. Upgrade the {{org.apache.maven.shared:maven-dependency-analyzer}} Maven
dependency version to at least 1.11.3. Already upgraded.
h1. Pull request
1. [[MDEP-693] - `dependency:analyze-only` goal fails on OpenJDK 14 by sbrunov
· Pull Request #129 ·
apache/maven-dependency-plugin|https://github.com/apache/maven-dependency-plugin/pull/129].
h1. Request for release
Could you please release the new version of the {{maven-dependency-plugin}},
once the pull request has been merged?
Best regards,
Sergey Vyacheslavovich Brunov.
was (Author: sbrunov):
h1. Solution
1. Upgrade the {{org.ow2.asm:asm}} Maven dependency version to at least 9.0.
Upgraded to the 9.1 version that as per [its release
notes|https://asm.ow2.io/versions.html] introduced the JDK 17 support.
2. Upgrade the {{org.apache.maven.shared:maven-dependency-analyzer}} Maven
dependency version to at least 1.11.3. Already upgraded.
h1. Pull request
1. [[MDEP-693] - `dependency:analyze-only` goal fails on OpenJDK 14 by sbrunov
· Pull Request #129 ·
apache/maven-dependency-plugin|https://github.com/apache/maven-dependency-plugin/pull/129].
h1. Request for release
Could you please release the new version of the {{maven-dependency-plugin}},
once the pull request has been merged?
Best regards,
Sergey Brunov.
> `dependency:analyze-only` goal fails on OpenJDK 14
> --
>
> Key: MDEP-693
> URL: https://issues.apache.org/jira/browse/MDEP-693
> Project: Maven Dependency Plugin
> Issue Type: Bug
>Affects Versions: 3.1.2
> Environment: OpenJDK Runtime Environment (build 14.0.1+7-Debian-1)
> Apache Maven 3.6.3
> Maven Dependency Plugin 3.1.2
>Reporter: Sergey Vyacheslavovich Brunov
>Assignee: Sylwester Lachiewicz
>Priority: Major
> Fix For: 3.2.0
>
>
> h1. Environment
> h2. Java
> {code}
> $ java -version
> openjdk version "14.0.1" 2020-04-14
> OpenJDK Runtime Environment (build 14.0.1+7-Debian-1)
> OpenJDK 64-Bit Server VM (build 14.0.1+7-Debian-1, mixed mode, sharing)
> {code}
> h2. Maven
> {code}
> $ mvn --version
> Apache Maven 3.6.3
> Maven home: /usr/share/maven
> Java version: 14.0.1, vendor: Debian, runtime:
> /usr/lib/jvm/java-14-openjdk-amd64
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "5.6.0-1-amd64", arch: "amd64", family: "unix"
> {code}
> h2. Maven Dependency Plugin
> {code:xml}
>
> org.apache.maven.plugins
> maven-dependency-plugin
> 3.1.2
>
>
> analyze
>
> analyze-only
>
>
> true
> true
>
>
>
>
> {code}
> h1. Problem
> When running the {{dependency:analyze-only}} goal on a JDK 14 project that
> uses the «Java Records» feature ([JEP 359: Records
> (Preview)|https://openjdk.java.net/jeps/359]), the goal fails with the
> following error:
> {code}
> $ mvn clean install -X
> <...>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-dependency-plugin:3.1.2:analyze-only (analyze)
> on project the-maven-project: Execution analyze of goal
> org.apache.maven.plugins:maven-dependency-plugin:3.1.2:analyze-only failed:
> This feature requires ASM8_EXPERIMENTAL -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-dependency-plugin:3.1.2:analyze-only
> (analyze) on project the-maven-project: Execution analyze of goal
> org.apache.maven.plugins:maven-dependency-plugin:3.1.2:analyze-only failed:
> This feature requires ASM8_EXPERIMENTAL
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:215)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:156)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:148)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:56)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:
[jira] [Commented] (MDEP-751) Publish `maven-dependency-plugin:3.2.0` artifacts to the Central Maven repository
[
https://issues.apache.org/jira/browse/MDEP-751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17362458#comment-17362458
]
Sergey Vyacheslavovich Brunov commented on MDEP-751:
Just for the record.
The Maven artifact that contains the changes — the {{3.2.0}} version — has been
published to the Central Maven repository.
Best regards,
Sergey Vyacheslavovich Brunov.
> Publish `maven-dependency-plugin:3.2.0` artifacts to the Central Maven
> repository
> -
>
> Key: MDEP-751
> URL: https://issues.apache.org/jira/browse/MDEP-751
> Project: Maven Dependency Plugin
> Issue Type: Improvement
>Reporter: Sergey Vyacheslavovich Brunov
>Priority: Minor
>
> To whom it may concern,
> It seems the {{maven-dependency-plugin:3.2.0}} artifacts have not been
> published to the Central Maven repository.
> But, at the same time, the development of a new version seems to have
> started: note {{3.2.1-SNAPSHOT}} in the
> [pom.xml|https://github.com/apache/maven-dependency-plugin/blob/1ac708df7ccf0245f8c91a6f57db9468670f11a1/pom.xml].
> Therefore, could you please publish `maven-dependency-plugin:3.2.0` artifacts
> to the Central Maven repository?
> Best regards,
> Sergey Vyacheslavovich Brunov.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (MDEP-751) Publish `maven-dependency-plugin:3.2.0` artifacts to the Central Maven repository
[
https://issues.apache.org/jira/browse/MDEP-751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17362458#comment-17362458
]
Sergey Vyacheslavovich Brunov edited comment on MDEP-751 at 6/12/21, 11:37 PM:
---
Just for the record.
The Maven artifact of the {{3.2.0}} version has been published to the Central
Maven repository.
Best regards,
Sergey Vyacheslavovich Brunov.
was (Author: sbrunov):
Just for the record.
The Maven artifact that contains the changes — the {{3.2.0}} version — has been
published to the Central Maven repository.
Best regards,
Sergey Vyacheslavovich Brunov.
> Publish `maven-dependency-plugin:3.2.0` artifacts to the Central Maven
> repository
> -
>
> Key: MDEP-751
> URL: https://issues.apache.org/jira/browse/MDEP-751
> Project: Maven Dependency Plugin
> Issue Type: Improvement
>Reporter: Sergey Vyacheslavovich Brunov
>Priority: Minor
>
> To whom it may concern,
> It seems the {{maven-dependency-plugin:3.2.0}} artifacts have not been
> published to the Central Maven repository.
> But, at the same time, the development of a new version seems to have
> started: note {{3.2.1-SNAPSHOT}} in the
> [pom.xml|https://github.com/apache/maven-dependency-plugin/blob/1ac708df7ccf0245f8c91a6f57db9468670f11a1/pom.xml].
> Therefore, could you please publish `maven-dependency-plugin:3.2.0` artifacts
> to the Central Maven repository?
> Best regards,
> Sergey Vyacheslavovich Brunov.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MDEP-753) Non-test dependency reported as Non-test scoped test only dependency
[
https://issues.apache.org/jira/browse/MDEP-753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17366010#comment-17366010
]
Sergey Vyacheslavovich Brunov commented on MDEP-753:
Dear [~elharo]!
Recently, I faced the same problem with the upgraded plugin ({{3.2.0}}) and was
going to report it.
{quote}What we really need to fix this is a super simple project that exhibits
the problem suitable for use in an integration test.
{quote}
I have created such a MVCE (Minimal, Complete, and Verifiable example) project:
[maven-dependency-plugin-examples/issues.apache.org/MDEP-753 at master ·
svbrunov/maven-dependency-plugin-examples|https://github.com/svbrunov/maven-dependency-plugin-examples/tree/master/issues.apache.org/MDEP-753].
Please, notice that it seems the problem occurs because the production code
uses one class from Guava, while the test code uses another (different) class
from Guava.
Best regards,
Sergey Vyacheslavovich Brunov.
> Non-test dependency reported as Non-test scoped test only dependency
>
>
> Key: MDEP-753
> URL: https://issues.apache.org/jira/browse/MDEP-753
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: analyze
>Reporter: Elliotte Rusty Harold
>Priority: Minor
>
> Saw this when updating the google-http-java-client from 3.1.2 to 3.2.0 of the
> plugin. I'm not immediately sure whether this is a regression:
> [INFO] --- maven-dependency-plugin:3.2.0:analyze (default-cli) @
> google-http-client ---
> Warning: Non-test scoped test only dependencies found:
> Warning: com.google.guava:guava:jar:30.1.1-android:compile
> Warning: io.opencensus:opencensus-api:jar:0.28.0:compile
> Changing Guava to scope test breaks the build, which is expected based on the
> code. The warning seems incorrect.
> https://github.com/googleapis/google-http-java-client/pull/1396
> https://github.com/googleapis/google-http-java-client/pull/1396/checks?check_run_id=2809438131
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (MDEP-753) Non-test dependency reported as Non-test scoped test only dependency
[
https://issues.apache.org/jira/browse/MDEP-753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17366010#comment-17366010
]
Sergey Vyacheslavovich Brunov edited comment on MDEP-753 at 6/19/21, 7:37 PM:
--
Dear [~elharo],
Recently, I faced the same problem with the upgraded plugin ({{3.2.0}}) and was
going to report it.
{quote}What we really need to fix this is a super simple project that exhibits
the problem suitable for use in an integration test.
{quote}
I have created such a MVCE (Minimal, Complete, and Verifiable example) project:
[maven-dependency-plugin-examples/issues.apache.org/MDEP-753 at master ·
svbrunov/maven-dependency-plugin-examples|https://github.com/svbrunov/maven-dependency-plugin-examples/tree/master/issues.apache.org/MDEP-753].
Please, notice that it seems the problem occurs because the production code
uses one class from Guava, while the test code uses another (different) class
from Guava.
Best regards,
Sergey Vyacheslavovich Brunov.
was (Author: sbrunov):
Dear [~elharo]!
Recently, I faced the same problem with the upgraded plugin ({{3.2.0}}) and was
going to report it.
{quote}What we really need to fix this is a super simple project that exhibits
the problem suitable for use in an integration test.
{quote}
I have created such a MVCE (Minimal, Complete, and Verifiable example) project:
[maven-dependency-plugin-examples/issues.apache.org/MDEP-753 at master ·
svbrunov/maven-dependency-plugin-examples|https://github.com/svbrunov/maven-dependency-plugin-examples/tree/master/issues.apache.org/MDEP-753].
Please, notice that it seems the problem occurs because the production code
uses one class from Guava, while the test code uses another (different) class
from Guava.
Best regards,
Sergey Vyacheslavovich Brunov.
> Non-test dependency reported as Non-test scoped test only dependency
>
>
> Key: MDEP-753
> URL: https://issues.apache.org/jira/browse/MDEP-753
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: analyze
>Reporter: Elliotte Rusty Harold
>Priority: Minor
>
> Saw this when updating the google-http-java-client from 3.1.2 to 3.2.0 of the
> plugin. I'm not immediately sure whether this is a regression:
> [INFO] --- maven-dependency-plugin:3.2.0:analyze (default-cli) @
> google-http-client ---
> Warning: Non-test scoped test only dependencies found:
> Warning: com.google.guava:guava:jar:30.1.1-android:compile
> Warning: io.opencensus:opencensus-api:jar:0.28.0:compile
> Changing Guava to scope test breaks the build, which is expected based on the
> code. The warning seems incorrect.
> https://github.com/googleapis/google-http-java-client/pull/1396
> https://github.com/googleapis/google-http-java-client/pull/1396/checks?check_run_id=2809438131
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (MDEP-753) Non-test dependency reported as Non-test scoped test only dependency
[
https://issues.apache.org/jira/browse/MDEP-753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17366010#comment-17366010
]
Sergey Vyacheslavovich Brunov edited comment on MDEP-753 at 6/19/21, 7:46 PM:
--
Dear [~stevenschlansker] and [~elharo],
Recently, I faced the same problem with the upgraded plugin ({{3.2.0}}) and was
going to report it.
{quote}What we really need to fix this is a super simple project that exhibits
the problem suitable for use in an integration test.
{quote}
I have created such a MVCE (Minimal, Complete, and Verifiable example) project:
[maven-dependency-plugin-examples/issues.apache.org/MDEP-753 at master ·
svbrunov/maven-dependency-plugin-examples|https://github.com/svbrunov/maven-dependency-plugin-examples/tree/master/issues.apache.org/MDEP-753].
Please, notice that it seems the problem occurs because the production code
uses one class from Guava, while the test code uses another (different) class
from Guava.
{quote}I would recommend raising the priority of this bug, potentially even to
Blocker, this is a serious regression.
{quote}
I agree with [~stevenschlansker] because it is a serious regression defect.
Best regards,
Sergey Vyacheslavovich Brunov.
was (Author: sbrunov):
Dear [~elharo],
Recently, I faced the same problem with the upgraded plugin ({{3.2.0}}) and was
going to report it.
{quote}What we really need to fix this is a super simple project that exhibits
the problem suitable for use in an integration test.
{quote}
I have created such a MVCE (Minimal, Complete, and Verifiable example) project:
[maven-dependency-plugin-examples/issues.apache.org/MDEP-753 at master ·
svbrunov/maven-dependency-plugin-examples|https://github.com/svbrunov/maven-dependency-plugin-examples/tree/master/issues.apache.org/MDEP-753].
Please, notice that it seems the problem occurs because the production code
uses one class from Guava, while the test code uses another (different) class
from Guava.
Best regards,
Sergey Vyacheslavovich Brunov.
> Non-test dependency reported as Non-test scoped test only dependency
>
>
> Key: MDEP-753
> URL: https://issues.apache.org/jira/browse/MDEP-753
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: analyze
>Reporter: Elliotte Rusty Harold
>Priority: Minor
>
> Saw this when updating the google-http-java-client from 3.1.2 to 3.2.0 of the
> plugin. I'm not immediately sure whether this is a regression:
> [INFO] --- maven-dependency-plugin:3.2.0:analyze (default-cli) @
> google-http-client ---
> Warning: Non-test scoped test only dependencies found:
> Warning: com.google.guava:guava:jar:30.1.1-android:compile
> Warning: io.opencensus:opencensus-api:jar:0.28.0:compile
> Changing Guava to scope test breaks the build, which is expected based on the
> code. The warning seems incorrect.
> https://github.com/googleapis/google-http-java-client/pull/1396
> https://github.com/googleapis/google-http-java-client/pull/1396/checks?check_run_id=2809438131
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (MDEP-753) Non-test dependency reported as Non-test scoped test only dependency
[
https://issues.apache.org/jira/browse/MDEP-753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17366010#comment-17366010
]
Sergey Vyacheslavovich Brunov edited comment on MDEP-753 at 6/19/21, 7:46 PM:
--
Dear [~stevenschlansker] and [~elharo],
Recently, I faced the same problem with the upgraded plugin ({{3.2.0}}) and was
going to report it.
{quote}What we really need to fix this is a super simple project that exhibits
the problem suitable for use in an integration test.
{quote}
[~elharo], I have created such a MVCE (Minimal, Complete, and Verifiable
example) project: [maven-dependency-plugin-examples/issues.apache.org/MDEP-753
at master ·
svbrunov/maven-dependency-plugin-examples|https://github.com/svbrunov/maven-dependency-plugin-examples/tree/master/issues.apache.org/MDEP-753].
Please, notice that it seems the problem occurs because the production code
uses one class from Guava, while the test code uses another (different) class
from Guava.
{quote}I would recommend raising the priority of this bug, potentially even to
Blocker, this is a serious regression.
{quote}
I agree with [~stevenschlansker] because it is a serious regression defect.
Best regards,
Sergey Vyacheslavovich Brunov.
was (Author: sbrunov):
Dear [~stevenschlansker] and [~elharo],
Recently, I faced the same problem with the upgraded plugin ({{3.2.0}}) and was
going to report it.
{quote}What we really need to fix this is a super simple project that exhibits
the problem suitable for use in an integration test.
{quote}
I have created such a MVCE (Minimal, Complete, and Verifiable example) project:
[maven-dependency-plugin-examples/issues.apache.org/MDEP-753 at master ·
svbrunov/maven-dependency-plugin-examples|https://github.com/svbrunov/maven-dependency-plugin-examples/tree/master/issues.apache.org/MDEP-753].
Please, notice that it seems the problem occurs because the production code
uses one class from Guava, while the test code uses another (different) class
from Guava.
{quote}I would recommend raising the priority of this bug, potentially even to
Blocker, this is a serious regression.
{quote}
I agree with [~stevenschlansker] because it is a serious regression defect.
Best regards,
Sergey Vyacheslavovich Brunov.
> Non-test dependency reported as Non-test scoped test only dependency
>
>
> Key: MDEP-753
> URL: https://issues.apache.org/jira/browse/MDEP-753
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: analyze
>Reporter: Elliotte Rusty Harold
>Priority: Minor
>
> Saw this when updating the google-http-java-client from 3.1.2 to 3.2.0 of the
> plugin. I'm not immediately sure whether this is a regression:
> [INFO] --- maven-dependency-plugin:3.2.0:analyze (default-cli) @
> google-http-client ---
> Warning: Non-test scoped test only dependencies found:
> Warning: com.google.guava:guava:jar:30.1.1-android:compile
> Warning: io.opencensus:opencensus-api:jar:0.28.0:compile
> Changing Guava to scope test breaks the build, which is expected based on the
> code. The warning seems incorrect.
> https://github.com/googleapis/google-http-java-client/pull/1396
> https://github.com/googleapis/google-http-java-client/pull/1396/checks?check_run_id=2809438131
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (MDEP-753) Non-test dependency reported as Non-test scoped test only dependency
[
https://issues.apache.org/jira/browse/MDEP-753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17366010#comment-17366010
]
Sergey Vyacheslavovich Brunov edited comment on MDEP-753 at 6/19/21, 7:50 PM:
--
Dear [~stevenschlansker] and [~elharo],
Recently, I faced the same problem with the upgraded plugin ({{3.2.0}}) and was
going to report it.
{quote}What we really need to fix this is a super simple project that exhibits
the problem suitable for use in an integration test.
{quote}
[~elharo], I have created such a MVCE (Minimal, Complete, and Verifiable
example) project: [maven-dependency-plugin-examples/issues.apache.org/MDEP-753
at master ·
svbrunov/maven-dependency-plugin-examples|https://github.com/svbrunov/maven-dependency-plugin-examples/tree/master/issues.apache.org/MDEP-753].
Please, notice that it seems the problem occurs because the production code
uses one class from Guava, while the test code uses another (different) class
from Guava.
{quote}I would recommend raising the priority of this bug, potentially even to
Blocker, this is a serious regression.
{quote}
I agree with [~stevenschlansker] because it is a serious regression defect.
I had to downgrade the plugin to the {{3.1.2}} version.
Best regards,
Sergey Vyacheslavovich Brunov.
was (Author: sbrunov):
Dear [~stevenschlansker] and [~elharo],
Recently, I faced the same problem with the upgraded plugin ({{3.2.0}}) and was
going to report it.
{quote}What we really need to fix this is a super simple project that exhibits
the problem suitable for use in an integration test.
{quote}
[~elharo], I have created such a MVCE (Minimal, Complete, and Verifiable
example) project: [maven-dependency-plugin-examples/issues.apache.org/MDEP-753
at master ·
svbrunov/maven-dependency-plugin-examples|https://github.com/svbrunov/maven-dependency-plugin-examples/tree/master/issues.apache.org/MDEP-753].
Please, notice that it seems the problem occurs because the production code
uses one class from Guava, while the test code uses another (different) class
from Guava.
{quote}I would recommend raising the priority of this bug, potentially even to
Blocker, this is a serious regression.
{quote}
I agree with [~stevenschlansker] because it is a serious regression defect.
Best regards,
Sergey Vyacheslavovich Brunov.
> Non-test dependency reported as Non-test scoped test only dependency
>
>
> Key: MDEP-753
> URL: https://issues.apache.org/jira/browse/MDEP-753
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: analyze
>Reporter: Elliotte Rusty Harold
>Priority: Minor
>
> Saw this when updating the google-http-java-client from 3.1.2 to 3.2.0 of the
> plugin. I'm not immediately sure whether this is a regression:
> [INFO] --- maven-dependency-plugin:3.2.0:analyze (default-cli) @
> google-http-client ---
> Warning: Non-test scoped test only dependencies found:
> Warning: com.google.guava:guava:jar:30.1.1-android:compile
> Warning: io.opencensus:opencensus-api:jar:0.28.0:compile
> Changing Guava to scope test breaks the build, which is expected based on the
> code. The warning seems incorrect.
> https://github.com/googleapis/google-http-java-client/pull/1396
> https://github.com/googleapis/google-http-java-client/pull/1396/checks?check_run_id=2809438131
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (MDEP-753) Non-test dependency reported as Non-test scoped test only dependency
[
https://issues.apache.org/jira/browse/MDEP-753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17366010#comment-17366010
]
Sergey Vyacheslavovich Brunov edited comment on MDEP-753 at 6/19/21, 7:51 PM:
--
Dear [~stevenschlansker] and [~elharo],
Recently, I faced the same problem with the upgraded plugin ({{3.2.0}}) and was
going to report it.
{quote}What we really need to fix this is a super simple project that exhibits
the problem suitable for use in an integration test.
{quote}
[~elharo], I have created such a MVCE (Minimal, Complete, and Verifiable
example) project: [maven-dependency-plugin-examples/issues.apache.org/MDEP-753
at master ·
svbrunov/maven-dependency-plugin-examples|https://github.com/svbrunov/maven-dependency-plugin-examples/tree/master/issues.apache.org/MDEP-753].
Please, consider using this project as a starting point.
Please, notice that it seems the problem occurs because the production code
uses one class from Guava, while the test code uses another (different) class
from Guava.
{quote}I would recommend raising the priority of this bug, potentially even to
Blocker, this is a serious regression.
{quote}
I agree with [~stevenschlansker] because it is a serious regression defect.
I had to downgrade the plugin to the {{3.1.2}} version.
Best regards,
Sergey Vyacheslavovich Brunov.
was (Author: sbrunov):
Dear [~stevenschlansker] and [~elharo],
Recently, I faced the same problem with the upgraded plugin ({{3.2.0}}) and was
going to report it.
{quote}What we really need to fix this is a super simple project that exhibits
the problem suitable for use in an integration test.
{quote}
[~elharo], I have created such a MVCE (Minimal, Complete, and Verifiable
example) project: [maven-dependency-plugin-examples/issues.apache.org/MDEP-753
at master ·
svbrunov/maven-dependency-plugin-examples|https://github.com/svbrunov/maven-dependency-plugin-examples/tree/master/issues.apache.org/MDEP-753].
Please, notice that it seems the problem occurs because the production code
uses one class from Guava, while the test code uses another (different) class
from Guava.
{quote}I would recommend raising the priority of this bug, potentially even to
Blocker, this is a serious regression.
{quote}
I agree with [~stevenschlansker] because it is a serious regression defect.
I had to downgrade the plugin to the {{3.1.2}} version.
Best regards,
Sergey Vyacheslavovich Brunov.
> Non-test dependency reported as Non-test scoped test only dependency
>
>
> Key: MDEP-753
> URL: https://issues.apache.org/jira/browse/MDEP-753
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: analyze
>Reporter: Elliotte Rusty Harold
>Priority: Minor
>
> Saw this when updating the google-http-java-client from 3.1.2 to 3.2.0 of the
> plugin. I'm not immediately sure whether this is a regression:
> [INFO] --- maven-dependency-plugin:3.2.0:analyze (default-cli) @
> google-http-client ---
> Warning: Non-test scoped test only dependencies found:
> Warning: com.google.guava:guava:jar:30.1.1-android:compile
> Warning: io.opencensus:opencensus-api:jar:0.28.0:compile
> Changing Guava to scope test breaks the build, which is expected based on the
> code. The warning seems incorrect.
> https://github.com/googleapis/google-http-java-client/pull/1396
> https://github.com/googleapis/google-http-java-client/pull/1396/checks?check_run_id=2809438131
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (MDEP-753) Non-test dependency reported as Non-test scoped test only dependency
[
https://issues.apache.org/jira/browse/MDEP-753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17366010#comment-17366010
]
Sergey Vyacheslavovich Brunov edited comment on MDEP-753 at 6/19/21, 7:55 PM:
--
Dear [~stevenschlansker] and [~elharo],
Recently, I faced the same problem with the upgraded plugin ({{3.2.0}}) and was
going to report it.
{quote}What we really need to fix this is a super simple project that exhibits
the problem suitable for use in an integration test.
{quote}
[~elharo], I have created such a MVCE (Minimal, Complete, and Verifiable
example) project: [maven-dependency-plugin-examples/issues.apache.org/MDEP-753
at master ·
svbrunov/maven-dependency-plugin-examples|https://github.com/svbrunov/maven-dependency-plugin-examples/tree/master/issues.apache.org/MDEP-753].
Please, consider using this project as a starting point.
The build fails with the error message:
{code}
[INFO] --- maven-dependency-plugin:3.2.0:analyze-only (analyze) @ maven-example
---
[INFO] Used declared dependencies found:
[INFO]com.google.guava:guava:jar:30.1.1-jre:compile
[INFO]org.junit.jupiter:junit-jupiter-api:jar:5.8.0-M1:test
[INFO]org.junit.jupiter:junit-jupiter-params:jar:5.8.0-M1:test
[WARNING] Non-test scoped test only dependencies found:
[WARNING]com.google.guava:guava:jar:30.1.1-jre:compile
[INFO]
[INFO] BUILD FAILURE
[INFO]
<…>
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-dependency-plugin:3.2.0:analyze-only (analyze)
on project maven-example: Dependency problems found -> [Help 1]
[ERROR]
{code}
Please, notice that it seems the problem occurs because the production code
uses one class from Guava, while the test code uses another (different) class
from Guava.
{quote}I would recommend raising the priority of this bug, potentially even to
Blocker, this is a serious regression.
{quote}
I agree with [~stevenschlansker] because it is a serious regression defect.
I had to downgrade the plugin to the {{3.1.2}} version.
Best regards,
Sergey Vyacheslavovich Brunov.
was (Author: sbrunov):
Dear [~stevenschlansker] and [~elharo],
Recently, I faced the same problem with the upgraded plugin ({{3.2.0}}) and was
going to report it.
{quote}What we really need to fix this is a super simple project that exhibits
the problem suitable for use in an integration test.
{quote}
[~elharo], I have created such a MVCE (Minimal, Complete, and Verifiable
example) project: [maven-dependency-plugin-examples/issues.apache.org/MDEP-753
at master ·
svbrunov/maven-dependency-plugin-examples|https://github.com/svbrunov/maven-dependency-plugin-examples/tree/master/issues.apache.org/MDEP-753].
Please, consider using this project as a starting point.
The build fails with the error message:
{code}
[INFO] --- maven-dependency-plugin:3.2.0:analyze-only (analyze) @ maven-example
---
[INFO] Used declared dependencies found:
[INFO]com.google.guava:guava:jar:30.1.1-jre:compile
[INFO]org.junit.jupiter:junit-jupiter-api:jar:5.8.0-M1:test
[INFO]org.junit.jupiter:junit-jupiter-params:jar:5.8.0-M1:test
[WARNING] Non-test scoped test only dependencies found:
[WARNING]com.google.guava:guava:jar:30.1.1-jre:compile
[INFO]
[INFO] BUILD FAILURE
[INFO]
{code}
Please, notice that it seems the problem occurs because the production code
uses one class from Guava, while the test code uses another (different) class
from Guava.
{quote}I would recommend raising the priority of this bug, potentially even to
Blocker, this is a serious regression.
{quote}
I agree with [~stevenschlansker] because it is a serious regression defect.
I had to downgrade the plugin to the {{3.1.2}} version.
Best regards,
Sergey Vyacheslavovich Brunov.
> Non-test dependency reported as Non-test scoped test only dependency
>
>
> Key: MDEP-753
> URL: https://issues.apache.org/jira/browse/MDEP-753
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: analyze
>Reporter: Elliotte Rusty Harold
>Priority: Minor
>
> Saw this when updating the google-http-java-client from 3.1.2 to 3.2.0 of the
> plugin. I'm not immediately sure whether this is a regression:
> [INFO] --- maven-dependency-plugin:3.2.0:analyze (default-cli) @
> google-http-client ---
> Warning: Non-test scoped test only dependencies found:
> Warning: com.google.guava:guava:jar:30.1.1-android:compile
> Warning: io.opencensus:opencensus-api:jar:0.28.0:compile
> Changing Guava to
[jira] [Comment Edited] (MDEP-753) Non-test dependency reported as Non-test scoped test only dependency
[
https://issues.apache.org/jira/browse/MDEP-753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17366010#comment-17366010
]
Sergey Vyacheslavovich Brunov edited comment on MDEP-753 at 6/19/21, 7:55 PM:
--
Dear [~stevenschlansker] and [~elharo],
Recently, I faced the same problem with the upgraded plugin ({{3.2.0}}) and was
going to report it.
{quote}What we really need to fix this is a super simple project that exhibits
the problem suitable for use in an integration test.
{quote}
[~elharo], I have created such a MVCE (Minimal, Complete, and Verifiable
example) project: [maven-dependency-plugin-examples/issues.apache.org/MDEP-753
at master ·
svbrunov/maven-dependency-plugin-examples|https://github.com/svbrunov/maven-dependency-plugin-examples/tree/master/issues.apache.org/MDEP-753].
Please, consider using this project as a starting point.
The build fails with the error message:
{code}
[INFO] --- maven-dependency-plugin:3.2.0:analyze-only (analyze) @ maven-example
---
[INFO] Used declared dependencies found:
[INFO]com.google.guava:guava:jar:30.1.1-jre:compile
[INFO]org.junit.jupiter:junit-jupiter-api:jar:5.8.0-M1:test
[INFO]org.junit.jupiter:junit-jupiter-params:jar:5.8.0-M1:test
[WARNING] Non-test scoped test only dependencies found:
[WARNING]com.google.guava:guava:jar:30.1.1-jre:compile
[INFO]
[INFO] BUILD FAILURE
[INFO]
{code}
Please, notice that it seems the problem occurs because the production code
uses one class from Guava, while the test code uses another (different) class
from Guava.
{quote}I would recommend raising the priority of this bug, potentially even to
Blocker, this is a serious regression.
{quote}
I agree with [~stevenschlansker] because it is a serious regression defect.
I had to downgrade the plugin to the {{3.1.2}} version.
Best regards,
Sergey Vyacheslavovich Brunov.
was (Author: sbrunov):
Dear [~stevenschlansker] and [~elharo],
Recently, I faced the same problem with the upgraded plugin ({{3.2.0}}) and was
going to report it.
{quote}What we really need to fix this is a super simple project that exhibits
the problem suitable for use in an integration test.
{quote}
[~elharo], I have created such a MVCE (Minimal, Complete, and Verifiable
example) project: [maven-dependency-plugin-examples/issues.apache.org/MDEP-753
at master ·
svbrunov/maven-dependency-plugin-examples|https://github.com/svbrunov/maven-dependency-plugin-examples/tree/master/issues.apache.org/MDEP-753].
Please, consider using this project as a starting point.
Please, notice that it seems the problem occurs because the production code
uses one class from Guava, while the test code uses another (different) class
from Guava.
{quote}I would recommend raising the priority of this bug, potentially even to
Blocker, this is a serious regression.
{quote}
I agree with [~stevenschlansker] because it is a serious regression defect.
I had to downgrade the plugin to the {{3.1.2}} version.
Best regards,
Sergey Vyacheslavovich Brunov.
> Non-test dependency reported as Non-test scoped test only dependency
>
>
> Key: MDEP-753
> URL: https://issues.apache.org/jira/browse/MDEP-753
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: analyze
>Reporter: Elliotte Rusty Harold
>Priority: Minor
>
> Saw this when updating the google-http-java-client from 3.1.2 to 3.2.0 of the
> plugin. I'm not immediately sure whether this is a regression:
> [INFO] --- maven-dependency-plugin:3.2.0:analyze (default-cli) @
> google-http-client ---
> Warning: Non-test scoped test only dependencies found:
> Warning: com.google.guava:guava:jar:30.1.1-android:compile
> Warning: io.opencensus:opencensus-api:jar:0.28.0:compile
> Changing Guava to scope test breaks the build, which is expected based on the
> code. The warning seems incorrect.
> https://github.com/googleapis/google-http-java-client/pull/1396
> https://github.com/googleapis/google-http-java-client/pull/1396/checks?check_run_id=2809438131
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (MDEP-753) Non-test dependency reported as Non-test scoped test only dependency
[
https://issues.apache.org/jira/browse/MDEP-753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17366010#comment-17366010
]
Sergey Vyacheslavovich Brunov edited comment on MDEP-753 at 6/21/21, 3:54 PM:
--
Dear [~stevenschlansker] and [~elharo],
Recently, I faced the same problem with the upgraded plugin ({{3.2.0}}) and was
going to report it.
{quote}What we really need to fix this is a super simple project that exhibits
the problem suitable for use in an integration test.
{quote}
[~elharo], I have created such a MVCE (Minimal, Complete, and Verifiable
example) project:
* Branch-based link:
[maven-dependency-plugin-examples/issues.apache.org/MDEP-753 at master ·
svbrunov/maven-dependency-plugin-examples|https://github.com/svbrunov/maven-dependency-plugin-examples/tree/master/issues.apache.org/MDEP-753].
* Commit-based link:
[maven-dependency-plugin-examples/issues.apache.org/MDEP-753 at master ·
svbrunov/maven-dependency-plugin-examples](https://github.com/svbrunov/maven-dependency-plugin-examples/tree/60b00691f7720581ba463813a700ba340610fe5b/issues.apache.org/MDEP-753).
Please, consider using this project as a starting point.
The build fails with the error message:
{code}
[INFO] --- maven-dependency-plugin:3.2.0:analyze-only (analyze) @ maven-example
---
[INFO] Used declared dependencies found:
[INFO]com.google.guava:guava:jar:30.1.1-jre:compile
[INFO]org.junit.jupiter:junit-jupiter-api:jar:5.8.0-M1:test
[INFO]org.junit.jupiter:junit-jupiter-params:jar:5.8.0-M1:test
[WARNING] Non-test scoped test only dependencies found:
[WARNING]com.google.guava:guava:jar:30.1.1-jre:compile
[INFO]
[INFO] BUILD FAILURE
[INFO]
<…>
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-dependency-plugin:3.2.0:analyze-only (analyze)
on project maven-example: Dependency problems found -> [Help 1]
[ERROR]
{code}
Please, notice that it seems the problem occurs because the production code
uses one class from Guava, while the test code uses another (different) class
from Guava.
{quote}I would recommend raising the priority of this bug, potentially even to
Blocker, this is a serious regression.
{quote}
I agree with [~stevenschlansker] because it is a serious regression defect.
I had to downgrade the plugin to the {{3.1.2}} version.
Best regards,
Sergey Vyacheslavovich Brunov.
was (Author: sbrunov):
Dear [~stevenschlansker] and [~elharo],
Recently, I faced the same problem with the upgraded plugin ({{3.2.0}}) and was
going to report it.
{quote}What we really need to fix this is a super simple project that exhibits
the problem suitable for use in an integration test.
{quote}
[~elharo], I have created such a MVCE (Minimal, Complete, and Verifiable
example) project: [maven-dependency-plugin-examples/issues.apache.org/MDEP-753
at master ·
svbrunov/maven-dependency-plugin-examples|https://github.com/svbrunov/maven-dependency-plugin-examples/tree/master/issues.apache.org/MDEP-753].
Please, consider using this project as a starting point.
The build fails with the error message:
{code}
[INFO] --- maven-dependency-plugin:3.2.0:analyze-only (analyze) @ maven-example
---
[INFO] Used declared dependencies found:
[INFO]com.google.guava:guava:jar:30.1.1-jre:compile
[INFO]org.junit.jupiter:junit-jupiter-api:jar:5.8.0-M1:test
[INFO]org.junit.jupiter:junit-jupiter-params:jar:5.8.0-M1:test
[WARNING] Non-test scoped test only dependencies found:
[WARNING]com.google.guava:guava:jar:30.1.1-jre:compile
[INFO]
[INFO] BUILD FAILURE
[INFO]
<…>
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-dependency-plugin:3.2.0:analyze-only (analyze)
on project maven-example: Dependency problems found -> [Help 1]
[ERROR]
{code}
Please, notice that it seems the problem occurs because the production code
uses one class from Guava, while the test code uses another (different) class
from Guava.
{quote}I would recommend raising the priority of this bug, potentially even to
Blocker, this is a serious regression.
{quote}
I agree with [~stevenschlansker] because it is a serious regression defect.
I had to downgrade the plugin to the {{3.1.2}} version.
Best regards,
Sergey Vyacheslavovich Brunov.
> Non-test dependency reported as Non-test scoped test only dependency
>
>
> Key: MDEP-753
> URL: https://issues.apache.org/jira/browse/MDEP-753
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: analyze
>Reporter: Elliotte Ru
[jira] [Comment Edited] (MDEP-753) Non-test dependency reported as Non-test scoped test only dependency
[
https://issues.apache.org/jira/browse/MDEP-753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17366010#comment-17366010
]
Sergey Vyacheslavovich Brunov edited comment on MDEP-753 at 6/21/21, 3:55 PM:
--
Dear [~stevenschlansker] and [~elharo],
Recently, I faced the same problem with the upgraded plugin ({{3.2.0}}) and was
going to report it.
{quote}What we really need to fix this is a super simple project that exhibits
the problem suitable for use in an integration test.
{quote}
[~elharo], I have created such a MVCE (Minimal, Complete, and Verifiable
example) project:
* Branch-based link:
[maven-dependency-plugin-examples/issues.apache.org/MDEP-753 at master ·
svbrunov/maven-dependency-plugin-examples|https://github.com/svbrunov/maven-dependency-plugin-examples/tree/master/issues.apache.org/MDEP-753].
* Commit-based link:
[maven-dependency-plugin-examples/issues.apache.org/MDEP-753 at master ·
svbrunov/maven-dependency-plugin-examples|https://github.com/svbrunov/maven-dependency-plugin-examples/tree/60b00691f7720581ba463813a700ba340610fe5b/issues.apache.org/MDEP-753].
Please, consider using this project as a starting point.
The build fails with the error message:
{code}
[INFO] --- maven-dependency-plugin:3.2.0:analyze-only (analyze) @ maven-example
---
[INFO] Used declared dependencies found:
[INFO]com.google.guava:guava:jar:30.1.1-jre:compile
[INFO]org.junit.jupiter:junit-jupiter-api:jar:5.8.0-M1:test
[INFO]org.junit.jupiter:junit-jupiter-params:jar:5.8.0-M1:test
[WARNING] Non-test scoped test only dependencies found:
[WARNING]com.google.guava:guava:jar:30.1.1-jre:compile
[INFO]
[INFO] BUILD FAILURE
[INFO]
<…>
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-dependency-plugin:3.2.0:analyze-only (analyze)
on project maven-example: Dependency problems found -> [Help 1]
[ERROR]
{code}
Please, notice that it seems the problem occurs because the production code
uses one class from Guava, while the test code uses another (different) class
from Guava.
{quote}I would recommend raising the priority of this bug, potentially even to
Blocker, this is a serious regression.
{quote}
I agree with [~stevenschlansker] because it is a serious regression defect.
I had to downgrade the plugin to the {{3.1.2}} version.
Best regards,
Sergey Vyacheslavovich Brunov.
was (Author: sbrunov):
Dear [~stevenschlansker] and [~elharo],
Recently, I faced the same problem with the upgraded plugin ({{3.2.0}}) and was
going to report it.
{quote}What we really need to fix this is a super simple project that exhibits
the problem suitable for use in an integration test.
{quote}
[~elharo], I have created such a MVCE (Minimal, Complete, and Verifiable
example) project:
* Branch-based link:
[maven-dependency-plugin-examples/issues.apache.org/MDEP-753 at master ·
svbrunov/maven-dependency-plugin-examples|https://github.com/svbrunov/maven-dependency-plugin-examples/tree/master/issues.apache.org/MDEP-753].
* Commit-based link:
[maven-dependency-plugin-examples/issues.apache.org/MDEP-753 at master ·
svbrunov/maven-dependency-plugin-examples](https://github.com/svbrunov/maven-dependency-plugin-examples/tree/60b00691f7720581ba463813a700ba340610fe5b/issues.apache.org/MDEP-753).
Please, consider using this project as a starting point.
The build fails with the error message:
{code}
[INFO] --- maven-dependency-plugin:3.2.0:analyze-only (analyze) @ maven-example
---
[INFO] Used declared dependencies found:
[INFO]com.google.guava:guava:jar:30.1.1-jre:compile
[INFO]org.junit.jupiter:junit-jupiter-api:jar:5.8.0-M1:test
[INFO]org.junit.jupiter:junit-jupiter-params:jar:5.8.0-M1:test
[WARNING] Non-test scoped test only dependencies found:
[WARNING]com.google.guava:guava:jar:30.1.1-jre:compile
[INFO]
[INFO] BUILD FAILURE
[INFO]
<…>
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-dependency-plugin:3.2.0:analyze-only (analyze)
on project maven-example: Dependency problems found -> [Help 1]
[ERROR]
{code}
Please, notice that it seems the problem occurs because the production code
uses one class from Guava, while the test code uses another (different) class
from Guava.
{quote}I would recommend raising the priority of this bug, potentially even to
Blocker, this is a serious regression.
{quote}
I agree with [~stevenschlansker] because it is a serious regression defect.
I had to downgrade the plugin to the {{3.1.2}} version.
Best regards,
Sergey Vyacheslavovich Brunov.
> Non-test dependency reported as Non-test scoped test only dependency
> ---
[jira] [Commented] (MDEP-753) Non-test dependency reported as Non-test scoped test only dependency
[
https://issues.apache.org/jira/browse/MDEP-753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17367774#comment-17367774
]
Sergey Vyacheslavovich Brunov commented on MDEP-753:
Dear [~elharo],
{quote}
I've committed a fix for the bug. It now needs a release of the
maven-dependency-analyzer and an upgrade of the maven-dependency-plugin to the
fixed version of the analyzer.
{quote}
This is great.
Could you please provide us with the {{maven-dependency-plugin}} estimated
release date?
Best regards,
Sergey Vyacheslavovich Brunov.
> Non-test dependency reported as Non-test scoped test only dependency
>
>
> Key: MDEP-753
> URL: https://issues.apache.org/jira/browse/MDEP-753
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: analyze
>Reporter: Elliotte Rusty Harold
>Assignee: Elliotte Rusty Harold
>Priority: Minor
>
> Saw this when updating the google-http-java-client from 3.1.2 to 3.2.0 of the
> plugin. I'm not immediately sure whether this is a regression:
> [INFO] --- maven-dependency-plugin:3.2.0:analyze (default-cli) @
> google-http-client ---
> Warning: Non-test scoped test only dependencies found:
> Warning: com.google.guava:guava:jar:30.1.1-android:compile
> Warning: io.opencensus:opencensus-api:jar:0.28.0:compile
> Changing Guava to scope test breaks the build, which is expected based on the
> code. The warning seems incorrect.
> https://github.com/googleapis/google-http-java-client/pull/1396
> https://github.com/googleapis/google-http-java-client/pull/1396/checks?check_run_id=2809438131
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (MDEP-753) Non-test dependency reported as Non-test scoped test only dependency
[
https://issues.apache.org/jira/browse/MDEP-753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17367774#comment-17367774
]
Sergey Vyacheslavovich Brunov edited comment on MDEP-753 at 6/23/21, 6:07 PM:
--
Dear [~elharo],
{quote}
I've committed a fix for the bug. It now needs a release of the
maven-dependency-analyzer and an upgrade of the maven-dependency-plugin to the
fixed version of the analyzer.
{quote}
This is great.
Could you please provide us with the estimated release date of
{{maven-dependency-plugin}}?
Best regards,
Sergey Vyacheslavovich Brunov.
was (Author: sbrunov):
Dear [~elharo],
{quote}
I've committed a fix for the bug. It now needs a release of the
maven-dependency-analyzer and an upgrade of the maven-dependency-plugin to the
fixed version of the analyzer.
{quote}
This is great.
Could you please provide us with the {{maven-dependency-plugin}} estimated
release date?
Best regards,
Sergey Vyacheslavovich Brunov.
> Non-test dependency reported as Non-test scoped test only dependency
>
>
> Key: MDEP-753
> URL: https://issues.apache.org/jira/browse/MDEP-753
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: analyze
>Reporter: Elliotte Rusty Harold
>Assignee: Elliotte Rusty Harold
>Priority: Minor
>
> Saw this when updating the google-http-java-client from 3.1.2 to 3.2.0 of the
> plugin. I'm not immediately sure whether this is a regression:
> [INFO] --- maven-dependency-plugin:3.2.0:analyze (default-cli) @
> google-http-client ---
> Warning: Non-test scoped test only dependencies found:
> Warning: com.google.guava:guava:jar:30.1.1-android:compile
> Warning: io.opencensus:opencensus-api:jar:0.28.0:compile
> Changing Guava to scope test breaks the build, which is expected based on the
> code. The warning seems incorrect.
> https://github.com/googleapis/google-http-java-client/pull/1396
> https://github.com/googleapis/google-http-java-client/pull/1396/checks?check_run_id=2809438131
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (MDEP-753) Non-test dependency reported as Non-test scoped test only dependency
[
https://issues.apache.org/jira/browse/MDEP-753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401817#comment-17401817
]
Sergey Vyacheslavovich Brunov edited comment on MDEP-753 at 8/19/21, 6:44 PM:
--
Dear [~elharo] and [~rfscholte],
As it was highlighted earlier, this defect is critical.
Therefore, it would be great to have it fixed and to release the fixed version.
Could you please provide us with the estimated release date of
{{maven-dependency-plugin}}?
Thank you in advance!
Best regards,
Sergey Vyacheslavovich Brunov.
was (Author: sbrunov):
Dear [~elharo] and [~rfscholte],
As it was highlighted earlier, this defect is critical.
Therefore, it would be great to have it fixed and to release the fixed version.
Could you please provide us with the estimated release date of
{{maven-dependency-plugin}}?
Best regards,
Sergey Vyacheslavovich Brunov.
> Non-test dependency reported as Non-test scoped test only dependency
>
>
> Key: MDEP-753
> URL: https://issues.apache.org/jira/browse/MDEP-753
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: analyze
>Reporter: Elliotte Rusty Harold
>Assignee: Elliotte Rusty Harold
>Priority: Minor
>
> Saw this when updating the google-http-java-client from 3.1.2 to 3.2.0 of the
> plugin. I'm not immediately sure whether this is a regression:
> [INFO] --- maven-dependency-plugin:3.2.0:analyze (default-cli) @
> google-http-client ---
> Warning: Non-test scoped test only dependencies found:
> Warning: com.google.guava:guava:jar:30.1.1-android:compile
> Warning: io.opencensus:opencensus-api:jar:0.28.0:compile
> Changing Guava to scope test breaks the build, which is expected based on the
> code. The warning seems incorrect.
> https://github.com/googleapis/google-http-java-client/pull/1396
> https://github.com/googleapis/google-http-java-client/pull/1396/checks?check_run_id=2809438131
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MDEP-753) Non-test dependency reported as Non-test scoped test only dependency
[
https://issues.apache.org/jira/browse/MDEP-753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401817#comment-17401817
]
Sergey Vyacheslavovich Brunov commented on MDEP-753:
Dear [~elharo] and [~rfscholte],
As it was highlighted earlier, this defect is critical.
Therefore, it would be great to have it fixed and to release the fixed version.
Could you please provide us with the estimated release date of
{{maven-dependency-plugin}}?
Best regards,
Sergey Vyacheslavovich Brunov.
> Non-test dependency reported as Non-test scoped test only dependency
>
>
> Key: MDEP-753
> URL: https://issues.apache.org/jira/browse/MDEP-753
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: analyze
>Reporter: Elliotte Rusty Harold
>Assignee: Elliotte Rusty Harold
>Priority: Minor
>
> Saw this when updating the google-http-java-client from 3.1.2 to 3.2.0 of the
> plugin. I'm not immediately sure whether this is a regression:
> [INFO] --- maven-dependency-plugin:3.2.0:analyze (default-cli) @
> google-http-client ---
> Warning: Non-test scoped test only dependencies found:
> Warning: com.google.guava:guava:jar:30.1.1-android:compile
> Warning: io.opencensus:opencensus-api:jar:0.28.0:compile
> Changing Guava to scope test breaks the build, which is expected based on the
> code. The warning seems incorrect.
> https://github.com/googleapis/google-http-java-client/pull/1396
> https://github.com/googleapis/google-http-java-client/pull/1396/checks?check_run_id=2809438131
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MNG-7038) Introduce public property to point to a root directory of (multi-module) project
[
https://issues.apache.org/jira/browse/MNG-7038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17403024#comment-17403024
]
Sergey Vyacheslavovich Brunov commented on MNG-7038:
To whom it may concern,
The «Project root directory» property is a missing feature.
It would be great to have the built-in support for this property.
Please, see how many different workarounds are used to get it: [Finding the
root directory of a multi module maven reactor project - Stack
Overflow|https://stackoverflow.com/questions/3084629/finding-the-root-directory-of-a-multi-module-maven-reactor-project].
Best regards,
Sergey Vyacheslavovich Brunov.
> Introduce public property to point to a root directory of (multi-module)
> project
>
>
> Key: MNG-7038
> URL: https://issues.apache.org/jira/browse/MNG-7038
> Project: Maven
> Issue Type: Improvement
>Reporter: Envious Guest
>Priority: Major
> Fix For: Issues to be reviewed for 4.x
>
>
> This is a request to expose a property *maven.multiModuleProjectDirectory*
> which is currently internal (or introduce a brand new one with analogous
> functionality).
> * For a single-module project, its value should be same as *project.basedir*
> * For multi-module project, its value should point to a project.basedir of a
> root module
> Example:
> multi-module // located at /home/me/sources
> +- module-a
> +- module B
> Sample multi-module/pom.xml:
> {{}}
> {{ }}
> {{ com.acme}}
> {{ corp-parent}}
> {{ 1.0.0-RELEASE}}
> {{ }}
> {{ com.acme}}
> {{ multi-module}}
> {{ 0.5.2-SNAPSHOT}}
> {{ }}
> {{ module-a}}
> {{ module-b}}
> {{ }}
> {{}}
> The property requested should return /home/me/sources/multi-module,
> regardless of whether it's referenced in any of the child modules (module-a,
> module-b) or in multi-module.
> Note that multi-module itself has parent (e.g. installed in a local
> repository), so the new property should be smart enough to detect it and
> still point to /home/me/sources/multi-module instead of the local repository
> where the corp-parent is installed.
> The use-case for such a property could be to have a directory for combined
> report of static analysis tools. Typical example - jacoco combined coverage
> reports.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (MNG-7038) Introduce public property to point to a root directory of (multi-module) project
[
https://issues.apache.org/jira/browse/MNG-7038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17403024#comment-17403024
]
Sergey Vyacheslavovich Brunov edited comment on MNG-7038 at 8/23/21, 8:17 AM:
--
To whom it may concern,
The «Root project directory path» property is a missing feature.
It would be great to have the built-in support for this property.
Please, see how many different workarounds are used to get it: [Finding the
root directory of a multi module maven reactor project - Stack
Overflow|https://stackoverflow.com/questions/3084629/finding-the-root-directory-of-a-multi-module-maven-reactor-project].
Best regards,
Sergey Vyacheslavovich Brunov.
was (Author: sbrunov):
To whom it may concern,
The «Project root directory» property is a missing feature.
It would be great to have the built-in support for this property.
Please, see how many different workarounds are used to get it: [Finding the
root directory of a multi module maven reactor project - Stack
Overflow|https://stackoverflow.com/questions/3084629/finding-the-root-directory-of-a-multi-module-maven-reactor-project].
Best regards,
Sergey Vyacheslavovich Brunov.
> Introduce public property to point to a root directory of (multi-module)
> project
>
>
> Key: MNG-7038
> URL: https://issues.apache.org/jira/browse/MNG-7038
> Project: Maven
> Issue Type: Improvement
>Reporter: Envious Guest
>Priority: Major
> Fix For: Issues to be reviewed for 4.x
>
>
> This is a request to expose a property *maven.multiModuleProjectDirectory*
> which is currently internal (or introduce a brand new one with analogous
> functionality).
> * For a single-module project, its value should be same as *project.basedir*
> * For multi-module project, its value should point to a project.basedir of a
> root module
> Example:
> multi-module // located at /home/me/sources
> +- module-a
> +- module B
> Sample multi-module/pom.xml:
> {{}}
> {{ }}
> {{ com.acme}}
> {{ corp-parent}}
> {{ 1.0.0-RELEASE}}
> {{ }}
> {{ com.acme}}
> {{ multi-module}}
> {{ 0.5.2-SNAPSHOT}}
> {{ }}
> {{ module-a}}
> {{ module-b}}
> {{ }}
> {{}}
> The property requested should return /home/me/sources/multi-module,
> regardless of whether it's referenced in any of the child modules (module-a,
> module-b) or in multi-module.
> Note that multi-module itself has parent (e.g. installed in a local
> repository), so the new property should be smart enough to detect it and
> still point to /home/me/sources/multi-module instead of the local repository
> where the corp-parent is installed.
> The use-case for such a property could be to have a directory for combined
> report of static analysis tools. Typical example - jacoco combined coverage
> reports.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (MNG-7038) Introduce public property to point to a root directory of (multi-module) project
[
https://issues.apache.org/jira/browse/MNG-7038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17403024#comment-17403024
]
Sergey Vyacheslavovich Brunov edited comment on MNG-7038 at 8/23/21, 8:18 AM:
--
To whom it may concern,
The «Root project directory path» property is missing.
It would be great to have the built-in support for this property.
Please, see how many different workarounds are used to get it: [Finding the
root directory of a multi module maven reactor project - Stack
Overflow|https://stackoverflow.com/questions/3084629/finding-the-root-directory-of-a-multi-module-maven-reactor-project].
Best regards,
Sergey Vyacheslavovich Brunov.
was (Author: sbrunov):
To whom it may concern,
The «Root project directory path» property is a missing feature.
It would be great to have the built-in support for this property.
Please, see how many different workarounds are used to get it: [Finding the
root directory of a multi module maven reactor project - Stack
Overflow|https://stackoverflow.com/questions/3084629/finding-the-root-directory-of-a-multi-module-maven-reactor-project].
Best regards,
Sergey Vyacheslavovich Brunov.
> Introduce public property to point to a root directory of (multi-module)
> project
>
>
> Key: MNG-7038
> URL: https://issues.apache.org/jira/browse/MNG-7038
> Project: Maven
> Issue Type: Improvement
>Reporter: Envious Guest
>Priority: Major
> Fix For: Issues to be reviewed for 4.x
>
>
> This is a request to expose a property *maven.multiModuleProjectDirectory*
> which is currently internal (or introduce a brand new one with analogous
> functionality).
> * For a single-module project, its value should be same as *project.basedir*
> * For multi-module project, its value should point to a project.basedir of a
> root module
> Example:
> multi-module // located at /home/me/sources
> +- module-a
> +- module B
> Sample multi-module/pom.xml:
> {{}}
> {{ }}
> {{ com.acme}}
> {{ corp-parent}}
> {{ 1.0.0-RELEASE}}
> {{ }}
> {{ com.acme}}
> {{ multi-module}}
> {{ 0.5.2-SNAPSHOT}}
> {{ }}
> {{ module-a}}
> {{ module-b}}
> {{ }}
> {{}}
> The property requested should return /home/me/sources/multi-module,
> regardless of whether it's referenced in any of the child modules (module-a,
> module-b) or in multi-module.
> Note that multi-module itself has parent (e.g. installed in a local
> repository), so the new property should be smart enough to detect it and
> still point to /home/me/sources/multi-module instead of the local repository
> where the corp-parent is installed.
> The use-case for such a property could be to have a directory for combined
> report of static analysis tools. Typical example - jacoco combined coverage
> reports.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (MNG-7038) Introduce public property to point to a root directory of (multi-module) project
[
https://issues.apache.org/jira/browse/MNG-7038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17403024#comment-17403024
]
Sergey Vyacheslavovich Brunov edited comment on MNG-7038 at 8/23/21, 8:25 AM:
--
To whom it may concern,
The «Root project directory path» property is missing.
«Root project» means the «topmost» parent project.
It would be great to have the built-in support for this property.
Please, see how many different workarounds are used to get it: [Finding the
root directory of a multi module maven reactor project - Stack
Overflow|https://stackoverflow.com/questions/3084629/finding-the-root-directory-of-a-multi-module-maven-reactor-project].
Best regards,
Sergey Vyacheslavovich Brunov.
was (Author: sbrunov):
To whom it may concern,
The «Root project directory path» property is missing.
It would be great to have the built-in support for this property.
Please, see how many different workarounds are used to get it: [Finding the
root directory of a multi module maven reactor project - Stack
Overflow|https://stackoverflow.com/questions/3084629/finding-the-root-directory-of-a-multi-module-maven-reactor-project].
Best regards,
Sergey Vyacheslavovich Brunov.
> Introduce public property to point to a root directory of (multi-module)
> project
>
>
> Key: MNG-7038
> URL: https://issues.apache.org/jira/browse/MNG-7038
> Project: Maven
> Issue Type: Improvement
>Reporter: Envious Guest
>Priority: Major
> Fix For: Issues to be reviewed for 4.x
>
>
> This is a request to expose a property *maven.multiModuleProjectDirectory*
> which is currently internal (or introduce a brand new one with analogous
> functionality).
> * For a single-module project, its value should be same as *project.basedir*
> * For multi-module project, its value should point to a project.basedir of a
> root module
> Example:
> multi-module // located at /home/me/sources
> +- module-a
> +- module B
> Sample multi-module/pom.xml:
> {{}}
> {{ }}
> {{ com.acme}}
> {{ corp-parent}}
> {{ 1.0.0-RELEASE}}
> {{ }}
> {{ com.acme}}
> {{ multi-module}}
> {{ 0.5.2-SNAPSHOT}}
> {{ }}
> {{ module-a}}
> {{ module-b}}
> {{ }}
> {{}}
> The property requested should return /home/me/sources/multi-module,
> regardless of whether it's referenced in any of the child modules (module-a,
> module-b) or in multi-module.
> Note that multi-module itself has parent (e.g. installed in a local
> repository), so the new property should be smart enough to detect it and
> still point to /home/me/sources/multi-module instead of the local repository
> where the corp-parent is installed.
> The use-case for such a property could be to have a directory for combined
> report of static analysis tools. Typical example - jacoco combined coverage
> reports.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MDEP-753) Non-test dependency reported as Non-test scoped test only dependency
[
https://issues.apache.org/jira/browse/MDEP-753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17411682#comment-17411682
]
Sergey Vyacheslavovich Brunov commented on MDEP-753:
Dear [~rfscholte],
I am sorry to bother you again.
Is there any way to proceed with the {{maven-dependency-plugin}} release?
Maybe some other Maven teammate could take care of it?
Thank you in advance!
Best regards,
Sergey Vyacheslavovich Brunov.
> Non-test dependency reported as Non-test scoped test only dependency
>
>
> Key: MDEP-753
> URL: https://issues.apache.org/jira/browse/MDEP-753
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: analyze
>Reporter: Elliotte Rusty Harold
>Assignee: Elliotte Rusty Harold
>Priority: Minor
>
> Saw this when updating the google-http-java-client from 3.1.2 to 3.2.0 of the
> plugin. I'm not immediately sure whether this is a regression:
> [INFO] --- maven-dependency-plugin:3.2.0:analyze (default-cli) @
> google-http-client ---
> Warning: Non-test scoped test only dependencies found:
> Warning: com.google.guava:guava:jar:30.1.1-android:compile
> Warning: io.opencensus:opencensus-api:jar:0.28.0:compile
> Changing Guava to scope test breaks the build, which is expected based on the
> code. The warning seems incorrect.
> https://github.com/googleapis/google-http-java-client/pull/1396
> https://github.com/googleapis/google-http-java-client/pull/1396/checks?check_run_id=2809438131
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MDEP-753) Non-test dependency reported as Non-test scoped test only dependency
[ https://issues.apache.org/jira/browse/MDEP-753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17413170#comment-17413170 ] Sergey Vyacheslavovich Brunov commented on MDEP-753: Dear [~rfscholte], Thank you for the suggestion! I have used it. Just for the record. Here is the [d...@maven.apache.org mailing list|https://lists.apache.org/list.html?d...@maven.apache.org] thread: [maven-dependency-plugin Release request MDEP-753 Release MDEP-753 changes - Pony Mail|https://lists.apache.org/thread.html/r4324feee5e328c0e1452c68c0d684307c14809667949915b0039a422%40%3Cdev.maven.apache.org%3E]. Best regards, Sergey Vyacheslavovich Brunov. > Non-test dependency reported as Non-test scoped test only dependency > > > Key: MDEP-753 > URL: https://issues.apache.org/jira/browse/MDEP-753 > Project: Maven Dependency Plugin > Issue Type: Bug > Components: analyze >Reporter: Elliotte Rusty Harold >Assignee: Elliotte Rusty Harold >Priority: Minor > > Saw this when updating the google-http-java-client from 3.1.2 to 3.2.0 of the > plugin. I'm not immediately sure whether this is a regression: > [INFO] --- maven-dependency-plugin:3.2.0:analyze (default-cli) @ > google-http-client --- > Warning: Non-test scoped test only dependencies found: > Warning: com.google.guava:guava:jar:30.1.1-android:compile > Warning: io.opencensus:opencensus-api:jar:0.28.0:compile > Changing Guava to scope test breaks the build, which is expected based on the > code. The warning seems incorrect. > https://github.com/googleapis/google-http-java-client/pull/1396 > https://github.com/googleapis/google-http-java-client/pull/1396/checks?check_run_id=2809438131 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (MDEP-753) Non-test dependency reported as Non-test scoped test only dependency
[ https://issues.apache.org/jira/browse/MDEP-753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17413170#comment-17413170 ] Sergey Vyacheslavovich Brunov edited comment on MDEP-753 at 9/10/21, 1:04 PM: -- Dear [~rfscholte], Thank you for the suggestion! I have used it. Just for the record. Here is the [d...@maven.apache.org mailing list|https://lists.apache.org/list.html?d...@maven.apache.org] thread: [\[maven-dependency-plugin\] \[Release request\] \[MDEP-753\] Release MDEP-753 changes - Pony Mail|https://lists.apache.org/thread.html/r4324feee5e328c0e1452c68c0d684307c14809667949915b0039a422%40%3Cdev.maven.apache.org%3E]. Best regards, Sergey Vyacheslavovich Brunov. was (Author: sbrunov): Dear [~rfscholte], Thank you for the suggestion! I have used it. Just for the record. Here is the [d...@maven.apache.org mailing list|https://lists.apache.org/list.html?d...@maven.apache.org] thread: [maven-dependency-plugin Release request MDEP-753 Release MDEP-753 changes - Pony Mail|https://lists.apache.org/thread.html/r4324feee5e328c0e1452c68c0d684307c14809667949915b0039a422%40%3Cdev.maven.apache.org%3E]. Best regards, Sergey Vyacheslavovich Brunov. > Non-test dependency reported as Non-test scoped test only dependency > > > Key: MDEP-753 > URL: https://issues.apache.org/jira/browse/MDEP-753 > Project: Maven Dependency Plugin > Issue Type: Bug > Components: analyze >Reporter: Elliotte Rusty Harold >Assignee: Elliotte Rusty Harold >Priority: Minor > > Saw this when updating the google-http-java-client from 3.1.2 to 3.2.0 of the > plugin. I'm not immediately sure whether this is a regression: > [INFO] --- maven-dependency-plugin:3.2.0:analyze (default-cli) @ > google-http-client --- > Warning: Non-test scoped test only dependencies found: > Warning: com.google.guava:guava:jar:30.1.1-android:compile > Warning: io.opencensus:opencensus-api:jar:0.28.0:compile > Changing Guava to scope test breaks the build, which is expected based on the > code. The warning seems incorrect. > https://github.com/googleapis/google-http-java-client/pull/1396 > https://github.com/googleapis/google-http-java-client/pull/1396/checks?check_run_id=2809438131 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (MDEP-753) Non-test dependency reported as Non-test scoped test only dependency
[
https://issues.apache.org/jira/browse/MDEP-753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17413441#comment-17413441
]
Sergey Vyacheslavovich Brunov edited comment on MDEP-753 at 9/10/21, 11:52 PM:
---
Dear [~rune],
Thank you for replying!
As I mentioned the plugin downgrade in [the above
comment|https://issues.apache.org/jira/browse/MDEP-753?focusedCommentId=17366010&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17366010],
I am still using almost the same (different order of dependencies, but this is
not significant: {{asm}} and {{maven-dependency-analyzer}}) workaround as you.
The workaround works.
All in all, it seems that we have the same situation.
{quote}
Just because I am curious, are there new features you are waiting for in
version >= 3.2.0 of the plugin?
{quote}
I am not blocked, because there is the workaround.
I don't need (wait) any new features in the release.
{quote}
So while I would sure appreciate a new release myself
{quote}
I am requesting the release to address (to start addressing) the technical debt
of my projects:
# The defect is critical.
# The defect is becoming (has already become?) quite long-standing.
Best regards,
Sergey Vyacheslavovich Brunov.
was (Author: sbrunov):
Dear [~rune],
Thank you for replying!
As I mentioned the plugin downgrade in [the above
comment|https://issues.apache.org/jira/browse/MDEP-753?focusedCommentId=17366010&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17366010],
I am still using almost the same (different order of dependencies, but this is
not significant: {{asm}} and {{maven-dependency-analyzer}}) workaround as you.
The workaround works.
All in all, it seems that we have the same situation.
{quote}
Just because I am curious, are there new features you are waiting for in
version >= 3.2.0 of the plugin?
{quote}
I am not blocked, because there is the workaround.
I don't need (wait) any new features in the release.
{quote}
So while I would sure appreciate a new release myself
{quote}
I am requesting the release to address (to start addressing) the technical debt
of my projects:
# The defect is critical.
# The defect is becoming (has become?) quite long-standing.
Best regards,
Sergey Vyacheslavovich Brunov.
> Non-test dependency reported as Non-test scoped test only dependency
>
>
> Key: MDEP-753
> URL: https://issues.apache.org/jira/browse/MDEP-753
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: analyze
>Reporter: Elliotte Rusty Harold
>Assignee: Elliotte Rusty Harold
>Priority: Minor
>
> Saw this when updating the google-http-java-client from 3.1.2 to 3.2.0 of the
> plugin. I'm not immediately sure whether this is a regression:
> [INFO] --- maven-dependency-plugin:3.2.0:analyze (default-cli) @
> google-http-client ---
> Warning: Non-test scoped test only dependencies found:
> Warning: com.google.guava:guava:jar:30.1.1-android:compile
> Warning: io.opencensus:opencensus-api:jar:0.28.0:compile
> Changing Guava to scope test breaks the build, which is expected based on the
> code. The warning seems incorrect.
> https://github.com/googleapis/google-http-java-client/pull/1396
> https://github.com/googleapis/google-http-java-client/pull/1396/checks?check_run_id=2809438131
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MDEP-753) Non-test dependency reported as Non-test scoped test only dependency
[
https://issues.apache.org/jira/browse/MDEP-753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17413441#comment-17413441
]
Sergey Vyacheslavovich Brunov commented on MDEP-753:
Dear [~rune],
Thank you for replying!
As I mentioned the plugin downgrade in [the above
comment|https://issues.apache.org/jira/browse/MDEP-753?focusedCommentId=17366010&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17366010],
I am still using almost the same (different order of dependencies, but this is
not significant: {{asm}} and {{maven-dependency-analyzer}}) workaround as you.
The workaround works.
All in all, it seems that we have the same situation.
{quote}
Just because I am curious, are there new features you are waiting for in
version >= 3.2.0 of the plugin?
{quote}
I am not blocked, because there is the workaround.
I don't need (wait) any new features in the release.
{quote}
So while I would sure appreciate a new release myself
{quote}
I am requesting the release to address (to start addressing) the technical debt
of my projects:
# The defect is critical.
# The defect is becoming (has become?) quite long-standing.
Best regards,
Sergey Vyacheslavovich Brunov.
> Non-test dependency reported as Non-test scoped test only dependency
>
>
> Key: MDEP-753
> URL: https://issues.apache.org/jira/browse/MDEP-753
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: analyze
>Reporter: Elliotte Rusty Harold
>Assignee: Elliotte Rusty Harold
>Priority: Minor
>
> Saw this when updating the google-http-java-client from 3.1.2 to 3.2.0 of the
> plugin. I'm not immediately sure whether this is a regression:
> [INFO] --- maven-dependency-plugin:3.2.0:analyze (default-cli) @
> google-http-client ---
> Warning: Non-test scoped test only dependencies found:
> Warning: com.google.guava:guava:jar:30.1.1-android:compile
> Warning: io.opencensus:opencensus-api:jar:0.28.0:compile
> Changing Guava to scope test breaks the build, which is expected based on the
> code. The warning seems incorrect.
> https://github.com/googleapis/google-http-java-client/pull/1396
> https://github.com/googleapis/google-http-java-client/pull/1396/checks?check_run_id=2809438131
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (MDEP-753) Non-test dependency reported as Non-test scoped test only dependency
[
https://issues.apache.org/jira/browse/MDEP-753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17413441#comment-17413441
]
Sergey Vyacheslavovich Brunov edited comment on MDEP-753 at 9/10/21, 11:53 PM:
---
Dear [~rune],
Thank you for replying!
I mentioned the plugin downgrade in [the above
comment|https://issues.apache.org/jira/browse/MDEP-753?focusedCommentId=17366010&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17366010].
I am still using almost the same (different order of dependencies, but this is
not significant: {{asm}} and {{maven-dependency-analyzer}}) workaround as you.
The workaround works.
All in all, it seems that we have the same situation.
{quote}
Just because I am curious, are there new features you are waiting for in
version >= 3.2.0 of the plugin?
{quote}
I am not blocked, because there is the workaround.
I don't need (wait) any new features in the release.
{quote}
So while I would sure appreciate a new release myself
{quote}
I am requesting the release to address (to start addressing) the technical debt
of my projects:
# The defect is critical.
# The defect is becoming (has already become?) quite long-standing.
Best regards,
Sergey Vyacheslavovich Brunov.
was (Author: sbrunov):
Dear [~rune],
Thank you for replying!
As I mentioned the plugin downgrade in [the above
comment|https://issues.apache.org/jira/browse/MDEP-753?focusedCommentId=17366010&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17366010],
I am still using almost the same (different order of dependencies, but this is
not significant: {{asm}} and {{maven-dependency-analyzer}}) workaround as you.
The workaround works.
All in all, it seems that we have the same situation.
{quote}
Just because I am curious, are there new features you are waiting for in
version >= 3.2.0 of the plugin?
{quote}
I am not blocked, because there is the workaround.
I don't need (wait) any new features in the release.
{quote}
So while I would sure appreciate a new release myself
{quote}
I am requesting the release to address (to start addressing) the technical debt
of my projects:
# The defect is critical.
# The defect is becoming (has already become?) quite long-standing.
Best regards,
Sergey Vyacheslavovich Brunov.
> Non-test dependency reported as Non-test scoped test only dependency
>
>
> Key: MDEP-753
> URL: https://issues.apache.org/jira/browse/MDEP-753
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: analyze
>Reporter: Elliotte Rusty Harold
>Assignee: Elliotte Rusty Harold
>Priority: Minor
>
> Saw this when updating the google-http-java-client from 3.1.2 to 3.2.0 of the
> plugin. I'm not immediately sure whether this is a regression:
> [INFO] --- maven-dependency-plugin:3.2.0:analyze (default-cli) @
> google-http-client ---
> Warning: Non-test scoped test only dependencies found:
> Warning: com.google.guava:guava:jar:30.1.1-android:compile
> Warning: io.opencensus:opencensus-api:jar:0.28.0:compile
> Changing Guava to scope test breaks the build, which is expected based on the
> code. The warning seems incorrect.
> https://github.com/googleapis/google-http-java-client/pull/1396
> https://github.com/googleapis/google-http-java-client/pull/1396/checks?check_run_id=2809438131
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (MDEP-753) Non-test dependency reported as Non-test scoped test only dependency
[
https://issues.apache.org/jira/browse/MDEP-753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17413441#comment-17413441
]
Sergey Vyacheslavovich Brunov edited comment on MDEP-753 at 9/10/21, 11:54 PM:
---
Dear [~rune],
Thank you for replying!
I mentioned the plugin downgrade in [the above
comment|https://issues.apache.org/jira/browse/MDEP-753?focusedCommentId=17366010&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17366010].
I am still using almost the same (different order of dependencies, but this is
not significant: {{asm}} and {{maven-dependency-analyzer}}) workaround as you.
The workaround works.
All in all, it seems that we have the same situation.
{quote}
Just because I am curious, are there new features you are waiting for in
version >= 3.2.0 of the plugin?
{quote}
I am not blocked, because there is the workaround.
I don't need (wait) any new features in the release.
{quote}
So while I would sure appreciate a new release myself
{quote}
I am requesting the release to address (to start addressing) the technical debt
of my Maven projects:
# The defect is critical.
# The defect is becoming (has already become?) quite long-standing.
Best regards,
Sergey Vyacheslavovich Brunov.
was (Author: sbrunov):
Dear [~rune],
Thank you for replying!
I mentioned the plugin downgrade in [the above
comment|https://issues.apache.org/jira/browse/MDEP-753?focusedCommentId=17366010&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17366010].
I am still using almost the same (different order of dependencies, but this is
not significant: {{asm}} and {{maven-dependency-analyzer}}) workaround as you.
The workaround works.
All in all, it seems that we have the same situation.
{quote}
Just because I am curious, are there new features you are waiting for in
version >= 3.2.0 of the plugin?
{quote}
I am not blocked, because there is the workaround.
I don't need (wait) any new features in the release.
{quote}
So while I would sure appreciate a new release myself
{quote}
I am requesting the release to address (to start addressing) the technical debt
of my projects:
# The defect is critical.
# The defect is becoming (has already become?) quite long-standing.
Best regards,
Sergey Vyacheslavovich Brunov.
> Non-test dependency reported as Non-test scoped test only dependency
>
>
> Key: MDEP-753
> URL: https://issues.apache.org/jira/browse/MDEP-753
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: analyze
>Reporter: Elliotte Rusty Harold
>Assignee: Elliotte Rusty Harold
>Priority: Minor
>
> Saw this when updating the google-http-java-client from 3.1.2 to 3.2.0 of the
> plugin. I'm not immediately sure whether this is a regression:
> [INFO] --- maven-dependency-plugin:3.2.0:analyze (default-cli) @
> google-http-client ---
> Warning: Non-test scoped test only dependencies found:
> Warning: com.google.guava:guava:jar:30.1.1-android:compile
> Warning: io.opencensus:opencensus-api:jar:0.28.0:compile
> Changing Guava to scope test breaks the build, which is expected based on the
> code. The warning seems incorrect.
> https://github.com/googleapis/google-http-java-client/pull/1396
> https://github.com/googleapis/google-http-java-client/pull/1396/checks?check_run_id=2809438131
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (MDEP-753) Non-test dependency reported as Non-test scoped test only dependency
[
https://issues.apache.org/jira/browse/MDEP-753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17413441#comment-17413441
]
Sergey Vyacheslavovich Brunov edited comment on MDEP-753 at 9/10/21, 11:56 PM:
---
Dear [~rune],
Thank you for replying!
I mentioned the plugin downgrade in [the above
comment|https://issues.apache.org/jira/browse/MDEP-753?focusedCommentId=17366010&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17366010].
I am still using almost the same (different order of dependencies, but this is
not significant: {{asm}} and {{maven-dependency-analyzer}}) workaround as you.
The workaround works.
All in all, it seems that we have the same situation.
{quote}
Just because I am curious, are there new features you are waiting for in
version >= 3.2.0 of the plugin?
{quote}
I am not blocked, because there is the workaround.
I don't need (wait) any new features in the release.
{quote}
So while I would sure appreciate a new release myself
{quote}
I have requested the release to address (to start addressing) the technical
debt of my Maven projects:
# The defect is critical.
# The defect is becoming (has already become?) quite long-standing.
Best regards,
Sergey Vyacheslavovich Brunov.
was (Author: sbrunov):
Dear [~rune],
Thank you for replying!
I mentioned the plugin downgrade in [the above
comment|https://issues.apache.org/jira/browse/MDEP-753?focusedCommentId=17366010&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17366010].
I am still using almost the same (different order of dependencies, but this is
not significant: {{asm}} and {{maven-dependency-analyzer}}) workaround as you.
The workaround works.
All in all, it seems that we have the same situation.
{quote}
Just because I am curious, are there new features you are waiting for in
version >= 3.2.0 of the plugin?
{quote}
I am not blocked, because there is the workaround.
I don't need (wait) any new features in the release.
{quote}
So while I would sure appreciate a new release myself
{quote}
I am requesting the release to address (to start addressing) the technical debt
of my Maven projects:
# The defect is critical.
# The defect is becoming (has already become?) quite long-standing.
Best regards,
Sergey Vyacheslavovich Brunov.
> Non-test dependency reported as Non-test scoped test only dependency
>
>
> Key: MDEP-753
> URL: https://issues.apache.org/jira/browse/MDEP-753
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: analyze
>Reporter: Elliotte Rusty Harold
>Assignee: Elliotte Rusty Harold
>Priority: Minor
>
> Saw this when updating the google-http-java-client from 3.1.2 to 3.2.0 of the
> plugin. I'm not immediately sure whether this is a regression:
> [INFO] --- maven-dependency-plugin:3.2.0:analyze (default-cli) @
> google-http-client ---
> Warning: Non-test scoped test only dependencies found:
> Warning: com.google.guava:guava:jar:30.1.1-android:compile
> Warning: io.opencensus:opencensus-api:jar:0.28.0:compile
> Changing Guava to scope test breaks the build, which is expected based on the
> code. The warning seems incorrect.
> https://github.com/googleapis/google-http-java-client/pull/1396
> https://github.com/googleapis/google-http-java-client/pull/1396/checks?check_run_id=2809438131
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (MDEP-753) Non-test dependency reported as Non-test scoped test only dependency
[
https://issues.apache.org/jira/browse/MDEP-753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17413441#comment-17413441
]
Sergey Vyacheslavovich Brunov edited comment on MDEP-753 at 9/11/21, 1:28 AM:
--
Dear [~rune],
Thank you for replying!
I mentioned the plugin downgrade in [the above
comment|https://issues.apache.org/jira/browse/MDEP-753?focusedCommentId=17366010&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17366010].
I am still using almost the same (different order of dependencies, but this is
not significant: {{asm}} and {{maven-dependency-analyzer}}) workaround as you.
The workaround works.
All in all, it seems that we have the same situation.
{quote}
Just because I am curious, are there new features you are waiting for in
version >= 3.2.0 of the plugin?
{quote}
I don't need (wait) any new features in the release.
{quote}
So while I would sure appreciate a new release myself, there is nothing
blocking us from using the previous version 3.1.2 until it happens.
{quote}
I am not blocked, because there is the workaround.
I have requested the release to address (to start addressing) the technical
debt of my Maven projects:
# The defect is critical.
# The defect is becoming (has already become?) quite long-standing.
Best regards,
Sergey Vyacheslavovich Brunov.
was (Author: sbrunov):
Dear [~rune],
Thank you for replying!
I mentioned the plugin downgrade in [the above
comment|https://issues.apache.org/jira/browse/MDEP-753?focusedCommentId=17366010&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17366010].
I am still using almost the same (different order of dependencies, but this is
not significant: {{asm}} and {{maven-dependency-analyzer}}) workaround as you.
The workaround works.
All in all, it seems that we have the same situation.
{quote}
Just because I am curious, are there new features you are waiting for in
version >= 3.2.0 of the plugin?
{quote}
I am not blocked, because there is the workaround.
I don't need (wait) any new features in the release.
{quote}
So while I would sure appreciate a new release myself
{quote}
I have requested the release to address (to start addressing) the technical
debt of my Maven projects:
# The defect is critical.
# The defect is becoming (has already become?) quite long-standing.
Best regards,
Sergey Vyacheslavovich Brunov.
> Non-test dependency reported as Non-test scoped test only dependency
>
>
> Key: MDEP-753
> URL: https://issues.apache.org/jira/browse/MDEP-753
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: analyze
>Reporter: Elliotte Rusty Harold
>Assignee: Elliotte Rusty Harold
>Priority: Minor
>
> Saw this when updating the google-http-java-client from 3.1.2 to 3.2.0 of the
> plugin. I'm not immediately sure whether this is a regression:
> [INFO] --- maven-dependency-plugin:3.2.0:analyze (default-cli) @
> google-http-client ---
> Warning: Non-test scoped test only dependencies found:
> Warning: com.google.guava:guava:jar:30.1.1-android:compile
> Warning: io.opencensus:opencensus-api:jar:0.28.0:compile
> Changing Guava to scope test breaks the build, which is expected based on the
> code. The warning seems incorrect.
> https://github.com/googleapis/google-http-java-client/pull/1396
> https://github.com/googleapis/google-http-java-client/pull/1396/checks?check_run_id=2809438131
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (MDEP-753) Non-test dependency reported as Non-test scoped test only dependency
[
https://issues.apache.org/jira/browse/MDEP-753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17413441#comment-17413441
]
Sergey Vyacheslavovich Brunov edited comment on MDEP-753 at 9/11/21, 1:43 AM:
--
Dear [~rune],
Thank you for replying!
I mentioned the plugin downgrade in [the above
comment|https://issues.apache.org/jira/browse/MDEP-753?focusedCommentId=17366010&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17366010].
I am still using almost the same workaround as you: exactly the same versions
of the {{asm}} and {{maven-dependency-analyzer}} dependencies that you
mentioned.
The workaround works.
All in all, it seems that we have the same situation.
{quote}
Just because I am curious, are there new features you are waiting for in
version >= 3.2.0 of the plugin?
{quote}
I don't need (wait) any new features in the release.
{quote}
So while I would sure appreciate a new release myself, there is nothing
blocking us from using the previous version 3.1.2 until it happens.
{quote}
I am not blocked, because there is the workaround.
I have requested the release to address (to start addressing) the technical
debt of my Maven projects:
# The defect is critical.
# The defect is becoming (has already become?) quite long-standing.
Best regards,
Sergey Vyacheslavovich Brunov.
was (Author: sbrunov):
Dear [~rune],
Thank you for replying!
I mentioned the plugin downgrade in [the above
comment|https://issues.apache.org/jira/browse/MDEP-753?focusedCommentId=17366010&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17366010].
I am still using almost the same (different order of dependencies, but this is
not significant: {{asm}} and {{maven-dependency-analyzer}}) workaround as you.
The workaround works.
All in all, it seems that we have the same situation.
{quote}
Just because I am curious, are there new features you are waiting for in
version >= 3.2.0 of the plugin?
{quote}
I don't need (wait) any new features in the release.
{quote}
So while I would sure appreciate a new release myself, there is nothing
blocking us from using the previous version 3.1.2 until it happens.
{quote}
I am not blocked, because there is the workaround.
I have requested the release to address (to start addressing) the technical
debt of my Maven projects:
# The defect is critical.
# The defect is becoming (has already become?) quite long-standing.
Best regards,
Sergey Vyacheslavovich Brunov.
> Non-test dependency reported as Non-test scoped test only dependency
>
>
> Key: MDEP-753
> URL: https://issues.apache.org/jira/browse/MDEP-753
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: analyze
>Reporter: Elliotte Rusty Harold
>Assignee: Elliotte Rusty Harold
>Priority: Minor
>
> Saw this when updating the google-http-java-client from 3.1.2 to 3.2.0 of the
> plugin. I'm not immediately sure whether this is a regression:
> [INFO] --- maven-dependency-plugin:3.2.0:analyze (default-cli) @
> google-http-client ---
> Warning: Non-test scoped test only dependencies found:
> Warning: com.google.guava:guava:jar:30.1.1-android:compile
> Warning: io.opencensus:opencensus-api:jar:0.28.0:compile
> Changing Guava to scope test breaks the build, which is expected based on the
> code. The warning seems incorrect.
> https://github.com/googleapis/google-http-java-client/pull/1396
> https://github.com/googleapis/google-http-java-client/pull/1396/checks?check_run_id=2809438131
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (MDEP-753) Non-test dependency reported as Non-test scoped test only dependency
[
https://issues.apache.org/jira/browse/MDEP-753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17413441#comment-17413441
]
Sergey Vyacheslavovich Brunov edited comment on MDEP-753 at 9/18/21, 12:50 AM:
---
Dear [~rune],
Thank you for replying!
I mentioned the plugin downgrade in [the above
comment|https://issues.apache.org/jira/browse/MDEP-753?focusedCommentId=17366010&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17366010].
I am still using almost the same workaround as you: exactly the same versions
of the {{asm}} and {{maven-dependency-analyzer}} dependencies that you
mentioned.
The workaround works.
All in all, it seems that we have the same situation.
{quote}
Just because I am curious, are there new features you are waiting for in
version >= 3.2.0 of the plugin?
{quote}
I don't need (wait) any new features in the release.
{quote}
So while I would sure appreciate a new release myself, there is nothing
blocking us from using the previous version 3.1.2 until it happens.
{quote}
I am not blocked, because there is the workaround.
I have requested the release to address (to start addressing) the technical
debt of my Maven projects:
# The defect is critical.
# The defect has become quite long-standing.
Best regards,
Sergey Vyacheslavovich Brunov.
was (Author: sbrunov):
Dear [~rune],
Thank you for replying!
I mentioned the plugin downgrade in [the above
comment|https://issues.apache.org/jira/browse/MDEP-753?focusedCommentId=17366010&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17366010].
I am still using almost the same workaround as you: exactly the same versions
of the {{asm}} and {{maven-dependency-analyzer}} dependencies that you
mentioned.
The workaround works.
All in all, it seems that we have the same situation.
{quote}
Just because I am curious, are there new features you are waiting for in
version >= 3.2.0 of the plugin?
{quote}
I don't need (wait) any new features in the release.
{quote}
So while I would sure appreciate a new release myself, there is nothing
blocking us from using the previous version 3.1.2 until it happens.
{quote}
I am not blocked, because there is the workaround.
I have requested the release to address (to start addressing) the technical
debt of my Maven projects:
# The defect is critical.
# The defect is becoming (has already become?) quite long-standing.
Best regards,
Sergey Vyacheslavovich Brunov.
> Non-test dependency reported as Non-test scoped test only dependency
>
>
> Key: MDEP-753
> URL: https://issues.apache.org/jira/browse/MDEP-753
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: analyze
>Reporter: Elliotte Rusty Harold
>Assignee: Elliotte Rusty Harold
>Priority: Minor
>
> Saw this when updating the google-http-java-client from 3.1.2 to 3.2.0 of the
> plugin. I'm not immediately sure whether this is a regression:
> [INFO] --- maven-dependency-plugin:3.2.0:analyze (default-cli) @
> google-http-client ---
> Warning: Non-test scoped test only dependencies found:
> Warning: com.google.guava:guava:jar:30.1.1-android:compile
> Warning: io.opencensus:opencensus-api:jar:0.28.0:compile
> Changing Guava to scope test breaks the build, which is expected based on the
> code. The warning seems incorrect.
> https://github.com/googleapis/google-http-java-client/pull/1396
> https://github.com/googleapis/google-http-java-client/pull/1396/checks?check_run_id=2809438131
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MDEP-753) Non-test dependency reported as Non-test scoped test only dependency
[
https://issues.apache.org/jira/browse/MDEP-753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17491670#comment-17491670
]
Sergey Vyacheslavovich Brunov commented on MDEP-753:
Dear [~mirabilos],
{quote}
[~sbrunov] how did you create the box for the preformatted output? Mine ↑ here
looks awful ☹
{quote}
It seems that you have already found how to do it.
Answering for the sake of completeness.
To make a block of source code preformatted, surround it with \{code\}.
Best regards,
Sergey Vyacheslavovich Brunov.
> Non-test dependency reported as Non-test scoped test only dependency
>
>
> Key: MDEP-753
> URL: https://issues.apache.org/jira/browse/MDEP-753
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: analyze
>Affects Versions: 3.2.0
>Reporter: Elliotte Rusty Harold
>Assignee: Elliotte Rusty Harold
>Priority: Critical
> Fix For: 3.3.0
>
> Attachments: chas.zip, tj.zip
>
>
> Saw this when updating the google-http-java-client from 3.1.2 to 3.2.0 of the
> plugin. I'm not immediately sure whether this is a regression:
> [INFO] --- maven-dependency-plugin:3.2.0:analyze (default-cli) @
> google-http-client ---
> Warning: Non-test scoped test only dependencies found:
> Warning: com.google.guava:guava:jar:30.1.1-android:compile
> Warning: io.opencensus:opencensus-api:jar:0.28.0:compile
> Changing Guava to scope test breaks the build, which is expected based on the
> code. The warning seems incorrect.
> https://github.com/googleapis/google-http-java-client/pull/1396
> https://github.com/googleapis/google-http-java-client/pull/1396/checks?check_run_id=2809438131
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Comment Edited] (MDEP-753) Non-test dependency reported as Non-test scoped test only dependency
[
https://issues.apache.org/jira/browse/MDEP-753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17491670#comment-17491670
]
Sergey Vyacheslavovich Brunov edited comment on MDEP-753 at 2/13/22, 7:19 PM:
--
Dear [~mirabilos],
{quote}
[~sbrunov] how did you create the box for the preformatted output? Mine ↑ here
looks awful ☹
{quote}
It seems that you have already found how to do it.
Answering for the sake of completeness.
To make a block of source code preformatted, surround it with \{code\}.
For additional details, please, refer to the page: [Text Formatting Notation
Help - ASF
JIRA|https://issues.apache.org/jira/secure/WikiRendererHelpAction.jspa?section=all].
Best regards,
Sergey Vyacheslavovich Brunov.
was (Author: sbrunov):
Dear [~mirabilos],
{quote}
[~sbrunov] how did you create the box for the preformatted output? Mine ↑ here
looks awful ☹
{quote}
It seems that you have already found how to do it.
Answering for the sake of completeness.
To make a block of source code preformatted, surround it with \{code\}.
Best regards,
Sergey Vyacheslavovich Brunov.
> Non-test dependency reported as Non-test scoped test only dependency
>
>
> Key: MDEP-753
> URL: https://issues.apache.org/jira/browse/MDEP-753
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: analyze
>Affects Versions: 3.2.0
>Reporter: Elliotte Rusty Harold
>Assignee: Elliotte Rusty Harold
>Priority: Critical
> Fix For: 3.3.0
>
> Attachments: chas.zip, tj.zip
>
>
> Saw this when updating the google-http-java-client from 3.1.2 to 3.2.0 of the
> plugin. I'm not immediately sure whether this is a regression:
> [INFO] --- maven-dependency-plugin:3.2.0:analyze (default-cli) @
> google-http-client ---
> Warning: Non-test scoped test only dependencies found:
> Warning: com.google.guava:guava:jar:30.1.1-android:compile
> Warning: io.opencensus:opencensus-api:jar:0.28.0:compile
> Changing Guava to scope test breaks the build, which is expected based on the
> code. The warning seems incorrect.
> https://github.com/googleapis/google-http-java-client/pull/1396
> https://github.com/googleapis/google-http-java-client/pull/1396/checks?check_run_id=2809438131
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Comment Edited] (MDEP-693) `dependency:analyze-only` goal fails on OpenJDK 14
[
https://issues.apache.org/jira/browse/MDEP-693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17304025#comment-17304025
]
Sergey Vyacheslavovich Brunov edited comment on MDEP-693 at 2/20/22, 8:18 PM:
--
h1. Solution
1. Upgrade the {{org.ow2.asm:asm}} Maven dependency version to at least 9.0.
Upgraded to the 9.1 version that as per [its release
notes|https://asm.ow2.io/versions.html] introduced the JDK 17 support.
2. Upgrade the {{org.apache.maven.shared:maven-dependency-analyzer}} Maven
dependency version to at least 1.11.3. Already upgraded.
h1. Pull request
1. [[MDEP-693] - `dependency:analyze-only` goal fails on OpenJDK 14 by sbrunov
· Pull Request #129 ·
apache/maven-dependency-plugin|https://github.com/apache/maven-dependency-plugin/pull/129].
h1. Release request
Could you please release the new version of the {{maven-dependency-plugin}},
once the pull request has been merged?
Best regards,
Sergey Vyacheslavovich Brunov.
was (Author: sbrunov):
h1. Solution
1. Upgrade the {{org.ow2.asm:asm}} Maven dependency version to at least 9.0.
Upgraded to the 9.1 version that as per [its release
notes|https://asm.ow2.io/versions.html] introduced the JDK 17 support.
2. Upgrade the {{org.apache.maven.shared:maven-dependency-analyzer}} Maven
dependency version to at least 1.11.3. Already upgraded.
h1. Pull request
1. [[MDEP-693] - `dependency:analyze-only` goal fails on OpenJDK 14 by sbrunov
· Pull Request #129 ·
apache/maven-dependency-plugin|https://github.com/apache/maven-dependency-plugin/pull/129].
h1. Request for release
Could you please release the new version of the {{maven-dependency-plugin}},
once the pull request has been merged?
Best regards,
Sergey Vyacheslavovich Brunov.
> `dependency:analyze-only` goal fails on OpenJDK 14
> --
>
> Key: MDEP-693
> URL: https://issues.apache.org/jira/browse/MDEP-693
> Project: Maven Dependency Plugin
> Issue Type: Bug
>Affects Versions: 3.1.2
> Environment: OpenJDK Runtime Environment (build 14.0.1+7-Debian-1)
> Apache Maven 3.6.3
> Maven Dependency Plugin 3.1.2
>Reporter: Sergey Vyacheslavovich Brunov
>Assignee: Sylwester Lachiewicz
>Priority: Major
> Fix For: 3.2.0
>
>
> h1. Environment
> h2. Java
> {code}
> $ java -version
> openjdk version "14.0.1" 2020-04-14
> OpenJDK Runtime Environment (build 14.0.1+7-Debian-1)
> OpenJDK 64-Bit Server VM (build 14.0.1+7-Debian-1, mixed mode, sharing)
> {code}
> h2. Maven
> {code}
> $ mvn --version
> Apache Maven 3.6.3
> Maven home: /usr/share/maven
> Java version: 14.0.1, vendor: Debian, runtime:
> /usr/lib/jvm/java-14-openjdk-amd64
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "5.6.0-1-amd64", arch: "amd64", family: "unix"
> {code}
> h2. Maven Dependency Plugin
> {code:xml}
>
> org.apache.maven.plugins
> maven-dependency-plugin
> 3.1.2
>
>
> analyze
>
> analyze-only
>
>
> true
> true
>
>
>
>
> {code}
> h1. Problem
> When running the {{dependency:analyze-only}} goal on a JDK 14 project that
> uses the «Java Records» feature ([JEP 359: Records
> (Preview)|https://openjdk.java.net/jeps/359]), the goal fails with the
> following error:
> {code}
> $ mvn clean install -X
> <...>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-dependency-plugin:3.1.2:analyze-only (analyze)
> on project the-maven-project: Execution analyze of goal
> org.apache.maven.plugins:maven-dependency-plugin:3.1.2:analyze-only failed:
> This feature requires ASM8_EXPERIMENTAL -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-dependency-plugin:3.1.2:analyze-only
> (analyze) on project the-maven-project: Execution analyze of goal
> org.apache.maven.plugins:maven-dependency-plugin:3.1.2:analyze-only failed:
> This feature requires ASM8_EXPERIMENTAL
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:215)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:156)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:148)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:56)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleSta
