Eclipse Community Forums: Eclipse Platform » Why I need to add some .jar to the Java Build Path ?

Help

Home

Home » Eclipse Projects » Eclipse Platform » Why I need to add some .jar to the Java Build Path ?

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

Why I need to add some .jar to the Java Build Path ? [message #925335]

Thu, 27 September 2012 12:18

Yugi Muto
Messages: 28
Registered: February 2012

Junior Member

Hello,

there is a thing I don't understand on Eclipse 4.2.0.

If I try to import this:
import org.eclipse.emf.ecore.xmi.impl.XMIResourceFactoryImpl;
I need to add to the Java Build Path the Library corresponding :
Right click > Properties > Libraries > Add External JARs...

But if I try to import something else:
import org.eclipse.emf.ecore.resource.Resource;
I don't need to add something to the Java Build Path...

Why the behavior of Eclipse is different in the second case?

Thank you.
Regards.

Report message to a moderator

Re: Why I need to add some .jar to the Java Build Path ? [message #925497 is a reply to message #925335]

Thu, 27 September 2012 15:32

Eclipse User

Hi,

The EMF's EMF ecore XMI plugin isn't on your plugin's "required" plugins
list. You probably have the EMF resources plugin in required list (or
inherited from a required plugin that exported it). They are different
plugins. You don't need to have both as a required, and if you don't
require it then it won't be available.

Or if you are doing straight non-Eclipse java you have resources jar in
your classpath already (or inherited it through a pre-req export).

Rich

Report message to a moderator

Previous Topic:	Do VCS path ignores actually work?
Next Topic:	ResourcesPlugin.getWorkspace() returning wrong location

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Sat May 25 09:09:25 EDT 2013