Re: using Subversion keyword substitution instead of published date in skin navstrip - using Forrest 0.8
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 custom files between my multiple Forrest sites, and possibly help other Forrest users No, the project will not be adding copies of skins to SVN. If you make your changes optional in the pelt skin then yes we can add them. Right now I am stuck at step 2. I decided that it would be better to make a user-set variable to control whether to suppress the Last Modified text in the pelt skin's header and footer. I used an xsl:choose element to emulate an if/else construct. An xsl:when element tests a skinconfig variable named disable-last-published. Follow how that is done with other similar disable- variables. See below. The problem is that I do not know where to declare user-defined skin variables such as disable-last-published. I cannot declare my variable in skinconf.xml, because the name of my variable is not included in the list of legal elements in the skinconfig DTD. Furthermore, it appears that I would have to modify some other skin files in order for the skin to make my variable available for testing in my xsl:when element. Thorsten explained in another email that you need to add to the skinconf DTD. Initially I was going to declare my variable in forrest.properties, but I did not know what name to use. I tried setting disable-last-published=true but this did not seem to work. To incorporate this in the pelt skin, you need to follow how other default properties get set. Search the code and the mailing lists. Search the code for one of the other disable- variables: find . -type f | xargs grep disable-compliance-links | grep -v \.svn e.g. among other things, this show that you need to add to main/webapp/skins/common/skinconf.xsl ... As Thorsten says, you might prefer the Dispatcher. -David I know my changes to the pelt skin work because I made the changes unconditional at first. However, now I am trying to get both the variable declaration and the conditional xsl template working. I realise this is a poor idea since I am dealing with 2 unknowns, but I did not anticipate getting sidetracked by searching for the right place to declare my variable. Thanks, Brolin
Re: using Subversion keyword substitution instead of published date in skin navstrip - using Forrest 0.8
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 a working XSL(T) example. There are plenty of examples in the existing stylesheets. As i said in another email, use your system's find facility to follow how another parameter is handled. -David
Re: Custom XSL pipeline in sitemap.xmap causes build error
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 xmlns:map=http://apache.org/cocoon/sitemap/1.0;
map:components
map:selectors default=parameter
map:selector logger=sitemap.selector.parameter name=parameter
src=org.apache.cocoon.selection.ParameterSelector /
/map:selectors
map:actions
map:action logger=sitemap.action.sourcetype name=sourcetype
src=org.apache.forrest.sourcetype.SourceTypeAction
sourcetype name=md-v1.0
document-declaration public-id=-//MyDoc//DTD MyDoc
Document V1.0//EN /
/sourcetype
/map:action
/map:actions
/map:components
map:pipelines
map:pipeline
map:match pattern=**.xml
map:generate src={properties:content.xdocs}{1}{2}.xml /
map:act type=sourcetype
src={properties:content.xdocs}{1}{2}.xml
map:select type=parameter
map:parameter name=parameter-selector-test
value={sourcetype} /
map:when test=md-v1.0
map:transform
src={properties:resources.stylesheets}/mydoc-to-document.xsl /
/map:when
/map:select
/map:act
map:serialize type=xml/
This needs to be serialise type=xml-document, i.e.
Forrest's internal format.
-David
/map:match
/map:pipeline
/map:pipelines
/map:sitemap
When I run Forrest, I get the following:
linkmap.html BROKEN: C:\Forrest0_8\apache-forrest-0.8\main\webapp\.
(Access is denied)
Any help appreciated.
Thanks,
Steve
__
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
__
Re: Custom XSL pipeline in sitemap.xmap causes build error
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 go for a) then simply change your match to something like: map:match pattern=myCustomDocs/**.xml If you go for b) then copy the following elements from forrest.xmap and add your custom DTD and transformation to them: map:action logger=sitemap.action.sourcetype name=sourcetype src=org.apache.forrest.sourcetype.SourceTypeAction map:resource name=transform-to-document Unfortunately, both approaches result in the following error message: BROKEN: HIERARCHY_REQUEST_ERR: An attempt was made to insert a node where it is not permitted. Is there something wrong with my site, or the XSL? As I read the error your xsl/xml. Steve, is this error reported when you do 'forrest run' and request localhost:/blah/index.html ? Does your internal xml look okay? i.e. localhost:/blah/index.xml Compare that with cd $FORREST_HOME/site-author forrest run localhost:/index.xml It sounds like your -to-document XSL transformation is the problem. If you still have issues, then please prepare a basic site demo by doing 'cd my-demo; forrest seed-basic' and add a minimal example. Open a Jira issue and add your demo: http://forrest.apache.org/issues.html -David
Re: Newbie with some javascript questions
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 calling it correctly? XDoc has no script element. I don't recall at the moment how this is done with skins. By looking at pelt's document-to-html stylesheet, it looks like this element will be stripped implicitly. I don't think the solution calls for a custom skin, but I don't remember the details. It may be injected by skinconf.xml the way extra CSS is handled. With skins, I think the solution applies to every document and is not handled per document. Hmmm... that's interesting. Our FAQ clearly states that this is possible, but it appears the FAQ entry is misleading. Brian is correct that the script element is not allowed in our XDoc. There has been some discussion in the past, in particular see [1] (which interestingly enough was written by me, but it was a long time ago so you'll forgive me for not remembering, I hope. Note that my reference to forrest:views at the end should now be read as dispatcher which is now pretty stable in the whiteboard and will almost certainly be moving out sometime in the near(ish) future. In [2] you will find a little more discussion from someone who tried, but failed to get this working. Let us know if you too have help, but please give plenty of details, most of us do not embed javascript in out source so we'll be providing options and pointers rather than direct answers. It would be really helpful if you could provide us with a better answer to the FAQ question once you have this nailed. Ross [1] http://www.mail-archive.com/user@forrest.apache.org/msg00993.html [2] http://thread.gmane.org/gmane.text.xml.forrest.user/3703/focus=3709 There is a way to do it using xdoc source format. Add a script ... to the body element and disable validation of these xml sources. It is cheating but it should work. Another way might be to intercept the xml pipeline and add another transformation to inject the extra script ... element. Our internal format is not being validated, so it should be able to be overloaded with extra elements. Another way is to hack the pelt skin and explicitly add the script ... to the html output. As Brian said above, we could add a basic solution by doing something similar to extra-css in skinconf. None of these solutions are ideal. Hence Dispatcher. -David
Re: How to start using on eclipse
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 seem to be looking at the insides of Forrest, before understanding how it works. Follow the instructions in the FORREST_HOME/README.txt and index.html create a 'forrest seed' sample site, edit its forrest.properties to add the plugins of your choice. These are listed from the plugins tab of that sample site at localhost:/ and also at http://forrest.apache.org/pluginDocs/ -David
Re: Show text file with Forrest
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 it? :P Anyway, I did make some more progress after rereading the docs you linked to. :) http://forrest.apache.org/docs_0_90/validation.html says This custom DTD should be placed in your project resources directory at src/documentation/resources/schema/dtd/. However, my document-v20-jd.dtd was in schema/. I did not have a schema/dtd/. I created schema/dtd/ and moved document-v20-jd.dtd into it. It doesn't matter where the DTD is located. The important thing is that your project's XML Catalog refers to it properly and that you use the new Public Identifier in your source xml file. Now validation succeeds, until I try using an xi:include element in my XDocs source file. This causes validation to fail again: validate-xdocs: /home/brolin/WEB/techsol.ca/forrest/src/documentation/content/xdocs/products/index.xml:34:74: Element type xi:include must be declared. /home/brolin/WEB/techsol.ca/forrest/src/documentation/content/xdocs/products/index.xml:34:74: The prefix xi for element xi:include is not bound. I wonder if this is caused because I am using document-v20-jd.dtd in my Forrest project instead of installing document-v20-jd.dtd in the same place as document-v20.dtd in my Forrest installation. Jim does not say how he installed his new DTD file in his post. I would prefer to keep document-v20-jd.dtd in my Forrest project so that it can be kept under version control. Keeping it in my project also makes it easier for someone else who checks out a working copy of my Forrest site, since they get all the needed files in the checkout and do not need to modify their local Forrest installation. It should work in the project space. This is why we make this facility available. However, because you are trying to intercept one of the main DTDs and essentially re-define it, this might cause some troubles. A better solution would be to patch our DTD with Jims proposed changes. I would like to get my method working before I try to patch the Forrest DTD. You are not providing sufficient information to enable us to help you. Please open a new issue in our issue tracker. Then attach example files: your new DTD, your project XML Catalog, a cut-down example of your index.xml file. -David
Re: using XInclude with Forrest 0.8 -- DTD validation problem
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
Re: using XInclude with Forrest 0.8 -- DTD validation problem
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: Select the Subject to get the threaded view. -David The Mail Archive has such navigation functions: http://www.mail-archive.com/user@forrest.apache.org/msg02813.html
Re: Show text file with Forrest
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
Re: Newbies questions on PDF generation
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 discussion about this issue, and you will also find references to FOR-635 images not reliably reproduced in PDFs. -David
Re: generate only pages changed since last static site build?
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 have a configuration problem with specifying checksums-uri in cli.xconf. I need checksums-uri to be relative to e.g. the root of my Forrest project (the directory containing forrest.properties and src/) so that I can use a relative path to a checksums file in my build/site/ directory. I do not want to hard-code an absolute path because this path will break if I move the SVN working copy of my Forrest site, or if someone else checks out a copy of my Forrest site. I tried setting checksums-uri to just checksums, but then the build process hangs when I run forrest to rebuild the static site because the JVM encounters a Java IO exception when attempting to write the checksums file. This happens because I do not have write permission for whichever directory checksums-uri is relative to. I tried enabling both verbose and debug output for both Forrest and the JVM, but when the JVM encounters the Java IO exception it still does not say which path it is trying to write to. So, my questions are: 1. Which directory is checksums-uri relative to? As said in the example cli.xconf file: The default path is relative to the core webapp directory. So, relative to $FORREST_HOME/main/webapp directory. I think that we have a problem in Forrest. Some stuff (e.g. main sitemaps) are relative to the above directory whereas other stuff is relative to project.home directory. 2. Is there any way to get the path of the file that could not be written when the JVM encounters a Java IO exception? I am using Sun's JDK on Linux: Did you look in the Cocoon logs? http://forrest.apache.org/faq.html#logs $ java -version java version 1.5.0_10 Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_10-b03) Java HotSpot(TM) Client VM (build 1.5.0_10-b03, mixed mode, sharing) 3. Can I make checksums-uri relative to e.g. the root of my Forrest project? I notice I can set e.g. a context directory in cli.xconf, but I do not know what else is affected by this setting. Sorry, i don't know. It might not even have any effect. Search the Forrest code. I see one mention of webapp at main/targets/site.xml line 37 in trunk SVN. Also search the Cocoon docs and code as mentioned in the top of the default config file at main/webapp/WEB-INF/cli.xconf http://cocoon.apache.org/2.1/userdocs/offline/ http://wiki.apache.org/cocoon/CommandLine More discussion should probably happen on the Forrest dev list as we are getting away from user-land discussion. -David If possible, I would like to avoid having to specify an absolute path to a temporary location, such as /tmp/checksums, and copy the checksums file back into my build/site/ directory. Thanks, Brolin
Re: forreestbot mail not being sent
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 PROTECTED]/ property name=notify.administrator value=Stuart Yeates/ The machine can connect to smtp.ox.ac.uk on port 25 via telnet, so that's not the issue. The output (stdout) is: notify.email: Override ignored for property NOW Override ignored for property DSTAMP Override ignored for property TSTAMP Override ignored for property TODAY Using plain mail Sending email: ForrestBot build for simalbot succeeded From Forrestbot ReplyTo [] To [EMAIL PROTECTED] Cc [] Bcc [] Failed to send email Can anyone see what I'm doing wrong? Does anyone know how to turn debugging on in org.apache.commons.net (which appears to be where things are going wrong)? Do you have the notify.on.failure etc. set in your forrestbot descriptor? I suppose yes, or it wouldn't be trying to send the mail. Our docs say that some mailers need notify.email.from. http://forrest.apache.org/tools/forrestbot.html#notify.email The forrestbot on our zone has notify.email.host as localhost. Our descriptors are in our SVN if that helps for examples: http://forrest.apache.org/zone.html Try a test to ensure that you can send mail direct from the command-line on your server, as the user which runs forrestbot. That is all that i can think of for now. -David
Re: Forrest Debian Package
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 issues listed on our issue tracker. Our out-of-date Cocoon version is holding us back. Uwe, please also talk about potential packaging on our Forrest dev list. We need to be careful, as Forrest is large and complex, and half-baked packaging could do damage for the project. We have plans to use Ivy to better manage our dependencies and so packaging would be easier. -David Uwe Korn wrote: Hey, As some already noticed, I made a likely hacky packaging of Forrest for Ubuntu 7.10: - http://xhochy.org/en/2007/12/21/apache-forrest-on-ubuntu/ - http://xhochy.org/en/2007/12/21/announcing-my-own-ubuntu-package-repositority/ This was just done quickly und not with regard to stability and effience. In future I would like to offer my help to package Forrest for Debian/Ubuntu/... but I am not really familiar with the technical structure of Forrest, so I would need someone who helps me. The aim should be to get Forrest into the official repositorities of Ubuntu and Debian and not to have it in a thirdparty repositority. Regards Uwe Korn
Re: all_site/ fails with (Is a directory) broken link?
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: http://forrest.apache.org/faq.html#logs -David
Re: all_site/ fails with (Is a directory) broken link?
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 in our issue tracker [1]. One of the top issues is http://issues.apache.org/jira/browse/FOR-733 wholesite.pdf does not work with the locationmap. We need to emphasise in our docs that wholesite is broken. Anyone who needs this wholesite ability and wants to help fix it, we would welcome you on our dev mail list. [1] Remember everyone, me included, that the Forrestbar is a good tool to accompany Forrest use/development. http://forrest.apache.org/tools/forrestbar.html -David
Re: Integrating Javascript / Namespaces
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 there some information/documentation out there about this issue? Each of Forrest's plugins are described here: http://forrest.apache.org/pluginDocs/ Follow the links to each plugin's documentation website. As already mentioned, we can only discuss stuff that is in development on the dev mail list. -David
Re: PDF not working correctly in deployed WAR file on Tomcat
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 than what you describe. Good questions Mark. We need to know if it works in 'forrest run'. Also see the demo in the forrest seed sample site. Try building and deploying its WAR. There are some general issues with placement of source images. http://issues.apache.org/jira/browse/FOR-635 More below ... Steve Odlind wrote: Hello all, I am hoping you can help me with a Forrest/Tomcat problem. I am running Forrest 0.8, and am trying to deploy a WAR file on Tomcat. The problem is that PDFs get stripped of their images, and only text is displayed. I can't get PDFs to display at all by deploying the Webapp on Tomcat. I have read http://issues.apache.org/jira/browse/FOR-735, and followed the advice, but cannot get PDFs to be displayed at all. FOR-735 was closed prior to 0.8 release, so that should be fine. So, is there an update to this already-known-problem? I am half of the way there with WAR files, I just need to get the images displayed as well. You don't say, but have you followed the FAQ: http://forrest.apache.org/docs/faq.html#pdf_images ... but i suppose you would have or images would also be missing in 'forrest run' mode. -David
Re: PDF not working correctly in deployed WAR file on Tomcat
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 recommended. I don't have time to try the war in a Tomcat. Steve is trying that. -David
Re: Xinclude in xdoc document
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 know, we have no example in our XDocs - amazing. You can see examples in the Cocoon XInclude transformer docs at http://cocoon.apache.org/2.1/userdocs/xinclude-transformer.html There were some very useful discussions in our mailing lists recently. Try this with Google: site:apache.org forrest xinclude 2007 -David Once you've got it working we would really appreciate a FAQ entry for subsequent users. Just drop it into our issue tracker. Be sure ;-) Excellent. Since there are no examples it would be worth adding such an example to our sample.xml doc as well - thanks Ross
Re: Running Forrest under OS/X 10.5
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 checkout' of current trunk (i.e. head of trunk) into his local directory /Applications/forrest/head. -David I have forrest in ~/Library. So is my FORREST_HOME: /Users/xxx/Library/apache-forrest-0.8 and set my PATH to: PATH=$PATH:/Users/xxx/Library/apache-forrest-0.8/bin The user need right to write in apache-forrest-0.8. Sorry for my little english. Regards, Udo Wendler
Re: Running Forrest under OS/X 10.5
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 Forrest 0.7 and 0.8 versions on Mac OS 10.4 -David
Re: Running Forrest under OS/X 10.5
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 complained during the pre-release testing phase about running on Windows. -David
Re: Using the navigation page for org.apache.forrest.plugin.input.Daisy
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 pattern=locationmap-project.xml
map:generate
src=http://user:[EMAIL PROTECTED]:9263/publisher/blob?documentId=NAVIG
ATION-DOCUMENT-IDamp;version=liveamp;partType=1/
map:transform
src={forrest:plugins}/org.apache.forrest.plugin.input.Daisy/resources/s
tylesheets/navigation-to-locationmap.xsl
map:parameter name=publisherURL
value=http://username:[EMAIL PROTECTED]:9263/publisher//
map:parameter name=pathPrefix value=//
/map:transform
map:serialize type=xml/
/map:match
Do I have to change NAVIGATION-DOCUMENT-ID to the navigation document
number? Or is it number + namespace??
2. If I'm not using content other than daisy, do I need a site xml file?
3. Where do I run forrest from for a daisy site?? I was guessing
DaisyRoot\WikiData\sites\site_name
4. Do I need to seed a daisy site? Or do I need to change some
properties file so it knows to use the daisy plugin?
It sounds like you have not understood the basics of Forrest.
In a new directory, somewhere away from the Forrest sources,
type:
forrest seed-basic
This gives you a very minimal seed site with all the
configuration files.
forrest run
Have a look around, tweak things, see the effect.
In your forrest.properties file, add Daisy as another
required plugin. Now you can start to build up your
Daisy-based Forrest project.
Get ideas from Forrest's Daisy Plugin website, as Ross suggested.
This is a simple Forrest project site that demonstrates the
capabilities. See its configuration files, especially the
forrest.properties* files and the locationmap.xmap files.
If you are using the current SVN trunk of Forrest (0.9-dev)
then 'cd
$FORREST_HOME/whiteboard/plugins/org.apache.forrest.plugin.input.Daisy'.
You can do 'forrest run' there to see the demo in action.
You would need to change the port number for your own
Forrest project to be able to run the both at once.
Search the FAQ for jetty.port.
Get other ideas from Apache Cocoon's use of Forrest/Daisy
for their v2.1 docs.
http://svn.apache.org/repos/asf/cocoon/whiteboard/daisy-to-docs
See escpecially the forrest.properties* files and the
src/documentation/locationmap-daisy-include.xml file.
Daisy is in the whiteboard, so we really should be discussing
it on the Forrest dev mailing list.
By the way, please do not append disclaimers to your email footers.
They have no bearing in a public forum.
-David
Re: how to use photogallery plugin?
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 wrote: Can you copy your site to a simple path (e.g. C:\temp) and try to build from there? I'm wondering if the spaces in the directory path aren't the issue. as you said I change the path...both nothing has changed...when I check error.log,it is empty So something has changed. That means that the error that you reported earlier is gone, which indicates that the use of spaces in the directory name might be causing problems. However, it seems that you have something else wrong with your use of the PhotoGallery plugin. I think that you need to take a step back and explain exactly where you have placed your images and what is in your album.xml file for one of the galleries. I suggest that you create an issue [1] and attach your index.xml file, and an album.xml file, and a listing of your xdocs/images/gallery/*/ directory. [1] http://forrest.apache.org/issues.html The PhotoGallery works fine for me. What version of Forrest are you using? Also, have a look at these issues and see if any apply to you: https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=truemode=hidepid=1231sorter/order=DESCsorter/field=priorityresolution=-1component=12310045 -David
Re: Broken links in pdf-tab.html
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 https://issues.apache.org/jira/browse/FOR-211 which is a duplicate of the bug identified above. Either way, I suspect this is a scratch your own itch problem. The bugs have been on file for a long time and have been marked as minor by the existing project team. The only way these are likely to be fixed is to fix them yourselves. That is always how it is. For example, i haven't tried because i never use the wholesite ability. However, it points to an underlying problem with our linkrewriting so it would be good to address it. Of course, we'll help out where we can but we need complete debugging info and perhaps a sample site that reproduces the problem so we can test it. Probably one of our existing seed sites will demonstrate this. By default we have the wholesite.* commented-out in site.xml file. A good start for your debugging info is to turn on logging for the linkrewriter and send the relevant parts of the logs to this thread. It would be great if Andreas and Michael can help to track this down. On the dev list please. -David
Re: Broken links in pdf-tab.html
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 https://issues.apache.org/jira/browse/FOR-211 which is a duplicate of the bug identified above. It's the same bug. I'll try to get some debug informations david asked for and I'll post them on the dev list. It was Ross. It is better to attach stuff to an Issue in Jira, rather than send to the mailing list. However, i don't think that will help. If the behaviour can be demonstrated by one of our seed sample sites then any developer can see the logs for themselves. What we really need is for developers to help solve the problem on the dev list. Other developers can help to guide. -David
Re: php plugin?
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: http://forrest.apache.org/faq.html#output-filename-extension http://forrest.apache.org/faq.html#php They were easy to find via Google search. -David
Re: Locationmap does not work with dispatcher
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
Re: Problems with build
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: C\Dosuments and Settings\...\index.xml: The content of element type body must match (section|p|source|note|warning|fixme|table|ol|ul|figure|anchor)+ BUILD FAILED ...index.xml fis not a valid xml document. Any insight will be very appreciated! The code: ?xml version=1.0 encoding=UTF-8? !DOCTYPE document PUBLIC -//APACHE//DTD Documentation V2.0//EN http://forrest.apache.org/dtd/document-v20.dtd; document header titleContact ViroGen/title /header body p class=center ../resources/images/about.jpg /p /body /document I have no idea sorry. It looks legitimate to me. In fact i added your file to a test site and it does validate correctly here. Please try a seed-sample site ... cd my-new-directory forrest seed-sample forrest validate-xdocs Then add your file as src/documentation/content/xdocs/irrra-test.xml and try again: forrest validate-xdocs -David
Re: Problems with build
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 validation. The error messages that Irrra is reporting are not the same as that issues symptoms.. But I might have both 5 and 6 installed on my machine. May it be the problem? 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 does validate okay for me. There are no xml issues. Irrra would you please respond to the question that i asked yesterday. I feel that we are wasting time here. -David
Re: Problems with build
Please do not do top-posting like this. Rather add your comments in-line with the context of the conversation. Irrra wrote: The build was successful when I created a new directory, populated it with forrest seed' and copied my index.xml file to it. As soon as I tried to run 'forrest validate-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 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: C\Dosuments and Settings\...\index.xml: The content of element type body must match (section|p|source|note|warning|fixme|table|ol|ul|figure|anchor)+ BUILD FAILED ...index.xml fis not a valid xml document. Any insight will be very appreciated! The code: ?xml version=1.0 encoding=UTF-8? !DOCTYPE document PUBLIC -//APACHE//DTD Documentation V2.0//EN http://forrest.apache.org/dtd/document-v20.dtd; document header titleContact ViroGen/title /header body p class=center ../resources/images/about.jpg /p /body /document I have no idea sorry. It looks legitimate to me. In fact i added your file to a test site and it does validate correctly here. Please try a seed-sample site ... cd my-new-directory forrest seed-sample forrest validate-xdocs This is what i mainly want to know. -David Then add your file as src/documentation/content/xdocs/irrra-test.xml and try again: forrest validate-xdocs -David
Re: Problems with build
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 know. The build was successful both times. Okay, that proves that there is nothing wrong with your Forrest installation. As i described earlier, i did copy-and-paste of your xml into a new file on my system. That passes xml validation with no problems. So there must be some strange invisible character in your copy of the document that trips up the xml validation system. I suggest that you create a complete new copy of your test document. Also try copying one of the existing documents in the seed site and remove the content until just your single test paragraph remains. -David
Re: Problems with build
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 does validate okay for me. There are no xml issues. Sorry Thorsten. Those words came out wrong. I was trying to steer back towards such issues after getting Irrra to be sure that the xml validation was actually working. See the other part of this email thread. Irrra, you replied to Thorsten's suggestion, saying that it made no difference. Did you actually re-enter that content as bodyp.../p/body or did you just modify your existing bad document? In the latter case the spurious characters might still remain. -David Irrra would you please respond to the question that i asked yesterday. I feel that we are wasting time here. -David
Re: Can I place the project logo left?
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 like it better if it were left above the menu (the place where the group logo is placed by default, but I turned this one off). Is there a way the place the project logo left? As far as i remember, not with skins. That is the type of issue that led to the ongoing development of a new facility that we call Dispatcher. However that is not a released feature. Hence we don't discuss that on this user mailing list. We invite people to the dev mailing list to discuss its capabilities. I can tell you that a number of us use the current Subversion trunk in production for our sites. e.g. see some public examples listed at the bottom of http://forrest.apache.org/live-sites.html#dispatcher -David
Re: IDs in How-to FAQ - no anchors in HTML documents?
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 -//APACHE//DTD How-to V2.0//EN http://forrest.apache.org/dtd/howto-v20.dtd; howto header titleSample/title last-modified-content-date date=2008-10-12 / /header steps title=The Steps pSee a href=#entrysdaf/a/p /steps faqs faq id=entry questionThe question/question answerAnd the answer/answer /faq /faqs /howto My problem is that no HTML-anchor is created for the FAQ entry. I mean normally when I write a FAQ page without the surrounding how to such an anchor will be created, it looks something like: a name=entry/a Well, when using the FAQ in a how to document no anchor with my defined ID seems to be created. Instead I find the following: a name=1+The+question/a Did I do something wrong? And if not, is there possibly a reason why the behavior of forrest seems to change when using faqs in a howto? Thanks a lot, Not much time to look, but i can give you some quick pointers. It seems that you might have found a bug. Or maybe the automated id-generation is a feature (i don't know). I looked at the example document: http://forrest.apache.org/docs/howto/howto-howto.html Its first FAQ should be #faq-difference. The current version of that document has moved to http://forrest.apache.org/howto-howto.html i.e. $FORREST_HOME/site-author/content/xdocs/howto-howto.xml If you are seriously considering using Forrest then it would be good to understand its internal processing. Following this bug might be a good exercise. The sitemaps involved in howto and faq processing are $FORREST_HOME/main/webapp/sitemap.xmap which passes to $FORREST_HOME/main/webapp/forrest.xmap and faq.xmap which refer to the stylesheets $FORREST_HOME/resources/stylesheets/howto-to-document.xsl and faq-to-document.xsl and faqv20-to-faqv13.xsl (the latter is because document-v13 is the internal format, not document-v20). -David
Re: Cannot get variable 'plugin.xmap.output' in expression '{lm:plugin.xmap.output}'
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 have reference to any old occurances of this issue?. The issue that Ross refers to is only with the current head of development, i.e. the svn trunk 0.9-dev, not with the 0.8 release. This issue only raised its head when we changed the version of Cocoon in trunk. It does not affect 0.8 version. For more info on how it manifests iteself search our issue tracker and our mailing lists (although I already did that and only found references to the problem in SVN head so you may not want to bother). I've not had the opportunity to look into the problem myself so I'll not make any wild guesses right now. But whilst we wait for someone else to have an idea can you please tell us: What operating system? What version of Java? (I think 0.8 has known problems with Java 1.6) No, there is a solitary known issue with Java 6 and it is not related to what Paul is reporting. I downloaded a fresh release from the mirrors and there is no problem for me. It all works as expected. Paul could you please capture the output from doing 'forrest seed' and then 'forrest site'. Then create a new issue at our issue tracker and attach that output file. http://forrest.apache.org/issues.html -David
Re: Cannot get variable 'plugin.xmap.output' in expression '{lm:plugin.xmap.output}'
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 FOR-1129-site.txt around line 16, etc. Subsequently, if you declare other plugins to be used then Forrest will need network access to retrieve them. Also from time-to-time use forrest while connected, so that it can update its list of available plugins. The error message is because it was looking for the file called output.xmap which is automatically generated. Probably missing due to the initial errors. Forrest should be more graceful. While searching the issue tracker, i found that there is a Note about this on our home page. http://forrest.apache.org/#Explanation+and+features We should add that to Forrest getting started instructions. -David
Re: problem using own DTD
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 the development version. This next thing is version-independent, so i will answer here ... One problem is that my own DTD cannot be found anymore, although it is proper registered in the catalog.xcat-file. It seems that forrest cannot find it since it doesn't look at the correct location... You can verify this by doing the following steps: mkdir tmp; cd tmp forrest seed cd src/documentation/resources/schema/ cp hello-v10.dtd helloxxx-v10.dtd now change the file catalog.xcat by replacing hello by helloxxx like this: public publicId=-//Acme//DTD Hello Document V1.0//EN uri=helloxxx-v10.dtd/ Correct. next change back to the root of your forrest-dir and change src/documentation/content/xdocs/samples-b/custom.xml to reference this new dtd This step would only be needed if the Public Identifier was changed. Our xml catalogs generally respond on that PublicId, so the value of the System Identifier in the XML instance documents has no bearing. finally run forrest -v validate-xdocs you should get an error that helloxxx-v10.dtd cannot be found. That is the expected behavior. Your xml catalog told the catalog entity resolver where the new DTD was located. If not, I am missing something serious. It seems so. Read up on how our xml catalog system works. As said above, it responds on the public identifiers and finds the DTDs relative to the various catalog.xcat files. There is one in your project at src/documentation/resources/schema/ and others in the Forrest core at main/webapp/resources/schema/ Now that said, there is something that might be confusing you. There is a dummy copy of the hello DTD next to the document that references that DTD. Note that that copy is *not used*. Instead, it uses the ones found by the catalog resolver as explained above. We need to investigate why that copy is there. The svn log says ... to pass the build.sh test. That copy should still not be needed and should be removed to avoid confusion. -David
Re: cannot 'forrest run' after 'forrest seed' with 0.9-dev
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 does. Make a fresh project and run it with forrest seed forrest run Now try to contact the server. I get this error: Internal Server Error Message: null Description: No details available. Sender: org.apache.cocoon.servlet.CocoonServlet Source: Cocoon Servlet Request URI cause org.apache.forrest.generation.ModuleGenerator request-uri / Where can I find any further info. When using the dev version you need to follow the dev mail list and the evolving changes document. There was a major change with the inputModule moving to the core. See Thorsten's alert: [HEADSUP] Move output.inputModule into core http://marc.info/?l=forrest-devm=122172485101564 We usually document such things in the relevant Upgrading doc, but that seems to have been forgotten in this case http://forrest.apache.org/docs_0_90/upgrading_09.html This might not be your issue. Please follow up on dev@ -David
Re: Forrest news
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 see recent activity at [1] And [1.5] an overall summary which shows the svn list too. Tibetoine was probably referring to such web pages as http://forrest.apache.org/#news and the linked events page. We really should keep those things more up-to-date. Perhaps we could automatically generate a summary of the important changes since the last release. Other ways to keep abreast: - Changes [4] - Quarterly reports to ASF Board [5] -David What's more I would like to know if it was possible to help for this project? We are always as welcoming as possible to new blood. If you care to join us on the developer list [2] we'll be happy to help you get settled in. you might want to start by looking at our introductory developer docs, e.g. [3] - however, don't be afraid to ask for more guidance on the dev list - we're a friendly bunch ;-) Ross [1] http://markmail.org/search/?q=list%3Aforrest#query:list%3Aforrest%20type%3Adevelopment+page:1+state:facets [1.5] http://forrest.markmail.org/search/?q= [2] http://forrest.apache.org/mail-lists.html [3] http://forrest.apache.org/contrib.html#wanted [4] http://forrest.apache.org/docs/dev/changes.html [5] http://forrest.apache.org/guidelines.html#report
Re: Forrest news
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 In my opinion : - Forrest web site is bad structured, it's hard to find information in documention I agree 100% I know roughly what content we have yet I can't find it! There is some unfinished development effort in our dev mail archives. A rearrangement was commenced but not completed. It is better than it was but still needs some tweaking. IIRC some issues were resolved but not yet implemented. - Forrest web site is not really beautiful, it would be fine to find a Forrest icone (Hope I'm not offending someone) and to work on Forrest CSS (Since it's quite easy with the generated Forrest HTML code) Forrest is still using the same skin it was using when started in 2002 - it's certainly time for an update. We have tried to encourage CSS experts to assist. One new committer helped with some essential groundwork development. Search the dev archives and the issue tracker. We need to now go the next stage. - The news page seems died. No news is sometimes good news. Forrest 0.8 is stable and extremely useful. 0.9 is ticking along. However, I agree that it can give the impression of no activity and should be rectified in some way. - It's hard to find the Jira or Nabble page on Google. Well I would argue that we don't want nabble and jira appearing as the number one searches. Nabble is nothing to do with us, Jira is only of interest to developers who should know where to go. That was my reaction too. There is an assumption on our website that most people who need to use the Issue tracker or the mail lists etc. are developers. So see the Developers tab. Having said that, Tim Williams recently posted on the dev list about having created a custom Google search for Forrest. We should make that the default search engine from the Forrest home page. This can include mail archives and Jira Yes. However, Forrest users could take advantage of the Forrestbar (for Firefox). I find it such a valuable tool. Providing direct search of Forrest resources and also access to behind-the-scenes data of forrest processing steps. http://forrest.apache.org/tools/forrestbar.html - It's hard to find support on google. Google searches the internet. The best place to find support for any project is via the search facilities provided by that project which will usually be more narrowly focussed. (although see above about custom search engine) - I always find information about forrest 0.7 whereas i'm looking for 0.8 :( There is a trick if you stumble across old docs: Replace docs_0_70 in the URL with either docs or docs/dev. 0.7 has been around longer than 0.8 and therefore is linked to more. Perhaps we should put a header on the 0.7 pages saying that these are not the docs for the latest version and providing a link to the latest (this can be done automatically). There is already. See the top-right under the PDF icon. I recognised that problem ages ago and made some solution with the Message of the day facility. Perhaps it could be more emphatic on the old release docs. -David
Re: PDF not working correctly in deployed WAR file on Tomcat
ARobert wrote: Hi thanks for your answer ! Yes I tried verything ! So you are saying that you have tried 0.9-dev and it is broken too. I will not be commenting anymore on the user list about this issue. -David What's more I think every one can see this error quite easily, since you only need to do that On any OS, on any browser 1/ Download apache-forrest-0.8 (Actual release) 2/ Downlaod apache-tomcat-6-0.18 (Actual release) 3/ Use java 1.6 (Actual release) 4/ forrest seed (To create sample forrest site) 5/ forrest war (to create WAR sample forrest site) 6/ put the .war in the tomcat webapps folder 7/ Launch sample forrest application from tomcat 8/ Go to any page with any image of this war sample forrest site 9/ Try to see it in PDF version 10/ See that you don't have image displayed That take about 10 minutes (After having download Tomcat, apache and java 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 the things suggested earlier in this thread? Do you see the same problems with the forrest seed sample site? Anyway, if it still persists after trying the 0.9-dev then i suggest raising the issue on the dev mail list. -David
ApacheCon Europe 2009: Early Bird Deadline Extended until 13th of February
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 13th - and remember, there is a discount of 150 Euro on registration for anyone staying at the M??venpick Hotel. Register at http://www.eu.apachecon.com. ApacheCon is a week of open source goodness straight from the source of The Apache Software Foundation: - More than 60 1-Hour Sessions on System Administration, Development, Data Mining and Search Technologies, Enterprise Web Services, SOA, and Cloud Technologies, Open Source Business and Community, and more - Over a dozen Training Workshops from industry experts (see below) - World-class Keynotes and vendor Expo - Lightning Talks and Birds-of-a-Feather sessions - New this year: Geeks for Geeks Track, BarCampApache, and Hackathon! ApacheCon Europe 2009 features 2-day, 1-day, and half-day Training Workshops on the following topics: Data Mining and Search Technologies --- - Lucene Boot Camp (Grant Ingersoll) - Solr Boot Camp (Erik Hatcher) The Next Generation of Web Data Storage --- - Building Standalone CouchDB Applications (J. Chris Anderson) - High Performance CouchDB (J. Chris Anderson) Cloud and Distributed Computing Technologies - Hadoop Tools and Tricks for Data Processing Pipelines (Christophe Bisciglia and Aaron Kimball) System Administration - - Apache HTTP Server - Nuts to Bolts (Jim Jagielski) - Everything Tomcat - Administering, Tuning, Troubleshooting and Developing (Mark Thomas) Developing State-of-the-Art Web Applications - A Day of REST (J Aaron Farr) - Apache CXF - Developing and Deploying Open Source SOA Endpoints (Adrian Trenaman) - Ajax on Struts 2: How a Second Generation Web Application Framework Meets the Demands of RIA (Chad Michael Davis) - Behavior-Driving Your Apache Wicket Application: Making the Most of Webdriver and JDave-Wicket (Timo Rantalaiho) Building and Managing Java-based Projects - - Maven Workshop (Zeger Hendrikse) Professional Media Trainings - Media Analyst Training (Sally Khudairi) - Intermediate Media Analyst Training (Sally Khudairi) We hope to see you on the 23-27 March at the M??venpick Hotel in Amsterdam! Visit http://www.eu.apachecon.com for further information and registration details. Interested in sponsoring the ApacheCon conferences? Please contact Delia Frees at de...@apachecon.com for further information. -- ApacheCon Europe 2009 Team planners-2009-eu at apachecon.com http://www.eu.apachecon.com
Re: Not compatible with Java 1.6?
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 C:\bin\apache-forrest-0.8\main\webapp\resources\schema\relaxng\sitemap-v06.rng:81:31: error: datatype library http://www.w3.org/2001/XMLSchema-datatypes; not recognized I then found this message: http://www.mail-archive.com/user@forrest.apache.org/msg02833.html that seems to indicate that Forrest isn't compatible with Java 1.6. A bit more searching would lead to https://issues.apache.org/jira/browse/FOR-984 validate-sitemap target fails relaxng validation on some JDK 1.6: missing datatypes That is fixed in the current source SVN. -David
Re: How to do common pipelines?
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 examples of this. See the documentation about sitemaps http://forrest.apache.org/docs/sitemap-explain.html and others. See map:resource to define various resources, and then map:call to use them. -David ... So, from P1 I call pipeline P, transform with mytest.xsl and then how do I call pipeline Q? I would want something like this : map:match pattern=**P1.xml map:generate src=cocoon:/P.xml/ map:transform src=mytest.xsl/ map:transform src=cocoon:/Q.xml/ map:serialize type=xml/ /map:match map:match pattern=Q.xml map:generate src=test.xml/ map:transform src=test2.xsl/ map:serialize type=xml/ /map:match If this can be made to work, I do not have to repeat code for piplines P and Q and all the other piplines which need slightly modiefied transforms but for P and Q's portion itself.
Re: Japanese PDF rendering
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 then you need to local-deploy the plugin. See: http://forrest.apache.org/pluginDocs/plugins_0_80/usingPlugins.html#local-deploy http://forrest.apache.org/docs_0_80/howto/howto-buildPlugin.html#ant http://forrest.apache.org/docs_0_80/howto/howto-buildPlugin.html#Testing+During+Development -David
Re: Error generating PDF from .odt file using org.apache.forrest.plugin.input.odt
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. http://forrest.apache.org/pluginDocs/ So the dev mail list is more appropriate. You might grab the attention there of its developers. -David
Re: Japanese PDF rendering
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 has a better understanding of the cause of this discrepency, please let me know... Otherwise, I may look into this more at some later point and will update this thread if I have any further insight. Perhaps the FOP project will be able help with that and with the memory issue: http://xmlgraphics.apache.org/fop/ -David
Re: openoffice support fails to render some embedded images
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 embedded in the .odt file: .png and .jpg images render
fine, but .tiff images do not.
Is this just because the file extension in the OO file is .tif rather than
.tiff, or something else?
$ unzip -l InstallationGuide.odt
Archive: InstallationGuide.odt
Length Date TimeName
39 06-05-09 16:49 mimetype
0 06-05-09 16:49 Configurations2/images/Bitmaps/
127620 06-05-09 16:49 Pictures/128001E02A9E9828.tif
59894 06-05-09 16:49 Pictures/128001E0E2C50ACF.tif
7160 06-05-09 16:49 Pictures/119601142835D184.jpg
Up until now, we have just been replacing embedded .tiff images with .png or
.jpg, but this is a pain.
Can anyone suggest how to fix this properly?
See $FORREST_HOME/main/webapp/raw.xmap
and search in file for jpg and jpeg.
Add similar handling to read other raw formats,
such as TIFF.
Please add a patch to our issue tracker:
http://forrest.apache.org/issues.html
-David
Fwd: Sign up for ApacheCon US by 14 August and save up to $500!
- 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 Anniversary. The San Francisco Bay Area is where the very first ASF official user conference was held, and we hope that you will join us in celebrating the ASF's success! Apache members, code contributors, users, developers, system administrators, business managers, service providers, and vendors will convene 2-6 November in Oakland, California, for a week of training, presentations, sharing and hacking. ApacheCon US 2009 features new content tracks, MeetUps, and GetTogethers, as well as a number of events open to the public free of charge, such as the Hackathon and 2-day BarCampApache, in appreciation of their support over the past decade. Be sure to register by 14 August to save up to $500! To sign up, visit http://www.us.apachecon.com/ Those wishing to attend ApacheCon, but may be unable to do so due to financial reasons are encouraged to apply for Travel Assistance by completing the form at http://www.apache.org/travel/ Financial support for flights, accommodation, subsistence, and conference fees are availablAnyone involved in Open Source is welcome to apply for financial support for flights, accommodation, subsistence and Conference fees. Hurry, applications close on 17 August. Conference sponsor, exhibitor, and community partnerships are also available: please contact Delia Frees at de...@apachecon.com for details. # # # - End forwarded message -
Re: Skinned Sites
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. -David
Re: New Skinned Site
Done now. Thanks for using Forrest. -David
Re: UTF-8 setting for Japanese characters
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
Re: UTF-8 setting for Japanese characters
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 in the past we had similar issues for our forrest.a.o site. See $FORREST_HOME/site-author/content/.htaccess # # FIXME: Do we still need this? See FOR-877 AddDefaultCharset UTF-8 # That issue links to a some other issues which might provide some background. Ah, following through from http://issues.apache.org/jira/browse/FOR-877 to the linked issue: https://issues.apache.org/bugzilla/show_bug.cgi?id=23421 provides very educational reading on this matter. -David
Re: Unable to build xml-commons website with Forrest 0.7
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. Hoping someone who uses Forrest more often would have an idea what's going on here. I cannot help with those errors. One workaround to get the release published would be to disable the PDF production: In src/documentation/skinconf.xml disable-pdf-link = true In forrest.properties project.required.plugins remove pdf plugin -David
Re: Rendering XML transformed from aggregated content
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 displayed with the Forrest skin but as raw HTML.
How can I apply the default Forrest skin to this XML output?
I have searched the Forrest FAQ and the mail Archives without finding
a solution. Please help.
sitemap.xmap insert :
map:pipelines
map:pipeline
map:match pattern=**index.html
Not 100% sure of my answer, but i reckon that should be
map:match pattern=**index.xml
i.e. the internal request for the content xml.
With the match as you have it, it is intercepting the output
html request and finalising (i.e. map:serialize) the output
to xml.
map:aggregate element=site
map:part src={properties:content.xdocs}index.xml/
map:part src={properties:content.xdocs}index-two.xml/
Also to match sources in sub-directories you will need:
map:part src={properties:content.xdocs}{1}index.xml/
etc.
There is a document explaining the ** and * pattern matching
and token usage.
/map:aggregate
map:transform
src={properties:resources.stylesheets}/docs-to-document.xsl/
map:serialize type=xml-document/
/map:match
/map:pipeline
My docs-to-document.xsl transform :
xsl:stylesheet version=1.0
xmlns:xsl=http://www.w3.org/1999/XSL/Transform;
xsl:output method=xml/
This output method has no effect in a Cocoon-based app.
The map:serialize in the sitemaps does that job.
-David
xsl:template match=/site
xsl:element name=document
xsl:element name=header
xsl:element name=title
xsl:value-of select=/site/document/header/title/
/xsl:element
/xsl:element
xsl:element name=body
xsl:for-each select=//section
xsl:copy-of select=./
/xsl:for-each
/xsl:element
/xsl:element
/xsl:template
/xsl:stylesheet
Re: problem with incorrect tab selection
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 the snippet of your site.xml that relates to this issue. -David
Re: SourceTypeAction does not start a transformation
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 don't know if this is relevant, but i did have trouble using the namespace method. See my comment in http://issues.apache.org/jira/browse/FOR-1173 I did also try using the namespace method of SourceTypeAction. It does detect that properly, but then something further down the forrest processing gets confused about the namespace. -David
Re: For input string: :0
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) http://marc.info/?l=forrest-devm=127302239319841 -David
Re: validate error when I run the forrest command
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 So trying to say that the issue is fixed in Forrest trunk SVN. For released versions, you have two options: 1) Follow the workaround described in that issue to switch off that sitemap validation task. 2) Follow the Subversion Commits tab of that JIRA to see how to upgrade Jing. This validate sitemap task doesn't really do much anyway. Its main purpose is to demonstrate the power of using Jing to do xml validation during the build phase. There are other better demonstrations of that. -David
Re: Tracking Codes and Java Script
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 DTDs be made local? They are local. See the Catalog Entity Resolver. Use the forrest.apache.org site search or the Forrestbar search, and look for catalog gives some docs. -David
Re: Lucene Search
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 the exsiting template. I could just take a look at what the xml2xdoc stylesheet does but it would be a lot easyer if i could take a look at an actual xdoc fileis there a way to store those intermediate xdoc files ?! Do 'forrest run' then request localhost:/index.xml See some other tips in http://forrest.apache.org/howto-dev.html Also perhaps see the main/webapp/search.xmap which will show some other internal requests that might be useful such as localhost:/index.lucene I'm not very familiar with cocoon jet so that might be a dumb question. The pipeline goes like this: our xml (dita) - xdoc - html, pdf, ... Right ?! Yes. -David
Re: Lucene Search for a range of dates
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 is the same as the version then I'm using 1.4.3.
I want to search for files that have been modified between the
21.06.2010 and the 24.06.2010.
I know that there is a file with the value 23.06.2010 in the version
field so that should show up in the resultlist.
I did the following:
version:{21.06.2010 TO 24.06.2010}
unfortunately Lucene gives me no results.
If I search for version:23.06.2010 I do get a few hits.
Any ideas ?!
Is there a way to use regex in lucene ?!
Thanks in advance...
kind regards
. . . . . . . . . . . . . . . . . . . . . . . . . .
Patrick Szabo
XSLT-Entwickler
LexisNexis
Marxergasse 25, 1030 Wien
mailto:patrick.sz...@lexisnexis.at
Tel.: +43 (1) 534 52 - 1573
Fax: +43 (1) 534 52 - 146
Re: moving to different hardware
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 not...why not ?! Hi Patrick, Assuming you have Java installed on the new machine, simply copying everything (Forrest + Your Project) should work just fine. Good luck! Patrick, the configuration should not have any system-specific settings, so it should be okay. I was wondering about the cache. I expect that it too should be portable. If you do see issues then do 'forrest clean' in each of your projects. -David
Re: moving to different hardware
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 that all is well with your Forrest setup. -David
Re: moving to different hardware
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 you please do the following. Not sure of the syntax for Windows but you see what i mean. We are cleaning and re-building Forrest. ] cd $FORREST_HOME/main ] build clean ] build Then try the 'forrest run' again in that test seed site. -David
Re: moving to different hardware
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
[Important] calling all developers, test 0.9 release candidate
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 subscribe and archives at http://forrest.apache.org/mail-lists.html -David
[Announce] Apache Forrest 0.9 released
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 extensible plug-in architecture of Apache Forrest is based on Apache Cocoon and the relevant industry standards that separate presentation from content. Forrest can generate static documents, or be used as a dynamic server, or be deployed by its automated facility. Features of this version include: * Consolidation and bug fixing. * Our packaged version of Apache Cocoon has been upgraded to use the latest version of their stable 2.1 branch. Download: http://forrest.apache.org/mirrors.cgi Release notes, including a list of some of the more important changes, are available from the download mirrors. Full list of changes: http://forrest.apache.org/docs/changes.html See also lists of changes in each plugin's documentation. Upgrade guide: http://forrest.apache.org/docs/upgrading_09.html See the issue tracker for known issues: http://forrest.apache.org/issues.html Thanks for your interest, from the Apache Forrest project. pgpSrLHGNC8ca.pgp Description: PGP signature
Call for Participation ApacheCon North America 2011 closes 29 April
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 about submissions and about the conference in general. http://na11.apachecon.com/
Re: More forrest based sites
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 be fine. Anyway please discuss any issues that you encounter. Looking from the outside it seems to be a straight-forward site. Follow the upgrading notes at http://forrest.apache.org/docs_0_90/ and as recommended the previous notes need to be scanned. Anyway, I've build a site that has quite a lot of content, internal and external links. Forrest scores because producing this content is a lot of effort and the last thing you want to end up with is content that can only ever live in one domain. Forrest's document spec is simple and this way it is relatively easy to process your content for something else, should you want to. That alone is a great motivator for putting effort into one's website. Glad that it meets your needs. I've used Forrest to create the website for Inq - a scripting language that, while much like others of its kind can be used in a general purpose way, also includes cooperating client and server environments. It reifies many programming concepts (for example variable references) so that common tasks (like say MVC dispatching and database mapping) can be handled by the environment. Very interesting. Perhaps Forrest software can interact in some way. Join us on the dev mail list. If you consider it useful and worthy, perhaps you would add it to the list of Forrest-powered sites. Definitely. Someone will patch that list soon. -David Kind regards Tom http://www.inqwell.com
Re: Problem attaching a TM symbol to website logo
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 to the Apache Nutch web site [2]. Now in particular I am stuck with the seemingly trivial task of adding a TM symbol e.g. *#153 *to the Nutch website logo as described here [3]. After building the site source [4] I've been searching through all of the files in an attempt to locate some HTML I can edit however all I can find in /site/forrest/src/documentation is skinconf.xml which contains the snippet below. !-- project logo -- project-nameNutch/project-name project-descriptionOpen Source Web Search Software/project-description project-urlhttp://nutch.apache.org//project-url project-logoimages/nutch-logo.gif/project-logo I understand that this is a real trivial issue, however I've searched high and low and can't seem to get it. The nutch-logo.gif needs to have a trademark symbol added to it and the graphic reproduced. That is not Forrest's job. When your graphics expert has the replacement logo, if it is still named nutch-logo.gif then all that is needed is to replace the image at nutch/site/forrest/src/documentation/resources/images/ then re-generate the site. If it has a different filename, then declare the new filename in nutch/site/forrest/src/documentation/skinconf.xml at the project-logo element. If your team is not able to tweak the logo image to add the trademark symbol, i.e. you do not have access to the sources and expertise that produced it, then there is a Forrest plugin that might be able to assist. However it requires a PNG format logo. So need to use a graphics tool, e.g. Gimp, to convert the GIF. Then Forrest can be instructed to do a once-off job to apply a trademark or registered trademark to the original PNG to produce a new PNG. See: http://forrest.apache.org/pluginDocs/plugins_0_90/index.html#org.apache.forrest.plugin.input.logo -David Thank you [1] https://issues.apache.org/jira/browse/NUTCH-914 [2] http://nutch.apache.org [3] http://www.apache.org/foundation/marks/pmcs#graphics [4] https://svn.apache.org/repos/asf/nutch/site/ -- *Lewis*
Re: Not copying new project logo when building
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 /documentation a follows !-- project logo -- project-nameNutch/project-name project-descriptionOpen Source Web Search Software/project-description project-urlhttp://nutch.apache.org//project-url project-logoimages/nutch_logo_tm.gif/project-logo However when I build the project in /forrest with 'forrest',, copy /build/site to /publish then commit, the logo doesn't change, infact it actually shows a dead link to the image as you will see here [1]. Looking at the Nutch SVN i do not see either the source logo, which should be in http://svn.apache.org/viewvc/nutch/site/forrest/src/documentation/resources/images/ nor the published copy, which should be in http://svn.apache.org/viewvc/nutch/site/publish/images/ Perhaps you forgot to do 'svn add' for each of those. I've tried rebuilding and re-committing and it doesn't seem to be working at all. I suggest viewing the site before publishing, e.g. via 'forrest run' or by opening the relevant local generated pages. This helps to isolate such problems. The Forrest project also suggests http://forrest.apache.org/howto-forrestbot-svn.html as a better way to deploy the published documents. -David Users lists have provided some unexpected leads on other topics such as SVG which I am happy I found however I am still puzzling over this one. Any pointers please? Thank you [1] http://nutch.apache.org -- *Lewis*
Re: Problem understanding broken-links.xml after making changes to site
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 to find such an error by doing: cd $PROJECT_HOME svn diff tmp then look through the differences using grep or by eye, looking for ext:wiki. The new link was probably not added to site.xml configuration file. Ah, i just now looked at the recent commit for site.xml r 1172043 and it seems that you removed the entry for external-refswiki. So that would have caused the abovementioned error. -David
Re: Adding site documentation to project
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 is rather trivial and that there must be documentation on it somewhere but I have not been able to get my hands on it from the Forrest site yet! Thanks for any pointers. [1] https://svn.apache.org/repos/asf/nutch/site/ [2] https://svn.apache.org/repos/asf/nutch/branches/branch-1.4/ I gather that you mean the generated relevant docs for that version. You could use the Forrestbot as we do for our Forrest project docs. http://forrest.apache.org/howto-forrestbot-svn.html How to deploy documentation with the Forrestbot svn workstage In our case we deploy our generated documentation to SVN forrest/site which gets 'svn up' on people.apache.org to publish our website. The Nutch project could do that too for your website docs. Then have another Forrestbot buildfile which deploys the relevant docs to SVN nutch/branches/branch-1.4 -David
Re: Adding site documentation to project
Tim Williams wrote: lewis john mcgibbney lewis.mcgibb...@gmail.com wrote: I'm back working on this and could do with some pointers. Please see below for some of the keys areas. I've looked closely at your references and read both the forrestbot svn workstage and forrestbot automated build and deploying documentation. I understand completely how I want this to work and your suggestion for the process of editing sourc, updating the Nutch site, then an additional forrestbot task would update the new /docs directory within our SVN nutch/branches/branch-1.4/docs diretcory. 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: 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 is rather trivial and that there must be documentation on it somewhere but I have not been able to get my hands on it from the Forrest site yet! Thanks for any pointers. [1] https://svn.apache.org/repos/asf/nutch/site/ [2] https://svn.apache.org/repos/asf/nutch/branches/branch-1.4/ I gather that you mean the generated relevant docs for that version. You could use the Forrestbot as we do for our Forrest project docs. http://forrest.apache.org/howto-forrestbot-svn.html How to deploy documentation with the Forrestbot svn workstage In our case we deploy our generated documentation to SVN forrest/site which gets 'svn up' on people.apache.org to publish our website. I 'think' this is already done. I am waiting for a reply from the more experienced dev's to give me insight into how committed changes to the site source are actually fed through to nutch.apache.org. As I know of no other method for doing this other than the one your specified, I am going on the assumption that this is already in place. Your generated docs are committed to the site/publish/ directory. On the server it will be either an automated cron job by one or more of your committers doing 'svn up' in your nutch.a.o space (this is the old way like our Forrest project still does) or it will be under svnpubsub. [ snip] The Nutch project could do that too for your website docs. Excellent, this is now my intention :0) Then have another Forrestbot buildfile which deploys the relevant docs to SVN nutch/branches/branch-1.4 How does this task get executed? If my comments as above are correct, this appears to be the main task at hand, therefore I am trying to find out where the additional buildfile is located and if this process can be triggered should there be any update to the site documentation e.g. a commit from the dev's. There's another build file, typically publish.xml[see our example 1] that contains the details of where to publish it. You might find it easier to start with a condensed version of our own publishing instructions[2] or slightly more verbose[3] and expand your reading as necessary from there... There's no trigger to update them, but they're periodically pulled - it looks like your latest footer change, for example, was already pulled - sorry, I don't know the detailed mechanics of that arrangement. You've done plenty of research, ask away:) --tim [1] - http://svn.apache.org/repos/asf/forrest/trunk/site-author/publish.xml [2] - http://svn.apache.org/repos/asf/forrest/trunk/etc/publishing_our_site.txt [3] - http://forrest.apache.org/procedures/How_to_publish_docs.html Sure, Thanks Tim. Also see the orginal document that i referenced at http://forrest.apache.org/howto-forrestbot-svn.html#follow Nutch needs to create your own buildfile. When each committer wants to publish their changes, they run the local forrestbot build as explained. If all is well then commit their source edits and then do the deploy step. -David
Re: Is there a decent way of using different PDF fonts for different parts of a Forrest site?
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 output.xmap is unnecessary and you could have used a project-specific locationmap to point to your custom document-to-fo.xsl but maybe I'm missing something... Yes i reckon that is correct. -David --tim On Wed, Feb 1, 2012 at 8:02 AM, Karl Wright daddy...@gmail.com wrote: FWIW, the $path has just what I hoped in it and works well. Thanks! Karl On Tue, Jan 31, 2012 at 9:23 PM, Karl Wright daddy...@gmail.com wrote: Then, inside your own document-to-fo.xsl you should have access to a path parameter. You may add an additional condition to the font of interest (e.g. rootFontFamily) that uses XSL string functions against your $path parameter. I've set things up so that my document path includes the language code (e.g. 'en_US') as the first part of the path under src/documentation/content/xdocs. For example, src/documentation/content/xdocs/en_US/mydocument.xml would be the starting point. The question is what the $path variable will contain - if it's just en_US/mydocument.xml my job is easy. If it could be en_US\mydocument.xml on Windows and en_US/mydocument.xml on Unix it's a bit harder. But if it is the absolute path xsl expressions aren't going to help me and I'd better find a better solution. What I'd do (and this might even make a decent general patch) is look for the property with the language specifier first. For example, instead of looking for output.pdf.fontFamily.sansSerif first, I'd look for output.pdf.fontFamily.sansSerif.en_US first, and only look for the other if that property is not found. So, what can I expect to see for the $path parameter? Thanks again for your help! Karl
Re: Dispatcher: cannot see changes done in xml-files
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 the page. This is not the case if I don't use the dispatcher. Is there a solution to this problem? This sounds a little familiar to something I've seen. What are you using to serve the site, the embedded Jetty or an application server? Have you configured the Cocoon cache or left the defaults in place? I can see the behaviour that Børre describes. Using current head of svn trunk 0.10-dev with its sample site. Doing a fresh 'forrest seed-sample' and then configuring its forrest.properties to use Dispatcher. Then 'forrest run' so using the embedded Jetty. I found one old related discussion: Subject: Dispatcher caches too eagerly Date: 2010-05-22 http://thread.gmane.org/gmane.text.xml.forrest.devel/27855 I did not look further around that date or in JIRA. This sounds like something for the dev mailing list. -David
Re: forest project status
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 some svn activity. What is the status of the forest project? Is it still a viable project and is it likely to exist into the near future? Viability can be hard to define, but as you can see from the mailing lists it isn't very active at the moment. That said, there are still a number of developers hanging around, and some maintenance work is done from time to time. I am myself using forrest quite actively in my daily work, and am quite happy with it - thus no big incentive to take on any additional development work in addition to my regular tasks. Forrest is one of a number of tools, not a development target in itself for me. I like it quite a lot, and it has a few unique features I haven't found elsewhere: * ability to read a number of different input formats (and extend that list by writing a simple transform + some configs) * a similar ability to produce a number of different output format (likewise extendable) It also allows me to build large and complex sites while at the same time keeping the source files as text files instead of storing them in some RDB system. This again makes it easy to keep the documentation part of our version control system, which is important for our sites. All in all: forrest does what I need, and thus doesn't get a lot of attention development-wise. Regards, Sjur Very nice answer. Eric, the project is still operating and ready to respond whenever someone spurs some activity. The Apache Software Foundation ensures that there is sufficient activity in each project. If there was not, then it would have been moved to the Apache Attic. Most discussion about the project is encouraged to be on the dev mail list. This user list is for assistance with specific usage issues. Thanks for your interest, and we hope to see you join us as a dev. -David
Re: Question on Broken Links
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 cannot find where the broken link is. Here is the message: $ cat /Users/noland/workspaces/hive-apache-site/site/author/build/site/broken-links.xml broken-links link message=org.apache.cocoon.blocks.fop.FOPNGSerializerlinkmap.html/link /broken-links My only thought is that there is a missing PNG somewhere or perhaps a missing class? A missing PNG should give a different error. Sounds like the PDF document generation, and so the PDF output plugin. I did an svn checkout of the hive/site and it generates with no problems using current trunk of Forrest. I do not have older Forrest versions on hand here. Hopefully someone else could try. Earlier in the output, was there any strangeness reported when it tried to install the output.pdf plugin? You could disable the generation of PDFs by editing src/documentation/skinconf.xml and see if you get past that problem. Brock [exec] X [0] linkmap.html BROKEN: org.apache.cocoon.blocks.fop.FOPNGSerializer [exec] Total time: 0 minutes 1 seconds, Site size: 0 Site pages: 0 [exec] Java Result: 1 [exec] [exec] BUILD FAILED [exec] /data/local/apache-forrest-0.9/main/targets/site.xml:224: Error building site. [exec] [exec] There appears to be a problem with your site build. [exec] [exec] Read the output above: [exec] * Cocoon will report the status of each document: [exec] - in column 1: *=okay X=brokenLink ^=pageSkipped (see FAQ). [exec] * Even if only one link is broken, you will still get failed. [exec] * Your site would still be generated, but some pages would be broken. [exec] - See /Users/noland/workspaces/hive-apache-site/site/author/build/site/broken-links.xml [exec] [exec] Total time: 23 seconds [exec] [exec] Copying broken links file to site root. [exec] [exec] Copying 1 file to /Users/noland/workspaces/hive-apache-site/site/author/build/site
[REMINDER] ApacheCon NA 2016 Travel Assistance Applications now open!
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 attend. Could you please forward this announcement to your community, along with (if possible) information on how your project is involved in ApacheCon this year? We will be supporting ApacheCon NA, Vancouver BC, May 9th - 13th 2016. TAC exists to help those that would like to attend ApacheCon events, but are unable to do so for financial reasons. For more info on this years applications and qualifying criteria please visit the TAC website at < http://www.apache.org/travel/ >. Applications are already open, so don't delay! *Important dates*... - CFP Close: February 12, 2016 - CFP Notifications: February 29, 2016 - TAC Applications close: March 2, 2016 - Schedule Announced: March 3, 2016 Applicants have until the the closing date above to submit their applications (which should contain as much supporting material as required to efficiently and accurately process your request), this will enable TAC to announce successful awards shortly afterwards. As usual TAC expects to deal with a range of applications from a diverse range of backgrounds. We therefore encourage (as always) anyone thinking about sending in an application to do so ASAP. We look forward to greeting many of you in Vancouver, BC in May 2016! Kind Regards Lewis (On behalf of the Travel Assistance Committee)
Apache Forrest project considering retiring to the Attic
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 and expression of renewed interest, on the developers mailing list: https://lists.apache.org/thread.html/fda24957e049f10d282037594d2aa61ce9a31cf8fc5313959aa81672@%3Cdev.forrest.apache.org%3E There being no further discussion either here or on the developer mailing list, please refer to the new thread about the next steps: Subject: [VOTE] Move Apache Forrest to the Attic https://lists.apache.org/thread.html/c49f6223e82bf32b559dc4bf0a061a75369856e11cf05cf654e51036@%3Cdev.forrest.apache.org%3E
