Sorry I missed this post because it got mixed in the rest of the Cocoon
users posts while I expected it to show up in my inbox only.
I have looked at external tools and ant build... and noticed what the
difference is:
If you right click on the the build.xml file in your Cocoon repository and
,
Torsten
--- Weitergeleitete Nachricht / Forwarded Message ---
Date: Mon, 27 Dec 2004 17:05:49 +0100 (MET)
From: Torsten Schlabach [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: RE: Still challenged with building Cocoon in Eclipse
Hi!
Just wondering, did you manage to get it to work?
Thanks
Hi!
Just wondering, did you manage to get it to work?
Thanks for asking ...
The answer is: yes and no! But I think I finally sorted this out, I am
just not yet too sure about it.
To make a long story short:
I finally managed to build Cocoon using the external Ant supplied by the
Cocoon
Torsten Schlabach wrote:
1. External tasks. The Cocoon build process starts with building some Ant
tasks (one of them being XPatch) that get used immediately during the very
same run of Ant. I actually wonder why that is and why those tasks are not
readily compiled to .class files inside the tools
Gregor,
i wonder that too. imho worth bringing up on the dev list.
I will do that!
presumably it runs inside the same VM as eclipse, and you can add these
options to your eclipse startup parameters.
i use eclipse.exe -Xmx1024m -Xms512m , for instance.
I remember having seen an option to
When put this way I assume I do build Cocoon in Eclipse 3.1 according to
your definitions. The ExceptionInInitializerError is caused by the fact that
Eclipse defaults to it's own Ant 1.6.2 version, as you've already figured
out. I solved this problem by going into the properties of the run ...
Torsten Schlabach wrote:
compile-deprecated:
BUILD FAILED: java.lang.ExceptionInInitializerError
i would advise to disable deprecation support in local.build.properties
it's a good check for any custom code anyway, helped me spot a couple
problems in lenya that way.
-gregor
Gregor,
i would advise to disable deprecation support in local.build.properties
I am not really sure what compile-deprecated does in Cocoon, but from what
I found in between my initial posting and now this would be circumventing
and not solving the problem.
The problem seems to be that the
