On 10/14/2015 1:56 PM, Steve Drach wrote:
The current test directory contains binary jar files. In fact in all the test
directories, there are 52 binary .jar files.
I know but we need to work to remove those.
I figured that might be the response, but thought it was worth the try ;-)
A reasonable way forward is to go with pre-baked jar files (it’s not making the
current situation particular any worse) then lets try and clear up this aspect
in a later push, hopefully using a common mechanism that can be used by all
such tests that need to construct jar files.
+1 on the common mechanism. For building jars and other common tasks.
It would also be nice to have some form of test sequencing or other way to
indicate that multiple tests depend on a common set of artifacts and that set
only needs to be created once.
You can put multiple @build and @run directives in a test. In
particular, you can build and run multiple Java sources files, such as
sources for different logical tests, from a single jtreg @test file. I
believe you can use this capability to implement sequencing.
HTH,
-Joe
