> 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 ;)
its all connected ;)
But new features and plugins (like my feature and now the jre plugin)
is installed in the user home
C:\Users\jcomp\.eclipse\org.eclipse.platform_4.13.0_396182393_win32_win32_x86_64
so you can adjust a installation just fine, you can install features and plugins...
That dir above has for me a "features", "plugins" "configuration" and a "p2" dir
And those have the same meaning i think as in a normal install
Except that in the configuration dir we have also that "eclipse.ini.ignored"
