Brolin Empey wrote:
Here is my plan:
1. Copy pelt and common skins to my Forrest site
You should not need to copy the common.
2. Make needed changes to my local copies of above skins
3. Get my changes committed to SVN, in order to simplify future
Forrest upgrades, reduce duplication of
Brolin Empey wrote:
I got the disable-last-published variable working by modifying the
skinconfig DTD.
If this is intended for contribution, then that is
confusing. The disable-last-published should switch
it off. Some other parameter should control the method,
if it is enabled.
... I need
Steve Odlind wrote:
Hi there,
I have added a custom DTD, which seems to be working fine. I would like
all the files with the md-v1.0 DTD declared in the DOCTYPE to use a
custom XSL.
I have the following in my local sitemap.xmap:
map:sitemap
Thorsten Scherler wrote:
Steve Odlind wrote:
There are two (easy) solutions to your problem:
a) use a narrower match that will only work when you know the custom
DTD is to be used
b) don't worry about the match, just redefine the sourcetype action
that does the processing
If you
Ross Gardler wrote:
Brian M Dube wrote:
Lipsius, Eric M wrote:
This is how my code looks in my source file:
document
header
titleSearch Tools/title
script type=text/javascript src=/skins/validations.js/
/header
body
.
/body
/document
Am I not
Praveen Bhatia wrote:
Hi Ross,
Thanks. The plugins are I referred to are mentioned in the plugins
directory of the source code. The file mentions the plugins as follows. I
was wondering how and from where these plugins can be used.
Thanks
Praveen
plugin.xml file
You
Brolin Empey wrote:
Ross Gardler wrote:
To make Jim's DTD work you need to make Forrest aware of it, this is
documented at http://forrest.apache.org/docs_0_80/your-project.html#new_dtd
I know this. How do you think I got validation of document-v20-jd.dtd
to fail if Forrest is unaware of
A note for the email archives: Discussion continued in another thread:
http://article.gmane.org/gmane.text.xml.forrest.user/4304
Re: Show text file with Forrest
-David
Brolin Empey wrote:
David Crossley wrote:
A note for the email archives: Discussion continued in another thread:
http://article.gmane.org/gmane.text.xml.forrest.user/4304
The linked-to page does not appear to have any way to navigate to the
subsequent posts in the thread.
Yes it does
It got it working. See comments at
https://issues.apache.org/jira/browse/FOR-1032
The main changes were to use an xml entity to
declare the xmlns:xi attribute in the DTD and to
use the cocoon: protocol for the xi:include href.
There are some other changes, so see FOR-1032.
-David
Esther Mietzsch wrote:
Dear List,
in my forrest project, I came across two more questions.
1. My png image does not show up in the PDF file. I performed the Jimi
installation as described in the FAQ, but this did not help. What did I
miss?
Please search the mail archives. There is huge
I started this reply ages ago but never got around to finishing it ...
Brolin Empey wrote:
Brolin Empey wrote:
The Cocoon checksum feature sounds like it may work. I will try it
when I return to work and will let you know the results.
The Cocoon checksum feature seems to work, but I
Stuart Yeates wrote:
We've got a problem in which mail is not sent from forrestbot when a
run in completed. The build and upload work fine. The build file has
the following properties:
property name=notify.email.host value=smtp.ox.ac.uk/
property name=notify.email.to value=[EMAIL
Dieter Schicker wrote:
Hi,
this is a great idea!!! I'm new to Forrest but have been doing Cocoon
hacking for some years. So I could help with Cocoon issues.
Dieter, we definitely need help with Cocoon issues.
Please discuss stuff like that on the Forrest dev list.
We have a number of Cocoon
Philip Aston wrote:
Any ideas on what I might be doing wrong, or points as to how to track
this down?
I have seen such error messages before. IIRC it is something
to do with a missing resource and is a message from the locationmap.
Did you try looking in the Cocoon log files:
David Crossley wrote:
I have seen such error messages before. IIRC it is something
to do with a missing resource and is a message from the locationmap.
Found it.
This wholesite ability has caused trouble for a long time.
Moreso with the new locationmap.
I did a quick search for wholesite
Dieter Schicker wrote:
Thanks a lot for your valuable answers!
There is the dispatcher in the whiteboard that solves this problem very
nice since you add this script tags to the final output via a custom
contract. However details about the dispatcher we will answer on the dev
list.
Is
Mark Miller wrote:
Steve,
When you do 'forrest run' and have your site served by jetty - do you see
images in your PDFs then?
Where are you placing your images in the src file structure? What type of
file image are you trying to include? Just wondering if you have a more
general issue
Johannes Schaefer wrote:
You'll probably need to include the jimi.jar (or JAI) somehow in the
WAR (or tomcat) -- does anyone know how and where?
I just checked via our forrest seed site. Yes the jimi library
does get added to the *.war if it is present in $FORREST_HOME/lib/optional
as
Ross Gardler wrote:
Carlos Tejo Alonso wrote:
Hello Ross,
Use your favourite tools to search the Forrest source tree
for examples
of xinclude in XDocs.
I have made that search, but I haven't found an example of xinclude in an
xdoc. Could you show us an example ?
Well, what do you
Udo Wendler wrote:
Ferdinand Soethe wrote:
bash: /Applications/forrest/head/bin/forrest: /bin/sh^M: bad
I have no dir with *head*.
Thanks Udo, for trying to help.
Ferdinand probably has a few versions of Forrest
on his local computer. He did 'svn
Michael Conneen wrote:
I run it on 10.4 with no issues. Have yet to upgrade to 10.5.
Here is what I do..
- - installed forrest and set up my profile path
:which forrest
/Users/mconneen/apache-forrest-0.7/bin/forrest
Thanks Michael, for trying to help.
For each release we tested the
Ross Gardler wrote:
Ferdinand Soethe wrote:
Just for curiosities sake: Do I also need to rebuild a forrest that was
built under windows before?
Almost certainly, but I never tested this.
I built our past releases (which contain sources
plus a pre-built binary) on Mac and no-one
Michael Toback wrote:
Maybe I should start from the beginning?
We want to be able to take content from a Daisy repository and publish
it through Forrest.
1. How do I set up the http request? By looking in the index.xml in the
plugin documentation, I think it would be this:
map:match
gulfiz ergin wrote:
Tim Williams wrote:
Can you run the Photogallery sample site? Does it work properly?
yeah, it is working properly no problem with it..
Lets be sure. Can you see the beach picture?
at http://localhost:/gallery/demo/pic_1.html
gulfiz ergin wrote:
Tim Williams
Ross Gardler wrote:
Michael Parker wrote:
Hi Andreas,
f.y.i.:
I opened a report for the same bug a while ago
https://issues.apache.org/jira/browse/FOR-1056
but without any reponse by now.
Andreas, can you confirm your bug is the same as that reported in
Andreas.Lehmkuehler wrote:
Ross Gardler wrote:
Michael Parker wrote:
f.y.i.:
I opened a report for the same bug a while ago
https://issues.apache.org/jira/browse/FOR-1056
but without any reponse by now.
Andreas, can you confirm your bug is the same as that reported
in
gulfiz ergin wrote:
hi all;
We want to use forrest with php.I read that there should be a plugin in
whiteboard.However it is not written there.
Do forrest has that plugin or what should we do to use it?
Thanks in advance for your help:)
These references should help you:
Pablo Barrera wrote:
I have a problem with dispatcher and I am still stuck with it.
The Dispatcher is in development and issues with its
use should be discussed on the dev mailing list.
Most developers will have read your message here
so you can just refer to it.
-David
Irrra wrote:
I'm pretty sure I'm missing something simple. Below is the code from my xml
file. It shows up properly when using 'forrest run'. When I'm trying to run
'forrest' however, I'm getting an error and I don't know what should I do to
fix it. The erorr is:
validate-xdocs:
Thorsten Scherler wrote:
Irrra wrote:
Nope, it's JDK 5 the environment variable is referring to...
Ok, since there is an open issue with the validation and JDK 6.
I don't reckon that that is the issue. That was only related
to the use of RELAX NG with Jing in one certain part of the
-xdocs' in the initial directory I got the all too familiar
error... May it be something outside the file? Skinconf.xml? Anything?
Please do that *without* adding your document. I want to
see what happens with a fresh forrest seed site. See below.
David Crossley wrote:
Irrra wrote:
I'm
Irrra wrote:
David wrote:
Please do that *without* adding your document. I want to
see what happens with a fresh forrest seed site. See below.
...
Please try a seed-sample site ...
cd my-new-directory
forrest seed-sample
forrest validate-xdocs
This is what i mainly want to
David Crossley wrote:
Thorsten Scherler wrote:
No it is something different. I suspect there sneaked an illegal between
body and p. Try the following (one line no spaces between the tags):
...
bodyp.../pbody
What does gives that?
No. As i reported yesterday, Irrra's document
david wrote:
I'm intending to use forrest to create a website for the program I
designed.
It all works, but I've a question concerning the placement of the
project logo.
In your default skin (I think pelt was its name) the project logo is
placed on the top right of the page.
Well, I'd
David Crossley wrote:
david wrote:
I experienced another problem in my forrest project.
I wrote a short how to using the How-To DTD. Like in the sample page I
used a faqs item for the FAQ.
I created the following sample document to show the problem:
!DOCTYPE howto PUBLIC
Ross Gardler wrote:
[EMAIL PROTECTED] wrote:
I checked again but i'm very sure i've the correct 0.8 version, i took
it from here.
http://ftp.heanet.ie/mirrors/www.apache.org/dist/forrest/apache-forrest-0.8.zip
You mentioned that it might be a platform related issue on windows, do
you
paul.t.oconnell wrote:
thanks for tht guys, i raised issue :
https://issues.apache.org/jira/browse/FOR-1129
Thanks. I reckon that i can see the problem.
When Forrest runs for the first time after installation,
it needs network access to get the up-to-date lists
of available plugins. See your
EMMEL Thomas wrote:
I should say: 'Never touch a running system...'
I decided this morning to update my current svn copy of 0.9dev to test
whether there are fixes
within the pdf generation. Now, nothing works anymore :-/
As Ross said in the other thread, the dev@ list is for
issues with
Ross Gardler wrote:
EMMEL Thomas wrote:
another problem this morning:
I use the current 0.9dev svn-version.
[snip]
Please note, discussions about the svn head version should be on the
developers list as it is scary for users to read that Forrest doesn't
work - when the released version
Ross Gardler wrote:
Tibetoine wrote:
I have been watching the Apache Forrest web site for a couple of days, and
I was wandering if this project was still in dev ?
It is still in development, however development is slow. All development
activity happens on the developer list. you can
Ross Gardler wrote:
ARobert wrote:
First of all, thanks for your answer.
I will try to get involved in this project ... If I find time to ...
I would like to tell (with my poor english speaking) that Forrest is
a very
good project. But as a good forrest user I would like to add this
1.6)
David Crossley wrote:
ARobert wrote:
Hi guys !
Did someone take a look on this issue ? Are you reproducing ?
There has been work done on the PDF plugin. However, i think
that you would need to be using the 0.9-dev trunk to take
advantage.
Have you done all
Forwarded on behalf of ApacheCon Europe 2009 Team.
-
Here's some great news for everyone who's thinking of
traveling to Amsterdam for this year's ApacheCon Europe. The Early Bird
deadline has been extended to Friday, February
Klortho wrote:
validate-sitemap:
C:\bin\apache-forrest-0.8\main\webapp\resources\schema\relaxng\sitemap-v06.rng:72:31:
error: datatype library http://www.w3.org/2001/XMLSchema-datatypes; not
recognized
Dr. Bhatia Praveen wrote:
I want to take this example to the next level.
Redirecting the pipeline at the top with map:generate does work.
How to do it in between too?
As Ross said, see the Forrest core sitemaps,
e.g.
]$ cd $FORREST_HOME/main/webapp
]$ grep map:call *.xmap
There are many
Heather Phipps wrote:
Unfortunately, even after editing
$FORREST/apache-forrest-0.8/plugins/org.apache.forrest.plugin.output.pdf/output.xmap,
I am unable to get the font to display correctly in the PDF file.
Whenever a local plugin's resources (e.g. sitemaps or stylesheets, etc.)
are edited
Heather Phipps wrote:
My own file is version 1.1, whereas the sample file is version 1.0. Is this
a problem? Does the plugin not handle v 1.1?
I do not know anything about those office type plugins.
The docs show that the odt plugin is in the whiteboard
so is still in development.
Heather Phipps wrote:
Actually, with my little hack, the font is properly embedded in the PDF only
when pre-generated, i.e., when you do forrest site, but not when the PDFs
are generated on the fly, i.e., when you do forrest run. Not sure exactly
what accounts for the difference. If anyone
Derek Baum wrote:
We've been successfully using forrest 0.8 for over a year now and we like
the ability to build content from openoffice .odt documents. (
http://newton.codecauldron.org)
We largely have this working, but we still find that it is sensitive to what
type of images are
- Forwarded message from Sally Khudairi -
Sign up for ApacheCon US by 14 August and save up to $500!
This year's ApacheCon US promises to deliver our most extensive program to
date, and largest anticipated gathering of the global Apache community to
celebrate the ASF's milestone 10th
mgutbier wrote:
Please remove the link www.art-painter.com. This site has been re-launched
and is not built with forrest any more.
We moved to Joomla, because the gallery content is easier to maintain. But
thank you for all the years we had with forrest.
Done now. Thanks for using Forrest.
Done now. Thanks for using Forrest.
-David
Dr. Praveen Bhatia wrote:
Hello,
May i respectfully suggest that in the future you start a new
mail thread for each new topic, rather than reply to a
discussion from someone else. This greatly assists people who
will later read these mail archives.
-David
David Crossley wrote:
Dr. Praveen Bhatia wrote:
Clearly, the charset is not getting set to UTF-8 in spite of settings that I
did in forrest.properties, web.xml forrest.xconf, sitemap.xmap (xml
serializer and html serializer).
What settings I could be missing?
Some time
Michael Glavassevich wrote:
It's been a long time since I've tried building the XML Commons website and
I'm not sure how to get past this. I tried to build the site with a fresh
install of Forrest 0.7 (recommended in the build instructions on the XML
Commons website [1]) but had no luck.
Phillip Hall wrote:
I have a problem rendering the Forrest site from two XML files
aggregated in a pipeline from the Sitemap.xmap file.
I am using Forrest 8.0. I created an XSL stylesheet to format the
combined XML files wih document root tags as per v-13 DTD.
However this is not
Hello Ionut,
Search the FAQ:
http://forrest.apache.org/docs/faq.html#tab-site
I need help with the interaction between tabs.xml and site.xml
My guess it that there is something wrong in your site.xml file.
Such issues can be hard to resolve. Those tips might help.
If not, then please show us
Tobias Neef wrote:
I like to transform a XML file with various namespaces into the xdoc
format. The XML file is in the xdoc/sap directory and the
transformation is also in place. My problem now is, that nothing
appears on my screen when I want to have a look at the transformed
file.
I
We can only discuss *released* versions on this user mail list.
Development versions on the dev mail please.
Also the PDF plugin is a development version.
Richard, i moved this discussion over. Please follow there.
Subject: issues with PDF plugin (Was: For input string: :0)
David Crossley wrote:
Trasca Virgil wrote:
I just remembered it is because I have java1.6 and forrest has a problem
with it. On java 1.5 is working.
See https://issues.apache.org/jira/browse/FOR-984
validate-sitemap target fails relaxng validation on some JDK 1.6: missing
datatypes
Bryce Alcock wrote:
In addition to the previous email, while I am investigating this issue a bit
I was curious:
Is the XML/DTD validation done with Local or Remote (web based) dtd docs?
It seems like the DTD's are located here
http://forrest.apache.org/dtd/skinconfig-v08-1.dtd
Can the
Szabo, Patrick (LNG-VIE) wrote:
I thought it was going to have something to do with xdoc-to-lucene.xsl but i
don't know how to implement new field in that stylesheet. I can see how the
other fields are stored but what i don't know how the xdoc version of my
files look so i can't extend
Szabo, Patrick (LNG-VIE) wrote:
I'm probably using a quite old version of lucene. (where can i see which
i'm using !?)
See
$FORREST_HOME/lib/core/lucene-1.4.3.jar
You might be able to upgrade just by replacing
that jar. Check the docs at lucene.apache.org
-David
If the name of the .jar
Tim Williams wrote:
Szabo, Patrick wrote:
I have to move our forrest installation to a different hardware. Since i
didn't install and configure it myself i'm wondering how to do that.
Is it possible to just copy the directories, set the Enviroment Variables?!
Would that work ?! If
Patrick, i do not know what that Jetty problem is yet.
Would you please try this:
Create a new directory anywhere, and then cd to it, i.e.
] mkdir test
] cd test
] forrest seed-sample
] forrest run
Then with your web browser go to:
localhost:
That will run the test sample site to ensure
Szabo, Patrick (LNG-VIE) wrote:
Maybe i should say that i'm using version 7 because my existing project was
running with that version...
That explains why the 'forrest seed-sample' is not available
but 'forrest seed' is exactly the same thing.
Using the old Forrest-0.7 should be okay.
Would
Szabo, Patrick (LNG-VIE) wrote:
Thank you for your help.
I did not follow your last instructions because it seems to work now.
I got no clue why but it does ;-)
So thank you guys for your support !
Have a great weekend !
Thanks. That is strange. But good.
-David
I expect that many people on the Forrest user list
are really developers rather than users.
If so then please do your bit for open source
development and assist the community to test
the upcoming release. It is also in your own
interests to ensure it works for your use cases.
See the dev list
The Apache Forrest project is pleased to release the new version:
apache-forrest-0.9 http://forrest.apache.org/mirrors.cgi
Apache Forrest (tm) software is a publishing framework
that transforms input from various sources into a unified
presentation in one or more output formats. The modular
and
Submissions and early registration are open.
http://blogs.apache.org/conferences/
Call for Participation ApacheCon North America 2011
7-11 November 2011 Westin Bayshore, Vancouver, Canada
All submissions must be received by Friday, 29 April 2011
at midnight Pacific Time.
Please spread the word
Tom Sanders wrote:
I've been using Forrest since 0.7. In fact I'm long overdue an upgrade now
that 0.9 is out because I'm still using 0.7 - not had much time to spare for
that... and whilst on that subject is jumping two releases going to be easy?
Thanks so much for the feedback.
Yes should
lewis john mcgibbney wrote:
Hi list,
I must admit I'm relatively new to Forrest however I am finding it extremely
user friendly to date (even though I'm only making minor changes). I've been
trying to tackle our Jira issue as here [1] which is basically an update of
branding issues relating
lewis john mcgibbney wrote:
Hi list,
I have a small problem which is the addition of a new project logo to our
already running Forrest site.
In /forrest/src/documentation/resources/images/I have added my new logo
and have also specified it in the skinconf.xml which is in
lewis john mcgibbney wrote:
Well I've sorted the first of the complaints regarding link message=No
pipeline matched request: error:ext:wikierror:ext:wiki/link, this was a
case of methdically going through the full site after running the Jetty
webapp and checking all hyper-links.
I would try
lewis john mcgibbney wrote:
Hi all,
As a project, we are wanting to ship core documentation with the software
distribution. Currently the Nutch site documentation can be found here [1],
however we would like to start shipping it with our branch-1.4 [2] under a
new /docs directory.
I know
. This would then enable devs to
simply svn update and any documentation changes would be updated. It would
also provide an excellent way of shipping the generated docs with our next
release. The parts I am struggling to understand are below:
David Crossley wrote:
lewis john mcgibbney wrote
Tim Williams wrote:
For the archives, it looks like this is the commit [
http://svn.apache.org/viewvc?view=revisionrevision=1239111 ]. If
this is a common need, perhaps a candidate to just get rolled into
Forrest itself, I dunno.
For the document-to-fo.xsl part.
FWIW, I'm pretty sure the
Brian M Dube wrote:
Gaup Børre wrote:
I have enabled dispatcher for a site I use.
When I run a live instance of forrest and do changes in xml files, I don't
see
the changes in my web browser when I refresh the page.
To see the changes I have to restart forrest and then refresh
Sjur Moshagen wrote:
Hello Eric,
Den 19. feb 2013 kl. 16:06 skrev Eric Palmer:
I'm researching apache cms like projects for a specific project need and I
came across Forest. It seems interesting but the user mailing list has had
no updates since 2009 and the forest-dev list shows
Brock Noland wrote:
Hi,
I am trying to update the Apache Hive site with no prior experience with
Apache Forrest. I am hoping that someone can point me the right direction.
I have listed the output of the script all the way at the bottom. Basically
it appears there is a broken link but I
The Travel Assistance Committee (TAC) are pleased to announce that travel
assistance applications for ApacheCon North America 2016 are now open! This
announcement serves as a purpose for you (pmcs@) to let members of your
community know about both ApacheConNA 2016 and about the TAC assistance to
For a number of years the Apache Forrest project has been in low-activity
maintenance mode, as explained in the quarterly Board reports.
There had been hope for new committers and new development ideas, but these
have not eventuated.
In June 2019 there was another opportunity for discussion
201 - 283 of 283 matches
Mail list logo