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

Bug 364288

Summary:	API tools should warn the user when adding new dependencies
Product:	[Eclipse Project] PDE	Reporter:	Laurent Goubet <laurent.goubet>
Component:	API Tools	Assignee:	PDE API Tools Inbox <pde-apitools-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	enhancement
Priority:	P3
Version:	3.7
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
Whiteboard:	stalebug

Description Laurent Goubet

2011-11-21 05:32:06 EST

I recently added a dependency to a new library/bundle to my plugins, using import-package towards things that the plugins did not previously knew. Doing this, I broke any adopter of my previous API ... without even realizing it. These clients were greeted with a ClassNotFoundException as soon as they updated and launched their tool with my new API (see also bug 364265).

API tools should probably have a warning for "new dependencies" as these might very well break adopters of the API. The workaround I found, changing from "import-package" to "require-bundle" and reexporting the new dependency, is no more than a hack for "Java application" launches within Eclipse, and will still fail for standalone usages of my plugins.

Comment 1 Lars Vogel

2019-11-14 03:17:22 EST

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.

If the bug is still relevant, please remove the "stalebug" whiteboard tag.