[ http://issues.apache.org/jira/browse/FOR-690?page=all ]
Brian Dube updated FOR-690:
---
Attachment: menu.xmap.diff
A change in the catalogue entry related to i18n was missed.
> Use locationmap in menu.xmap
>
>
> Key: FOR-6
Mark Eggers wrote:
> Another note.
>
> Falling back to the older version of xml-resolver
> solves the other problem about taking both ANT_HOME
> and $ANT_HOME/bin out of my environment and PATH.
Hmm, how can you tell that it is not using
Forrest's packaged Ant?
> There is definitely something no
Gav wrote:
>
> > -Original Message-
> > From: Mark Eggers
> >
> > Another note.
> >
> > Falling back to the older version of xml-resolver
> > solves the other problem about taking both ANT_HOME
> > and $ANT_HOME/bin out of my environment and PATH.
> >
> > There is definitely somethi
> -Original Message-
> From: Mark Eggers [mailto:[EMAIL PROTECTED]
> Sent: Saturday, 20 May 2006 6:51 AM
> To: dev@forrest.apache.org
> Subject: Re: [heads up] Ant upgraded, please test
>
> Another note.
>
> Falling back to the older version of xml-resolver
> solves the other problem ab
> -Original Message-
> From: Ross Gardler [mailto:[EMAIL PROTECTED]
> Sent: Saturday, 20 May 2006 6:35 AM
> To: Forrest Developers List
> Subject: help - yet another Dispatcher false start
>
> I again tried to work with the dispatcher this evening. However, once
> again I failed miserabl
Ross Gardler wrote:
I again tried to work with the dispatcher this evening. However, once
again I failed miserably.
I just don't seem to be able to get things working.
I started from the getting started document, but that seems to be
horribly out of date. It still talks about using specific r
Ross,
Here's what works on Windows/2000 Professional using
jdk 1.5.0_06. Your mileage may vary.
1) Update to the latest svn head. At least under
Windows this is necessary due to some xml-resolver
issues.
2) cd $FORREST_HOME/etc
3) Run ./builddispatcher.sh (I run under cygwin). Use
builddispa
Another note.
Falling back to the older version of xml-resolver
solves the other problem about taking both ANT_HOME
and $ANT_HOME/bin out of my environment and PATH.
There is definitely something not friendly to Windows
in the development version of the resolver, at least
when it's used with ant.
Bertrand Delacretaz wrote:
On 5/19/06, Ross Gardler <[EMAIL PROTECTED]> wrote:
...Basically, you need to create a forrest.properties.xml file, you
can see
and example in the Daisy plugin in the whiteboard. You can add whatever
properties you want to this file and they will be axposed in the si
I again tried to work with the dispatcher this evening. However, once
again I failed miserably.
I just don't seem to be able to get things working.
I started from the getting started document, but that seems to be
horribly out of date. It still talks about using specific revisions and
applyin
David,
I did the switch, and ran into the same problem as
before (static site not being built on Windows).
I did a network trace while building a static site
with both the old resolver and the new resolver.
With the old resolver, a forrest site pulled back
plugins.xml and the Google logo.
With
Reverting to an older xml-resolver jar seems to have
fixed the problem.
site-author builds successfully.
A dispatcher site builds successfully.
A normal seed site builds successfully.
Thanks very much - nicely done.
/mde/
--- David Crossley <[EMAIL PROTECTED]> wrote:
> David Crossley wrote:
On 5/19/06, Ross Gardler <[EMAIL PROTECTED]> wrote:
...Basically, you need to create a forrest.properties.xml file, you can see
and example in the Daisy plugin in the whiteboard. You can add whatever
properties you want to this file and they will be axposed in the sitemap
just like any other p
Ferdinand Soethe wrote:
OK, I just committed the last fixes to broken links.
Docs compiles ok again. While at it I cleaned up a number of
technically working but contentwise useless links.
Still present are some inconsistencies in handling files that are
versioned but should probably not be. Will
Bertrand Delacretaz wrote:
Hi,
I'd like to make the i18n action and matcher settings (see [1] and [2]
for a list of their options) configurable in forrest.properties.
This would allow for different ways of specifying the current locale:
URL, request parameter, browser config, etc.
Question is,
On 5/19/06, Ross Gardler <[EMAIL PROTECTED]> wrote:
...I guess, since David has you up and running with this use case we will
put the improvement if i18n handling on hold. Current solution works for
you and I am limited on time right now...
I think my use-case will work fine once the i18n stuf
Ferdinand Soethe wrote:
> David Crossley wrote:
>
> > This is just a guess at the problem.
> > I reverted SVN to an older version of xml-resolver.
>
> > Would a Windows user please 'svn up' and try again.
>
> Yes, that fixed the problem.
Thanks. Okay we need to find out how to get more
verbose
Hi,
I'd like to make the i18n action and matcher settings (see [1] and [2]
for a list of their options) configurable in forrest.properties.
This would allow for different ways of specifying the current locale:
URL, request parameter, browser config, etc.
Question is, do you already have a recom
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 affects
David Crossley wrote:
> This is just a guess at the problem.
> I reverted SVN to an older version of xml-resolver.
> Would a Windows user please 'svn up' and try again.
Yes, that fixed the problem.
--
Ferdinand Soethe
Cyriaque Dupoirieux wrote:
> le 19/05/2006 10:44 David Crossley a ?crit :
> >David Crossley wrote:
> >
> >>David Crossley wrote:
> >>
> >>>I am using Java-1.4 ... could that be the difference?
> >>>
> >>Installed Java5 and all is well for me on Mac OS X.
> >>
> >>
> validate-xdo
Bertrand Delacretaz wrote:
(moving this from the user@ list here)
On 5/17/06, Ross Gardler <[EMAIL PROTECTED]> wrote:
...I've been wanting to improve the i18n support for some time. By using
the locationmap it should be possible to simulate the "Apache httpd
magic" in a static environment. But
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 pr
le 19/05/2006 10:44 David Crossley a écrit :
David Crossley wrote:
David Crossley wrote:
I am using Java-1.4 ... could that be the difference?
Installed Java5 and all is well for me on Mac OS X.
validate-xdocs:
BUILD FAILED
C:\src\forrest\main\targets\validate.xml:146: C
David Crossley wrote:
> David Crossley wrote:
> >
> > I am using Java-1.4 ... could that be the difference?
>
> Installed Java5 and all is well for me on Mac OS X.
>
> > > validate-xdocs:
> > >
> > > BUILD FAILED
> > > C:\src\forrest\main\targets\validate.xml:146: Could
> > > not validate docum
David Crossley wrote:
> In my opinion, no. We will just end up with a stack
> of xml validation problems to fix.
> Since this is only an intermittent problem for
> some Windows users, why not just edit your
> forrest.properties file.
Fine. will do that.
> Really the Windows users will need to
Ferdinand Soethe wrote:
>
> Tried turning validation off completely
>
> forrest.validate=false
>
> and it has started processing documents.
>
> Should I commit that change until we have fixed the problem?
In my opinion, no. We will just end up with a stack
of xml validation problems to fix.
S
Tried turning validation off completely
forrest.validate=false
and it has started processing documents.
Should I commit that change until we have fixed the problem?
--
Ferdinand Soethe
[
http://issues.apache.org/jira/browse/FOR-102?page=comments#action_12412498 ]
David Crossley commented on FOR-102:
Link to some other info:
http://cocoon.apache.org/2.1/userdocs/offline/ant.html
http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=1147960
29 matches
Mail list logo
