corba, jaxp and jaxws compiled before jdk repository

[Alan Bateman]

On 12/09/2012 15:54, Erik Joelsson wrote:
> Those repos are indeed compiled before the jdk just like in the old 
> build. As I understand it, jaxp and jaxws have historically been 
> delivered to other places as well as the jdk, which forced them to be 
> compatible with at least some earlier jdk version, so this wasn't an 
> issue. I also understand nobody touches corba, which makes it a non 
> issue too. We have not considered moving these builds as we haven't 
> thought it a problem.
>
> One way to solve this could be to leverage the GenStubs facility in 
> langtools. Another would be to add these source dirs to the main jdk 
> java compile line. I don't really like the second option though. In 
> that case I would rather see the source being folded into the jdk repo 
> instead of living in it's own repo.
>
> In hotspot, all javacode is compiled with the javac from the bootjdk 
> as far as I know, so in that respect there is no dependency on the jdk 
> being built.
>
> /Erik
JAXP used to come via a source bundle but this is no longer the case and 
the development (mostly maintenance) is now done in the jaxp repository. 
There is Xerces and Xalan code in there and I assume Joe will need to 
continue to pull in patches and keep that code in sync. However I think 
we need to allow for JAXP making use of new language features or new 
APIs. The java.util.spi example in the first mail is actually a real 
example as we may want to have JAXP implement a provider interface that 
is in the jdk repository.

Like JAXP then JAX-WS used to come via a source drop but now the source 
code is checked in. There is still upstream projects and I don't see the 
folks involved there much on the OpenJDK lists. So for this one then I 
think you are right and they will need to continue to have one source 
base that works with different JDK releases. However there is one 
example that comes to mind and that is the private (and stale) copy of 
ASM in that repository. If ASM is added to the jdk repository then I 
think it would be desirable to be able to dump the copy in the jaxws 
repository so that we only have one copy. Logistically this may be 
problematic and maybe it's not worth trying but it's an example that 
comes to mind.

In the jigsaw/jigsaw forest then I recently wanted to make some changes 
to code in the corba repo in order to run some tests with modules. The 
annoying thing is that I couldn't use any of the new and experimental 
APIs in jigsaw/jigsaw/jdk because corba was compiled too early. You are 
right that corba doesn't get much activity but I think it's worth at 
least seeing whether it make sense to allow code there make use of newer 
APIs in jdk8.

Now that we know that the new build builds these repositories before the 
jdk repository then it is critical that we can do boot cycle builds (as 
per the discussion on build-dev).

-Alan