<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>It would be a worthwhile audit to examine test class directories
after a test run to see whether any library clases have leaked
into those directories.</p>
<p>A different approach would be to compile test classes with
`-implicit:none` to ensure library classes do not leak into test
class directories.<br>
See
<a class="moz-txt-link-freetext" href="https://docs.oracle.com/en/java/javase/17/docs/specs/man/javac.html#option-implicit">https://docs.oracle.com/en/java/javase/17/docs/specs/man/javac.html#option-implicit</a><br>
</p>
<p>-- Jon</p>
<p><br>
</p>
<div class="moz-cite-prefix">On 4/1/25 12:04 PM, Jonathan Gibbons
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:fc1d91cf-e407-49b3-ad7a-bb9fc4635b46@pobox.com"><br>
<br>
<blockquote type="cite" style="color: #007cff;">Class directory of
a test case should be always used to compile a library
<br>
</blockquote>
That would be an anti-pattern to be discouraged. Libraries are
supposed to be shared between tests and as such, should not be
beholden to any individual test class directory.
<br>
<br>
-- Jon
<br>
</blockquote>
</body>
</html>