| Summary: | eclipse.ini.ignore generated when using -configuration | ||
|---|---|---|---|
| Product: | [Eclipse Project] Equinox | Reporter: | Salvatore Culcasi <salvatore.culcasi> |
| Component: | p2 | Assignee: | P2 Inbox <equinox.p2-inbox> |
| Status: | RESOLVED INVALID | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | simon_kaegi, tjwatson |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Salvatore Culcasi
Moving to p2. I think the engine is doing this, not sure if it is by design or not. Hi Salvatore, This is all expected. When you run using -configuration your configuration information cascades back to the parent. This is also sometimes called a shared install because your are re-using the parent's bundles. Because you are sharing the parent's bundles I would strongly suggest you make those folders read-only. In the user install you just see the parent's installation "roots" and in your case it looks like there is exactly one. The eclipse.ini.ignored in the user configuration folder is "really" ignored and is generated mainly as a trace mechanism to help the p2 team sort out bizarre installation layouts. |