* feat: Simple test with Junit Pioneer
* feat: Simple test for PATH env variable
* feat: Test for getting all the environment variables
* feat: Guardrails for an environment test
* feat: Fixed the test
* feat: Test for reflexive access to the environment
* feat: Renamed a test
* feat: Renamed a utility method
* feat: Removed unused import
* feat: Renamed a test class
* feat: Child process runner
* feat: Method and tag rename
* feat: Docker example
* feat: Testcontainer example
* feat: Cleanup and renames
* feat: Cleanup and renames
* feat: Prevent Docker test from running
* feat: Change assertion to JUnit to prevent adding assertj into the container
* feat: Renamed constants
* feat: Fixed the naming problem
* feat: Changed conditional execution
* feat: Changed conditional execution
* feat: Changed conditional execution
* [rm-char-in-other-str] BAEL-7355 Remove characters from a string that are present in a second string
* [rm-char-in-other-str] shorten the package name
* [static-ref-non-static] static context ref non-static memebers
Based on a comment:
Section 6 should be headlined with “Using System.exit()” since that’s what stops code execution, not the boolean variable (this is just a means to decide that execution should be stopped, like the negative array element in section 4.
Also it’s unclear why we’d need the “if (isInterrupted())” statement in the while loop of the 8th section: how should isInterrupted() be true one line after we’ve checked in the while loop header that it’s false? Admittedly there’s a little chance that the interrupt status changed between these 2 lines, but this if statement would make much more sense somewhere in the business logic code where more time has passed since the evaluation of “while (!isInterrupted())”… and if that business code doesn’t have that complexity/length, one should omit this if statement altogether, since it creates more confusion than it helps for timely reaction on an interruption.
* Creating a Deep vs Shallow Copy of an Object in Java
* [BAEL-6481]-Stop Executing Further Code in Java
* [BAEL-6481] - Stop Executing Further Code in Java
* [BAEL-6481] - Stop Executing Further Code in Java
* [BAEL-6481] - Stop Executing Further Code in Java.
* [BAEL-6481] - Stop Executing Further Code in Java.
* [BAEL-6481] - Stop Executing Further Code in Java.
* [BAEL-6481] Stop Executing Further Code in Java.
* [BAEL-6481] Stop Executing Further Code in Java. Moved to core java numbers - 6
* [BAEL-6481] Stop Executing Further Code in Java.
* [BAEL-6481] Stop Executing Further Code in Java.
* [BAEL-6481] Stop Executing Further Code in Java.
* [BAEL-6481] Stop Executing Further Code in Java. [Commented the Test cases]
* [BAEL-6481] Stop Executing Further Code in Java. [Commented the Two Test]
* [BAEL-6481] Stop Executing Further Code in Java. [Fixed Method Name's]
vunamtien
Eugene Kovko
Harry9656
rcalago
Bipin kumar
collaboratewithakash
Kai Yuan
panos-kakos
Maiklins
mikr
michaelin007
edizor
danielmcnally285
panos-kakos
Ulisses Lima
Vini
lajka
Loredana Crusoveanu
Partha Sutradhar
Tetiana