Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Plugin Development Environment (PDE) » JDT bootclasspath problem(Upgrading PDE (and Java) results in ERROR: The type java.lang.Object cannot be resolved.)
JDT bootclasspath problem [message #1754243] Wed, 15 February 2017 16:40 Go to next message
Steve Taylor is currently offline Steve TaylorFriend
Messages: 3
Registered: February 2017
Junior Member
I'm upgrading a collection of headless PDE builds from:

org.eclipse.pde.build_3.8.2.v20121114-140810
to
org.eclipse.pde.build_3.9.100.v20150521-1524

and

java 6 to java 7.

Nothing else has changed. I've started to get errors along the lines of:

"The type java.lang.Object cannot be resolved."

I'm guessing that somehow the bootclasspath is not getting set. I've read countless posts along similar lines but the solutions either don't apply or don't work.

Anyone seen this or know what the problem is?

Thanks

Report message to a moderator

Re: JDT bootclasspath problem [message #1754323 is a reply to message #1754243] Thu, 16 February 2017 11:45 Go to previous messageGo to next message
Steve Taylor is currently offline Steve TaylorFriend
Messages: 3
Registered: February 2017
Junior Member
*UPDATE* - launching python bootstrapper in a different way has fixed this - not sure why but I'm presuming the cause was environmental. If I get time I'll go back and investigate why and add a further update.

[Updated on: Thu, 16 February 2017 11:46]

Report message to a moderator

Re: JDT bootclasspath problem [message #1754345 is a reply to message #1754323] Thu, 16 February 2017 15:00 Go to previous messageGo to next message
Steve Taylor is currently offline Steve TaylorFriend
Messages: 3
Registered: February 2017
Junior Member
*FURTHER UPDATE* - I spoke to soon - problem is back.

Report message to a moderator

Re: JDT bootclasspath problem [message #1754997 is a reply to message #1754345] Sat, 25 February 2017 17:21 Go to previous message
Stephan Herrmann is currently offline Stephan HerrmannFriend
Messages: 1845
Registered: July 2009
Senior Member
Do you have a "global" build.properties for your build?
Does it contain an entry for "JavaSE-1.7"?
Here's the entry from a build that I maintain:
JavaSE-1.7=/shared/common/oracle-jre1.7.0/lib/rt.jar:/shared/common/oracle-jre1.7.0/lib/charsets.jar:/shared/common/oracle-jre1.7.0/lib/deploy.jar:/shared/common/oracle-jre1.7.0/lib/management-agent.jar:/shared/common/oracle-jre1.7.0/lib/alt-rt.jar:/shared/common/oracle-jre1.7.0/lib/plugin.jar:/shared/common/oracle-jre1.7.0/lib/security/US_export_policy.jar:/shared/common/oracle-jre1.7.0/lib/security/local_policy.jar:/shared/common/oracle-jre1.7.0/lib/resources.jar:/shared/common/oracle-jre1.7.0/lib/jsse.jar:/shared/common/oracle-jre1.7.0/lib/jce.jar:/shared/common/oracle-jre1.7.0/lib/javaws.jar


OTOH, when you say you changed from Java 6 to 7, it is not clear if this concerns the JVM that runs the build or the target of the software being built?

Report message to a moderator

Previous Topic:API to access OSGi information at compile time
Next Topic:Register a ToolBar in an e4 view
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ]

Current Time: Sun Aug 14 00:23:27 GMT 2022

Powered by FUDForum. Page generated in 0.01769 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top

Sign up to our Newsletter

A fresh new issue delivered monthly