corba, jaxp and jaxws compiled before jdk repository
Kelly O'Hair
kelly.ohair at oracle.com
Wed Sep 12 10:09:36 PDT 2012
On Sep 12, 2012, at 8:46 AM, Jonathan Gibbons wrote:
> On 09/12/2012 07:18 AM, Alan Bateman wrote:
>>
>> In the discussion on build-dev about boot cycle builds then Andrew Hughes mentioned the problem with the old build system where jaxp, jaxws and corba are compiled before the jdk repo and this can lead to several problems. I had assumed this would not be an issue with the new build but now I'm not sure.
>>
>> As a test for something that we may need to do in JDK8, I added an interface to java.util.spi (jdk repository) and then attempted to implement that interface in a class in the jaxp repository. This is a good example of code in jaxp needing to make use of something that is new in jdk8. On re-build the compile of the jaxp repository failed because the new class is not known to the bootstrap JDK (and the jdk/classes directory is not on the classpath specific to javac).
>>
>> Are corba, jaxp and jaxws compiled before jdk just to follow the old build system? Given circular dependencies between these repositories then has there been any consideration given to compiling them together? (I'm ignoring hotspot for now, I realize that SA and JDI are issues too).
>>
>> -Alan
>
> Alan,
>
> Given the ongoing desire, for now, to verify the equivalence of old and new builds, this may be hard to fix before we fully commit to the new build system.
>
> -- Jon
Alan,
We have quite a bit to do now on build-infra.
If this is critical and you have no obvious workaround, let's talk.
If it is not critical, I would like to delay this as long as possible.
-kto
More information about the build-infra-dev
mailing list