[MNG-6410] Clean suggestion on build resume. #166
Closed
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
|
Sure, no problem - I will just strip this commit and update PR. The 6028 was open for some time so I decided to work on it while I was around. All CLI parameters are available in cliRequest. Whole command may be printed with -rf, if there will be such requirement. |
|
Sure, no problem - I will just strip this commit and update PR. The 6028 was open for some time so I decided to work on it while I was around. |
splatch
force-pushed
the
MNG-6410
branch
3 times, most recently
from
c4e4e6a
to
2540e23
Compare
asfgit
pushed a commit
that referenced
this pull request
May 18, 2018
…ot unique in reactor This closes #166
pzygielo
pushed a commit
to pzygielo/maven
that referenced
this pull request
Jan 4, 2023
…/actions/cache-v2
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.
Make sure that resume suggestion contains a valid value for restarting the build, as same artifact name might occur in different places of multi-module project, it is necessary to check if there is conflict in name.
By this way returned suggestion will always be correct and less experienced developers will not get confused with it.
JIRA issue: https://issues.apache.org/jira/browse/MNG-6410.
A extra note, this pull request depends on another pull #165 - for MNG-6028, which changes the same line, both commits are included in this PR.