[sdc-support]

We have had customer requests for the ability to provision target platforms alongside packages so that teams can work off of unified target platforms in addition to unified tool stacks.

As another example of the flexibility of SDC, we have written an extension to the workspace task mechanism that allows users to specify target platforms in their packages. The full installation notes are included in the zip file, but the simple flow is import a feature, import some binary 3rd party update sites, edit a file, and add it as a workspace task.

Features of this example:

1. Add one or more uniquely named target platforms to your Eclipse
2. Support for any version of Eclipse or MyEclipse you can install via SDC
3. Define target platforms via Eclipse profiles, plugin/feature directories, or the running platform
4. Specify one target platform to be set as the active platform
5. Filter target platforms based on os, architecture, or windowing system
6. Mark specific bundles as included, implicitly included, or optionally included

We would love to hear your feedback on this extension!

Update Feb. 26, 2013: We have improved the extension’s robustness. The site now has only one feature exposed and will install the correct plugins based off of what versions of PDE you have installed in your base Eclipse.

Attachments:

You must be logged in to view attached files.

[sdc-support]

It should be noted that in SDC 2013 SR2 and higher it is no longer necessary to import the PDE Workspace Tasks update site nor add it to your package. This feature has been integrated into SDC and the addition of the support is done automatically for you when you add a .targetplatform task to your package.

To be clear, you can skip steps 1 & 2 in the readme.txt

[Author]

Posts