Date: 2004-12-28T06:20:04
   Editor: TorstenSchlabach
   Wiki: Cocoon Wiki
   Page: LoadInEclipse
   URL: http://wiki.apache.org/cocoon/LoadInEclipse

   no comment

Change Log:

------------------------------------------------------------------------------
@@ -159,7 +159,17 @@
  * Import the Cocoon project into your workspace according to the section 
''Eclipse, its workspace and how to import a project''
  * Go to the External Tools dialogue by clicking on the External Tools button 
(it's a right pointing triangle on a green circle with a red tool case)
 
- * 
+attachment:eclipse-cocoon-setup-01.jpg
+
+ * Give your external tool a name such as ''Build Cocoon'' and use the 
''Browse'' button to choose the build.bat or build.sh file and set the working 
directory to the Cocoon source directory.
+
+attachment:eclipse-cocoon-setup-02.jpg
+
+ * Turn over to the ''Refresh'' tab and make sure you configure Eclipse to do 
a refresh of its view of the source (and binary) tree after the build. 
+
+attachment:eclipse-cocoon-setup-03.jpg
+
+''Note'': This again is something very ''eclipsy'': Probably for performance 
reasons Eclipse has a very strong caching of file system contents and is 
heavily relying on the assumption that during development all changes to the 
file system will happen through the Eclipse workbench itself, either by the 
user editing or the compiler building any output files. As the external Ant 
build breaks this assumption the refresh is needed to make sure Eclipse is in 
synch again after the build.
 
 === Running Cocoon Jetty from within Eclipse ===
 

Reply via email to