[jira] [Updated] (MNG-6511) Option -pl ! foo should not fail if foo does not exist
[ https://issues.apache.org/jira/browse/MNG-6511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet updated MNG-6511: - Fix Version/s: (was: 4.0.0-alpha-1) > 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-alpha-2, 4.0.0 > > > 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.20.10#820010)
[jira] [Updated] (MNG-6511) Option -pl ! foo should not fail if foo does not exist
[ https://issues.apache.org/jira/browse/MNG-6511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet updated MNG-6511: - Fix Version/s: 4.0.0-alpha-2 > 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-alpha-1, 4.0.0-alpha-2, 4.0.0 > > > 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.20.10#820010)
[jira] [Updated] (MNG-6511) Option -pl ! foo should not fail if foo does not exist
[ https://issues.apache.org/jira/browse/MNG-6511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MNG-6511: Component/s: Command Line > 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 >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)