[MRELEASE-1104] fix stage goal when having both arguments and stagingRepository #151
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
olamy
force-pushed
the
MRELEASE-1104-stagingRepository-ignored
branch
2 times, most recently
from
b15ff9f
to
f3166d2
Compare
olamy
requested review from
michael-o and
slawekjaranowski
and removed request for
michael-o
...-release-manager/src/main/java/org/apache/maven/shared/release/exec/ForkedMavenExecutor.java
Show resolved
Hide resolved
...release-manager/src/main/java/org/apache/maven/shared/release/exec/InvokerMavenExecutor.java
Show resolved
Hide resolved
slawekjaranowski
approved these changes
Sep 24, 2022
michael-o
requested changes
Sep 27, 2022
maven-release-plugin/src/main/java/org/apache/maven/plugins/release/StageReleaseMojo.java
Outdated
Show resolved
Hide resolved
|
Let me try to run ITs here... |
…Repository Signed-off-by: Olivier Lamy <olamy@apache.org>
olamy
force-pushed
the
MRELEASE-1104-stagingRepository-ignored
branch
from
f7d5937
to
30d3ef1
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Signed-off-by: Olivier Lamy olamy@apache.org
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.