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. I don't have another problem with Eclipse.

Carsten added a target 'eclipse-prepare-webapp' to circumvent this problem and restore the xpatch'ed cocoon.roles.

Joerg

Geoff Howard wrote:
I just noticed that eclipse now has support for different destination folders for each source folder, something that was needed before one could have eclipse compile into the same build dir that cocoon does. Is there value in setting this up? (it's just a matter of adding an output attribute on the classpathentry element in .classpath.

I'd be particularly interested to hear from anyone who's tried it and found problems or benefits. I'd imagine that the cocoon build would
go faster, and possibly build clean would be less often necessary.


Geoff

Reply via email to