You are viewing a plain text version of this content. The canonical link for it is here.
Posted to docs@cocoon.apache.org by st...@outerthought.org on 2004/05/18 16:00:04 UTC
[WIKI-UPDATE] LenyaProjectStatus LoadInEclipse Tue May 18 16:00:04 2004
Page: http://wiki.cocoondev.org/Wiki.jsp?page=LenyaProjectStatus , version: 22 on Mon May 18 13:50:39 2004 by GregorRothfuss
- The notion of translating the Lenya documentation came up, while a non-english mailing list proposal was rejected because of concerns over fracturing.
? --------------------
+ The notion of translating the Lenya documentation came up, while a non-english mailing list proposal was rejected over fracturing concerns.
? +++++++++
Page: http://wiki.cocoondev.org/Wiki.jsp?page=LoadInEclipse , version: 20 on Mon May 18 13:56:21 2004 by OlivierLange
- Please note: this seems to be quite inefficient. May be I overlooked something in the setup. But to debug, I suggest running Cocoon outside of Eclipse and using remote JVM debugging. See [Cocoon Debugging]. Note also that you'll need to rebuild the libs you wiped away with 'build eclipse-prepare-webapp' command, so that Cocoon debugging and running Cocoon Jetty within Eclipse seem to conflict. Or is there another way? [Olivier Lange]
? -- ^^^^^^^^^^^^^^^^ ------ ^^^^^^^^ ^ ------- ^^^ ------- ^ ^^^
+ Please 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 [Debugging Cocoon]. 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. Or is there another way? [Olivier Lange]
? ++ +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++ ^ ^^ ^ ++ +++++++ ++++++++++++++++++++++++++++++++++ ^^^ +++++++ ^^ ^^^^^^^^^^^^^^^^^^^^ ++