[jira] [Resolved] (MNG-6511) Option -pl ! foo should not fail if foo does not exist

["Maarten Mulders (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MNG-6511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maarten Mulders resolved MNG-6511.
----------------------------------
    Fix Version/s: 4.0.0-alpha-1
                   4.0.0
       Resolution: Fixed

Fixed in [c3cf2943|https://github.com/apache/maven/commit/c3cf29438e3d65d6ee5c5726f8611af99d9a649a] with integration test in [9be9c249|https://github.com/apache/maven-integration-testing/commit/9be9c24999bfca177efdc5881b149a487ef5d6fc].

> Option -pl ! foo should not fail if foo does not exist
> ------------------------------------------------------
>
>                 Key: MNG-6511
>                 URL: https://issues.apache.org/jira/browse/MNG-6511
>             Project: Maven
>          Issue Type: Improvement
>          Components: Command Line
>    Affects Versions: 3.3.9, 3.6.0
>            Reporter: Falko Modler
>            Assignee: Martin Kanters
>            Priority: Major
>             Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> While I completely understand why Maven throws an error when {{\-pl/--projects}} defines/contains a non-existing project, I don't really see why the negation of a non-existing project yields the same error, e.g.:
> {noformat}
> c:\_dev\git\gitflow-incremental-builder>mvn -pl !foo
> [INFO] Scanning for projects...
> [ERROR] [ERROR] Could not find the selected project in the reactor: foo @
> [ERROR] Could not find the selected project in the reactor: foo -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MavenExecutionException
> {noformat}
> I'd say that at most this should be a warning, not an error.
> This change would come in handy to reuse scripts with certain default options (e.g. quickly build everything without tests, checkstyle, _exclude moduleX_, etc.) on different hierarchy levels of larger multi module project.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)