Multi release jars on boot classpath

[Andrew Dinn]

On 02/06/16 13:25, Alan Bateman wrote:
> . . . Also with the ongoing effort to move
> modules away from the boot loader then it starts to reduce the set of
> possible libraries that can be deployed with -Xbootclasspath/a. So I
> think it is right to keep JEP 238 focused and get it right for the
> common scenarios first.

Can you explain what this means in any more precise detail?

Those of us who are trying to maintain agents are currently having to
work on shifting ground where it seems the only guidance we have as to
what will and won't work is the current code. This is the second
occasion where a throwaway comment has revealed to me that plans are
afoot to change functionality that my agent (and doubtless others too)
relies on. If there are plans afoot of this nature then we need to know
about them well before it happens. OpenJDK project members -- especially
those who have implemented agents -- need to discuss whether the
resulting breakage of existing functionality is acceptable. That sort of
decision cannot be arrived at as a fait accompli simply by virtue of the
fact that your envisaged Jigsaw design will produce it as a side effect.

regards,


Andrew Dinn
-----------
Senior Principal Software Engineer
Red Hat UK Ltd
Registered in England and Wales under Company Registration No. 03798903
Directors: Michael Cunningham, Michael ("Mike") O'Neill, Eric Shander