[
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)
