Remove duplicate integration test version output #11360
Open
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.
Problem
When running integration tests, we see duplicate and confusing output like:
The first line shows the wrong version (from the outer Maven process), and the subsequent lines are redundant output from forked JVMs.
Root Cause
The
TestSuiteOrderingstatic block was printing Maven version information every time the class was loaded, which happens:Solution
This change removes the console output while preserving essential functionality:
maven.versionsystem property (needed by some tests likeMavenITmng3652UserAgentHeaderTest)target/info.txtfor debuggingBenefits
Testing
The change preserves all existing functionality while removing only the problematic console output. Integration tests will continue to work as before, just without the duplicate version messages.
Files Changed
its/core-it-suite/src/test/java/org/apache/maven/it/TestSuiteOrdering.javaPull Request opened by Augment Code with guidance from the PR author