Proposal to revise forest graph and integration practices for JDK 9
Alan.Bateman at oracle.com
Wed Dec 4 07:52:49 PST 2013
On 04/12/2013 13:41, Magnus Ihse Bursie wrote:
> So if we really don't need it for jdk, nor the rt.jar -- then what use
> is it? :-) Even if I know how jaxws is *built*, I don't really have a
> clue what it's *for*. :-)
The APIs in the jaxws repository are part of Java SE and so we do need
to build it, it's just each of them (JAX-WS, JAXB, SAAJ, ..) lead a
double life as a standalone technology. Many of the app servers ship
with newer implementations and don't use the versions that are in the JRE.
> Currently, we have a dependency on jaxws from jdk in the build system.
> Right now, I can't see why, since as you say, it works just as well to
> compile after the JDK (if you hack away the artifical dependencies
> currently in place in the build system). Don't know why we're not
> doing it that way already.
I believe that things are built in this order to match the old build (to
get identical bits, modulo the compare script). The old build is gone
now so there is an opportunity to fix a number of things. If there are
changes to the number of repositories then maybe it's the perfect storm
to fix this one too.
More information about the jdk9-dev