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