Summary: | [doc] PDE ignores the delta pack | ||
---|---|---|---|
Product: | [Eclipse Project] PDE | Reporter: | Wendell Beckwith <wbeckwith> |
Component: | UI | Assignee: | Chris Aniszczyk <caniszczyk> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | CC: | caniszczyk, daniel_megert, jfrantzius |
Version: | 3.4 | Keywords: | readme |
Target Milestone: | 3.4 RC1 | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Whiteboard: |
Description
Wendell Beckwith
2008-05-04 23:31:33 EDT
In the target platform preference page, uncheck the 'build target platform based on the target's installed plugins' That should rebuild your target platform and include the delta pack... install it the way you use to install it... ie., just unzipping it. The problem here is that even if you install the delta pack via p2, PDE still won't see it by default because if your target == host, PDE just builds its platform based on what p2 thinks is installed. P2 won't install the deltapack plug-ins because they aren't valid for the current platform. Let me know if this solves your problem. This is a slight workflow change for people who use the deltapack when target == host. Thanks for the update and quick response. This does appear to be the case. Normally I don't install plug-ins into my eclipse home since I usually use link folders. However, when the link folders didn't work for the delta pack, I figured it was some p2 wackiness and tried installing them in the eclipse home to no avail. This will be something we need to do for RC1. This is a documentation issue for people using the delta pack. The workflow has slightly changed. I updated the PDE documentation to be more clear with how you deal with the delta pack. Hopefully this will resolve people's confusion. If not, we can see if we can do more. *** Bug 232480 has been marked as a duplicate of this bug. *** |