Creating jar files as part of a test?

[David Holmes]

On 2/04/2014 6:32 AM, Jonathan Gibbons wrote:
>
> On 03/31/2014 10:34 PM, David Holmes wrote:
>> The test has to use @library because it is using processtools to
>> launch another VM to run the "real" test via the jar file I am
>> creating (and the fact it is a jar file is a critical part of the
>> thing under test).
>>
>> So I guess I'm going to have to run the jar tool passing the value of
>> test.classes as the path to the actual classes I want in the jar, and
>> list the actual classes individually.
>>
>> Thanks,
>> David
>
>
> test.classes points to a directory which only contains the classes for
> the files in the main test source directory.
>
> test.class.path is a path which contains a series of directories or jars
> for all the classes for the test.  The includes the same directory as
> for test.classes as well as directories for the library classes.
>
>
> I understand that you are using processtools to launch the real test via
> the jar file.   But is it the case that you don't need any library
> classes in the .jar file? In that case, you may be able to get away with
> just jarring up the test.classes directory.

Correct. The jar only needs some trivial test logic - nothing from 
processtools or any other library classes.

Thanks,
David

> -- Jon