Eclipse Community Forums: Plugin Development Environment (PDE)

Help

Home

Home » Eclipse Projects » Plugin Development Environment (PDE) » Can't see what's wrong

Show: Today's Messages :: Show Polls :: Message Navigator

Can't see what's wrong [message #54308]

Fri, 10 April 2009 00:22

Eric Jain

Messages: 266
Registered: July 2009

Senior Member

After adding some dependencies ("Imported Packages") to a plug-in project,
the project is no longer building (no class files generated when I do
"Project" > "Clean..." and there is an error icon on the project in the
Package Explorer). Quite possible that there is a problem with one of the
dependencies, but I can't find any indication of what the exact error is,
either in the Problems View or Error Log, in the manifest editor, or in
the project property pages. And doing Validate Plug-ins in the launch
configuration doesn't return an error, either... Where else can I look?

Report message to a moderator

Re: Can't see what's wrong [message #54336 is a reply to message #54308]

Fri, 10 April 2009 07:09

Ankur Sharma

Messages: 84
Registered: July 2009

Member

Eric Jain wrote:
> After adding some dependencies ("Imported Packages") to a plug-in
> project, the project is no longer building (no class files generated
> when I do "Project" > "Clean..." and there is an error icon on the
> project in the Package Explorer). Quite possible that there is a problem
> with one of the dependencies, but I can't find any indication of what
> the exact error is, either in the Problems View or Error Log, in the
> manifest editor, or in the project property pages. And doing Validate
> Plug-ins in the launch configuration doesn't return an error, either...
> Where else can I look?
>

Does the project build if you remove those "imported packages". If yes, once remove them, do a clean rebuild. And then add the dependency again. If there an error something SHOULD come up in problems view. If not, open a bug report.

--
hth,
Ankur..

Report message to a moderator

Re: Can't see what's wrong [message #54471 is a reply to message #54336]

Fri, 10 April 2009 18:13

Eric Jain

Messages: 266
Registered: July 2009

Senior Member

Ankur Sharma wrote:
> Does the project build if you remove those "imported packages". If yes, once
remove them, do a clean rebuild. And then add the dependency again. If there
an error something SHOULD come up in problems view. If not, open a bug report.

Turns out the error message was being hidden by a rogue custom filter :-)

Now I have:

"A cycle was detected in the build path of project 'xyz'"

But I'm still having trouble seeing what that is due to: Performing "Look
for cycles in the dependency graph" in the manifest editor (in any of the
projects in my workspace) tells me that "the dependency graph of this
plug-in does not contain cycles". And as mentioned, I don't see any
warning or error markers in any of the projects "Java Build Properties"...

Report message to a moderator

Re: Can't see what's wrong [message #54498 is a reply to message #54471]

Fri, 10 April 2009 23:41

Eric Jain

Messages: 266
Registered: July 2009

Senior Member

Eric Jain wrote:
> "A cycle was detected in the build path of project 'xyz'"

> But I'm still having trouble seeing what that is due to: Performing "Look
> for cycles in the dependency graph" in the manifest editor (in any of the
> projects in my workspace) tells me that "the dependency graph of this
> plug-in does not contain cycles". And as mentioned, I don't see any
> warning or error markers in any of the projects "Java Build Properties"...

Follow-up: I found a circular dependency between the "Imported Packages"
of two plug-ins (though both imports were marked with with
resolution:=optional). After resolving that issue everything works fine.
Wish Eclipse had been able to pinpoint the problem more accurately (and
not simply mark the projects + all projects that depend on them with the
same, unspecific error message)!

Report message to a moderator

Re: Can't see what's wrong [message #54524 is a reply to message #54498]

Sat, 11 April 2009 02:11

Chris Aniszczyk

Messages: 674
Registered: July 2009

Senior Member

Eric Jain wrote:
> Eric Jain wrote:
>> "A cycle was detected in the build path of project 'xyz'"
>
>> But I'm still having trouble seeing what that is due to: Performing
>> "Look for cycles in the dependency graph" in the manifest editor (in
>> any of the projects in my workspace) tells me that "the dependency
>> graph of this plug-in does not contain cycles". And as mentioned, I
>> don't see any warning or error markers in any of the projects "Java
>> Build Properties"...
>
> Follow-up: I found a circular dependency between the "Imported Packages"
> of two plug-ins (though both imports were marked with with
> resolution:=optional). After resolving that issue everything works fine.
> Wish Eclipse had been able to pinpoint the problem more accurately (and
> not simply mark the projects + all projects that depend on them with the
> same, unspecific error message)!

I would file a bug if you can. In the plug-in dependencies view, there
should be a "Show State Status" option (in 3.5, this is now in a
separate view known as 'Target Platform State':

http://help.eclipse.org/ganymede/topic/org.eclipse.pde.doc.u ser/guide/tools/views/plugin_dependencies.htm

I wonder if that would have revealed the problem.

Cheers,

Chris Aniszczyk | EclipseSource Austin | +1 860 839 2465
http://twitter.com/eclipsesource | http://twitter.com/caniszczyk

Report message to a moderator