Community
Participate
Working Groups
Since e4 is about shaping the future of the platform, a few weeks back during the p2 call we have discussed what we wanted to see happening in e4 wrt to provisioning. Several things came up: 1) Get rid of the org.eclipse.update* bundles 2) Replace the dropins support to something more structured that would behave more like what the UI does. We called that the "install-in".
A few more questions: 1. IIRC, the plugins/ features/ folders act as a drop-ins (you can still unzip over your install). Do we want to keep this behaviour? 2. What about the platform.xml (this is likely covered in the org.eclipse.update* bundles)? 3. Do we need to / want to keep shipping features? 4. Do we want to continue to support site.xml (publish them and consume them as p2 repos)? (Again, it might be part of org.eclipse.update*, but this will probably require an explicit decision).
Thx for these additions Ian. > 1. IIRC, the plugins/ features/ folders act as a drop-ins (you can still unzip > over your install). Do we want to keep this behaviour? No. > 2. What about the platform.xml (this is likely covered in the > org.eclipse.update* bundles)? This is covered in platform.xml > 3. Do we need to / want to keep shipping features? We can try, but I think this would mean changes in PDE around how they deal with grouping. > 4. Do we want to continue to support site.xml (publish them and consume them as > p2 repos)? (Again, it might be part of org.eclipse.update*, but this will > probably require an explicit decision). Yes, we want to be able to keep installing from legacy update sites. However this support is already in a separate plug-in: org.eclipse.equinox.p2.updatesite.
