[
https://issues.apache.org/jira/browse/MNG-6511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16682526#comment-16682526
]
Robert Scholte commented on MNG-6511:
-------------------------------------
It is likely we have to disappoint somebody with any decision. In general that
means strict is better to match the expected result.
However, I think there are already some options available that can help.
Since it seems you're already using scripts, maybe mavenrc is an option or the
Maven Project options introduced with
[MNG-5767|https://issues.apache.org/jira/browse/MNG-5767] which seems to be
porely documented.
Maybe there are other options. If your wish is like "If only I could make the
project-list argument less strict", I would actually think of Maven Extensions.
It will be a customized solution that needs to be implemented, but so should
any other solution.
> 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
> Affects Versions: 3.3.9, 3.6.0
> Reporter: Falko Modler
> Priority: Major
>
> 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
(v7.6.3#76005)
