Now, I have not been looking at it until some minutes ago. But unfortunately it did not help me. The first steps I have already done and the xpatching of any files I don't really need (at least until now).

And I wonder how the validate jars works for you if not only by accident. The hard coded "relativation" of a possible absolute path can not work in many cases. If I deactivate javadoc and validate jars it works for me as I want it.

Joerg

Steven Noels wrote:
Joerg Heinicke wrote:

We have a global repository that now also stores the Cocoon 2.1.1 sources. If one wants to use Cocoon in his project he has to build it after setting some properties (the normal local.*.properties). The Cocoon sources in the repository shall stay untouched of course. Therefore I set the properties ${build.root}, ${tools.tasks.dest}, ${tools.loader.dest} and almost everything works ...


Joerg, off the top of my head: have you looked at http://wiki.cocoondev.org/Wiki.jsp?page=YourCocoonBasedProject

We use this approach for a large Woody-based project we are working on with a customer, and it works rather well.

</Steven>

-- System Development VIRBUS AG Fon +49(0)341-979-7419 Fax +49(0)341-979-7409 [EMAIL PROTECTED] www.virbus.de



Reply via email to