JAXP 1.4.3 Integration into JDK7 M6

[Joe Darcy]

Joseph D. Darcy wrote:
> Hello.
> 
> Kelly O'Hair wrote:
>>
>> I will be changing the jdk7/tl/jaxp repository to use the JAXP 1.4.3
>> source bundle at:
>>    https://jaxp.dev.java.net/files/documents/913/147490/jdk7-jaxp-m6.zip
>>
>> ReleaseNotes: https://jaxp.dev.java.net/1.4/1.4.3/ReleaseNotes.html
>> Changelog:    https://jaxp.dev.java.net/1.4/1.4.3/changelog.html
>>
>> Currently we have 1.4.2, and I'm told 10 of the bugs in the above list
>> are the ones we are getting with this upgrade.
>>
>> Questions:
>>   1. Should we file jdk 7 SubCR's of the 10 JAXP bugs fixed in this m6 
>> drop?
> 
> Yes, I think this is the right approach to make bug queries easier; "Is 
> this bug fixed in the jaxp in JDK 7?  Yes, there is a subCR in JDK 7 for 
> it."
> 
> In addition, there can be a "upgrade JDK 7 to jaxp x.y.z" bug to track 
> the changes specific to the JDK, such as updating the properties files.
> 
>>   2. Should the changeset comment include all 10 of these JAXP bugs, or
>>      should I just create one CR "Upgraded to JAXP 1.4.3"?
> 
> I definately think there should be an "Upgraded to JAXP 1.4.3" bug in 
> the changeset and that the bug database should have the subCRs.  Listing 
> all 10 jaxp bugs would be more informative, but a bit more work.

After some discussion with other members of the release team, in the 
situation where the delivered component is using the same bug system as 
the JDK, it is preferable to

1) Have a bug to upgrade the component in the JDK
2) Have the changset for the JDK upgrade list both the "upgrade the 
component" bug and the bugs being fixed by the upgrade, the 10 or so 
jaxp bugs in this case.

-Joe