[jira] [Commented] (MNG-7492) Invalid POMs are blithefully ignored

["Michael Osipov (Jira)" <ji...@apache.org>]

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

Michael Osipov commented on MNG-7492:
-------------------------------------

Still waiting...

> Invalid POMs are blithefully ignored
> ------------------------------------
>
>                 Key: MNG-7492
>                 URL: https://issues.apache.org/jira/browse/MNG-7492
>             Project: Maven
>          Issue Type: Improvement
>          Components: Dependencies
>    Affects Versions: 3.6.3
>            Reporter: Robert Krajewski
>            Priority: Major
>              Labels: dependency, invalid, model, transitive
>             Fix For: waiting-for-feedback, wontfix-candidate
>
>
> Invalid poms prevent construction of the model's dependencies tree (and thus the model itself) and yet are only warnings:
> {{[WARNING] Invalid POM xxxx, transitive dependencies (if any) will not be available, enable debug logging for more details}}
> Once this happens, Java compiler errors often ensue and are completely mysterious. Debug logging will tell you why the POM is missing, but it doesn't stop a nonsensical model from being treated as valid. Which it's {*}not{*}.
> See https://stackoverflow.com/questions/59944898/fail-on-invalid-or-missing-poms for a discussion. Workarounds don't fix the issue.
> Please implement an option to make this situation fail the build in Maven 3. Even better, make it the default in a future version like Maven 4.
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)