[ 
https://issues.apache.org/jira/browse/MDEP-780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17470937#comment-17470937
 ] 

Thorsten Glaser edited comment on MDEP-780 at 1/7/22, 11:03 PM:
----------------------------------------------------------------

Thanks [~mttjj] it is… WTF‽ This bug is {*}critical{*}, known for {*}seven 
months{*}, has had an MWE for an it {+}five days later{+}, has had an 
{+}apparent *fix another two days later* (seven _days_ after the report){+}, 
has *several dozen* votes and even more watchers, and is still unfixed‽


was (Author: mirabilos):
Thanks [~mttjj] it is… WTF‽ This bug is {*}critical{*}, known for {*}seven 
months{*}, has had an MWE for an it {+}five days later{+}, has had an 
{+}apparent *fix another two days later* (seven _days_ after the report){+}, 
and is still unfixed‽

> “Non-test scoped test only dependencies found” false-positive in 3.2.0/1.11.2
> -----------------------------------------------------------------------------
>
>                 Key: MDEP-780
>                 URL: https://issues.apache.org/jira/browse/MDEP-780
>             Project: Maven Dependency Plugin
>          Issue Type: Bug
>    Affects Versions: 3.2.0
>            Reporter: Thorsten Glaser
>            Priority: Critical
>
> After upgrading maven-dependency-plugin 3.1.2 → 3.2.0 I get the following 
> false positives in [a 
> project|https://evolvis.org/plugins/scmgit/cgi-bin/gitweb.cgi?p=tartools/extract-tool.git]:
> {{[WARNING] Non-test scoped test only dependencies found:}}
> {{[WARNING]    org.springframework:spring-jdbc:jar:4.3.30.RELEASE:compile}}
> This isn’t right, and with spring-jdbc scoped to test, the project doesn’t 
> even compile.
> This also applies if I dowgrade the Maven dependency analyser to 1.11.2 [as 
> in this 
> commit|https://evolvis.org/plugins/scmgit/cgi-bin/gitweb.cgi?p=tartools/extract-tool.git;a=commitdiff;h=d2b923304b6d2dfd2f52186d17843c492e4f5957];
>  I cannot test with 1.11.1 (same version maven-dependency-plugin 3.1.2 used) 
> because that’s incompatible with 3.2.0 so I cannot say for sure which of the 
> two introduced this bug. If this is a bug in the shared component, please 
> reassign appropriately.
> I’m setting the severity as it is because this effectively prevents me from 
> upgrading past 3.1.2 in my projects.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to