Question about FileManagers in Jigsaw.

[Alan Bateman]

On 13/03/2012 20:53, Kelly O'Hair wrote:
> :
> I was actually thinking that the import jdk would have the jmod packages.
> But I'm a jigsaw-newbie at this point.
>
> I was assuming that corba, jaxp, and jaxws would deliver a distinct set of modules as their deliverables,
> and if those repos were not present at build time, the modules could be gotten from the import jdk.
> HOWEVER, I could also see us just requiring those repositories to always exist and be built when the
> jdk repository was being built. The assumption was that the build would be so fast that this would never be
> a speed issue. It might then eventually make sense then that corba, jaxp, and jaxws sit inside the jdk repository,
> either as nested repos or imported into it, but that's a decision for later.
>
> The partial builds are a maintenance burden from my point of view, and there have been no end of
> problems people have sent me when their partial build did not work.
> When it was just j2se and hotspot, that was one thing, but the complexity of 7 repos and all combinations
> of them, well, it's a bit out of control. If we can limit the variations on partial builds, that would be a good thing
> in my opinion.
>
> I had a plan of creating some top level Makefile logic that would enforce what sets of repositories were
> valid to build in a partial build, e.g. top+hotspot  top+langtools+corba+jaxp+jaxws+jdk etc.
> And consider a stop of the build when certain repositories were missing, or foreign ones were present, or
> they were located in the wrong place or with the wrong names.
> But that was a selfish act meant to stop some of the emails I get about failed builds. :^(
>
> -kto
>
Yep, partial builds can be a pain, folks are always mixing up the 
bootstrap and import JDKs.

So if certain sets of repos are required to be present then, and the 
build is speedy as expected, then it means that jaxp + jaxws+ corba (+ 
maybe others) shouldn't be a major issue but they may require separate 
compilations due to different source code organization.

I suspect that hotspot might be tricky as the SA classes are needed for 
the jdk.tools module (in the current prototype) and also complicated by 
the fact that they implement JDI interfaces. It might be interesting to 
put jvmti.h on the table too to avoid having to check in the output of 
the build into the jdk repo.

-Alan.