View source for FAQ When does PDE change a plug-in's Java build path?

Whenever you add dependent plug-ins in the Manifest Editor, the underlying  classpath has to be updated to give you access to the classes defined by the plug-in. When you save the <tt>plugin.xml</tt> file, the  editor will also update the Java build path: the <tt>.classpath</tt> file.

In Eclipse 3.0, the PDE uses a special classpath entry called a <i>classpath container</i> to avoid having to directly modify the <tt>.classpath</tt> file every time your plug-in&#146;s dependencies change.  During builds, this classpath container resolves to  the set of dependencies specified in the <tt>plugin.xml</tt> file.

Regardless of whether classpath containers are used, it makes little  sense to edit the <tt>.classpath</tt> file by hand or to make changes directly to the '''Java Build Path''' property page for plug-in projects.  Any changes you make there will be silently  overwritten the next time you save the Manifest Editor.

== See Also: ==
*[[FAQ Why doesn't my plug-in build correctly?]]
*[[FAQ What is the classpath of a plug-in?]]

{{Template:FAQ_Tagline}}