[MRELEASE-1088] Remove parsing of CLI arguments #120
Conversation
|
Yes I know ... it will conflict with #118 😄 |
| @@ -37,7 +37,7 @@ | |||
| </dependency> | |||
| </dependencies> | |||
| <configuration> | |||
| <arguments>-Prelease,!mrelease-677 ${arguments}</arguments> | |||
There was a problem hiding this comment.
maybe leave to see if removal do not have side effects?
this usage pattern <arguments>.... ${arguments}</arguments> is used a lot
There was a problem hiding this comment.
It is one change - now arguments is pass directly to Invoker, and here property ${arguments} is not resolved so is passed as is.
When we parsed CLI such not resolvable property was not used.
There was a problem hiding this comment.
do you mean leaving <arguments>-Prelease,!mrelease-677 ${arguments}</arguments> is now failing the build when ${arguments} is not defined?
uhm this doesn't look right to me. at least should not fail.
There was a problem hiding this comment.
exactly ... if any property in arguments are not resolvable build will fail it.
It is a cost ... parsing everything and duplicate code or pass value as is.
It worked in the same way with old forked executor.
There was a problem hiding this comment.
I know of projects that depend on ${arguments}, so better to fix the code instead of adjusting this IT.
There was a problem hiding this comment.
Ok, I will print warning about unresolved properties in arguments and strip its before pass to Invoker.
Can be a case that will be need pass to invoker something like ${.*} ?
| { | ||
| req.setLocalRepositoryDirectory( localRepoDir ); | ||
| // additionalArguments will be parsed be MavenInvoker | ||
| targetGoals.add( additionalArguments ); |
There was a problem hiding this comment.
Not related to this, but InvocationRequest needs to rename #setGoals() to #setArgs()
...release-manager/src/main/java/org/apache/maven/shared/release/exec/InvokerMavenExecutor.java
Outdated
Show resolved
Hide resolved
slawekjaranowski
force-pushed
the
MRELEASE-1088
branch
from
e6a7cad
to
38bd363
Compare
|
Best change ever after the massive change from @cstamas .... |
|
Is this fix included in version 3.0.0-M5? I'm still getting an error trying to use --no-transfer-progress |
|
@peterkronenberg it is in 3.0.0-M6 |
Following this checklist to help us incorporate your
contribution quickly and easily:
for the change (usually before you start working on it). Trivial changes like typos do not
require a JIRA issue. Your pull request should address just this issue, without
pulling in other changes.
[MJAVADOC-XXX] - Fixes bug in ApproximateQuantiles,where you replace
MJAVADOC-XXXwith the appropriate JIRA issue. Best practiceis to use the JIRA issue title in the pull request title and in the first line of the
commit message.
mvn clean verify -Prun-itsto make sure basic checks pass. A more thorough check willbe performed on your pull request automatically.
If your pull request is about ~20 lines of code you don't need to sign an
Individual Contributor License Agreement if you are unsure
please ask on the developers list.
To make clear that you license your contribution under
the Apache License Version 2.0, January 2004
you have to acknowledge this by using the following check-box.
I hereby declare this contribution to be licenced under the Apache License Version 2.0, January 2004
In any other case, please file an Apache Individual Contributor License Agreement.