cocoon-docs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [Cocoon Wiki] Updated: LoadInEclipse
Date Tue, 28 Dec 2004 14:39:39 GMT
   Date: 2004-12-28T06:39:39
   Editor: TorstenSchlabach
   Wiki: Cocoon Wiki
   Page: LoadInEclipse

   no comment

Change Log:

@@ -206,7 +206,7 @@
   * on the 'Classpath' tab, uncheck 'Use default class path'
-  * add './tools/jetty/lib/jetty-x.y.z.jar' to the classpath (Add JARs...)
+  * add './tools/jetty/lib/jetty-x.y.z.jar' and './tools/jetty/lib/servlet-2.3.jar' to the
classpath (Add JARs...)
   * add the './tools/loader/' Folder to the classpath (Advanced... > Add Folder)
@@ -235,3 +235,23 @@
  *  Debug
 ''Note'': this seems to be a quite inefficient way to debug Cocoon, it is ''much slower''
than remote debugging. May be did I overlook a setting? I'd suggest running Cocoon outside
of Eclipse and using remote JVM debugging. See DebuggingCocoon. Note also that to run Cocoon
outside of Eclipse, you'll need to rebuild the JARs you wiped away with 'build eclipse-webapp-prepare'
from the WEB-INF\lib folder, so that Cocoon debugging and running Cocoon Jetty within Eclipse
seem to conflict.
+I tried this. I omitted the step
+ *  build eclipse-webapp-prepare
+and it did not hurt. What is this good for?
+Also I was unable to find this option:
+  * on the 'Classpath' tab, uncheck 'Use default class path'
+so I ignored this. Did not hurt; it works anyway.
+It might be worth having a look at the Tomcat plugins available for Eclipse. Maybe anything
similar exists for Jetty as well.

View raw message