Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 520037

Summary: Remove forced compile-time dependency on the deployment assembly jars
Product: [Eclipse Project] JDT Reporter: Edward Pershwitz <epersh>
Component: CoreAssignee: JDT-Core-Inbox <jdt-core-inbox>
Status: CLOSED WONTFIX QA Contact:
Severity: normal    
Priority: P3 CC: stephan.herrmann
Version: 4.6   
Target Milestone: ---   
Hardware: All   
OS: Linux   
Whiteboard: stalebug

Description Edward Pershwitz CLA 2017-07-21 14:39:17 EDT 
Eclipse forces jars in the deployment assembly onto the build path of the project. There needs to be a mechanism to override this behavior. Currently, for a scenario when a jar needs to be on the class path at run time but not on the build path at compile time deployment has to be handled manually.

Here's an example scenario:  Project A, a dynamic web project, defines interface I; project B, a utility project, depends on A and defines class C that implements I. Code in A instantiates C reflectively by name and casts it to I. A knows nothing about B. Forcing B on the build path for A creates a circular dependency.
Comment 1 Eclipse Genie CLA 2020-04-13 17:49:56 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. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. 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.
Comment 2 Stephan Herrmann CLA 2020-04-13 18:49:26 EDT 
If this is still relevant to s.o., please consider that JDT itself does not know about "deployment assembly", so likely some other plugin which manages the deployment assembly should be the target of this report?