Geoff Howard wrote:
BUILD SUCCESSFUL Total time: 14 minutes 29 seconds
Yes, the build takes again very much time ... and memory. Especially because of JavaDoc, that creates 3.500 files and copies them afterwards. And copying so many so little files takes very much time :-(
Maybe the copy is unnecessary?
Furthermore our cocoon.war is between 32 and 37 MB (I don't know why it's so different. I used it last week for JSP Resin tests.) Do we have to much in the repository? Could we clean up anything?
Is that with all blocks? With most of them excluded I think it is much smaller.
I don't have another problem with Eclipse.
Me either (except the debugger and flowscript possibly)
Ok, little problems:
1. CVS commands take much time (much more than WinCVS).
2. CVS does not support a local repository using local: and I wonder why.
3. There is no really good XML editor: tabs => spaces, auto-indent, configuring the colors, catalogues as in Cocoon build. I tried XMLbuddy and Sunbow. Oxygen (http://www.oxygenxml.com/) seems to support all I need, but costs money ...
I haven't noticed the problem with slow cvs - I was just using commandline (via cygwin) and haven't tried using local:. I have had occasional problems with eclipse failing and leaving a lock file, and then repeatedly failing without telling me that the lock file was the problem. Is there a way to execute raw cvs from the command line in the cvs console? I guess this is OT for cocoon though.
Geoff
