Remove <mavenExecutorId>forked-path</mavenExecutorId>
#717
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
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.
Fixes #683. We don't customize this in
jenkinsci/pom, and automated release of both Jenkins core and core components seem to work fine without it, as do manual releases withmaven-release-plugin. Seems more straightforward to get rid of this customization and follow a more standard code path that is in line with Maven defaults. I was unable to find any commit messages or tickets that explain the reason why this was customized to begin with. This change is not tested, but I believe the risk is low given that we are already using this configuration injenkinsci/pom. If any issues arise, we can iterate from here or revert this change if necessary.