Remove JAVA_TOOL_OPTIONS when running platform tooling supports tests by filiphr · Pull Request #4148 · junit-team/junit-framework (original) (raw)
Navigation Menu
Provide feedback
Saved searches
Use saved searches to filter your results more quickly
Appearance settings
Conversation
Overview
When a user has the JAVA_TOOL_OPTIONS set in their environment, java will print "Picked up JAVA_TOOL_OPTIONS: ..." on the error stream.
This leads to failure in some of the Platform Tooling Tests
I hereby agree to the terms of the JUnit Contributor License Agreement.
Definition of Done
- There are no TODOs left in the code
- Method preconditions are checked and documented in the method's Javadoc
- Coding conventions (e.g. for logging) have been followed
- Change is covered by automated tests including corner cases, errors, and exception handling
- Public API has Javadoc and @API annotations
- Change is documented in the User Guide and Release Notes
When a user has the JAVA_TOOL_OPTIONS set in their environment, java will print "Picked up JAVA_TOOL_OPTIONS: ..." on the error stream This leads to failure in some of the Platform Tooling Tests
This was referenced
Feb 24, 2025
This was referenced
Mar 17, 2025
This was referenced
Apr 14, 2025
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
[ Show hidden characters]({{ revealButtonHref }})
2 participants
