[Issue-3309] Clarify forkNode default communication docs#3361
Open
officialasishkumar wants to merge 1 commit into
Open
[Issue-3309] Clarify forkNode default communication docs#3361officialasishkumar wants to merge 1 commit into
officialasishkumar wants to merge 1 commit into
Conversation
The forkNode documentation still said the default would switch to TCP/IP in 3.0.0. Process pipes remain the default, while TCP/IP is an opt-in alternative. Update the plugin parameter docs and site examples accordingly.
This file contains hidden or 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
2 participants
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 #3309.
The forkNode parameter and site documentation no longer say that TCP/IP would become the default in 3.0.0. They now state that process pipes remain the default and that TCP/IP sockets are available as an opt-in alternative.
Verification:
/tmp/apache-maven-3.9.11/bin/mvn -pl maven-surefire-plugin,maven-failsafe-plugin -am -DskipTests -Drat.skip=true -Dcheckstyle.skip=true -Dspotless.apply.skip=true -Dspotless.check.skip=true -Danimal.sniffer.skip=true -Dmaven.build.cache.enabled=false packageFollowing this checklist to help us incorporate your
contribution quickly and easily:
mvn clean installto make sure basic checks pass. A more thorough check willbe performed on your pull request automatically.
mvn -Prun-its clean install).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.