Community
Participate
Working Groups
Build Identifier: 3.6M6 It should be allowed to use the slicer (include all environments) and planner (include required software) per feature or per site when setting up .target files. Or to use the planner to include required software and also include all environments. Problem with the current situation is, if you want to setup a cross-platform-target platform you end up with listing every dependent bundle/IU yourself - a little bit of help from the planner would be very helpful. Reproducible: Always
The slicer should attempt at getting all required IUs that are available in the selected repositories. Unlike the planner, it won't throw errors when something is not available. It might be possible to mix the two styles in the same target, but not with our current code (settings are stored as properties of the target's profile). It had been suggested (by Jeff I think) that the slicer might be the only style we should support.
Despite the fact that only one style per .target is supported, in PDE .target files the style/mode is specified per repository location: <location includeAllPlatforms="false" includeMode="slicer" type="InstallableUnit"> <unit id="org.eclipse.rcp.sdk.id" version="3.5.2.M20100211-1343"/> <repository location="http://download.eclipse.org/releases/galileo"/> </location> If the slicer could resolve dependencies as well, this would fix the issue and simplify the setup. Any arguments against such a solution? If I understand correctly, this would make every target cross-platform ("Include all environments" could be removed and would be enabled by default for targets). Any reason to keep targets that are for the running platform only?
As Curtis mentioned, the slicer attempts to gather all dependencies, but does not complain when they are not found. I just made a target of the "sliced SDK" with all platforms and it appears to work fine (noting that you need the fix to bug 247766 in order to see the correct SWT source when debugging). Moving forward, I think it makes sense to simplify the target provisioning story by using just the slicer (and I think the experimental target provisioning work Curtis did in a branch recently did just this). Perhaps this is just a duplicate of bug 287619?
Created attachment 164301 [details] rcphelp.target Attached .target contains Eclipse RCP SDK + Eclipse Help + Eclipse Help Developer Resources. Using the planner, I get 99 plug-ins _including_ org.eclipse.ui.forms. Using the slicer, I get 95 plug-ins _excluding_ org.eclipse.ui.forms. I concluded from this observation that the slicer doesn't resolve dependencies. I just tested this on I20100406-1034.
