maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karl Heinz Marbaise (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MNG-6511) Option -pl ! foo should not fail if foo does not exist
Date Sat, 10 Nov 2018 07:24:00 GMT

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

Karl Heinz Marbaise commented on MNG-6511:
------------------------------------------

I'm not sure if I understand your problem but the {{-pl}} option does not have a negation
{code}
 -pl,--projects <arg>                   Comma-delimited list of specified
                                        reactor projects to build instead
                                        of all projects. A project can be
                                        specified by [groupId]:artifactId
                                        or by its relative path
{code}
Apart from the negation. If a given project is not part of the reactor it must fail...?

> 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)

Mime
View raw message