Hi wh1z,

thanks for sharing your experiences!

wh1z schrieb:
Yes you guys are right! I cleaned up the directory with a fresh install and
just ran the build.sh and voila it worked. Interesting thing to note is that
if i do run configure.sh (as mentioned in the installation instructions) to
generally alter a few properties, cocoon isn't really comfortable with that,

does someone else use the configure.sh script successfully?
Does it simplify the installation? WDOT?

-- Andreas



probably needs a build alteration as well? I will keep digging though. For
now, running just the build.sh did the trick and i have the default page up
and running. Sac, yes i have used the cocoon shipped along with lenya and i haven't
modified any part of it yet :-P
I truly appreciate your help on this. Would post my findings on my research
since this is my first step towards cocoon

Regards
Sid


sac sha wrote:
Hi

I agree that only build.sh will do the task.
But if you are using some other cocoon rather than one shipped with lenya.
Dont forget to mention it correctly in local.build.properties.

Regards
Sac

On Tue, Jan 27, 2009 at 11:18 PM, Richard Frovarp
<[email protected]>wrote:

Andreas Hartmann wrote:

Hi wh1z,

wh1z schrieb:

Well i am running the usual scripts shipped with lenya.
1. configure.sh - i changed the cocoon directory during configuration
from
externals/cocoon-2.1.12-dev to just cocoon

did you rename the Cocoon directory accordingly? Or did you download
Cocoon separately? Is there a special reason for this change?

BTW, does someone else use the configure.sh script? I haven't tried it
for
a while.

 I don't know that I've ever used the configure.sh script.

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]






--
Andreas Hartmann, CTO
BeCompany GmbH
http://www.becompany.ch
Tel.: +41 (0) 43 818 57 01


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to