Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: for the plan.

Jump to: navigation, search

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

Revision as of 23:35, 24 May 2012 by (Talk | contribs) (Removed unneccessary wording which were confusing)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

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 plugin.xml file, the editor will also update the Java build path: the .classpath file.

In Eclipse 3.0, the PDE uses a special classpath entry called a classpath container to avoid having to directly modify the .classpath file every time your plug-in’s dependencies change. During builds, this classpath container resolves to the set of dependencies specified in the plugin.xml file.

Regardless of whether classpath containers are used, it makes little sense to edit the .classpath 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:

This FAQ was originally published in Official Eclipse 3.0 FAQs. Copyright 2004, Pearson Education, Inc. All rights reserved. This text is made available here under the terms of the Eclipse Public License v1.0.

Back to the top