Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 326259 - Eclipse does not find class from plugin deployed as directory inside a custom Target Platform
Summary: Eclipse does not find class from plugin deployed as directory inside a custom...
Status: CLOSED WONTFIX
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.6.1   Edit
Hardware: PC Windows XP
: P3 normal with 5 votes (vote)
Target Milestone: ---   Edit
Assignee: PDE-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-26 14:54 EDT by Joe CLA
Modified: 2019-05-16 14:40 EDT (History)
4 users (show)

See Also:


Attachments
testcase added (11.96 KB, application/x-zip-compressed)
2010-09-26 14:57 EDT, Joe CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Joe CLA 2010-09-26 14:54:34 EDT
Build Identifier: Eclipse 3.6.1 M20100909-0800

I have a Target Platform which contains one plugin deployed as directory. One of my projects uses a class from this plugin. Eclipse will not find classes from plugin. 
If the plugin is deployed as jar file then Eclipse will find the classes.

Expected behaviour: Eclipse should find classes from both bundle shapes (jar and directory).

Reproducible: Always

Steps to Reproduce:
Testcase will be attached
1. Extract the testcase and import it into a workspace.
2. Close project a.testcase. It contains the source for the plugin used in Target Platform
3. Create and activate a custom target platform. The custom platform uses Platform/plugins and ${eclipse_home} as Locations.
4. Rebuild the workspace
5. Project b.testcase will show 3 compile errors. 'A cannot be resolved to a type' (2x) and 'The import a cannot be resolved'.

6. The compilation problems can be fixed by packing the plugin as a jar.
7. A restart may be required.
Comment 1 Joe CLA 2010-09-26 14:57:46 EDT
Created attachment 179589 [details]
testcase added
Comment 2 Joe CLA 2010-09-26 15:00:32 EDT
Accidentaly set the version to 3.7. 3.6.1 is correct
Comment 3 Ayushman Jain CLA 2010-09-27 03:00:23 EDT
May be a PDE problem. Moving to PDE/UI for comment.
Comment 4 Ankur Sharma CLA 2010-09-27 03:11:51 EDT
The problem is real. Tested and confirmed on latest I-build.
May be Dupe of Bug 298479.
Comment 5 Darin Wright CLA 2010-09-27 10:12:03 EDT
The bundle "a.testcase" is configured to have class files compiled/located at the root of the bundle (since no bundle classpath is specified, and build.properties includes the default output locatoin of "."). However, the class files are in the /bin folder of the bundle, and as such will not be found. The project is not in a "deployed bundle" format and cannot be used as part of a target platform.

Marking as dup.

*** This bug has been marked as a duplicate of bug 298479 ***
Comment 6 Joe CLA 2010-09-27 15:59:32 EDT
I think you have closed this too early.
I haven't talked about the bundle 'a.testcase'. 'a.testcase' is just there to provide the source code. This bundle is just there to provide the source code.

Please look at 'Platform\plugins\a.testcase_1.0.0.201009261748' it contains the exported version of the bundle. If you set 'Platform\plugins' as your custom target platform then eclipse will not find classes inside the bundle 'Platform\plugins\a.testcase_1.0.0.201009261748'.
If you jar the bundle to 'Platform\plugins\a.testcase_1.0.0.201009261748.jar' then eclipse will find the classes. A restart might be required.
Comment 7 Curtis Windatt CLA 2010-09-29 16:03:06 EDT
(In reply to comment #6)
> I think you have closed this too early.

Yeah, we might have.  The jarred plug-in does appear to be the right format.  We'll have to take a second look.
Comment 8 Eclipse Genie CLA 2019-05-16 14:40:28 EDT
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.

--
The automated Eclipse Genie.