8078820 -> Re: RFR: 8068938: Test deploying a XML parser as a module

huizhe wang huizhe.wang at oracle.com
Sat Mar 19 23:14:53 UTC 2016


Saw Alan's update for JDK-8078820. 8078820 is the right id for this, 
isn't it? :-)  8068938 was a different issue that Sundar has already 
resolved.

By the way, I just realized that the previous webrevs didn't include 
org.xml.sax.helpers.XMLReaderFactory. Would you want to add that too?

Best,
Joe

On 1/27/2016 3:10 AM, Alan Bateman wrote:
>
> On 26/01/2016 17:30, huizhe wang wrote:
>> Hi Felix,
>>
>> I would feel sorry for Frank since at the time we wanted all tests to 
>> be hosted in the JAXP repo. I understand the intention to consolidate 
>> repos as Alan suggested. However, if the JAXP repo is not hampering 
>> JDK development, I'd prefer an independent JAXP repo as is since it 
>> made JAXP dev much easier. That said, I have no objection to moving 
>> JAXP tests to JDK/test, that'll at least consolidate all of the tests 
>> and you may then take advantage of the JDK/test utilities for current 
>> and future test development.
>>
>> Alan, what would you think?
> We're probably going a bit off-topic here but I don't see why we 
> persist with the jaxp repository. I think we should have moved the 
> code to the jdk repository a long time ago. In the short term then it 
> might be annoying to not have the revision history (hg log) but we've 
> been through this kinda of transition already. Also in the short term 
> then it might require you or others to do some adjustments to your IDE 
> setup but that shouldn't be a big deal, esp. with the source code 
> layout that we put in via the JEP 201 work.
>
> In any case, this all started with my comment about the tests being 
> split between the jdk and jaxp repo. What would it take to get the new 
> tests to be located with the existing jaxp tests?
>
> -Alan.



More information about the jigsaw-dev mailing list