You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Sylwester Lachiewicz (JIRA)" <ji...@apache.org> on 2019/01/14 00:02:00 UTC
[jira] [Closed] (MNG-6060) better and precise error reporting when
project is not found e.g. with -rf option
[ https://issues.apache.org/jira/browse/MNG-6060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sylwester Lachiewicz closed MNG-6060.
-------------------------------------
Resolution: Not A Problem
> better and precise error reporting when project is not found e.g. with -rf option
> ---------------------------------------------------------------------------------
>
> Key: MNG-6060
> URL: https://issues.apache.org/jira/browse/MNG-6060
> Project: Maven
> Issue Type: Improvement
> Components: Command Line, Errors, POM, Reactor and workspace
> Affects Versions: 3.3.9
> Environment: Linux 4.6.2 with Oracle JDK 8
> Reporter: Gregor B. Rosenauer
> Priority: Trivial
> Labels: maven
>
> when building a multi-module project with -rf and the project is not found, Maven explodes all over your face and prints the *entire* POM instead of just pointing out the missing project - it does, but hides it before the POM dump so the info is easily lost:
> {{[ERROR] [ERROR] Could not find project to resume reactor build from: :missing-in-action vs [MavenProject: (entire POM dumped here)}}
> Good old make would just tell you this precise and helpful message, instead of dumping the entire makefile:
> {{make: *** No rule to make target 'some-nonexisting-target'. Stop.}}
> Please make maven a bit more user friendly when reporting errors...
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)