Difference between revisions of "FAQ When does PDE change a plug-in's Java build path?"

From Eclipsepedia

Jump to: navigation, search
m
m
Line 1: Line 1:
Whenever you add dependent plug-ins in the Manifest Editor, the underlying  
+
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 in question. When you save the <tt>plugin.xml</tt> file, the editor will also update the Java build path: the <tt>.classpath</tt> file.
classpath has to be updated to give you access to the classes defined by the
+
plug-in in question. 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
+
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.
<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  
+
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.
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: ==
 
== See Also: ==
*[[FAQ_Why_doesn't_my_plug-in_build_correctly%3F]]
+
*[[FAQ Why doesn't my plug-in build correctly?]]
*[[FAQ_What_is_the_classpath_of_a_plug-in%3F]]
+
*[[FAQ What is the classpath of a plug-in?]]
  
 
{{Template:FAQ_Tagline}}
 
{{Template:FAQ_Tagline}}

Revision as of 04:54, 17 June 2006

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 in question. 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.