On Thu, Dec 22, 2016 at 2:38 PM, Waldek Kozaczuk <[email protected]> wrote:
> Also as I suggested in one of my older emails it might be worth to ponder > the idea of changing the default from java-isolated to java-non-isolated as > the former one requires java.beans package which does not exist in compact > profiles. Also java-isolated jar will not work in Java 9 without making > some significant changes as some of the deprecated methods in LogManager > (that relied on java.beans) were simply removed. So if think that > java-isolated is really dead-end at some point unless there is appetite to > invest into making it work under Java 9 and < Java 9. > I was never a big fan of the whole "isolated Java" concept, so I'm not the best advocate to defend it, but I think at this point we've reached some sort of equilibrium - the old things work as before and new things can use non-isolated java - and we should probably stay in this state of equilibrium for a while before changing it again. > Now I am aware that https://github.com/mikelangelo-project/capstan and > https://github.com/emc-advanced-dev/unik projects rely on presence of > /usr/mgmt/javamains file that is only used by io.osv.isolated.MultiJarLoader. > One possibility would be to make io/osv/nonisolated/RunNonIsolatedJvmApp > somehow be able to handle this file. > -- You received this message because you are subscribed to the Google Groups "OSv Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
