### Eclipse Workspace Patch 1.0
#P org.eclipse.jdt.core
Index: model/org/eclipse/jdt/core/compiler/CompilationParticipant.java
===================================================================
RCS file: /cvsroot/eclipse/org.eclipse.jdt.core/model/org/eclipse/jdt/core/compiler/CompilationParticipant.java,v
retrieving revision 1.12
diff -u -r1.12 CompilationParticipant.java
--- model/org/eclipse/jdt/core/compiler/CompilationParticipant.java	29 Mar 2006 03:08:49 -0000	1.12
+++ model/org/eclipse/jdt/core/compiler/CompilationParticipant.java	11 Jan 2007 19:07:03 -0000
@@ -23,6 +23,11 @@
  * So the notified events are the result of a build action, a clean action, a reconcile operation 
  * (for a working copy), etc.
  * <p>
+ * Code that participates in the build should in general be implemented with a separate Builder,
+ * rather than a CompilationParticipant. It is only necessary to use a CompilationParticipant if 
+ * the build step needs to interact with the Java build, for instance by creating additional 
+ * Java source files that must themselves in turn be compiled. 
+ * <p>
  * Clients wishing to participate in the compilation process must suclass this class, and implement
  * {@link #isActive(IJavaProject)}, {@link #aboutToBuild(IJavaProject)}, 
  * {@link #reconcile(ReconcileContext)}, etc.