Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 353409 - [target] Target platform with equinox launchers for multiple environments fails to resolve
Summary: [target] Target platform with equinox launchers for multiple environments fai...
Status: CLOSED DUPLICATE of bug 350772
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.0   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: 3.8   Edit
Assignee: PDE-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-29 09:29 EDT by Thorsten Vitt CLA
Modified: 2011-08-02 08:43 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Thorsten Vitt CLA 2011-07-29 09:29:18 EDT 
Build Identifier: I20110613-1736

I am trying to create a target platform built on an update site that contains the Equinox Target Components. This was no problem in Eclipse 3.6, but it does not seem to work in Eclipse 3.7; instead, I get an entry "Unable to satisfy dependency from org.eclipse.equinox.executable.feature.group 3.5.0V20110530-7P7NFUFFLWUI76mart to org.eclipse.equinox.executable_root.carbon.macosx.ppc [3.5.0V20110530-7P7NFUFFLWUI76mart]." for every platform except for the one of my own machine.

Reproducible: Always

Steps to Reproduce:
1. Create a new (empty) target platform definition: File -> New -> Other -> Plug-in development -> Target Definition
2. in the target definition editor, Click the "Add" button
3. In the Add Content wizard, select "Software Site"
4. Work with: Indigo repository - http://download.eclipse.org/releases/indigo/
5. uncheck [ ] Install required Software
6. check [X] Include all environments
7. Add EclipseRT Target Platform Components -> Equinox Target Components
8. OK

This worked fine with Eclipse 3.6.
Comment 1 Curtis Windatt CLA 2011-08-02 08:43:19 EDT 

*** This bug has been marked as a duplicate of bug 350772 ***