Eclipse Community Forums: Eclipse Platform

Home » Eclipse Projects » Eclipse Platform » PDE "organize manifests"

PDE "organize manifests" [message #306557]

Tue, 01 August 2006 18:35

Eclipse User

Originally posted by: wharley.bea.com

I'm using Eclipse 3.2. When I run the PDE Tools -> Organize Manifests tool
on my plug-in (org.eclipse.jdt.apt.tests), and tell it to remove unused
dependencies, it removes a required dependency, so the ensuing build
immediately breaks with "The project was not built since its build path is
incomplete" and "the type xxx cannot be resolved".

Is this a bug? Or am I misunderstanding what it means by "unused
dependencies"?

The particular situation is:

(class hierarchy:)
org.eclipse.jdt.apt.tests.APTTestBase [in plug-in org.eclipse.jdt.apt.tests]
extends
org.eclipse.jdt.core.tests.builder.BuilderTests [in
org.eclipse.jdt.core.tests.builder] extends
org.eclipse.jdt.core.tests.junit.extension.TestCase [in
org.eclipse.jdt.core.tests.compiler] extends
org.eclipse.test.performance.PerformanceTestCase [in
org.eclipse.test.performance] extends
junit.framework.TestCase [in junit.jar, in org.junit] extends ...

(partial tree of plug-in dependencies:)
org.eclipse.jdt.apt.tests depends on
org.eclipse.jdt.core.tests.builder depends on
org.eclipse.jdt.core.tests.compiler depends on
org.eclipse.test.performance depends on
junit.jar from org.junit

The problem happens because Organize Manifests removes
org.eclipse.test.performance from the plug-in manifest's list of
dependencies. Maybe it thinks that it should be getting it transitively?

Re: PDE "organize manifests" [message #306585 is a reply to message #306557]

Wed, 02 August 2006 09:30

Eclipse User

it is possibly doing that because org.eclipse.test.performace is
probably an optional dependency somewhere.

As a work around you could make it a deliberate dependency in your plugin.

Then have a look through https://bugs.eclipse.org/bugs/ and if there
isn't one there, open a bug against eclipse PDE.

Later,
PW

Re: PDE "organize manifests" [message #306619 is a reply to message #306585]

Wed, 02 August 2006 16:51

Eclipse User

Originally posted by: wharley.bea.com

"Paul Webster" <pwebster@ca.ibm.com> wrote in message
news:eaq9f9$2j3$2@utils.eclipse.org...
> it is possibly doing that because org.eclipse.test.performace is probably
> an optional dependency somewhere.
>
> As a work around you could make it a deliberate dependency in your plugin.
>
> Then have a look through https://bugs.eclipse.org/bugs/ and if there isn't
> one there, open a bug against eclipse PDE.

It looks like I'm running into
https://bugs.eclipse.org/bugs/show_bug.cgi?id=148844. That bug is aimed at
JDT, though there is disagreement whether they should fix it (ie
disagreement over whether it is really a "bug"); but the consequence of the
bug is that the PDE Organize Manifests tool does not agree with the compiler
over what is and is not a dependency.

Previous Topic:	How to get Nested ActionSets to show properly
Next Topic:	What on earth is causing "Type Foo is not accessible due to restriction on required project bar

Goto Forum:

-=] Back to Top [=-

Current Time: Fri Jul 18 00:46:35 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter