testing jigsaw builds

[Jonathan Gibbons]

getSystemJavaCompiler() will only look in tools.jar if the classes are 
not already available in the existing classloader.  If you're running a 
jdk module image, does that not have the javac classes available?

-- Jon




Jonathan Gibbons wrote:
> Hmm, it sounds like jtreg changes maybe more urgent than I thought.  
> Also, changes to javax.tools.ToolProvider.getSystemJavaCompiler()
>
> -- Jon
>
>
> Mandy Chung wrote:
>> On 03/15/10 16:29, Jonathan Gibbons wrote:
>>> Thanks. Dare I ask whether all these can be run in samevm mode?
>>
>> No, unfortunately since tools.jar no longer exists in any module 
>> image.   javax.tools.ToolProvider.getSystemJavaCompiler()  looks for 
>> the javac classes from tools.jar.  As we discussed some time ago, 
>> fixing it will be tricky since the code needs to be able to compiled 
>> and run on JDK 6. (i.e. bootstrap mode.)
>>
>> Mandy
>>
>>> -- Jon
>>>
>>>
>>> Mandy Chung wrote:
>>>> I have been running the following tests for testing jigsaw builds 
>>>> on jdk-module-image.
>>>>
>>>>      ${TEST}/java/lang
>>>>      ${TEST}/java/nio
>>>>      ${TEST}/java/util
>>>>      ${TEST}/java/text
>>>>      ${TEST}/java/security
>>>>      ${TEST}/java/beans
>>>>      ${TEST}/java/math
>>>>      ${TEST}/org/openjdk/jigsaw
>>>>
>>>> This is not a standard set of tests for testing the jigsaw build 
>>>> but these tests test classes in multiple modules and it should 
>>>> provide good coverage.
>>>>
>>>> Mandy
>>>>
>>>> On 03/15/10 16:10, Jonathan Gibbons wrote:
>>>>> Is there a standard set of tests (other than "everything") for 
>>>>> testing a jigsaw build?
>>>>>
>>>>> -- Jon
>>>
>
>