Nico Veenkamp wrote:
I have been on this list for quite some time but never contributed just
listened. Recently I started following the Forrest development more
closely and today I pullen the forrest tree from SVN onto my machine and
succesfully build forrest and then seeded a test site.
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project forrest has an issue affecting its community integration.
This issue affects 1
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project forrest-test has an issue affecting its community integration.
This issue
quote David Crossley/quote
[snip]
Or am I missing other places I need to translate stuff.
Such questions have been asked many times.
The answer is that it is not well documented
and you need to explore.
ok
Each time we encourage people to do so, but
the docs remain in the same state.
[
http://issues.apache.org/jira/browse/FOR-822?page=comments#action_12416881 ]
Gavin commented on FOR-822:
---
I tested this using checkout 414415 and on a Dispatcher and i18n enabled
seed-sample site and these errors are now gone and it all seems to work fine
(as
David Crossley escribió:
BTW is the blog entry by Cheche still valid for 0.8?
Don't know. Someone needs to follow it and
hopefully enhance our demo.
After todays change on the repository, I can confirm that they seem to work.
Please report back if you find any trouble.
Cheers,
cheche
Nico Veenkamp wrote:
Did you commit this demo already to the repository? If so, where can I
find it? I grepped the repository but did not find a link to FOR-707.
Of course this may also reflect sadly on my grepping skills :)
You need to do:
cd $FORREST_HOME
svn update
... See
