> So that would mean if somebody installs it in a readonly location that has already a jvm shipped with it.
Right, and to be honest I think it's consistent with having the application in a read-only place: if app is in read-only area (typically for control of the content), then it's fair that the main configuration is also read-only. However, I'm curious about how that works for general plugin installations. Where are the new bundles placed, and what is the file that's used locally to describe the user-specific additions? However, we're diverging here ;) > that works a bit better [...] At least for now it doesn't result in a none starting eclipse. Cool! > But we should still fix the problem that the updated vm is not used when restarting.. I gave another round of thoughts about it, and commented in https://bugs.eclipse.org/bugs/show_bug.cgi?id=551378#c31 .
_______________________________________________ p2-dev mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/p2-dev
