From: Geoff Howard [mailto:[EMAIL PROTECTED]
> Joerg Heinicke wrote: > > Why exactly? I only found out - when setting output path to > > WEB-INF/classes - that Eclipse kicked the complete content > and replaces > > the xpatch'ed cocoon.roles. > > Maybe that is the smarter way to go. I've been wanting to > set the output path to the same as the build before > prepare-webapp (i.e., > build/cocoon-2.1rc1dev/classes, > build/cocoon-2.1rc1dev/scratchpad/dest, > and so on for each source path) so I could let eclipse do the > compiling (since it usually already has anyway) but still use > the regular build. I don't know that eclipse's compiling is > orders of magnitude better, but > it does it incrementally. > > But compiling/copying straight to WEB-INF would save even > more time in > some situations. Well, I'll start experimenting and see what > I learn. > Anything to improve: > BUILD SUCCESSFUL > Total time: 14 minutes 29 seconds Therefore I added the paramter ide.eclipse.outputdir to build.properties. Here you can set your WEB-INF/classes directory and compile directly into your servlet container. This works pretty good for me. If you need more fine grained output directories this should be possible but I haven't needed it yet. HTH Reinhard
