[ http://issues.apache.org/jira/browse/FOR-905?page=all ]
Mark Eggers updated FOR-905:
Attachment: forrest-sh.patch
Patch to handle apparent change in Cygwin's behavior
> Recent change in cygwin appears to prevent the classpath for loop in the
&
Project: Forrest
Type: Bug
Components: Core operations
Versions: 0.8-dev
Reporter: Mark Eggers
Priority: Minor
I recently upgraded Cygwin on a Windows/2000
Professional machine to:
bash-3.1$ uname -a
CYGWIN_NT-5.0 phoenix 1.5.20(0.156/4/2) 2006-07-01
02:22 i686 Cygwin
bash
I recently upgraded Cygwin on a Windows/2000
Professional machine to:
bash-3.1$ uname -a
CYGWIN_NT-5.0 phoenix 1.5.20(0.156/4/2) 2006-07-01
02:22 i686 Cygwin
bash-3.1$ cygpath --version
cygpath (cygwin) 1.42
Path Conversion Utility
Copyright 1998, 1999, 2000, 2001, 2002, 2003, 2004,
2005 Red Hat,
Thanks everyone for responding. I had based my work
on reading the code (before there was documentation).
I didn't wade through the entire xslt sheet, so I was
a bit unclear as to how it all worked.
I did read the new documentation (forrest run, forrest
toolbar to point at ls.contracts).
It's p
Hello,
Adding a second css file with branding-css-links.ft
does not work under Firefox, but does under IE 6. It
turns out that there is a reason according to both the
Bugzilla comments and the W3 recommendations:
https://bugzilla.mozilla.org/show_bug.cgi?id=223410
http://www.w3.org/TR/html4/pres
[ http://issues.apache.org/jira/browse/FOR-889?page=all ]
Mark Eggers updated FOR-889:
Attachment: static-cocoon.log
dynamic-cocoon.log
I put together two runs.
static build of resolver-test after changing verbosity to 10 in
forrest
[ http://issues.apache.org/jira/browse/FOR-889?page=all ]
Mark Eggers updated FOR-889:
Attachment: ant-debug.log
I pulled down the two jars from your site this morning and did the following:
a) Replaced ant.jar in $FORREST_HOME/tools/ant/lib with the
David,
> Hmm, how can you tell that it is not using
> Forrest's packaged Ant?
Without taking $ANT_HOME and $ANT_HOME/bin out of my
environment:
C:\src\sites-src\resolver-test>ant -version
Apache Ant version 1.6.5 compiled on June 2 2005
C:\src\sites-src\resolver-test>%FORREST_HOME%\tools\ant\bin
[ http://issues.apache.org/jira/browse/FOR-889?page=all ]
Mark Eggers updated FOR-889:
Attachment: debug-new.log
Forgot to attach file:
bash-3.1$ forrest -debug validate-xdocs >& debug-new.log
> Use by Ant of newer catalog entity resolver f
[
http://issues.apache.org/jira/browse/FOR-889?page=comments#action_12412982 ]
Mark Eggers commented on FOR-889:
-
Here's the result from:
bash-3.1$ forrest -debug validate-xdocs >& debug-new.log
> Use by Ant of newer catalog entity resol
[ http://issues.apache.org/jira/browse/FOR-889?page=all ]
Mark Eggers updated FOR-889:
Attachment: o-cyg-resolver.log
This file was generated with the old resolver by running:
forrest -v validate-xdocs >& o-cyg-resolver.log
under cygwin and Windo
[ http://issues.apache.org/jira/browse/FOR-889?page=all ]
Mark Eggers updated FOR-889:
Attachment: n-cyg-resolver.log
n-cyg-resolver.log is the new resolver generated by running:
forrest -v validate-xdocs >& n-cyg-resolver.log
under cygwin on Windo
David,
> We should be able to set "verbosity=10" in a
> CatalogManager.properties file. We have one in
> main/webapp/WEB-INF/classes which is properly
> used by Cocoon.
I didn't see one here.
> We also have a project one at
> site-author/classes/CatalogManager.properties
> but it seems to have n
Ross,
Ah, ha! That's the problem. I never specified the
directory location in the required plugins line.
You put:
project.required.plugins.src=${forrest.home}/plugins,${forrest.home}/whiteboard/plugins
I normally only put:
project.required.plugins=org.apache.forrest.plugin.output.pdf,org.apa
Ross,
> > 2) cd $FORREST_HOME/etc
> >
> > 3) Run ./builddispatcher.sh (I run under cygwin).
> > Use builddispatcher.bat if you're running under
> > CMD.exe
>
> There should be no need for that with head as
> plugins should be auto deployed from src if they are
> available.
I think that the au
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
h ant.
/mde/
--- Mark Eggers <[EMAIL PROTECTED]> wrote:
> 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
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:
patcher, so I build those plugins in order to work
with contracts, views, and custom css files.
What other information can I go after that would help?
/mde/
--- David Crossley <[EMAIL PROTECTED]> wrote:
> Mark Eggers wrote:
> So i gather that you don'
I did.
Actually, I did something much more severe. I deleted
my entire Forrest directory and pulled down a fresh
copy via subversion.
I then did the following:
1) ./builddispatcher.sh in $FORREST_HOME/etc
2) Built each of the plugins in $FORREST_HOME/plugins
3) Built glossary and citations in
The only way I've been able to build static sites
since the upgrade of ant is to turn off validation.
I'm running on Windows/2000 Professional and jdk
1.5.0_06. I've removed ANT_HOME, all CLASSPATH
information, and %ANT_HOME%\bin from my path.
When I do that, I get the following error when runni
I'm running Furrest under nt-emacs, the cygwin bash
shell, and jdk 1.5.0_04.
I did a /build.sh clean in main/, a
./builddispatcher.sh in etc/ (which apparently does a
clean), and then built all the standard plugins.
I monitored ./build.sh test via Ethereal and didn't
see any DTD traffic.
I did s
My fault on that.
I only read the Install guide at:
http://localhost/forrest/docs_0_80/howto/howto-dispatcher-install.html
which doesn't seem to mention the patch.
I have updated to the HEAD revision, and have applied
the patch.
I added the patch and all is OK.
Would it be appropriate to add
Once again I have time use forrest. I would like to
create sites that don't look like they've been built
from forrest.
The next generation of skinning (ie., dispatcher)
looks perfect for that.
My goals are to work through a completely custom
layout, and then write up how I approached the design
Thorsten,
I don't know how comfortable you are with subversion.
Wouldn't a branch be good for this?
I'm thinking, branch, hack, test, merge. Since you
are the primary (only?) person working on the views
plugin would this create a merge challenge?
Just some random thoughts from a (mostly) reade
[ http://issues.apache.org/jira/browse/FOR-724?page=all ]
Mark Eggers updated FOR-724:
Attachment: catalog.forrest.diff
Trivial patch applied. Tested and works under submitted environment. I am now
able to use xae under emacs again.
> catalog.forr
1.5, emacs 21.4, xae 1.0 beta 8, psgml
1.2.5
Reporter: Mark Eggers
Priority: Trivial
Typo in catalog.forrest prevents older tools from validating documents. There
is an xml style comment in catalog.forrest
--
This message is automatically generated by JIRA.
-
If you think it was
Changing the script did not help. However, I did the
following and things work.
1. svn up (now at revision 290635)
2. cd $FORREST_HOME/main
3. ./build.sh clean
4. ./buidl.sh
5. cd $FORREST_HOME/plugins
6. build pdf output plugin only
7. verify the default environment works:
cd ~mdeggers/src/site
I'll change my script and see how that works.
Running your script under cygwin and setting up the
following environment variable:
export FORREST_HOME=C:\\src\\forrest
created the ${plugins.localDeploy-dir} again.
I think I found that problem:
should be
Building views with your $FORREST_HO
I'll add the --noconfig and see what happens. I am
using Sun's java instead of GNU's java as supplied by
Fedora. My PATH is set appropriately to call Sun's
java first. I've not had any problems until recently.
I've also seen the same problem on Windows/2000
Professional.
Same error.
I also de
nvironment.
Thoughts on what I might be doing wrong (or different)
would be greatly appreciated.
/mde/
--- Juan Jose Pablos <[EMAIL PROTECTED]> wrote:
> Mark Eggers wrote:
> > This is on Windows/2000 Professional. I've not
> tried
> > it on Fedora Core 4 yet.
>
> It
This is on Windows/2000 Professional. I've not tried
it on Fedora Core 4 yet.
svn info:
Path: .
URL: http://svn.apache.org/repos/asf/forrest/trunk
Repository UUID: 13f79535-47bb-0310-9956-ffa450edef68
Revision: 290585
Node Kind: directory
Schedule: normal
Last Changed Author: rgardler
Last Change
-- Lots of good stuff snipped --
Anil,
Very nice and informative. Great job!
If you don't mind, I would like to use this as an
example for programmers here to follow.
Being mostly on the operations side of the house, I
often get code thrown over the wall with no idea of
what was fixed, how it
I apologize for joining this discussion late.
--- Ross Gardler <[EMAIL PROTECTED]> wrote:
> Ferdinand Soethe wrote:
> > I think it would be great to have optional support
> > for advanced features of smarter browsers. Though
> > that means you would have to support several
access
> > options (sm
l file you will get non-validating html from
the pelt skin. Even if you don't include a meta tag, you get an empty
element in the output and the html no longer validates.
Hopefully I can get that figured out.
--
Mark Eggers <[EMAIL PROTECTED]>
llow the pattern for other translations
in $FORREST_HOME/main/webapp/resources/stylesheets and went from there.
--
Mark Eggers <[EMAIL PROTECTED]>
w well this
solution really works.
--
Mark Eggers <[EMAIL PROTECTED]>
On Tue, 2005-01-04 at 09:15 +0100, Nicola Ken Barozzi wrote:
> We should also suggest a list of correct XHTML1.x editors.
>
> Suggestions?
>
> PS: Emacs, vi, jedit, notepad, etc are not the editors I'm talking about
This may be too far afield for the developer list. What are your use
cases fo
On Mon, 2005-01-03 at 22:03 -0600, Antonio Gallardo wrote:
> On Lun, 3 de Enero de 2005, 18:47, Ross Gardler dijo:
> I would therefore like to add my support to the suggestion (from David I
> > think) that we simply change the documentation to make it clear that
> > HTML and XHTML are suitable inpu
I'm just a long-time reader of the dev mailing list,
so I don't know if my comments are appropriate.
However:
-1 since it removes document content structure. This
lack of structure will make skinning and
transformations much more complex.
>From the welcome:
Apache Forrest is an XML standards-o
41 matches
Mail list logo
