Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 331266 - Classpath is missing dependencies from Manifest.mf
Summary: Classpath is missing dependencies from Manifest.mf
Status: CLOSED WONTFIX
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.7   Edit
Hardware: PC Windows 7
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: PDE-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-27 00:52 EST by Eike Stepper CLA
Modified: 2019-09-09 02:24 EDT (History)
1 user (show)

See Also:

Attachments
Package Explorer (81.94 KB, image/png)
2010-11-27 00:52 EST, Eike Stepper CLA 		no flags Details
Manifest Editor (Dependency Hierarchy) (40.38 KB, image/png)
2010-11-27 00:53 EST, Eike Stepper CLA 		no flags Details
View All 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 Eike Stepper CLA 2010-11-27 00:52:39 EST 
Created attachment 183971 [details]
Package Explorer

Version: 3.7.0
Build id: I20101028-1441

I have a plugin in my workspace that recursively requires the following bundles from the target platform:

ClientDemo (WS)
--> org.eclipse.emf.cdo (TP)
--> org.eclipse.emf.cdo.common (TP)
--> org.eclipse.emf.ecore.change (TP)

But the last one is not put on the classpath!

I'll attach two screenshots to show this issue. At runtime I get ClassDefNotFoundErrors
Comment 1 Eike Stepper CLA 2010-11-27 00:53:31 EST 
Created attachment 183972 [details]
Manifest Editor (Dependency Hierarchy)
Comment 2 Eclipse Webmaster CLA 2019-09-06 15:35:22 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.
Comment 3 Julian Honnen CLA 2019-09-09 02:24:06 EDT 
Please remove the stalebug flag, if this issue is still relevant and can be reproduced on the latest release.