Community
Participate
Working Groups
When i install eclipse in a readonly location Then i install plugins or features, those are going into the user home dir so you can adjust a installation just fine Problem is when that is an new install or update of for example of a plugin that provides a JRE and uses the SetJvmAction of p2 to update the ini file We do get in the user.home\.eclipes\somedir\configuration\ directory a "eclipse.ini.ignored" file That does have the updated stuff that i need. But it will never use that So these kind of plugins or feature that depend on changes to the ini file will never work. I guess this can be a bit tricky, but can the launcher itself not already see this and look if there is a ini file in the home dir for this installation and use that one? (use the newer of the 2...) For now all those p2 touchpoints are kind of useless (SetJvmAction, AddProgramArgument, AddVmArgument) because you have no idea if they really are installed and used..
(In reply to Johan Compagner from comment #0) > I guess this can be a bit tricky, but can the launcher itself not already > see this and look if there is a ini file in the home dir for this > installation and use that one? (use the newer of the 2...) IMO, that's a good proposal. However, I don't know how hard it'd be to implement.
