Bugzilla – Full Text Bug Listing
| Summary: | PDE different behavior compiling against TargetPlatform from dir or site | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] PDE | Reporter: | ekkehard gentz <ekke> | ||||
| Component: | UI | Assignee: | PDE-UI-Inbox <pde-ui-inbox> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | aniefer, florian.pirchner, jhelming, koegel | ||||
| Version: | 3.6 | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | Macintosh | ||||||
| OS: | Mac OS X | ||||||
| Whiteboard: | stalebug | ||||||
| Attachments: |
|
||||||
tested this again using RC1 now the error I reported first seems to be fixed. in one case I can use my exported target platform without any problems - in the other case I'm getting compile errors (...java problems - couldn't resolve xxx as type ...) this is reproducable: switching back to the TP using update-sites: all is OK switching to the exported TP: compile errors. (I noticed that the number of plugins from exported TP is much less, as if I summarize all from the different software sites This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. Please remove the stalebug flag, if this issue is still relevant and can be reproduced on the latest release. |
Created attachment 168295 [details] the problematic plug-in I'm using the new feature to export a complete Target Platform into a directory. If I switch then the TP to work from this directory I got compile errors, because some classes from org.unicase.emfstore were not found. This happens only, if my TP was exported into a directory. Using the same TP with sites as location, then all works well. workaround: import the plug-in into the workspace ...think that this is a problem because of nested jars, but behavior should be the same from directory or sites.