"forrest webapp" broken?

[Stefano Mazzocchi <st...@apache.org>]

Gump is using forrest to generate the web site after the runs.

This is creating problems because forrest is too slow to allow fast 
try/fail cycles. So, my proposed solution was to use forrest dynamic 
instead.

So, I'm now playing with it.

Here is what I did:

 > cvs co xml-forrest
 > cd xml-forrest
 > ./build.sh
 > cd build/dist/shbat
 > set FORREST_HOME=[the cwd]
 > ./bin/forrest webapp
 > ./bin/forrest run
 > lynx http://127.0.0.1:8888/

and it doesn't work.

It seems that the skins, the documents, the schemas and all the other 
goodies are not copied over to the webapps.

Before I fix this, is this broken or I'm using it the wrong way?

Note: I did try "forrest war" and this does copy the documentation, but 
the cocoon.xconf file is not updated and the rest is not copied.

Please help.

-- 
Stefano.

Re: "forrest webapp" broken?

[Stefano Mazzocchi <st...@apache.org>]

Juan Jose Pablos wrote:

> Stefano,
> 
>>  > cvs co xml-forrest
> 
> we are using SVN here.

[blush] gets I should pay more attention. But why is the xml-forrest CVS 
repository still accessible?

>> Before I fix this, is this broken or I'm using it the wrong way?
>>
> 
> Yes it it broken, I could not find what was wrong apart of the libs that 
> were not copied accross...
> 
> 
>>
>> Please help.
>>
> 
> I will give it a try to see If I can fix it.

let me try downloading the version from SVN.

-- 
Stefano.

Re: 'forrest webapp' broken?

["Adam R. B. Jack" <aj...@trysybase.com>]

> The webapp has been broken, fixed and brokjen again quite a few times
> recently wqith the move to reduce the amount of copying from src to build
to
> run the local wbapp or to build the static site.

Ok, understood.

> I've fixed it a few times and know my way around what is going on fairly
> well. However, I don't have the tim to focus on this right now (I have a
> looming deadline).

Good luck w/ that.

> The problem is that the copying of files for the webapp (as in remotely
> distributed not locally run in Jetty) is getting very untidy. The target
in
> question is "webapp", it essentially uses "webapp-local" to do all the
> groundwork and then it, should, copy in all other required files (libs
etc.)
> and create a different cocoon.xconf.
>
> If anyone wnats to tackle this I recomend you look there, if you are
better
> at Ant scripting than I, then I am sure you can tidy up what I have dopne
in
> that target. If no-one can find a solution I will need to update a live
site
> around the end of April, but I won't be able to tackle it before then.

Does it help that we wish to write (and re-write) xdocs into the directory
once done? Is there a simple way to get this installed and then us just
update docs by writting into the directory? Is it easy to tell su what to
move over?

> A JIRA bug is a good idea, I'll be reminded of it when I return if it
hasn't
> been fixed beforehand.

ok.

regards

Adam

Re: 'forrest webapp' broken?

[Ross Gardler <ro...@saafe.org>]

> Cheche responded to Stefano with:
>
>> > Before I fix this, is this broken or I'm using it the wrong way?
>> >
>>
>> Yes it it broken, I could not find what was wrong apart of the libs
>> that were not copied accross...
>>
>> > Please help.
>>
>> I will give it a try to see If I can fix it.
>
> Thanks. Any update on this?
>
> We are quite eager to experiment with (and are dependent upon CVS HEAD,
> or pretty close). Would a JIRA entry help?

The webapp has been broken, fixed and brokjen again quite a few times
recently wqith the move to reduce the amount of copying from src to build to
run the local wbapp or to build the static site.

I've fixed it a few times and know my way around what is going on fairly
well. However, I don't have the tim to focus on this right now (I have a
looming deadline).

The problem is that the copying of files for the webapp (as in remotely
distributed not locally run in Jetty) is getting very untidy. The target in
question is "webapp", it essentially uses "webapp-local" to do all the
groundwork and then it, should, copy in all other required files (libs etc.)
and create a different cocoon.xconf.

If anyone wnats to tackle this I recomend you look there, if you are better
at Ant scripting than I, then I am sure you can tidy up what I have dopne in
that target. If no-one can find a solution I will need to update a live site
around the end of April, but I won't be able to tackle it before then.

A JIRA bug is a good idea, I'll be reminded of it when I return if it hasn't
been fixed beforehand.

Ross

Re: "forrest webapp" broken?

[Juan Jose Pablos <ch...@che-che.com>]

Adam R. B. Jack escribió:
> 
> 
> Thanks. Any update on this?
> 
Yes,
There is basically 2 issues here:
libs were not not copied to the webapp
skinconf and cocoon-live were overwrited so since I updated from cocoon 
2.1.4 I have just only update cocoon.xconf.

But the main one is that over build setup is really bad. we need to 
address this. I have already split on various files, but it needs to get 
  some order.


Please test it, and let me know if everything is working for you.


> We are quite eager to experiment with (and are dependent upon CVS HEAD, or
> pretty close). Would a JIRA entry help?
> 
> regards
> 
> Adam

Re: "forrest webapp" broken?

["Adam R. B. Jack" <aj...@trysybase.com>]

Cheche responded to Stefano with:

> > Before I fix this, is this broken or I'm using it the wrong way?
> >
>
> Yes it it broken, I could not find what was wrong apart of the libs that
> were not copied accross...
>
> > Please help.
>
> I will give it a try to see If I can fix it.

Thanks. Any update on this?

We are quite eager to experiment with (and are dependent upon CVS HEAD, or
pretty close). Would a JIRA entry help?

regards

Adam

Re: "forrest webapp" broken?

[Juan Jose Pablos <ch...@che-che.com>]

Stefano,

>  > cvs co xml-forrest

we are using SVN here.


> Before I fix this, is this broken or I'm using it the wrong way?
> 

Yes it it broken, I could not find what was wrong apart of the libs that 
were not copied accross...


> 
> Please help.
> 

I will give it a try to see If I can fix it.

Cheers,
Cheche