Re: Gump CI build failing for Apache Forrest for more than 1 year
Hey Mark, I suspect not... instead, we should have the dreaded attic discussion I reckon. Thanks, --tim On Mon, Jun 17, 2019 at 6:55 AM Mark Thomas wrote: > All, > > The last successful Apache Forrest build on Gump was over 12 months ago. > > Looking back ~6 months I don't see any indications of the Apache Forrest > community working on the build failures. Granted the issues are mostly > in dependencies but that shouldn't prevent the Forrest community > addressing them. > > The current issue is a dependency on xml-stylebook that in turn depends > on JVM internals that were removed in Java 7. > > Are Gump builds still of interest to the Apache Forrest community? > > Mark >
apachecon
anyone planning on going to Seville? thanks, --tim
Re: Javascript mime type
On Thu, Jan 24, 2013 at 4:25 PM, Sjur Moshagen sju...@mac.com wrote: According to this page: http://stackoverflow.com/questions/4101394/javascript-mime-type and many others on the net, application/javascript is the correct answer, but not accepted by MS IE ≤ 8. Which leaves us with text/javascript. But several places (including the above) argues that leaving it empty is fine, and the most compatible. I have no strong opinions, though, just that the present mime type definitely is wrong :) I'd go with text/javascript - it's a reasonable default. It's worth noting that we serve it as 'application/javascript' because that's the default mime-type mapping for httpd[1]. --tim [1] - http://svn.apache.org/repos/asf/httpd/httpd/trunk/docs/conf/mime.types
Re: Javascript mime type
On Thu, Jan 24, 2013 at 4:32 PM, Tim Williams william...@gmail.com wrote: On Thu, Jan 24, 2013 at 4:25 PM, Sjur Moshagen sju...@mac.com wrote: According to this page: http://stackoverflow.com/questions/4101394/javascript-mime-type and many others on the net, application/javascript is the correct answer, but not accepted by MS IE ≤ 8. Which leaves us with text/javascript. But several places (including the above) argues that leaving it empty is fine, and the most compatible. I have no strong opinions, though, just that the present mime type definitely is wrong :) I'd go with text/javascript - it's a reasonable default. It's worth noting that we serve it as 'application/javascript' because that's the default mime-type mapping for httpd[1]. Ooops.. dangling pronoun:( we == forrest.apache.org :) --tim
Re: [VOTE] re-release version 0.9
Late, but +1... Tim-Williamss-MacBook-Pro:forrest-source twilliams$ md5 *.gz openssl sha1 *.gz MD5 (apache-forrest-0.9-dependencies.tar.gz) = 7752ee4f85066dd7a0901c06c5949c9d MD5 (apache-forrest-0.9-sources.tar.gz) = 2bc9e0b220f8ec5bc1f228dbc3023e0e SHA1(apache-forrest-0.9-dependencies.tar.gz)= 10a4442d46baeadd3ba3377ed29ed694c86ece25 SHA1(apache-forrest-0.9-sources.tar.gz)= 8c7b49a7dff4b3f60a52c7696684168b6d454a47 --tim On Wed, Apr 11, 2012 at 1:00 AM, David Crossley cross...@apache.org wrote: As explained in the Proposal [1] an issue was discovered with our release of Apache Forrest 0.9, in that our vote was conducted on a package that contained more than just our sources. I have used the voted package from our 0.9 release, verified it, and split it into two separate packages for sources and dependencies. So please download the new release candidate and supporting files: http://people.apache.org/~crossley/apache-forrest-0.9/ Get apache-forrest-0.9-sources.tar.gz (md5sum 2bc9e0b220f8ec5bc1f228dbc3023e0e) Get the *.asc and *.md5 files and follow verification notes at http://forrest.apache.org/mirrors.cgi#verify Unpack those source and ensure that you are satisifed. To test, download the dependencies apache-forrest-0.9-dependencies.tar.gz and follow the verification notes. Now unpack this directly over the top of the sources. Java 1.5 or later is required. Testing and vote period concludes after 7 days on Wednesday 2012-04-18 at 22:00 UTC [2]. Anyone can test and vote, not just PMC members. However only the Forrest PMC votes are binding [3]. When voting, quote the md5 to ensure that we are all using the correct final release candidate sources package. The votes need to happen against the final source release package. After a successful vote, i will put the files back on the distribution mirrors and adjust our download page to link to the new files and explain how to use it. [1] Subject: [Proposal] re-release 0.9 with proper source code package http://s.apache.org/mCW [2] end of vote is Wednesday 2012-04-18 at 22:00 UTC http://www.timeanddate.com/worldclock/fixedtime.html?day=18month=4year=2012hour=22min=0sec=0p1=0 [3] Guidelines for Voting A lazy majority vote requires 3 binding +1 votes and more binding +1 votes than -1 votes. http://forrest.apache.org/guidelines.html#actions http://forrest.apache.org/guidelines.html#voting
Re: [VOTE] re-release version 0.9
Sorry David, I'm gonna get around to it - hopefully tonight - thanks for the reminder:) --tim On Tue, Apr 17, 2012 at 8:09 AM, David Crossley cross...@apache.org wrote: A gentle reminder. About 1.5 days remain. -David David Crossley wrote: As explained in the Proposal [1] an issue was discovered with our release of Apache Forrest 0.9, in that our vote was conducted on a package that contained more than just our sources. I have used the voted package from our 0.9 release, verified it, and split it into two separate packages for sources and dependencies. So please download the new release candidate and supporting files: http://people.apache.org/~crossley/apache-forrest-0.9/ Get apache-forrest-0.9-sources.tar.gz (md5sum 2bc9e0b220f8ec5bc1f228dbc3023e0e) Get the *.asc and *.md5 files and follow verification notes at http://forrest.apache.org/mirrors.cgi#verify Unpack those source and ensure that you are satisifed. To test, download the dependencies apache-forrest-0.9-dependencies.tar.gz and follow the verification notes. Now unpack this directly over the top of the sources. Java 1.5 or later is required. Testing and vote period concludes after 7 days on Wednesday 2012-04-18 at 22:00 UTC [2]. Anyone can test and vote, not just PMC members. However only the Forrest PMC votes are binding [3]. When voting, quote the md5 to ensure that we are all using the correct final release candidate sources package. The votes need to happen against the final source release package. After a successful vote, i will put the files back on the distribution mirrors and adjust our download page to link to the new files and explain how to use it. [1] Subject: [Proposal] re-release 0.9 with proper source code package http://s.apache.org/mCW [2] end of vote is Wednesday 2012-04-18 at 22:00 UTC http://www.timeanddate.com/worldclock/fixedtime.html?day=18month=4year=2012hour=22min=0sec=0p1=0 [3] Guidelines for Voting A lazy majority vote requires 3 binding +1 votes and more binding +1 votes than -1 votes. http://forrest.apache.org/guidelines.html#actions http://forrest.apache.org/guidelines.html#voting
bootstrap
I've been playing with bootstrap[0] lately, I'm thinking it could freshen up our heavy look. Is anyone interested in helping? Or perhaps a part of a rewrite? I've used it for the barcamp site[1] - it naturally scales to different devices as well. Thanks, --tim [0] - http://twitter.github.com/bootstrap/ [1] - http://events.apache.org/event/2012/barcamp-dc/
forrest-osgi
I finally checked this out and ran into a couple snags. o) I had to create empty ./src/test directories in all the bundle packages. I didn't look into it as I just wanted to get running. If that's correct, I'm happy to check it in. o) It seemed to want forrest.build.xml in $FORREST_HOME/main instead of directly in $FORREST_HOME Anyone else have similar troubles? Thanks, --tim
Re: [VOTE] please review release candidate then vote
On Wed, Feb 2, 2011 at 11:10 PM, David Crossley cross...@apache.org wrote: As seen with http://svn.apache.org/viewvc?rev=1066728 and 1066729 we had made a tiny mistake with the trademark footer. IMO it would not cause another RC. +1 to ship it as is. --tim
Re: [VOTE] please review release candidate then vote
On Mon, Jan 31, 2011 at 10:47 PM, David Crossley cross...@apache.org wrote: We need people to review the release candidate and to test it on your projects, especially on different operating systems and Java version. See testing hints below. It seems that we forgot to update our Jetty version and it's *really* old. It's not technically a blocker and we wouldn't recommend a production deployment using our embedded Jetty anyway, but it's embarrassingly old. I don't know what's involved in updating it but it shouldn't be that difficult. Anyway, I could go either way on this one. Another thing is that the site-author docs include ApacheCon NA 2010 in them. I'm thinking that might deserve a new rc? Based on: Tim-Williamss-MacBook-Pro:forrest-rc twilliams$ md5 apache-forrest-0.9.tar.gz java -version MD5 (apache-forrest-0.9.tar.gz) = ea58a078e3861d4dfc8bf3296a53a5f8 java version 1.6.0_20 Java(TM) SE Runtime Environment (build 1.6.0_20-b02-279-10M3065) Java HotSpot(TM) 64-Bit Server VM (build 16.3-b01-279, mixed mode) --tim
Re: [VOTE] please review release candidate then vote
On Wed, Feb 2, 2011 at 8:14 PM, David Crossley cross...@apache.org wrote: Tim Williams wrote: Another thing is that the site-author docs include ApacheCon NA 2010 in them. I'm thinking that might deserve a new rc? That banner on the left-hand navigation is included by reference. So when the ASF Conferences people replace it with the next event, then it will show the new banner. Shucks, thanks David I didn't even look - it used to be specific to an event. Thanks for clearing it up:) Do you have any thoughts on our such an old Jetty version? --tim
Re: [Vote] Release Plan for Forrest 0.90
On Mon, Dec 13, 2010 at 6:15 PM, David Crossley cross...@apache.org wrote: Please vote on this release plan. According to our guidelines, http://forrest.apache.org/guidelines.html#actions A lazy majority vote requires 3 binding +1 votes and more binding +1 votes than -1 votes. As usual anyone is encouraged to vote, just the votes of PMC members are binding. +1 --tim
Re: [Proposal] Release Plan for Forrest 0.90
Thanks David! I'm in the midst of a double move - once to temporary housing; then a couple weeks later, to the new house - and some other rather large life-changes during this period but I'll certainly pitch in as much as possible. I could be more involved if all the dates shifted by 2-3 weeks but if this works best for your schedule, I'll do everything I can to support it. --tim On Tue, Dec 7, 2010 at 12:59 AM, David Crossley cross...@apache.org wrote: Here is my proposal for the Release Plan. After a discussion period, we will vote on this Release Plan. Aiming for a release date of 17 January 2011 [4]. Please check with your time schedules and comment. We want to have as many people available as possible to test the release candidate. So we can adjust the time schedule a bit to suit. For background info on this step and on the release process in general, see http://forrest.apache.org/procedures/release/How_to_release.html#PrepRelPlan The minimum Java version for this release is Java 1.5 I will be the Release Manager. People can help with various aspects of the release process. See [9]. People can also help between now and then to prepare the codebase. For Plugins, see the proposal below. The phases are: Voting to accept the Release Plan ends on: Monday 2010-12-20 at 22:00 UTC [1]. The first release candidate and start of testing: Monday 2011-01-10 at 22:00 UTC [2]. We create the release candidate on this day and start the testing. One week is available for this phase. Don't bother voting until towards the end of the week, because we might need a new release candidate. The vote needs to happen against the actual final packages. During code freeze we do not add any new functionality or non-essential work, just bug fixes and documentation tweaks [5]. If necessary then we create another release candidate on Saturday 2011-01-15 at 22:00 UTC [3] to give people time to verify the signatures and checksums and to do final tests. Between this date and the release date there must no changes to SVN. If any are absolutely necessary, then we delay the release date and do another release candidate. End of voting period: Monday 2011-01-17 at 22:00 UTC [4] This is the scheduled release date, then wait for the mirrors to receive it before sending the announcements. Plugins release plan: In the past we have never done a proper release for any of the plugins. We have just done a deploy for some of them, which packages a plugin and copies it to our website to make it available to people who use a Forrest release. That is not suitable. See [7]: Releases are, by definition, anything that is published beyond the group that owns it. i.e. beyond our dev list. To rectify that, i propose that we follow up after the core 0.9 release to actually vote and release each plugin that is suitable to be made widely available. Please see the list showing the state of each Plugin [8]. Between now and mid-January, please work on your favourite plugin to get it ready, send patches etc. Deploy any that need to be either updated or made available. After the 0.9 release is done, we will follow up to either release each one or to retract it. Any that are suitable to be released would also be moved out of the whiteboard/plugins. If this general Plugin release plan is okay, then we can devise a more detailed procedure. After this batch of plugin releases, they can each be independently released as new plugin versions are needed. The proposed milestones are: [1] end of vote on Release Plan Monday 2010-12-20 at 22:00 UTC http://www.timeanddate.com/worldclock/fixedtime.html?day=20month=12year=2010hour=22min=0sec=0p1=0 [2] create initial release candidate, start testing Monday 2011-01-10 at 22:00 UTC http://www.timeanddate.com/worldclock/fixedtime.html?day=10month=1year=2011hour=22min=0sec=0p1=0 [3] create final release candidate if necessary Saturday 2011-01-15 at 22:00 UTC http://www.timeanddate.com/worldclock/fixedtime.html?day=15month=1year=2011hour=22min=0sec=0p1=0 [4] end of vote on final release candidate and commence the upload phase Monday 2011-01-17 at 22:00 UTC (i.e. planned release date) http://www.timeanddate.com/worldclock/fixedtime.html?day=17month=1year=2011hour=22min=0sec=0p1=0 [5] Code freeze is defined here http://forrest.apache.org/procedures/release/announce_code_freeze.txt [6] Guidelines for Voting http://forrest.apache.org/guidelines.html#voting http://forrest.apache.org/guidelines.html#actions [7] What is a Release? http://www.apache.org/dev/release.html#what [8] State of Plugin deployment http://svn.apache.org/repos/asf/forrest/trunk/etc/review-plugin-deployment.txt [9] How to release Forrest http://forrest.apache.org/procedures/release/How_to_release.html
Re: Forrest Web sites have squished print layout in Opera
Hi Brolin, I don't use Opera, but it's an interesting observation. Would you mind opening up an issue[1] for this with all the details and attaching your screenshots? Thanks, --tim [1] - https://issues.apache.org/jira/browse/FOR On Fri, Nov 5, 2010 at 3:00 PM, Brolin Empey bro...@brolin.be wrote: I noticed the Forrest Web sites I maintain for my employer have a squished print layout in Opera Desktop. I am using Opera v10.63 on Windows 7 Professional IA-32, but I think the same issue exists with Opera on other platforms. I tried Opera Mobile v10.1 beta on Maemo 5 on my Nokia N900 too, but Opera Mobile apparently does not support printing. Here is a screenshot: http://brolin.be/graphics/screens/techsol.ca_squished_print_layout_in_Opera_v10.63.png I use Forrest v0.9-dev (with Sun’s JDK/JRE on Ubuntu) with pelt-brolin, my heavily customised fork of the pelt skin. I have not updated my working copy of Forrest v0.9-dev for months, though. Interestingly, the Forrest Web site appears to have the same squished print layout in Opera: http://brolin.be/graphics/screens/forrest.apache.org_squished_print_layout_in_Opera_v10.63.png The print layout of both sites appears OK in the other Web browsers I have tested. Has anyone noticed this issue before? What is the cause? How can we fix it? Thanks, Brolin -- Sometimes I forget how to do small talk: http://xkcd.com/222/ “If you have to ask why, you’re not a member of the intended audience.” — Bob Zimbinski, http://webpages.mr.net/bobz/ttyquake/
[jira] Commented: (FOR-1204) show the NOTICE of packaged supporting products
[ https://issues.apache.org/jira/browse/FOR-1204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12924798#action_12924798 ] Tim Williams commented on FOR-1204: --- Are we sure there's such a requirement to upack a jar file in order to grab a NOTICE file? I figure if they don't give it with their tar, gz or zip then all is well. I dunno, it seems we're adding undue burden here. show the NOTICE of packaged supporting products --- Key: FOR-1204 URL: https://issues.apache.org/jira/browse/FOR-1204 Project: Forrest Issue Type: Task Components: Project administration Affects Versions: 0.9-dev Reporter: David Crossley Fix For: 0.9-dev Now that the license files of the packaged supporting products are listed (FOR-857) we need to review each to ensure that any notice requirements of their license are met. Also unpack their jar and copy any accompanying NOTICE file up next to their license file. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Moving Forrest Zone to a FreeBSD Jail
On Thu, Sep 16, 2010 at 3:57 AM, Gav... ga...@16degrees.com.au wrote: snip headers David Crossley wrote: Also we saw recently a failure with the old zone, but did not get an email message from the new zone. So perhaps something wrong with email orginating from the new zone. I will make a deliberate break, and see what happens. Yes, forrestbot on the new zone is not sending mail. Ok, I'll take a look and fix that tomorrow. looking, I believe I found the problem, testing... Problem solved I'd say, I will test a break in the morning to be sure. It was combination of : a) - I had turned off notify on failure whilst setting up the new jail so we didn't get false alarms and double lots of emails for genuine failures. I needed to revert that now that we actually want these emails. b) - The notify.email.from (default in notify.xml) value was not well liked by the new jail mail system, overriding it and appending the hostname made it work better. c) - due to b) and in combination with rdns being incorrectly set, it wouldn't relay. Curing b) means the rdns doesn't matter that much, but that is also being fixed. will report back my final tests and findings in the morning. Yep, all seems to be working well now. Any changes I made will be committed afterwards once the PMC has approved the move. I think we're good, are you thinking a vote to approve this? I'd be +1 in such a case - there's bound to be problems, we can resolve them as they arise... --tim
[jira] Commented: (FOR-922) update all docs that explain sitemap fragments
[ https://issues.apache.org/jira/browse/FOR-922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12905753#action_12905753 ] Tim Williams commented on FOR-922: -- sitemap-ref.xml is definitely not consistent with our current processing it seems to me (e.g. compare pdf output[1] to reality[2]. We could punt, of course, as Gav suggested, but this issue seems not resolved to me... --tim [1] - http://forrest.apache.org/docs_0_90/sitemap-ref.html#pdf [2] - http://svn.apache.org/viewvc/forrest/trunk/plugins/org.apache.forrest.plugin.output.pdf/output.xmap?revision=694215view=co update all docs that explain sitemap fragments -- Key: FOR-922 URL: https://issues.apache.org/jira/browse/FOR-922 Project: Forrest Issue Type: Task Components: Documentation and website Affects Versions: 0.9-dev Reporter: David Crossley Fix For: 0.9-dev There are various documents that explain parts of the sitemaps. Some of these mention pathnames, some have actual fragments of code copied from sitemaps. All of this needs to be updated to reflect the current sitemaps. The sitemaps were recently updated to use locationmap, some sitemaps were simplified, filenames were changed, e.g. document2html.xsl to document-to-html.xsl These changes need to be reflected in the current docs. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: building a sample site with dispatcher fails
On Tue, Aug 24, 2010 at 7:11 AM, Thorsten Scherler scher...@gmail.com wrote: On Thu, 2010-08-19 at 11:06 +0200, Vicent Mas wrote: Hi all, Hmm, I cannot reproduce your problem. I did cd $FORREST_HOME svn up - At revision 988481. cd main ./build.sh clean ;./build.sh cd ../whiteboard/plugins/org.apache.forrest.plugin.internal.dispatcher/ forrest run http://localhost:/index.html - Dispatcher based site. You do not have to deploy by hand (local deploy) since using the dispatcher plugin to test will automatically deploy the plugin. thors...@mckenny:~/src/apache/forrest$ find . -name *.dispatcher.jar ./whiteboard/plugins/org.apache.forrest.plugin.internal.dispatcher/build/org.apache.forrest.plugin.internal.dispatcher.jar ./build/plugins/lib/org.apache.forrest.plugin.internal.dispatcher.jar That is under ubuntu 10.04. I tried with forrest but that resulted in link message=net.sf.ehcache.Element; local class incompatible: stream classdesc serialVersionUID = 3343087714201120157, local class serialVersionUID = 1098572221246444544linkmap.html/link Hi Thorsten, I wonder if you missed my note and didn't do forrest clean on an already built site first? http://article.gmane.org/gmane.text.xml.forrest.devel/28065/match= If that's not it, can you provide the steps to reproduce? Thanks, --tim
[jira] Commented: (FOR-1122) Example site contentIntegration currently only works in forrest run mode
[ https://issues.apache.org/jira/browse/FOR-1122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12900131#action_12900131 ] Tim Williams commented on FOR-1122: --- Add relevant email discussion: http://www.mail-archive.com/dev@forrest.apache.org/msg16550.html Example site contentIntegration currently only works in forrest run mode Key: FOR-1122 URL: https://issues.apache.org/jira/browse/FOR-1122 Project: Forrest Issue Type: Bug Components: Example Sites Affects Versions: 0.9-dev Reporter: Gavin Fix For: 0.9-dev Due to some remote content being aggregated into the site, 'forrest site' will fail as it can not resolve the remote locations. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (FOR-1122) Example site contentIntegration currently only works in forrest run mode
[ https://issues.apache.org/jira/browse/FOR-1122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12900132#action_12900132 ] Tim Williams commented on FOR-1122: --- Also, briefly, here: http://www.mail-archive.com/dev@forrest.apache.org/msg16555.html Example site contentIntegration currently only works in forrest run mode Key: FOR-1122 URL: https://issues.apache.org/jira/browse/FOR-1122 Project: Forrest Issue Type: Bug Components: Example Sites Affects Versions: 0.9-dev Reporter: Gavin Fix For: 0.9-dev Due to some remote content being aggregated into the site, 'forrest site' will fail as it can not resolve the remote locations. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (FOR-1122) Example site contentIntegration currently only works in forrest run mode
[ https://issues.apache.org/jira/browse/FOR-1122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Williams updated FOR-1122: -- Fix Version/s: 0.10 (was: 0.9-dev) I think it just shouldn't be a part of the formal release, moving on for now. Example site contentIntegration currently only works in forrest run mode Key: FOR-1122 URL: https://issues.apache.org/jira/browse/FOR-1122 Project: Forrest Issue Type: Bug Components: Example Sites Affects Versions: 0.9-dev Reporter: Gavin Fix For: 0.10 Due to some remote content being aggregated into the site, 'forrest site' will fail as it can not resolve the remote locations. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [jira] Updated: (FOR-1122) Example site contentIntegration currently only works in forrest run mode
On Wed, Aug 18, 2010 at 9:35 PM, Gav... ga...@16degrees.com.au wrote: -Original Message- From: Tim Williams (JIRA) [mailto:j...@apache.org] Sent: Thursday, 19 August 2010 11:05 AM To: dev@forrest.apache.org Subject: [jira] Updated: (FOR-1122) Example site contentIntegration currently only works in forrest run mode [ https://issues.apache.org/jira/browse/FOR- 1122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Williams updated FOR-1122: -- Fix Version/s: 0.10 (was: 0.9-dev) I think it just shouldn't be a part of the formal release, moving on for now. Right. So, I can move this to a branch - meaning I guess we copy the trunk and then remove the contentIntegration site from trunk, or easier is to just move the content into whiteboard. Thoughts before I go ahead? Shucks, I'd just leave it where it is and simply exclude it from the release build itself. It's just another directory excluded from the release, like others described in various spots[1]. --tim [1] - https://issues.apache.org/jira/browse/FOR-911 Example site contentIntegration currently only works in forrest run mode - --- Key: FOR-1122 URL: https://issues.apache.org/jira/browse/FOR-1122 Project: Forrest Issue Type: Bug Components: Example Sites Affects Versions: 0.9-dev Reporter: Gavin Fix For: 0.10 Due to some remote content being aggregated into the site, 'forrest site' will fail as it can not resolve the remote locations. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: svn commit: r986211 - in /forrest/trunk: LICENSE.txt lib/core/commons-cli-1.2.jar.license.txt lib/core/commons-cli.license.txt
I missed the LICENSE.txt listing again! Geez... Anyway, I thought the
convention was to use ${filename}.license.txt?
--tim
On Tue, Aug 17, 2010 at 3:15 AM, cross...@apache.org wrote:
Author: crossley
Date: Tue Aug 17 07:15:15 2010
New Revision: 986211
URL: http://svn.apache.org/viewvc?rev=986211view=rev
Log:
The commons-cli is now licensed: Apache License 2.0
Issue: FOR-855 FOR-857
Added:
forrest/trunk/lib/core/commons-cli.license.txt
- copied unchanged from r986198,
forrest/trunk/lib/core/commons-cli-1.2.jar.license.txt
Removed:
forrest/trunk/lib/core/commons-cli-1.2.jar.license.txt
Modified:
forrest/trunk/LICENSE.txt
Modified: forrest/trunk/LICENSE.txt
URL:
http://svn.apache.org/viewvc/forrest/trunk/LICENSE.txt?rev=986211r1=986210r2=986211view=diff
==
--- forrest/trunk/LICENSE.txt (original)
+++ forrest/trunk/LICENSE.txt Tue Aug 17 07:15:15 2010
@@ -212,6 +212,7 @@ These supporting products are licensed:
license: lib/core/avalon-logkit-2.1.jar.license.txt
license: lib/core/batik-all-1.6.jar.license.txt
license: lib/core/cocoon.license.txt
+license: lib/core/commons-cli.license.txt
license: lib/core/commons-collections-3.2.jar.license.txt
license: lib/core/commons-httpclient-2.0.2.jar.license.txt
license: lib/core/commons-io.LICENSE.txt
@@ -280,7 +281,6 @@ license: lib/core/ehcache-core.license.t
These supporting products are licensed: Apache Software License, Version 1.1
license: lib/core/avalon-framework-api-4.3.jar.license.txt
license: lib/core/avalon-framework-impl-4.3.jar.license.txt
-license: lib/core/commons-cli-1.0.jar.license.txt
license: lib/core/excalibur-i18n-1.1.jar.license.txt
license: lib/core/excalibur-io-1.1.jar.license.txt
license: lib/core/excalibur-naming-1.0.jar.license.txt
Re: svn commit: r984293 - in /forrest/trunk/lib/core: commons-collections-3.2.1.jar commons-collections-3.2.1.jar.license.txt commons-collections-3.2.jar commons-collections-3.2.jar.license.txt
On Tue, Aug 17, 2010 at 2:35 AM, David Crossley cross...@apache.org wrote: That commons-collections*.license.txt is a notice file rather than a license file. Is that a mistake here, or is that how it comes from them? Nope, mistake. I did on another one and fixed it, I'll fix this one this evening. --tim
Dependency updates
I've gone through and updated what I can. I didn't touch Cocoon itself. I'm left with the following unresolved. If you can offer any help in either ruling out the need to update these or letting me know where it's used and how to test, I'd appreciate it. I'd be ok with leaving all of these as is personally. Anyway, help appreciated. --tim batik-all-1.6.jar - used? how to test? castor-0.9.6-xml.jar - used? how to test? chaperon-20040205.jar - Not sure about the version, but $current seems just as old. commons-httpclient-2.0.2.jar - i assume the excalibur protocol handlers use this and therefore we should leave? commons-jci-r306555.jar - used? how to test? commons-jexl-1.0.jar - used? how to test? concurrent-1.3.4.jar - is this still used anywhere - if so, it probably shouldn't? jcs-1.2.5-dev-20050313.jar - used? how to test? I thought the default storeimpl was ehcache now too? jtidy-04aug2000r7-dev.jar - not sure what do to. lucene-1.4.3.jar - cocoon dep, so I assume we're stuck with it. slf4j-api-1.5.11.jar - tempted to leave it slf4j-log4j12-1.5.11.jar - tempted to leave it xml-commons-resolver-1.2-dev-r395116.jar xmlbeans-1.0.3.jar - The next version is a major, and not sure where it's used. xmlgraphics-commons-1.3.1.jar - couldn't find checksums
Re: building a sample site with dispatcher fails
On Wed, Aug 11, 2010 at 4:13 AM, Vicent Mas uve...@gmail.com wrote: 2010/8/11 Tim Williams william...@gmail.com: On Tue, Aug 10, 2010 at 12:55 PM, Sina K. Heshmati s...@khakbaz.com wrote: -- Prior discussions have been snipped, please view the complete thread at: http://markmail.org/message/fyloqkqilo2tqalr -- Hi Vicent, Vicent Mas uve...@gmail.com said: I don't know why I always get those errors. My connectivity to Internet is just fine. It's been almost a week since you've reported your issue. At this point, I'd like to advise you to share a fairly complete screencast of your workflow, maybe someone could come up with an idea as to what's causing this issue. In case you're willing to choose this option, please make sure to echo e.g. the relevant environment variables, the output of 'java -version'. Actually, I've been working on upgrading some libraries and realized I've just ignored that my local ./build.sh test fails on the dispatcher test. Today, I looked at my log and also saw the ClassNotFoundException on the DispatcherTransformer. Are other folks able to ./build.sh test with success on the second [dispatcher] build? Thanks, --tim That is interesting. Maybe the problem is not just the configuration of my box. In fact, after reading your message I've installed forrest on a laptop with kubuntu. It is the first time I install forrest there. The installed JDK is the ubuntu package (java6-openjdk or something similar) not the Sun Java. When I try to create a dispatcher sample site I get the same error about DispatcherTransformer. Actually, the './build.sh test' issue seems to have been caused by using the ./build.xml classpath instead of the forrest.build.xml classpath. The 'test' target calls the 'site' target which needs the more robust classpath. This was resolved by not letting the 'site' target inherit the settings of the 'test' target. You may want to do 'forrest site -v' and grep the results for 'dispatcher.jar' --tim
Re: building a sample site with dispatcher fails
On Wed, Aug 11, 2010 at 7:28 AM, Vicent Mas uve...@gmail.com wrote: 2010/8/11 Tim Williams william...@gmail.com: On Wed, Aug 11, 2010 at 4:13 AM, Vicent Mas uve...@gmail.com wrote: 2010/8/11 Tim Williams william...@gmail.com: On Tue, Aug 10, 2010 at 12:55 PM, Sina K. Heshmati s...@khakbaz.com wrote: -- Prior discussions have been snipped, please view the complete thread at: http://markmail.org/message/fyloqkqilo2tqalr -- Hi Vicent, Vicent Mas uve...@gmail.com said: I don't know why I always get those errors. My connectivity to Internet is just fine. It's been almost a week since you've reported your issue. At this point, I'd like to advise you to share a fairly complete screencast of your workflow, maybe someone could come up with an idea as to what's causing this issue. In case you're willing to choose this option, please make sure to echo e.g. the relevant environment variables, the output of 'java -version'. Actually, I've been working on upgrading some libraries and realized I've just ignored that my local ./build.sh test fails on the dispatcher test. Today, I looked at my log and also saw the ClassNotFoundException on the DispatcherTransformer. Are other folks able to ./build.sh test with success on the second [dispatcher] build? Thanks, --tim That is interesting. Maybe the problem is not just the configuration of my box. In fact, after reading your message I've installed forrest on a laptop with kubuntu. It is the first time I install forrest there. The installed JDK is the ubuntu package (java6-openjdk or something similar) not the Sun Java. When I try to create a dispatcher sample site I get the same error about DispatcherTransformer. Actually, the './build.sh test' issue seems to have been caused by using the ./build.xml classpath instead of the forrest.build.xml classpath. The 'test' target calls the 'site' target which needs the more robust classpath. This was resolved by not letting the 'site' target inherit the settings of the 'test' target. And how can I do the same (sorry if it is a stupid question)? You shouldn't need to. You're using the standard site target which does add plugins (and all necessary jars) to the classpath. ...You may want to do 'forrest site -v' and grep the results for 'dispatcher.jar' --tim In the directory of my seed site (after $ forrest clean): v...@rachael:/tmp/my_test$ forrest site -v | grep dispatcher.jar Unable to find build/org.apache.forrest.plugin.internal.dispatcher.jar Warning: /tmp/my_test/build/webapp/resources not found. Warning: /tmp/my_test/src/documentation/skins/common/images not found. Warning: /tmp/my_test/src/documentation/skins/pelt/images not found. Warning: /tmp/my_test/src/documentation/skins/common not found. Warning: /tmp/my_test/src/documentation/skins/pelt not found. Java Result: 1 BUILD FAILED /opt/forrest/main/targets/site.xml:223: Error building site. There appears to be a problem with your site build. Read the output above: * Cocoon will report the status of each document: - in column 1: *=okay X=brokenLink ^=pageSkipped (see FAQ). * Even if only one link is broken, you will still get failed. * Your site would still be generated, but some pages would be broken. - See /tmp/my_test/build/site/broken-links.xml at org.apache.tools.ant.taskdefs.Exit.execute(Exit.java:142) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288) at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106) at org.apache.tools.ant.Task.perform(Task.java:348) at org.apache.tools.ant.taskdefs.Sequential.execute(Sequential.java:62) at net.sf.antcontrib.logic.IfTask.execute(IfTask.java:197) at sun.reflect.GeneratedMethodAccessor22.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106) at org.apache.tools.ant.TaskAdapter.execute(TaskAdapter.java:154) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288) at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106) at org.apache.tools.ant.Task.perform(Task.java:348) at org.apache.tools.ant.Target.execute(Target.java:357) at org.apache.tools.ant.Target.performTasks(Target.java:385
Re: [jira] Commented: (FOR-1122) Example site contentIntegration currently only works in forrest run mode
On Mon, Jul 26, 2010 at 2:20 AM, Gav... ga...@16degrees.com.au wrote: -Original Message- From: Gavin (JIRA) [mailto:j...@apache.org] Sent: Monday, 26 July 2010 3:50 PM To: dev@forrest.apache.org Subject: [jira] Commented: (FOR-1122) Example site contentIntegration currently only works in forrest run mode [ https://issues.apache.org/jira/browse/FOR- 1122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment- tabpanelfocusedCommentId=12892185#action_12892185 ] Gavin commented on FOR-1122: This refers to the site locared in trunk/examples/ContentIntegration. Just cd into that dir and do a 'forrest site' . Note that Forrest Run also now has problems which I'll bring up on list. This examples/ContentIntegration site I think is too far broken to fix real soon; and depends on the dispatcher for some of its usefulness. I think it might be a good idea to move it out of our trunk and into a branch where it can be worked on at leisure and re-inserted into trunk at a later date, thus not holding up the next release. Thoughts? +1, it seems that the tei plugin itself is broken too and may be (at least partly) to blame. --tim
Re: building a sample site with dispatcher fails
On Tue, Aug 10, 2010 at 12:55 PM, Sina K. Heshmati s...@khakbaz.com wrote: -- Prior discussions have been snipped, please view the complete thread at: http://markmail.org/message/fyloqkqilo2tqalr -- Hi Vicent, Vicent Mas uve...@gmail.com said: I don't know why I always get those errors. My connectivity to Internet is just fine. It's been almost a week since you've reported your issue. At this point, I'd like to advise you to share a fairly complete screencast of your workflow, maybe someone could come up with an idea as to what's causing this issue. In case you're willing to choose this option, please make sure to echo e.g. the relevant environment variables, the output of 'java -version'. Actually, I've been working on upgrading some libraries and realized I've just ignored that my local ./build.sh test fails on the dispatcher test. Today, I looked at my log and also saw the ClassNotFoundException on the DispatcherTransformer. Are other folks able to ./build.sh test with success on the second [dispatcher] build? Thanks, --tim
[jira] Commented: (FOR-303) upgrade to commons-jxpath-1.2 causes errors with site: links
[ https://issues.apache.org/jira/browse/FOR-303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12897120#action_12897120 ] Tim Williams commented on FOR-303: -- After updating to jxpath-1.3, I couldn't reproduce using 'forrest site' - can someone test this so that we can either close this issue or revert my update? upgrade to commons-jxpath-1.2 causes errors with site: links -- Key: FOR-303 URL: https://issues.apache.org/jira/browse/FOR-303 Project: Forrest Issue Type: Bug Components: Core operations Affects Versions: 0.6 Reporter: David Crossley The upgrade from commons-jxpath-20030909 to commons-jxpath-1.2 cause 'forrest' to report errors such as BROKEN: No pipeline matched request: samples/site:samples/faq. Reverted to commons-jxpath-2003090 at r47378. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: building a sample site with dispatcher fails
On Thu, Aug 5, 2010 at 7:14 AM, Vicent Mas uve...@gmail.com wrote: Hi again, after coming back to the initial situation (fresh check out of the repo) the problems with my dispatcher seed site are obviously reproduced. When executing $ forrest run the console displays the following errors: [... SNIP...] fetch-plugins-descriptors: Copying 1 file to /tmp/prova/build/tmp Copying 1 file to /tmp/prova/build/tmp Fetching plugins descriptor: http://forrest.apache.org/plugins/plugins.xml Getting: http://forrest.apache.org/plugins/plugins.xml To: /tmp/prova/build/tmp/plugins-1.xml local file date : Thu Aug 05 11:27:45 CEST 2010 Error getting http://forrest.apache.org/plugins/plugins.xml to /tmp/prova/build/tmp/plugins-1.xml Fetching plugins descriptor: http://forrest.apache.org/plugins/whiteboard-plugins.xml Getting: http://forrest.apache.org/plugins/whiteboard-plugins.xml To: /tmp/prova/build/tmp/plugins-2.xml local file date : Thu Aug 05 11:31:47 CEST 2010 Error getting http://forrest.apache.org/plugins/whiteboard-plugins.xml to /tmp/prova/build/tmp/plugins-2.xml Plugin list loaded from http://forrest.apache.org/plugins/plugins.xml. Plugin list loaded from http://forrest.apache.org/plugins/whiteboard-plugins.xml. Why isn't it able to retrieve the descriptors? I don't get those errors and it leads me to wonder whether the other errors reported are just side effects of this? Can you curl/wget the descriptors? --tim
Re: building a sample site with dispatcher fails
On Thu, Aug 5, 2010 at 4:34 AM, Vicent Mas uve...@gmail.com wrote: 2010/8/4 Vicent Mas uve...@gmail.com: Hi, while investigating the problems that I sent yesterday to this list (thread 'Unable to run forrest') and due to the long time I've been without using forrest I decided to start with the simplest task i.e. build a sample site using $ forrest seed. It works fine if I don't use dispatcher, but when I activated the dispatcher in the forrest.properties file I got an Internal Server Error page in my browser: [...SNIP...] After that I pressed CTRL-C, and executed $ forrest clean. Then I run the $ forrest command. I got the following: [... SNIP...] So a couple of errors getting http://forrest.apache.org/plugins/plugins.xml and a BROKEN: org.apache.forrest.dispatcher.transformation.DispatcherTransformer (basically the same problems that I get when trying to build my real site). As I said I haven't worked with forrest for a long time so maybe the problem is between the chair and the keyboard, but anyway I would really thank any help. Vicent [... SNIP ...] Hi again, I've been browsing the mailing list archives without luck. The only think I've found is the thread Re: Can't get Dispatcher working at all windows/linux from trunk. Following one of its suggestions I've went back to before the dispatcher merge. I've done a svn up to r882421 2009-11-20. It is not the solution I was looking for but at least now my local forrest is working again. If anyone knows a real solution I'll be glad to hear about it. Hi Vicent, I'm hoping someone more familiar with Dispatcher can come along and help but for now, can you turn up logging and see if that gives at least a better clue? FWIW, dispatcher on the seed works for me and appears to be working on our zone too so hopefully this is just a small configuration problem and logging will help unveil it. Unfortunately, I'm leaving for holiday right now and won't be around for a few days... --tim
Re: unable to run forrest
On Tue, Aug 3, 2010 at 8:16 AM, Vicent Mas uve...@gmail.com wrote:
Hi list,
after a long time (more than one year) without working with computers due to
several problems I'm trying to come back to my normal activity with computers.
One of the first things I'm trying to do is to update my dispatcher website
(www.vitables.org) but I'm unable to do it. I've done a fresh trunk check out
which built with no problems (just a couple of deprecation warnings):
rachael:/opt/forrest_trunk/main# ./build.sh
Using classpath:
../lib/endorsed/jakarta-bcel-20040329.jar:../lib/endorsed/jakarta-regexp-1.5.jar:../lib/endorsed/xalan-2.7.1.jar:../lib/endorsed/xercesImpl-2.9.1.jar:../lib/endorsed/xml-apis-1.3.04.jar
Buildfile: build.xml
init:
Created dir: /opt/forrest_trunk/build
--
Using Apache Ant version 1.7.1 compiled on September 26 2008
Build file /opt/forrest_trunk/main/build.xml
Use 'build.[sh|bat] -projecthelp' to see other options.
Build system home /opt/forrest_trunk/tools/ant
Build number 0
Project Name Forrest build file
Java Version 1.6
Timestamp 201008031357
This is: apache-forrest 0.9-dev
--
compile:
Created dir: /opt/forrest_trunk/build/classes
Compiling 33 source files to /opt/forrest_trunk/build/classes
/opt/forrest_trunk/main/java/org/apache/forrest/log/ForrestLogTargetFactory.java:22:
warning: [deprecation] org.apache.cocoon.util.log.CocoonTargetFactory
in org.apache.cocoon.util.log has been deprecated
import org.apache.cocoon.util.log.CocoonTargetFactory;
^
/opt/forrest_trunk/main/java/org/apache/forrest/log/ForrestLogTargetFactory.java:30:
warning: [deprecation] org.apache.cocoon.util.log.CocoonTargetFactory
in org.apache.cocoon.util.log has been deprecated
extends CocoonTargetFactory {
^
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
2 warnings
jar:
Building jar: /opt/forrest_trunk/build/xml-forrest.jar
*-
| Installation notice
*-
| You have now built the 0.9-dev version of Forrest.
| Please set the environment variable FORREST_HOME to point to
| /opt/forrest_trunk
| It is recommended to add
| unix: $FORREST_HOME/bin: to your $PATH
| win: %FORREST_HOME%\bin; to your %PATH%
| Then do 'forrest -projecthelp' to list options for the 'forrest' command
| More help at http://forrest.apache.org/
*-
BUILD SUCCESSFUL
Total time: 4 seconds
After that I've created a sample site with $ forrest seed, copied the
forrest.properties* files to my real site folder, and added my required
plugins to the forrest.properties file:
# project.required.plugins=org.apache.forrest.plugin.output.pdf
project.required.plugins=org.apache.forrest.plugin.internal.dispatcher,org.apache.forrest.plugin.input.feeder,org.apache.forrest.themes.core
Then I run $ forrest run. It fails. The output is lenghty but the only errors
I
see are the following:
[...]
fetch-plugins-descriptors:
Copying 1 file to /home/vmas/ViTables/website/forrest/build/tmp
Copying 1 file to /home/vmas/ViTables/website/forrest/build/tmp
Fetching plugins descriptor: http://forrest.apache.org/plugins/plugins.xml
Getting: http://forrest.apache.org/plugins/plugins.xml
To: /home/vmas/ViTables/website/forrest/build/tmp/plugins-1.xml
local file date : Tue Aug 03 08:53:46 CEST 2010
Error getting http://forrest.apache.org/plugins/plugins.xml to
/home/vmas/ViTables/website/forrest/build/tmp/plugins-1.xml
Fetching plugins descriptor:
http://forrest.apache.org/plugins/whiteboard-plugins.xml
Getting: http://forrest.apache.org/plugins/whiteboard-plugins.xml
To: /home/vmas/ViTables/website/forrest/build/tmp/plugins-2.xml
local file date : Tue Aug 03 08:53:57 CEST 2010
Error getting http://forrest.apache.org/plugins/whiteboard-plugins.xml
to /home/vmas/ViTables/website/forrest/build/tmp/plugins-2.xml
Plugin list loaded from http://forrest.apache.org/plugins/plugins.xml.
Plugin list loaded from
http://forrest.apache.org/plugins/whiteboard-plugins.xml.
[...]
--
Installing plugin: org.apache.forrest.themes.core
--
check-plugin:
org.apache.forrest.themes.core is not available in the build dir.
Trying to fetch it...
init-props:
echo-settings-condition:
echo-settings:
init-proxy:
fetch-plugins-descriptors:
fetch-plugin:
Trying to find the description of org.apache.forrest.themes.core in
the different descriptor files
Using the descriptor file
Re: svn commit: r981724 - /forrest/trunk/LICENSE.txt
Argghhh... sorry... Thanks David! --tim On Mon, Aug 2, 2010 at 10:13 PM, cross...@apache.org wrote: Author: crossley Date: Tue Aug 3 02:13:43 2010 New Revision: 981724 URL: http://svn.apache.org/viewvc?rev=981724view=rev Log: Refer to the ehcache and slf4j licenses of r981119 Modified: forrest/trunk/LICENSE.txt Modified: forrest/trunk/LICENSE.txt URL: http://svn.apache.org/viewvc/forrest/trunk/LICENSE.txt?rev=981724r1=981723r2=981724view=diff == --- forrest/trunk/LICENSE.txt (original) +++ forrest/trunk/LICENSE.txt Tue Aug 3 02:13:43 2010 @@ -274,7 +274,7 @@ See the license text displayed above for These supporting products are licensed: based on Apache License, Version 2.0 -license: lib/core/ehcache-1.2.3.jar.license.txt +license: lib/core/ehcache-2.2.0.jar.license.txt These supporting products are licensed: Apache Software License, Version 1.1 @@ -343,6 +343,10 @@ license: lib/core/jtidy-04aug2000r7-dev. license: tools/eclipse/plugins/org.apache.forrest.eclipse.servletEngine/lib/XMLParserAPIs-dom-software.LICENSE.txt +These supporting products are licensed: The MIT License +license: lib/core/slf4j-log4j12-1.5.11.jar.license.txt + + These supporting products are licensed: Mozilla Public License Version 1.1 license: lib/core/rhino-1.6R5.jar.license.txt
Heads Up! [was: Re: svn commit: r981119 - /forrest/trunk/lib/core/]
Devs, With this change, any on-disk cache will be inconsistent and unreadable with the new version. Any site that is built already will need to a forrest clean prior to forrest site. Sorry for the inconvenience... Thanks, --tim On Sat, Jul 31, 2010 at 10:49 PM, twilli...@apache.org wrote: Author: twilliams Date: Sun Aug 1 02:49:23 2010 New Revision: 981119 URL: http://svn.apache.org/viewvc?rev=981119view=rev Log: Updated ehcache to latest version Added: forrest/trunk/lib/core/ehcache-core-2.2.0.jar (with props) forrest/trunk/lib/core/ehcache-core-2.2.0.jar.license.txt (with props) forrest/trunk/lib/core/slf4j-api-1.5.11.jar (with props) forrest/trunk/lib/core/slf4j-api-1.5.11.jar.license.txt forrest/trunk/lib/core/slf4j-log4j12-1.5.11.jar (with props) forrest/trunk/lib/core/slf4j-log4j12-1.5.11.jar.license.txt Removed: forrest/trunk/lib/core/ehcache-1.2.3.jar forrest/trunk/lib/core/ehcache-1.2.3.jar.license.txt Added: forrest/trunk/lib/core/ehcache-core-2.2.0.jar URL: http://svn.apache.org/viewvc/forrest/trunk/lib/core/ehcache-core-2.2.0.jar?rev=981119view=auto == Binary file - no diff available. Propchange: forrest/trunk/lib/core/ehcache-core-2.2.0.jar -- svn:executable = * Propchange: forrest/trunk/lib/core/ehcache-core-2.2.0.jar -- svn:mime-type = application/octet-stream Added: forrest/trunk/lib/core/ehcache-core-2.2.0.jar.license.txt URL: http://svn.apache.org/viewvc/forrest/trunk/lib/core/ehcache-core-2.2.0.jar.license.txt?rev=981119view=auto == --- forrest/trunk/lib/core/ehcache-core-2.2.0.jar.license.txt (added) +++ forrest/trunk/lib/core/ehcache-core-2.2.0.jar.license.txt Sun Aug 1 02:49:23 2010 @@ -0,0 +1,15 @@ +/** + * Copyright 2003-2010 Terracotta, Inc. + * + * Licensed under the Apache License, Version 2.0 (the License); + * you may not use this file except in compliance with the License. + * You may obtain a copy of the License at + * + * http://www.apache.org/licenses/LICENSE-2.0 + * + * Unless required by applicable law or agreed to in writing, software + * distributed under the License is distributed on an AS IS BASIS, + * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + * See the License for the specific language governing permissions and + * limitations under the License. + */ \ No newline at end of file Propchange: forrest/trunk/lib/core/ehcache-core-2.2.0.jar.license.txt -- svn:executable = * Added: forrest/trunk/lib/core/slf4j-api-1.5.11.jar URL: http://svn.apache.org/viewvc/forrest/trunk/lib/core/slf4j-api-1.5.11.jar?rev=981119view=auto == Binary file - no diff available. Propchange: forrest/trunk/lib/core/slf4j-api-1.5.11.jar -- svn:executable = * Propchange: forrest/trunk/lib/core/slf4j-api-1.5.11.jar -- svn:mime-type = application/octet-stream Added: forrest/trunk/lib/core/slf4j-api-1.5.11.jar.license.txt URL: http://svn.apache.org/viewvc/forrest/trunk/lib/core/slf4j-api-1.5.11.jar.license.txt?rev=981119view=auto == --- forrest/trunk/lib/core/slf4j-api-1.5.11.jar.license.txt (added) +++ forrest/trunk/lib/core/slf4j-api-1.5.11.jar.license.txt Sun Aug 1 02:49:23 2010 @@ -0,0 +1,23 @@ + Copyright (c) 2004-2008 QOS.ch + All rights reserved. + + Permission is hereby granted, free of charge, to any person obtaining + a copy of this software and associated documentation files (the + Software), to deal in the Software without restriction, including + without limitation the rights to use, copy, modify, merge, publish, + distribute, sublicense, and/or sell copies of the Software, and to + permit persons to whom the Software is furnished to do so, subject to + the following conditions: + + The above copyright notice and this permission notice shall be + included in all copies or substantial portions of the Software. + + THE SOFTWARE IS PROVIDED AS IS, WITHOUT WARRANTY OF ANY KIND, + EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF + MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND + NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE + LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION + OF CONTRACT,
Re: upgrading some supporting products
On Fri, Jul 30, 2010 at 3:50 AM, David Crossley cross...@apache.org wrote: One of the things that we usually do in the lead-up to a release, especially one that is so long between, is to upgrade some important supporting products. Now that Gump is running Forrest again, it is showing that we can upgrade these with some confidence. [1] http://forrest.apache.org/gump.html Some candidates are Ant, Xerces, Xalan, xml-apis, Excalibur, ant-contrib, various Apache Commons stuff. See the list of supporting products being used by our Gump at [2] http://vmgump.apache.org/gump/public/forrest/forrest-test-basic/details.html The ones with Annotation = Work Entity are specific versions of some products. Of course Gump is using a packaged version of Cocoon-2.1.11 release, because Gump is not yet building the head of Cocoon-2.1 branch. See our Gump descriptor at [1] for more info. The rest in the list at [2] are the head of each product's development. So compare with what we have in our lib directories in SVN to see what might be upgraded. We are still using a very old version of Ehcache (v1.2.3) and Gump is not yet attempting to use the recent development version. So local testing would be needed to determine if that can be upgraded. If someone feels like doing those tasks, then please do. I can help here but I thought we *didn't* do updates really close to a release[1]? [of course, I'm assuming we're close to a release:) ] Thanks, --tim [1] - http://forrest.apache.org/procedures/release/How_to_release.html#prep
[jira] Updated: (FOR-1150) regularly ensure valid HTML
[ https://issues.apache.org/jira/browse/FOR-1150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Williams updated FOR-1150: -- Fix Version/s: 0.10 (was: 0.9-dev) http://www.mail-archive.com/dev@forrest.apache.org/msg16555.html As mentioned, Gav checked, I spot checked. regularly ensure valid HTML --- Key: FOR-1150 URL: https://issues.apache.org/jira/browse/FOR-1150 Project: Forrest Issue Type: Sub-task Components: Plugin: internal.dispatcher, Skins (general issues) Reporter: David Crossley Fix For: 0.10 Ensure that HTML validates okay for the test document referred to in the parent issue. Use http://validator.w3.org/ -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (FOR-1151) regularly ensure valid CSS
[ https://issues.apache.org/jira/browse/FOR-1151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Williams updated FOR-1151: -- Fix Version/s: 0.10 (was: 0.9-dev) http://www.mail-archive.com/dev@forrest.apache.org/msg16555.html As mentioned, Gav checked, I spot checked. regularly ensure valid CSS -- Key: FOR-1151 URL: https://issues.apache.org/jira/browse/FOR-1151 Project: Forrest Issue Type: Sub-task Components: Plugin: internal.dispatcher, Skins (general issues) Reporter: David Crossley Fix For: 0.10 Ensure that CSS validates okay for the test document referred to in the parent issue. Use http://jigsaw.w3.org/css-validator/ -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (FOR-1152) regularly ensure cross-browser consistency
[ https://issues.apache.org/jira/browse/FOR-1152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Williams updated FOR-1152: -- Fix Version/s: 0.10 (was: 0.9-dev) http://www.mail-archive.com/dev@forrest.apache.org/msg16555.html As mentioned, Gav checked, I spot checked. regularly ensure cross-browser consistency -- Key: FOR-1152 URL: https://issues.apache.org/jira/browse/FOR-1152 Project: Forrest Issue Type: Sub-task Components: Plugin: internal.dispatcher, Skins (general issues) Reporter: David Crossley Fix For: 0.10 Review the sites using cross-browser testing tools. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (FOR-1149) regularly review our example sites
[ https://issues.apache.org/jira/browse/FOR-1149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Williams updated FOR-1149: -- Fix Version/s: 0.10 (was: 0.9-dev) http://www.mail-archive.com/dev@forrest.apache.org/msg16555.html Gav reviewed, I've spot checked too. Seems ok. regularly review our example sites -- Key: FOR-1149 URL: https://issues.apache.org/jira/browse/FOR-1149 Project: Forrest Issue Type: Task Components: Plugin: internal.dispatcher, Skins (general issues) Reporter: David Crossley Fix For: 0.10 We need to continually re-assess our example sites, to ensure such things as xml validation, css validation, and cross-browser consistency. Please leave this issue and subtasks as an open reminder of what needs to be done. Create separate issues for each problem that arises. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (FOR-889) Use by Ant of newer catalog entity resolver failing for Windows
[ https://issues.apache.org/jira/browse/FOR-889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Williams updated FOR-889: - Fix Version/s: 0.10 (was: 0.9-dev) Workaround still appears valid. Use by Ant of newer catalog entity resolver failing for Windows --- Key: FOR-889 URL: https://issues.apache.org/jira/browse/FOR-889 Project: Forrest Issue Type: Bug Components: XML grammars validation Affects Versions: 0.8 Reporter: David Crossley Fix For: 0.10 Attachments: afterUpgrade.txt, ant-debug.log, beforeUpgrade.txt, debug-new.log, dynamic-cocoon.log, n-cyg-resolver.log, o-cyg-resolver.log, static-cocoon.log, unix-validate-r395116-resolver.txt, validate-xdocs-original-resolver.txt, validate-xodcs-r395116-resolver.txt Some people on Windows report that the 'forrest validate-xdocs' task is failing when we upgrade the $FORREST_HOME/tools/ant/lib/xml-commons-resolver.jar See discussion in: [heads up] Ant upgraded, please test http://marc.theaimsgroup.com/?t=11480039011 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (FOR-1073) link elements with no href are created by html-to-document.xsl for a/name
[ https://issues.apache.org/jira/browse/FOR-1073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Williams updated FOR-1073: -- Fix Version/s: 0.10 (was: 0.9-dev) Unable to reproduce, moving to next release. link elements with no href are created by html-to-document.xsl for a/name - Key: FOR-1073 URL: https://issues.apache.org/jira/browse/FOR-1073 Project: Forrest Issue Type: Bug Components: Core operations Affects Versions: 0.9-dev Reporter: David Crossley Fix For: 0.10 In FOR-1072 Jeremias said: Filtered out link elements with no href (which are created by html-to-document.xsl for a name=...). Forrest 0.7 didn't generate them as links at all but trunk does. Maybe that's wrong in the first place. There was also a mention of it previously on the dev list surrounding the recent FOP update branch work. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (FOR-1168) Sample pages that fail validation
[ https://issues.apache.org/jira/browse/FOR-1168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Williams updated FOR-1168: -- Fix Version/s: 0.10 (was: 0.9-dev) Effects dispatcher, pushing off 'til next release. Sample pages that fail validation - Key: FOR-1168 URL: https://issues.apache.org/jira/browse/FOR-1168 Project: Forrest Issue Type: Bug Components: Documentation and website, Plugin: internal.dispatcher Affects Versions: 0.9-dev Reporter: Gavin Assignee: Gavin Fix For: 0.10 The main 'sample.html' passes validation fine, however some other pages fail xhtml 1.0 strict validation. Mainly due to the use of the + symbol in name anchors. Not a problem for sites validating to HTML4.01. These pages include (but check for more) samples-b/usemap.html samples-b/xinclude.html samples-b/static.html samples-b/linking.html samples-b/howto-wowto.html samples-b/embedded_html.html samples-b/ascii-art.html locationmap/index.html samples-c/subdir/index.html samples-c/showonlywhenselected/page1.html samples-c/showonlywhenselected/page2.html pluginDocs/plugins_0_90/index.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (FOR-1166) Search Button is misplaced to the right in some browsers - Pelt Theme
[ https://issues.apache.org/jira/browse/FOR-1166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Williams updated FOR-1166: -- Fix Version/s: 0.10 (was: 0.9-dev) dispatcher; moving to next release. Search Button is misplaced to the right in some browsers - Pelt Theme - Key: FOR-1166 URL: https://issues.apache.org/jira/browse/FOR-1166 Project: Forrest Issue Type: Bug Components: Plugin: internal.dispatcher, Plugin: themes.core Affects Versions: 0.9-dev Reporter: Gavin Fix For: 0.10 Attachments: 090512-234506-forrest.zones.apache.org-2778316.zip The 'Search' Button used with the 'Search the site with ...' Feature is not correctly situated in Firefox on Linux machines. It is way off to the right, making the site pages horizontally scroll apart from it being ugly. Interestingly, it looks fine in Firefox on Windows. Also looks good in IE7 and Google Chrome on Windows. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (FOR-1080) Add Dispatcher Notes to compatible plugins
[ https://issues.apache.org/jira/browse/FOR-1080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Williams updated FOR-1080: -- Fix Version/s: 0.10 (was: 0.9-dev) dispatcher; pushing off to next release. Add Dispatcher Notes to compatible plugins -- Key: FOR-1080 URL: https://issues.apache.org/jira/browse/FOR-1080 Project: Forrest Issue Type: Improvement Components: Documentation and website, Plugin: internal.dispatcher, Plugins (general issues) Affects Versions: 0.9-dev Reporter: Gavin Priority: Minor Fix For: 0.10 Some (most?) Plugins are Dispatcher compatible, notes should be added to each plugin documentation summarising how to use the plugin in dispatcher enabled projects - such as adding contracts that make use of a plugin. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Moving Forrest Zone to a FreeBSD Jail
On Mon, Jul 19, 2010 at 6:46 AM, Gav... ga...@16degrees.com.au wrote: Hi All, Infra are working towards removing Helios our Zones machine. The Zones are to be replaced with FreeBSD (8.1-RC2 currently) Jails. All projects zones are to be moved over the next few weeks. I have been tasked mainly with this job, with help from others as required. I have created new Jails but have yet to migrate an existing zone to a jail, so I would like to start on familiar ground and get the Forrest Zone moved - this week if possible. Anyone who has an acct on our current zone setup will if they still require it, get an acct on the new Jail. Does anyone foresee any issues in doing this? Is the timing ok? The only thing I can see is that FreeBSD (and now Debian/Ubuntu) uses the Diablo Java rather than the sun jdk so if anyone knows of any issues with that please let me know. I envisage a short crossover period where we will have both available (forrest.zones.a.o and forrest2.zones.a.o) until we are happy all is well at our new digs. If no objections I'll start soon (next couple of days) +1, can you reset my password in the process too? Thanks, --tim
Re: Propose moving main website to svnpubsub system.
On Mon, Jul 19, 2010 at 7:04 AM, Gav... ga...@16degrees.com.au wrote: Hi All, Over in infra land we have svnpubsub system for the immediate publishing of website changes. The pubsub daemon watches our /www/forrest.apache.org area for commits and as they come in, does an immediate svn up on our web servers - making the changes live almost immediate, rather than having to wait an hour or two for the next sync to happen. This is currently being used by other projects such as httpd, apr, trafficserver and a few others. After some early trial issues I'm confident that this system is now working just fine and propose that Apache Forrest move over to this system. We as a project need do nothing (I will take care of infra changes.) Our own publishing methods such as using Forrestbot would not need to change (as all that does is commit to our /site/ are of svn.) We currently commit to our svn /site/ area and a cronjob checks for updates every 1/2 hour -- that cronjob would no longer be necessary and the pubsub deamon would take over listening for and performing updates. Thoughts or concerns on doing this? +1, Sounds like all good-ness to me:) --tim
[jira] Updated: (FOR-796) Merge all view/dispatcher work into org.apache.forrest.plugin.internal.dispatcher and org.apache.forrest.themes.core
[ https://issues.apache.org/jira/browse/FOR-796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Williams updated FOR-796: - Fix Version/s: 0.10 (was: 0.9-dev) Moving to 0.10 Merge all view/dispatcher work into org.apache.forrest.plugin.internal.dispatcher and org.apache.forrest.themes.core Key: FOR-796 URL: https://issues.apache.org/jira/browse/FOR-796 Project: Forrest Issue Type: New Feature Components: Plugin: internal.dispatcher Affects Versions: 0.8 Reporter: Thorsten Scherler Priority: Blocker Fix For: 0.10 Attachments: dispatcher-enabler.patch This is the global issue to keep track on the merging effort -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Moving dispatcher issues
We've discussed this many times (e.g. [1]) but I'd like to propose we leave the dispatcher in the whiteboard for the 0.9 release. This would allow us to remove the dispatcher-related blocker issues and push off many of the other dispatcher-related issues to the future - and, more importantly, allow us to get *something* out the door. Obviously, there are valid considerations for doing either but I think we've reached the point that we simply need to make a hard call and move on. In times like this, I think, the conservative decision is often best. For practical purposes, the folks that are using dispatcher functionality right now are well aware of how to keep on using it anyway so I'd suggest the only real downside is that it limits future adoption of it rather than significantly hampering any existing users - an very real but reasonable compromise. If no objections emerge, I'll go ahead and push off those issues in JIRA. Thoughts? Thanks, --tim [1] - http://www.mail-archive.com/dev@forrest.apache.org/msg16091.html
Author tags
Regarding FOR-855[1] and the @author tags, I couldn't get the
committer tool to work but this...
grep -r -i --exclude=*.{xsl,svn*} @author ./ | wc -l
...turns up 13 potential issues. Now, I'm glad to remove 3 of them
because their Ross and Thorsten's which understand our culture, but
the others are code dragged in from other projects. I reckon that the
license allows us to remove them too but I wanted to just confirm
before we get rid of them - as I understand it, if the author really
wanted attribution they would have asked us for mention in a NOTICE
file or somesuch vs. having any expectation from the author
annotations.
Good news is that there's only one that's outside the whiteboard and,
therefore, could slow things up.
Thanks,
--tim
[1] - https://issues.apache.org/jira/browse/FOR-855
[jira] Commented: (FOR-857) append license files to the top-level LICENSE.txt
[ https://issues.apache.org/jira/browse/FOR-857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12884887#action_12884887 ] Tim Williams commented on FOR-857: -- If you know of a good, reasonably reliable find command, pls share it. Otherwise, I'll try to write something in ruby to do this. On the other hand, this got me wondering, is RAT not verifying this for us? append license files to the top-level LICENSE.txt - Key: FOR-857 URL: https://issues.apache.org/jira/browse/FOR-857 Project: Forrest Issue Type: Bug Components: Project administration Reporter: David Crossley Assignee: David Crossley Fix For: 0.9-dev The license files for accompanying external products needs to be appended after the Apache License in the top-level $FORREST_HOME/LICENSE.txt file. Perhaps the current discussion on the legal-discuss mailing list will clarify http://www.apache.org/foundation/mailinglists.html#foundation-legal -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: stop re-generating PDF documents on Forrest website
On Mon, Jun 21, 2010 at 7:42 AM, David Crossley cross...@apache.org wrote: Done this now. See issue https://issues.apache.org/jira/browse/FOR-1200 This is good, as it fixes the symptoms, but we've got to find someone with pdf expertise to fix the underlying issue FOR-1077 as it's probably a blocker in our current state. I reckon I'm only stating the obvious though:) --tim
Re: stop re-generating PDF documents on Forrest website
On Mon, Jun 21, 2010 at 8:41 AM, Jeremias Maerki d...@jeremias-maerki.ch wrote: Right here! ;-) If I've got it right, there are two problems: Awesome, thanks Jeremias! 1. The creation date in the metadata defaults to the current date and time so that's different with each run. 2. The file ID in the PDF trailer is also dependent on the current date and time. N° 1 should be solveable by explicitely setting some creation date in an XMP metadata packet in the fo:declarations element. For example: fo:declarations x:xmpmeta xmlns:x=adobe:ns:meta/ rdf:RDF xmlns:rdf=http://www.w3.org/1999/02/22-rdf-syntax-ns#; rdf:Description rdf:about= xmlns:dc=http://purl.org/dc/elements/1.1/; !-- Dublin Core properties go here -- dc:titleA Forrest document/dc:title /rdf:Description rdf:Description rdf:about= xmlns:xmp=http://ns.adobe.com/xap/1.0/; !-- XMP properties go here -- xmp:CreatorToolApache Forrest/xmp:CreatorTool xmp:CreateDate2010-06-21T14:20:00+02:00/xmp:CreateDate xmp:MetadataDate2010-06-21T14:20:00+02:00/xmp:MetadataDate /rdf:Description /rdf:RDF /x:xmpmeta /fo:declarations See also http://xmlgraphics.apache.org/fop/0.95/metadata.html However, taking a short look, it looks like the metadata date is currently always set to the current date and time. So we'd have to change FOP to allow overriding the metadata date. N° 2 is only solveable by introducing a configuration setting that disables the creation of the file ID in the PDF trailer. Standard like PDF/A and PDF/X require the presence of the file ID. But in this case, it is unwanted, of course. I've created a Bugzilla issue for FOP with this: https://issues.apache.org/bugzilla/show_bug.cgi?id=49479 I added a link to that issue in our own FOR-1077 and a link to this conversation. That issue is listed for us as Major but I think it's practically a Blocker. I can't promise that I can look into this very soon. No problem - we'll be anxiously awaiting:) Thanks, --tim On 21.06.2010 13:50:31 Tim Williams wrote: On Mon, Jun 21, 2010 at 7:42 AM, David Crossley cross...@apache.org wrote: Done this now. See issue https://issues.apache.org/jira/browse/FOR-1200 This is good, as it fixes the symptoms, but we've got to find someone with pdf expertise to fix the underlying issue FOR-1077 as it's probably a blocker in our current state. I reckon I'm only stating the obvious though:) --tim Jeremias Maerki
[jira] Updated: (FOR-1103) Move output.inputModule code into core
[ https://issues.apache.org/jira/browse/FOR-1103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Williams updated FOR-1103: -- Fix Version/s: 0.10 (was: 0.9-dev) I'm tempted to close this since the current status needs more documentation could be said for *everything* here. For now, I'm just moving it to .10 Move output.inputModule code into core -- Key: FOR-1103 URL: https://issues.apache.org/jira/browse/FOR-1103 Project: Forrest Issue Type: Improvement Components: Core operations, Plugin: output.inputModule Affects Versions: 0.9-dev Reporter: Sjur N. Moshagen Fix For: 0.10 As discussed and decided in the thread http://www.mail-archive.com/dev@forrest.apache.org/msg14705.html see esp. the message: http://marc.info/?l=forrest-devm=122030056505478w=2 we want to move the code for the output.inputModule into the core, to get rid of plugin dependencies. This should be done before we release 0.9. This issue is created just to not loose track of it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (FOR-1122) Example site contentIntegration currently only works in forrest run mode
[ https://issues.apache.org/jira/browse/FOR-1122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12879613#action_12879613 ] Tim Williams commented on FOR-1122: --- What sample does this refer too? Steps to recreate? Thanks, --tim Example site contentIntegration currently only works in forrest run mode Key: FOR-1122 URL: https://issues.apache.org/jira/browse/FOR-1122 Project: Forrest Issue Type: Bug Components: Example Sites Affects Versions: 0.9-dev Reporter: Gavin Fix For: 0.9-dev Due to some remote content being aggregated into the site, 'forrest site' will fail as it can not resolve the remote locations. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: svn commit: r951824 - /forrest/trunk/plugins/build.xml
On Sun, Jun 6, 2010 at 1:26 AM, cross...@apache.org wrote: Author: crossley Date: Sun Jun 6 05:26:23 2010 New Revision: 951824 URL: http://svn.apache.org/viewvc?rev=951824view=rev Log: Use plain svn commands rather than Jsvn. Issue: FOR-1198 Sorry David, I said I'd take a look at this and never came back to it. Thanks... --tim
whiteboard fun
I'm playing with scala and using it to experiment with some new publishing ideas similar to what Ross did with forrest2. It doesn't really do anything useful yet but it's enough code that I need to get it under version control. Anyone mind my tossing it in the whiteboard? The main concern being the 'distraction factor' - but I think it's immature enough where it won't be:) Thanks, --tim
forrestbot switching to plain svn command
I've got this working locally, but I use cache credentials (e.g. keychain). I'd personally not be comfortable putting my credentials in clear text in a properties file. That's the part (deploy.svn.settings) that, I haven't worked. So, I'll offer some options up: 1) We can remove the credential business totally and assume that folks work out their authentication on their own and I'll check in what I have. 2) If someone else has an itch and really wants the credentials to be there, I can either a) checkin what I have and they can go about adding it in or b) we can create a JIRA ticket and I'll attach it to that. Any thoughts/recommendations? Thanks, --tim
Re: svn commit: r951719 - /forrest/trunk/plugins/build.xml
On Sat, Jun 5, 2010 at 6:42 PM, Gav... ga...@16degrees.com.au wrote:
-Original Message-
From: Gav... [mailto:ga...@16degrees.com.au]
Sent: Sunday, 6 June 2010 8:29 AM
To: dev@forrest.apache.org
Subject: RE: svn commit: r951719 - /forrest/trunk/plugins/build.xml
-Original Message-
From: Gav... [mailto:ga...@16degrees.com.au]
Sent: Sunday, 6 June 2010 8:17 AM
To: dev@forrest.apache.org
Subject: RE: svn commit: r951719 - /forrest/trunk/plugins/build.xml
-Original Message-
From: Tim Williams [mailto:william...@gmail.com]
Sent: Sunday, 6 June 2010 7:05 AM
To: Forrest Developers List
Subject: Re: svn commit: r951719 - /forrest/trunk/plugins/build.xml
On Sat, Jun 5, 2010 at 9:56 AM, cross...@apache.org wrote:
Author: crossley
Date: Sat Jun 5 13:56:23 2010
New Revision: 951719
URL: http://svn.apache.org/viewvc?rev=951719view=rev
Log:
Better detection of java_exists.
Issue: FOR-1137
Modified:
forrest/trunk/plugins/build.xml
Modified: forrest/trunk/plugins/build.xml
URL:
http://svn.apache.org/viewvc/forrest/trunk/plugins/build.xml?rev=951719
r1=951718r2=951719view=diff
===
===
--- forrest/trunk/plugins/build.xml (original)
+++ forrest/trunk/plugins/build.xml Sat Jun 5 13:56:23 2010
@@ -87,7 +87,8 @@
fileset dir=${plugin.lib.dir} includes=*.jar/
fileset dir=${plugin.lib.dir} includes=*.zip/
/path
- available file=${plugin.java.dir} property=java_exists
type=dir/
+ fileset dir=${plugin.java.dir} id=java_present
includes=**/*.java/
+ pathconvert property=java_exists refid=java_present
setonempty=false/
/target
target name=echo-init depends=init-build-compiler
unless=no.echo.init
buildnumber file=${build.dir}/build.number/
I'm pretty sure this is causing our ails at the moment. I don't
have
time to figure out what it's all about and update it properly,
should
we revert for now?
From what I can tell it should be something like:
fileset dir=${plugin.java.dir} id=java_present
include name =**/*.java/
/fileset
(the includes= seems to include a dir rather than a set of files)
I'll test it shortly.
I was wrong there, either should be acceptable and makes no difference
to
the output.
So, going back to the original form and altering it slightly:
available file=${plugin.java.dir}/**/*.java property=java_exists/
seems to work fine, though I haven’t seen wildcards in any examples, I'm
assuming this will work and set the property accordingly.
Thanks Gav, you gonna commit this one or you want me to do it?
--tim
Re: forrestbot switching to plain svn command
On Sat, Jun 5, 2010 at 6:59 PM, Sina K. Heshmati s...@khakbaz.com wrote: Tim Williams wrote: I've got this working locally, but I use cache credentials (e.g. keychain). I'd personally not be comfortable putting my credentials in clear text in a properties file. That's the part (deploy.svn.settings) that, I haven't worked. So, I'll offer some options up: 1) We can remove the credential business totally and assume that folks work out their authentication on their own and I'll check in what I have. 2) If someone else has an itch and really wants the credentials to be there, I can either a) checkin what I have and they can go about adding it in or b) we can create a JIRA ticket and I'll attach it to that. Any thoughts/recommendations? Maybe something like: 1) If the deploy.svn.settings file exists, use it, if not 2) Prompt user for credentials. If user input is empty, 3) Rely on ~/.subversion i.e. auth-cache. Thanks Sina, I wasn't clear. It was really whether or not people see it as significant enough to be missed. I'm happy to give pointers on how to get it done but I haven't the time or inclination to do the various credential-cache-clearing maneuvers required to properly test it. The code is trivial, testing this particular thing fully is the burden - I'd be happy to implement it if someone else were inclined to test it:) For now, I'll create a JIRA issue, check in what I have and if someone wants to build on it, they can. --tim
[jira] Created: (FOR-1198) Change forrestbot to use plain svn commands
Change forrestbot to use plain svn commands --- Key: FOR-1198 URL: https://issues.apache.org/jira/browse/FOR-1198 Project: Forrest Issue Type: Improvement Components: Tool: Forrestbot Affects Versions: 0.9-dev Reporter: Tim Williams Fix For: 0.9-dev Forrestbot currently uses jsvn which isn't actively maintained and is in a poor state of documentation. We already use regular svn commands in certain places and, given the state of jsvn, we should switch everywhere to using plain svn commands. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (FOR-1198) Change forrestbot to use plain svn commands
[ https://issues.apache.org/jira/browse/FOR-1198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Williams updated FOR-1198: -- Attachment: plain-svn.patch Patches forrestbot to use plain svn. It relies stricly on cached credentials and doesn't make use of the old deploy.svn.settings file at all. If that's important, we'll need to implement and test that. Change forrestbot to use plain svn commands --- Key: FOR-1198 URL: https://issues.apache.org/jira/browse/FOR-1198 Project: Forrest Issue Type: Improvement Components: Tool: Forrestbot Affects Versions: 0.9-dev Reporter: Tim Williams Fix For: 0.9-dev Attachments: plain-svn.patch Forrestbot currently uses jsvn which isn't actively maintained and is in a poor state of documentation. We already use regular svn commands in certain places and, given the state of jsvn, we should switch everywhere to using plain svn commands. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (FOR-1198) Change forrestbot to use plain svn commands
[ https://issues.apache.org/jira/browse/FOR-1198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Williams updated FOR-1198: -- Other Info: [Patch available] Change forrestbot to use plain svn commands --- Key: FOR-1198 URL: https://issues.apache.org/jira/browse/FOR-1198 Project: Forrest Issue Type: Improvement Components: Tool: Forrestbot Affects Versions: 0.9-dev Reporter: Tim Williams Fix For: 0.9-dev Attachments: plain-svn.patch Forrestbot currently uses jsvn which isn't actively maintained and is in a poor state of documentation. We already use regular svn commands in certain places and, given the state of jsvn, we should switch everywhere to using plain svn commands. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: svn commit: r951317 [1/10] - in /forrest/site: ./ docs_0_90/ docs_0_90/howto/ docs_0_90/howto/cvs-ssh/ docs_0_90/howto/multi/ dtdx/ plan/ pluginDocs/ pluginDocs/plugins_0_70/ pluginDocs/plugins_
On Fri, Jun 4, 2010 at 4:25 AM, cross...@apache.org wrote: Author: crossley Date: Fri Jun 4 08:24:58 2010 New Revision: 951317 URL: http://svn.apache.org/viewvc?rev=951317view=rev Log: Publish from forrestbot So... what was the issue? --tim
Re: Add RAT report to master summary
On Mon, May 31, 2010 at 10:57 PM, Gav... ga...@16degrees.com.au wrote: -Original Message- From: David Crossley [mailto:cross...@apache.org] Sent: Monday, 31 May 2010 3:11 PM To: dev@forrest.apache.org Subject: Re: Add RAT report to master summary Gav... wrote: I'd like to add our RAT report (http://ci.apache.org/projects/forrest/rat-output.txt) to the http://ci.apache.org/projects/rat-master-summary.html page. To do that, I need to produce an .xml output, not the .txt version currently produced. Any problems with me doing that or can I go ahead? Go ahead and just tell us what you have done is the most efficient way. It is, and inline with other projects, the txt reports will disappear soon. We are now listed at [1] and [2] with nice zero (0) against our name. Nice, thanks Gav... --tim
Re: Add RAT report to master summary
On Fri, May 28, 2010 at 3:32 AM, Gav... ga...@16degrees.com.au wrote: Hi, I'd like to add our RAT report (http://ci.apache.org/projects/forrest/rat-output.txt) to the http://ci.apache.org/projects/rat-master-summary.html page. To do that, I need to produce an .xml output, not the .txt version currently produced. Any problems with me doing that or can I go ahead? +1 --tim
Re: trouble publishing project docs
On Wed, May 26, 2010 at 9:36 PM, David Crossley cross...@apache.org wrote: Tim Williams wrote: Just a guess, if you use keychain, is it out of sync with a recently updated password change? Thanks for trying. No, it is not that. The ASF Committers password is there, and i can commit okay. However, it is just my local forrestbot that is not working. That is why i wonder if Ant or Jsvn might cache it. I also tried removing my deploy.svn.settings file, thinking that i would then get prompted for the password. But it didn't. And still gave the same credentials error. maybe: rm -Rf ~/.ssh/auth Though, it'd be strange that the command line would use keychain yet the ant task would use these credentials. I'm wildly guessing at this stage in case you haven't noticed:) --tim http://svnbook.red-bean.com/en/1.1/ch07.html#svn-ch-7-sect-1.1
Re: release process for our plugins
On Thu, May 27, 2010 at 5:16 AM, David Crossley cross...@apache.org wrote: We do have a process sorted out for releasing of Forrest core. [1] How to release Forrest http://forrest.apache.org/procedures/release/How_to_release.html I reckon that it meets the ASF requirements. Please see this email where i have before tried to ensure that we do: [2] http://markmail.org/message/kwecoaue7p4qcy2v To: forrest-dev Re: Clarification on the release requirements Unfortunately the links are broken in that display, so i tracked them down again. Here are a couple of places where Roy set out some principles/policy/reasons-for-doing-stuff ... [3] http://markmail.org/message/3odlybipss4wnczl [4] http://markmail.org/message/njray5dbazwcdcts I reckon that it would be worth our while to review that discussion. There is other background material at [5] http://www.apache.org/dev/#releases [6] http://www.apache.org/dev/release.html With those principles in mind, we need to attend to our release process for our plugins. We don't actually yet have a process. Do find in page for plugin at [1] to see the steps. You will reach a point where our doc says fixme and refers to a draft document at [7] $FORREST_HOME/plugins/RELEASE_PROCESS.txt There are some other notes at [8] http://forrest.apache.org/docs/dev/howto/howto-buildPlugin.html We do have tools for doing deploy of plugins, i.e. putting an updated version on the server. As described in [6] Releases FAQ, What Is A Release? Releases are, by definition, anything that is published beyond the group that owns it. In our case, that means any publication outside the group of people on the product dev list. If the general public is being instructed to download a package, then that package has been released. Each PMC must obey the ASF requirements on approving any release. How you label the package is a secondary issue, described below. It should be easy. For each plugin, the proposer puts a package at their apache.org space. We each download, install, review, and then vote. Then use the release Ant target rather than the deploy target. However, we have another issue. We have been providing that software via our website. If i understand correctly then we should be doing that from w.a.o/dist/forrest/ See some discussion at https://issues.apache.org/jira/browse/FOR-1068 Perhaps we should at least solve the release process issue now, and leave the deployment issue until post 0.9 release. The release process issue? relative to plugins I assume? The draft release doc in the plugins directory suggests that its possible to release plugins independent of the core but couldn't we, for now, just as well continue to do what we do and release the plugins with the core? In other words, it seems to me we're meeting Roy's intent fairly well by releasing the whole bundle together - formal process, signed, etc. I guess, what I'm wondering is... can we punt on plugin releases, move dispatcher to /plugins and just vote on the whole bundle as normal? Or, do you see something that needs addressing now, before a 0.9 release? Sorry, you were probably hoping for answers not questions:) --tim
[jira] Updated: (FOR-960) PNG Images not transparent in IE6 or below
[ https://issues.apache.org/jira/browse/FOR-960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Williams updated FOR-960: - Fix Version/s: 0.10 (was: 0.9-dev) Delaying to next release. PNG Images not transparent in IE6 or below -- Key: FOR-960 URL: https://issues.apache.org/jira/browse/FOR-960 Project: Forrest Issue Type: Bug Components: Plugin: internal.dispatcher Affects Versions: 0.8 Reporter: Gavin Assignee: Gavin Priority: Minor Fix For: 0.10 As an example, the project logo images appear with a white-ish background when viewed in IE6 or earlier. Fine in Firefox etc. This can be overcome with an AlphaImageLoader fix applied. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (FOR-891) css-validator reports CSS errors and many warnings for pelt skin
[ https://issues.apache.org/jira/browse/FOR-891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Williams updated FOR-891: - Fix Version/s: 0.10 (was: 0.9-dev) Moving to next release. css-validator reports CSS errors and many warnings for pelt skin Key: FOR-891 URL: https://issues.apache.org/jira/browse/FOR-891 Project: Forrest Issue Type: Bug Components: Documentation and website, Skins (general issues) Affects Versions: 0.8 Reporter: David Crossley Priority: Minor Fix For: 0.10 Attachments: screen.css.diff, screen_2.css.diff Our home page does not pass CSS validation with http://jigsaw.w3.org/css-validator/ -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (FOR-985) the plugins 'test' target does not local deploy its required plugins
[ https://issues.apache.org/jira/browse/FOR-985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Williams updated FOR-985: - Fix Version/s: 0.10 (was: 0.9-dev) Valid workaround exists, delaying. the plugins 'test' target does not local deploy its required plugins Key: FOR-985 URL: https://issues.apache.org/jira/browse/FOR-985 Project: Forrest Issue Type: Bug Components: Plugins (general issues) Affects Versions: 0.8, 0.9-dev Reporter: David Crossley Fix For: 0.10 For some reason our plugin 'test' Ant target only does a local deploy of the actual plugin that it is tesing and not the other plugins that are required by this plugin. See thread: plugins 'test' target April 13 when testing RC1. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
dispatcher compile errors
Anyone else getting: compile: [javac] Compiling 1 source file to /Users/twilliams/Development/forrest/whiteboard/plugins/org.apache.forrest.plugin.internal.dispatcher/build/classes [javac] /Users/twilliams/Development/forrest/whiteboard/plugins/org.apache.forrest.plugin.internal.dispatcher/src/java/org/apache/forrest/dispatcher/transformation/DispatcherTransformer.java:399: cannot access SourceResolver [javac] class file for SourceResolver not found [javac] resolverDispatcher = new CocoonResolver(m_resolver); [javac] ^ [javac] 1 error ... in dispatcher? I'll poke around locally but wanted to see if it was just me since zones is apparently working fine. --tim
Re: trouble publishing project docs
On Wed, May 26, 2010 at 4:46 AM, David Crossley cross...@apache.org wrote: I am still having this trouble deploying our website. Would another committer please see how they go: $] cat $FORREST_HOME/etc/publishing_our_site.txt Note that i have confirmed my $FORREST_HOME/deploy.svn.settings file. I can commit changes to the sources. Just having trouble with: $] forrest -f publish.xml deploy which gives ... BUILD FAILED com.alternatecomputing.jsvn.command.CommandException: svn: Commit failed (details follow): svn: MKACTIVITY of '/repos/asf/!svn/act/09d75e90-9268-4792-aad1-352ccc57da41': authorization failed: Could not authenticate to server: rejected Basic challenge (https://svn.apache.org) I can give it a try tonight if no one beats me too it. --tim
Re: Merging back the dispatcher
On Tue, May 25, 2010 at 11:18 PM, Brian M Dube bd...@apache.org wrote: On Tue, May 25, 2010 at 08:16:51AM -0400, Tim Williams wrote: On Tue, May 25, 2010 at 4:03 AM, Thorsten Scherler thors...@apache.org wrote: On 25/05/2010, at 03:15, Tim Williams wrote: On Tue, Apr 27, 2010 at 7:59 AM, Thorsten Scherler thors...@apache.org wrote: On 27/04/2010, at 08:04, David Crossley wrote: Tim Williams wrote: Well, if the dispatcher is all that changed in such a release, we could do a 0.91 afterwards. I think there's another consideration that I didn't mention too. I feel irresponsible releasing software that we can't support and I'm concerned that this would be the case with the dispatcher. I have a difficult enough time now digging up Cocoon knowledge when questions come across but with dispatcher-related ones I have no clue. Maybe it's an unfounded concern, I dunno... I have the same concerns. Perhaps we should get 0.9 released ASAP, then make a concerted effort to build a Dispatcher community. Make another release soon after. I understand what you are all saying, but the dispatcher is basically one transformer and the usage of locationmap for resolving the structurer and contracts. There is not much more to it. So, would you be against a 0.9 release with dispatcher in the whiteboard? Does anyone have the time in the near future to move it from the whiteboard anyway? I am not sure about the community support as reason to keep it in the whiteboard. There are many devs and committer that uses the dispatcher so I do not see the missing community around it. Thanks Thorsten, fair enough, I'm hoping someone finds time to move it to /plugins soon? I've been avoiding the dispatcher related 0.9 issues until this decision was made so we'll also need to start picking through those issues and figuring which can be pushed off. --tim I can find the time to move it, but do we have a consensus? It's hard to tell when it's so quiet. As I understand it, it could happen under lazy approval anyway. I dunno, maybe a vote is in order. On the other hand, I need to find our documentation on plugin releases and how they do/do not necessarily coincide with the app itself - I think Ross has written about this somewhere... --tim
Re: trouble publishing project docs
On Wed, May 26, 2010 at 8:04 AM, Tim Williams william...@gmail.com wrote: On Wed, May 26, 2010 at 4:46 AM, David Crossley cross...@apache.org wrote: I am still having this trouble deploying our website. Would another committer please see how they go: $] cat $FORREST_HOME/etc/publishing_our_site.txt Note that i have confirmed my $FORREST_HOME/deploy.svn.settings file. I can commit changes to the sources. Just having trouble with: $] forrest -f publish.xml deploy which gives ... BUILD FAILED com.alternatecomputing.jsvn.command.CommandException: svn: Commit failed (details follow): svn: MKACTIVITY of '/repos/asf/!svn/act/09d75e90-9268-4792-aad1-352ccc57da41': authorization failed: Could not authenticate to server: rejected Basic challenge (https://svn.apache.org) I can give it a try tonight if no one beats me too it. I just published and all appeared to go well. I got a complaint from an svn step of svn: invalid option character: but I don't see an obvious negative side effect of that. --tim
Re: trouble publishing project docs
On Wed, May 26, 2010 at 8:13 PM, Tim Williams william...@gmail.com wrote: On Wed, May 26, 2010 at 8:04 AM, Tim Williams william...@gmail.com wrote: On Wed, May 26, 2010 at 4:46 AM, David Crossley cross...@apache.org wrote: I am still having this trouble deploying our website. Would another committer please see how they go: $] cat $FORREST_HOME/etc/publishing_our_site.txt Note that i have confirmed my $FORREST_HOME/deploy.svn.settings file. I can commit changes to the sources. Just having trouble with: $] forrest -f publish.xml deploy which gives ... BUILD FAILED com.alternatecomputing.jsvn.command.CommandException: svn: Commit failed (details follow): svn: MKACTIVITY of '/repos/asf/!svn/act/09d75e90-9268-4792-aad1-352ccc57da41': authorization failed: Could not authenticate to server: rejected Basic challenge (https://svn.apache.org) I can give it a try tonight if no one beats me too it. I just published and all appeared to go well. I got a complaint from an svn step of svn: invalid option character: but I don't see an obvious negative side effect of that. Just a guess, if you use keychain, is it out of sync with a recently updated password change? --tim
Re: Merging back the dispatcher
On Tue, May 25, 2010 at 4:03 AM, Thorsten Scherler thors...@apache.org wrote: On 25/05/2010, at 03:15, Tim Williams wrote: On Tue, Apr 27, 2010 at 7:59 AM, Thorsten Scherler thors...@apache.org wrote: On 27/04/2010, at 08:04, David Crossley wrote: Tim Williams wrote: Well, if the dispatcher is all that changed in such a release, we could do a 0.91 afterwards. I think there's another consideration that I didn't mention too. I feel irresponsible releasing software that we can't support and I'm concerned that this would be the case with the dispatcher. I have a difficult enough time now digging up Cocoon knowledge when questions come across but with dispatcher-related ones I have no clue. Maybe it's an unfounded concern, I dunno... I have the same concerns. Perhaps we should get 0.9 released ASAP, then make a concerted effort to build a Dispatcher community. Make another release soon after. I understand what you are all saying, but the dispatcher is basically one transformer and the usage of locationmap for resolving the structurer and contracts. There is not much more to it. So, would you be against a 0.9 release with dispatcher in the whiteboard? Does anyone have the time in the near future to move it from the whiteboard anyway? I am not sure about the community support as reason to keep it in the whiteboard. There are many devs and committer that uses the dispatcher so I do not see the missing community around it. Thanks Thorsten, fair enough, I'm hoping someone finds time to move it to /plugins soon? I've been avoiding the dispatcher related 0.9 issues until this decision was made so we'll also need to start picking through those issues and figuring which can be pushed off. --tim
Re: Merging back the dispatcher
On Tue, Apr 27, 2010 at 7:59 AM, Thorsten Scherler thors...@apache.org wrote: On 27/04/2010, at 08:04, David Crossley wrote: Tim Williams wrote: Well, if the dispatcher is all that changed in such a release, we could do a 0.91 afterwards. I think there's another consideration that I didn't mention too. I feel irresponsible releasing software that we can't support and I'm concerned that this would be the case with the dispatcher. I have a difficult enough time now digging up Cocoon knowledge when questions come across but with dispatcher-related ones I have no clue. Maybe it's an unfounded concern, I dunno... I have the same concerns. Perhaps we should get 0.9 released ASAP, then make a concerted effort to build a Dispatcher community. Make another release soon after. I understand what you are all saying, but the dispatcher is basically one transformer and the usage of locationmap for resolving the structurer and contracts. There is not much more to it. So, would you be against a 0.9 release with dispatcher in the whiteboard? Does anyone have the time in the near future to move it from the whiteboard anyway? --tim
[jira] Updated: (FOR-1081) Create example document(s) with all common and pelt contracts enabled and working.
[ https://issues.apache.org/jira/browse/FOR-1081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Williams updated FOR-1081: -- Fix Version/s: (was: 0.9-dev) 0.10 Deferring... Create example document(s) with all common and pelt contracts enabled and working. -- Key: FOR-1081 URL: https://issues.apache.org/jira/browse/FOR-1081 Project: Forrest Issue Type: Improvement Components: Documentation and website, Plugin: internal.dispatcher Affects Versions: 0.9-dev Reporter: Gavin Fix For: 0.10 All available contracts should be enabled in Panels and working so that they may be used as examples and also as a test to ensure they work; and as a warning when they don't. So , in the style of document-v20 this should be created in seed-sample2 so that forrestbot can let us know when any contracts break. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (FOR-785) plugins/*/skinconf.xml does not validate since using entity to ease management
[ https://issues.apache.org/jira/browse/FOR-785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Williams updated FOR-785: - Fix Version/s: 0.10 (was: 0.9-dev) plugins/*/skinconf.xml does not validate since using entity to ease management -- Key: FOR-785 URL: https://issues.apache.org/jira/browse/FOR-785 Project: Forrest Issue Type: Bug Components: Plugins (general issues) Affects Versions: 0.8 Reporter: David Crossley Fix For: 0.10 Attachments: dtdchanges.diff, enableValidatePlugins.diff Recently i split the skinconf.xml for each plugin to refer to common stuff via an external entity. Works nicely. Okay, i admit it ... forgot to do 'build test' :-) and it doesn't validate. The DTD insists on having the elements in a specific order. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (FOR-776) rationalise the pluginTemplate and current plugins to have minimal configuration files, etc.
[ https://issues.apache.org/jira/browse/FOR-776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Williams updated FOR-776: - Fix Version/s: 0.10 (was: 0.9-dev) rationalise the pluginTemplate and current plugins to have minimal configuration files, etc. Key: FOR-776 URL: https://issues.apache.org/jira/browse/FOR-776 Project: Forrest Issue Type: Improvement Components: Plugins (general issues) Reporter: David Crossley Fix For: 0.10 forrest.properties can have minimal entries and rely on the default.forrest.properties Remove PDF from each project.required.plugins skinconf.xml needs to be ready-to-go for Apache Forrest hosted plugins. Helps with keeping the plugin docs consistent. (The need for skinconf.xml will probably go away with the new Dispatcher.) Fix whitespace in pluginTemplate files and existing plugins. Helps to use diff to keep consistent config. xdocs/images should be in documentation/resources/images site.xml needs to be consistent and remove any unneccessary files for xdocs. Tidy up the pluginTempate/status.xml -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (FOR-1166) Search Button is misplaced to the right in some browsers - Pelt Theme
[ https://issues.apache.org/jira/browse/FOR-1166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12868942#action_12868942 ] Tim Williams commented on FOR-1166: --- Chrome on Mac OS X Snow Leopard is terribly far right. Search Button is misplaced to the right in some browsers - Pelt Theme - Key: FOR-1166 URL: https://issues.apache.org/jira/browse/FOR-1166 Project: Forrest Issue Type: Bug Components: Plugin: internal.dispatcher, Plugin: themes.core Affects Versions: 0.9-dev Reporter: Gavin Fix For: 0.9-dev Attachments: 090512-234506-forrest.zones.apache.org-2778316.zip The 'Search' Button used with the 'Search the site with ...' Feature is not correctly situated in Firefox on Linux machines. It is way off to the right, making the site pages horizontally scroll apart from it being ugly. Interestingly, it looks fine in Firefox on Windows. Also looks good in IE7 and Google Chrome on Windows. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: svn commit: r945269 - in /forrest/trunk/whiteboard/plugins/org.apache.forrest.plugin.internal.dispatcher/src: cocoon-2.2-block/src/main/resources/COB-INF/ cocoon-2.2-block/src/main/resources/META
Hi Thorsten, is this working for you locally? I noticed the
Forrestbot failure just now and I'm also failing locally (with a NPE)
on a dispatcher sample site. Was thinking it might be related but
don't see anything obvious in here...
--tim
On Mon, May 17, 2010 at 1:42 PM, thors...@apache.org wrote:
Author: thorsten
Date: Mon May 17 17:42:05 2010
New Revision: 945269
URL: http://svn.apache.org/viewvc?rev=945269view=rev
Log:
FOR-1194 Fixing utf-8 compability by forcing to use UTF-8 in every step
Modified:
forrest/trunk/whiteboard/plugins/org.apache.forrest.plugin.internal.dispatcher/src/cocoon-2.2-block/src/main/resources/COB-INF/sitemap.xmap
forrest/trunk/whiteboard/plugins/org.apache.forrest.plugin.internal.dispatcher/src/cocoon-2.2-block/src/main/resources/META-INF/cocoon/avalon/dispatcher-sitemapcomponents.xconf
forrest/trunk/whiteboard/plugins/org.apache.forrest.plugin.internal.dispatcher/src/java/org/apache/forrest/dispatcher/impl/XSLContract.java
forrest/trunk/whiteboard/plugins/org.apache.forrest.plugin.internal.dispatcher/src/java/org/apache/forrest/dispatcher/impl/helper/XSLContractHelper.java
forrest/trunk/whiteboard/plugins/org.apache.forrest.plugin.internal.dispatcher/src/java/org/apache/forrest/dispatcher/transformation/DispatcherTransformer.java
forrest/trunk/whiteboard/plugins/org.apache.forrest.plugin.internal.dispatcher/src/java/org/apache/forrest/dispatcher/transformation/DispatcherWrapperTransformer.java
Modified:
forrest/trunk/whiteboard/plugins/org.apache.forrest.plugin.internal.dispatcher/src/cocoon-2.2-block/src/main/resources/COB-INF/sitemap.xmap
URL:
http://svn.apache.org/viewvc/forrest/trunk/whiteboard/plugins/org.apache.forrest.plugin.internal.dispatcher/src/cocoon-2.2-block/src/main/resources/COB-INF/sitemap.xmap?rev=945269r1=945268r2=945269view=diff
==
---
forrest/trunk/whiteboard/plugins/org.apache.forrest.plugin.internal.dispatcher/src/cocoon-2.2-block/src/main/resources/COB-INF/sitemap.xmap
(original)
+++
forrest/trunk/whiteboard/plugins/org.apache.forrest.plugin.internal.dispatcher/src/cocoon-2.2-block/src/main/resources/COB-INF/sitemap.xmap
Mon May 17 17:42:05 2010
@@ -22,7 +22,7 @@ xmlns:map=http://apache.org/cocoon/site
map:pipeline id=lm
map:match pattern=locationmap.xml
map:generate src=locationmap.xml /
- map:serialize type=xml /
+ map:serialize/
/map:match
/map:pipeline
map:pipeline id=dispatcher
@@ -61,7 +61,7 @@ xmlns:map=http://apache.org/cocoon/site
/map:transform
map:transform src=lm://hooks-to-fo.xsl /
map:transform src=lm://strip-dispatcher-remains-fo.xsl /
- map:serialize type=xml /
+ map:serialize/
/map:match
map:match pattern=**.prepare.dispatcher.css
map:generate src=lm://resolve.structurer.{1} type=jx
@@ -93,11 +93,11 @@ xmlns:map=http://apache.org/cocoon/site
map:act type=locale
map:match pattern=resolve.structurer.**
map:generate src=lm://resolve.structurer.{1} /
- map:serialize type=xml /
+ map:serialize/
/map:match
map:match pattern=resolve.contract.*.**
map:generate src={lm:resolve.contract.{1}.{2}} /
- map:serialize type=xml /
+ map:serialize/
/map:match
map:match pattern=prepare.contract.*.**
map:generate src={lm:resolve.contract.{1}.{2}} /
@@ -105,7 +105,7 @@ xmlns:map=http://apache.org/cocoon/site
map:transform type=i18n
map:parameter name=locale value={../locale} /
/map:transform
- map:serialize type=xml /
+ map:serialize/
/map:match
/map:act
/map:pipeline
@@ -116,7 +116,7 @@ xmlns:map=http://apache.org/cocoon/site
map:match pattern=prepare.panels.**
map:generate src={lm:resolve.panels.{1}} /
map:transform src={lm:root-strip.xsl} /
- map:serialize type=xml /
+ map:serialize/
/map:match
/map:pipeline
map:pipeline
@@ -126,7 +126,7 @@ xmlns:map=http://apache.org/cocoon/site
map:parameter name=path value={1}.html /
map:parameter name=theme value={global:dispatcher.theme} /
/map:transform
- map:serialize type=xml /
+ map:serialize/
/map:match
/map:pipeline
map:pipeline id=resources
Modified:
forrest/trunk/whiteboard/plugins/org.apache.forrest.plugin.internal.dispatcher/src/cocoon-2.2-block/src/main/resources/META-INF/cocoon/avalon/dispatcher-sitemapcomponents.xconf
URL:
http://svn.apache.org/viewvc/forrest/trunk/whiteboard/plugins/org.apache.forrest.plugin.internal.dispatcher/src/cocoon-2.2-block/src/main/resources/META-INF/cocoon/avalon/dispatcher-sitemapcomponents.xconf?rev=945269r1=945268r2=945269view=diff
[jira] Updated: (FOR-1102) Odt plugin does not manage tables correctly
[ https://issues.apache.org/jira/browse/FOR-1102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Williams updated FOR-1102: -- Fix Version/s: 0.10 (was: 0.9-dev) Deferring til next release. Odt plugin does not manage tables correctly --- Key: FOR-1102 URL: https://issues.apache.org/jira/browse/FOR-1102 Project: Forrest Issue Type: Bug Components: Plugin: input.odt Affects Versions: 0.9-dev Reporter: Cyriaque Dupoirieux Fix For: 0.10 The intermediate format generated for tables with the Odt input plugin is inherited from the org.apache.forrest.plugin.input.odt/resources/stylesheets/common/odt_to_xhtml.xsl style sheet and is far from Xdoc format. The genereted HTML page is a table because HTML tags are correct but the table layout is not applied. Something like the following is generated as intermdiate format : table class=Tableau1 colgroup col class=Tableau1_A/ col class=Tableau1_B/ col class=Tableau1_C/ col class=Tableau1_D/ /colgroup tbody tr td class=Tableau1_A1 pstrongemJeu/em/strong /p /td td class=Tableau1_A1 pstrongemEmulateur/em/strong/p /td td class=Tableau1_A1 pstrongemEtat/em/strong/p /td td class=Tableau1_A1 pstrongemCommentaires/em/strong/p /td /tr tr td class=Tableau1_A1 pUltima I/p /td td class=Tableau1_A1 plink href=http://sourceforge.net/projects/ultima-java/; target=_blankultima-java/link/p /td td class=Tableau1_A1 pInachevé/p /td td class=Tableau1_A1 pEmulateur java/p /td /tr /tbody /table Furthermore, if used with the pdf plugin the following error occurs : ERROR - Ignoring property: number-columns-repeated=NaN (No conversion defined NaN; property:'number-columns-repeated') WARN - Mismatch: table-body (http://www.w3.org/1999/XSL/Format) vs. flow (http://www.w3.org/1999/XSL/Format) WARN - Mismatch: table-body (http://www.w3.org/1999/XSL/Format) vs. page-sequence (http://www.w3.org/1999/XSL/Format) WARN - Mismatch: table-body (http://www.w3.org/1999/XSL/Format) vs. root (http://www.w3.org/1999/XSL/Format) I think it would be simple to correct this, my problem is do we have to update the common style sheet or is it better to correct the odt-to-forrest-xhtml.xsl ? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (FOR-210) whole-site html and pdf: broken link faq, broken image links
[ https://issues.apache.org/jira/browse/FOR-210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Williams updated FOR-210: - Fix Version/s: 0.10 (was: 0.9-dev) whole-site html and pdf: broken link faq, broken image links Key: FOR-210 URL: https://issues.apache.org/jira/browse/FOR-210 Project: Forrest Issue Type: Bug Components: Core operations Affects Versions: 0.6 Reporter: David Crossley Fix For: 0.10 The fresh-site build from 'forrest seed site' reports some failures for faq.html and various missing images. Wonder if sitemap issue? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (FOR-731) empty linkmap.html document, side-effect of workaround to FOR-675
[ https://issues.apache.org/jira/browse/FOR-731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Williams updated FOR-731: - Fix Version/s: 0.10 (was: 0.9-dev) empty linkmap.html document, side-effect of workaround to FOR-675 - Key: FOR-731 URL: https://issues.apache.org/jira/browse/FOR-731 Project: Forrest Issue Type: Bug Components: Core operations Affects Versions: 0.8 Reporter: David Crossley Priority: Minor Fix For: 0.10 The main/webapp/resources/stylesheets/linkmap-to-document.xsl has a workaround for a side-effect to the of the workaround for issue FOR-675. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (FOR-985) the plugins 'test' target does not local deploy its required plugins
[ https://issues.apache.org/jira/browse/FOR-985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12867977#action_12867977 ] Tim Williams commented on FOR-985: -- If I understand it, it's still busted for me: $FORREST_HOME/main/build.sh clean $FORREST_HOME/main/build.sh $FORREST_HOME/plugins/org.apache.forrest.plugin.input.PhotoGallery/ant clean $FORREST_HOME/plugins/org.apache.forrest.plugin.input.PhotoGallery/ant test The todo and changes resources of the dependent projectInfo plugin are broken. Is that what this issue is about? the plugins 'test' target does not local deploy its required plugins Key: FOR-985 URL: https://issues.apache.org/jira/browse/FOR-985 Project: Forrest Issue Type: Bug Components: Plugins (general issues) Affects Versions: 0.8, 0.9-dev Reporter: David Crossley Fix For: 0.9-dev For some reason our plugin 'test' Ant target only does a local deploy of the actual plugin that it is tesing and not the other plugins that are required by this plugin. See thread: plugins 'test' target April 13 when testing RC1. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (FOR-721) entries without labels in site.xml are now being crawled and generated
[ https://issues.apache.org/jira/browse/FOR-721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Williams updated FOR-721: - Fix Version/s: 0.10 (was: 0.9-dev) Pushing off unless someone wants to be an advocate for this one... entries without labels in site.xml are now being crawled and generated -- Key: FOR-721 URL: https://issues.apache.org/jira/browse/FOR-721 Project: Forrest Issue Type: Bug Components: Core operations Affects Versions: 0.8 Reporter: David Crossley Fix For: 0.10 In our forrest/site-author/content/xdocs/site.xml there are two entries without label attributes. Previously these documents were not being generated. Not sure if this change in behaviour is good or bad. Needs investigation. This is most likely a side-effect of the workaround for issue FOR-675 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[Travel Assistance] - Applications Open for ApacheCon NA 2010
FYI Forrest community... -- Forwarded message -- The Travel Assistance Committee is now taking in applications for those wanting to attend ApacheCon North America (NA) 2010, which is taking place between the 1st and 5th November in Atlanta. The Travel Assistance Committee is looking for people who would like to be able to attend ApacheCon, but who need some financial support in order to be able to get there. There are limited places available, and all applications will be scored on their individual merit. Financial assistance is available to cover travel to the event, either in part or in full, depending on circumstances. However, the support available for those attending only the barcamp is smaller than that for people attending the whole event. The Travel Assistance Committee aims to support all ApacheCons, and cross-project events, and so it may be prudent for those in Asia and the EU to wait for an event closer to them. More information can be found on the main Apache website at http://www.apache.org/travel/index.html - where you will also find a link to the online application and details for submitting. Applications for applying for travel assistance are now being accepted, and will close on the 7th July 2010. Good luck to all those that will apply. You are welcome to tweet, blog as appropriate. Regards, The Travel Assistance Committee.
[jira] Commented: (FOR-1069) add notices for US cryptographic export laws
[ https://issues.apache.org/jira/browse/FOR-1069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12868059#action_12868059 ] Tim Williams commented on FOR-1069: --- I've run: ../committers/tools/report_crypto_jars.pl | grep matches and didn't come up with anything particularly interesting beyond the jsch. The following packages also came up but some googling didn't turn up any immediate concerns. I've removed any Apache packages since, I think, they'd be covered under the same ECCN anyway... Binary file ./org/mortbay/http/handler/HTAccessHandler$HTAccess.class matches Binary file ./org/mortbay/util/Credential$Crypt.class matches Binary file ./org/mortbay/util/Credential.class matches Binary file ./org/mortbay/util/Password.class matches Binary file ./org/mortbay/util/UnixCrypt.class matches Binary file ./com/opensymphony/module/random/Rijndael.class matches Binary file ./com/opensymphony/module/random/Rijndael_Algorithm.class matches Binary file ./com/opensymphony/user/adapter/jrun/JRunUserManager.class matches Binary file ./org/mortbay/http/handler/HTAccessHandler$HTAccess.class matches Binary file ./org/mortbay/util/Credential$Crypt.class matches Binary file ./org/mortbay/util/Credential.class matches Binary file ./org/mortbay/util/Password.class matches Binary file ./org/mortbay/util/UnixCrypt.class matches Binary file ./fr/jayasoft/ivy/util/EncrytedProperties.class matches Binary file ./fr/jayasoft/ivy/util/StringUtils.class matches Binary file ./org/hsqldb/Server.class matches Were these ruled out as non-concerns last time? add notices for US cryptographic export laws Key: FOR-1069 URL: https://issues.apache.org/jira/browse/FOR-1069 Project: Forrest Issue Type: Task Components: Project administration Reporter: David Crossley Fix For: 0.9-dev We need to investigate our SVN and add crypto notices as explained at http://www.apache.org/licenses/exports/ and the legal-discuss mail list. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (FOR-591) MaxMemory needs increasing for large document sets: Memory Leak with XMLFileModule
[ https://issues.apache.org/jira/browse/FOR-591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Williams closed FOR-591. Resolution: Fixed Switched to the XPathXMLFileModule provided by a later version of Cocoon. MaxMemory needs increasing for large document sets: Memory Leak with XMLFileModule -- Key: FOR-591 URL: https://issues.apache.org/jira/browse/FOR-591 Project: Forrest Issue Type: Bug Components: Core operations Affects Versions: 0.7, 0.8 Reporter: Ross Gardler Priority: Blocker Fix For: 0.9-dev Since the docs restructuring for the 0.7 release it has become necessary to increase the maxmemory to be able to build the Forrest site. We gained three copies of the documents so suddenly have a large document set to trigger memory leakage issues. Possibly COCOON-1574 Memory Leak with XMLFileModule. Does someone have the tools to run some diagnostics? (NB maxmemory has been increased in our site-author/forrest.properties, if we resolve this issue it should be reduced again) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (FOR-572) run a memory profiler while forrest is operating
[ https://issues.apache.org/jira/browse/FOR-572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Williams updated FOR-572: - Fix Version/s: 0.10 (was: 0.9-dev) Honestly, I don't know what the real issue is here. The other one, FOR-591, had a concrete, testable problem but this one doesn't. It does have tons of good references though. I'm moving to 0.10 for now. If someone can articulate what the problem is, we can move it back. run a memory profiler while forrest is operating Key: FOR-572 URL: https://issues.apache.org/jira/browse/FOR-572 Project: Forrest Issue Type: Task Components: Core operations Affects Versions: 0.8 Reporter: David Crossley Priority: Critical Fix For: 0.10 Attachments: step1_profiling.patch We need to run a memory profiler while forrest is operating. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (FOR-1060) Use Cocoon XPathXMLFileModule rather than XMLFileModule
[ https://issues.apache.org/jira/browse/FOR-1060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Williams closed FOR-1060. - Assignee: Tim Williams Fix Version/s: 0.9-dev Resolution: Fixed Switched at r944615 I missed updating this because it didn't have a fix version. Use Cocoon XPathXMLFileModule rather than XMLFileModule --- Key: FOR-1060 URL: https://issues.apache.org/jira/browse/FOR-1060 Project: Forrest Issue Type: Task Components: Core operations Affects Versions: 0.9-dev Reporter: David Crossley Assignee: Tim Williams Fix For: 0.9-dev XMLFileModule has issues (e.g. see FOR-591 and COCOON-1574). Ralph Goers has implemented XPathXMLFileModule. See discussion in COCOON-1574. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (FOR-675) upgrading to commons-jxpath-1.2.jar causes failures with linkrewriter protocols site: etc.
[ https://issues.apache.org/jira/browse/FOR-675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Williams updated FOR-675: - Fix Version/s: 0.10 (was: 0.9-dev) Workaround has been in place for a long time, moving to .10 upgrading to commons-jxpath-1.2.jar causes failures with linkrewriter protocols site: etc. -- Key: FOR-675 URL: https://issues.apache.org/jira/browse/FOR-675 Project: Forrest Issue Type: Bug Components: Core operations Affects Versions: 0.7, 0.8 Reporter: David Crossley Fix For: 0.10 upgrading from commons-jxpath-20030909.jar to commons-jxpath-1.2.jar causes failures with linkrewriter protocols site: etc. This happens in both modes: 'forret run' and 'forrest'. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (FOR-986) Dispatcher war fails to build if no skinconf.xml is in place
[ https://issues.apache.org/jira/browse/FOR-986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12861387#action_12861387 ] Tim Williams commented on FOR-986: -- I started about resolving this as it seemed easy enough. The obvious solution is to only attempt loading it if it's not a dispatcher site, but since dispatcher is currently a plugin, it seems weird checkin for it in the core build. Seems to me we've got options: 1) If skinconf isnt' there, don't complain in any case. This would break any non-dispatcher sites but since we include it in most seeds, it's only likely to occur in cases where folks know what they're doing (ie. they explicitly deleted the skinconf). 2) Check if it's a dispatcher enabled site and, if so, don't complain about it missing. This would violate a separation of concerns between core-plugins and, generally, be dirty. 3) Punt until we figure out how dispatcher lands in core. A valid workaround exists and the problem has to be actively caused (by deleting skinconf). Thoughts? Dispatcher war fails to build if no skinconf.xml is in place Key: FOR-986 URL: https://issues.apache.org/jira/browse/FOR-986 Project: Forrest Issue Type: Bug Components: Plugin: internal.dispatcher Affects Versions: 0.8 Reporter: Ross Gardler Priority: Critical Fix For: 0.9-dev A dispatcher based site does not need a skinconf.xml file. However, if one is not present then the forrest war target fails with: BUILD FAILED C:\projects\apache-forrest-0.8\main\targets\webapp.xml:48: The following error occurred while executing this line: C:\projects\apache-forrest-0.8\main\forrest.build.xml:256: input file C:\projects\apache-forrest-0.8\main\webapp\skinconf.xml does not exist To work around this issue just put a skinconf.xml in place -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (FOR-1073) link elements with no href are created by html-to-document.xsl for a/name
[ https://issues.apache.org/jira/browse/FOR-1073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12861528#action_12861528 ] Tim Williams commented on FOR-1073: --- Can someone provide some instructions to recreate? Based on the description, I thought I might be able to simply open up an HTML source file (e.g. embedded_html.html), add an a name=, recreate the site and see an empty @href being created. I did this but observed no undesirable behavior (ie. the a name was propagated through as expected without an @href attribute. Thanks link elements with no href are created by html-to-document.xsl for a/name - Key: FOR-1073 URL: https://issues.apache.org/jira/browse/FOR-1073 Project: Forrest Issue Type: Bug Components: Core operations Affects Versions: 0.9-dev Reporter: David Crossley Fix For: 0.9-dev In FOR-1072 Jeremias said: Filtered out link elements with no href (which are created by html-to-document.xsl for a name=...). Forrest 0.7 didn't generate them as links at all but trunk does. Maybe that's wrong in the first place. There was also a mention of it previously on the dev list surrounding the recent FOP update branch work. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Merging back the dispatcher
On Mon, Apr 26, 2010 at 5:51 AM, Cyriaque Dupoirieux cyriaque.dupoiri...@pco-innovation.com wrote: le 22/04/2010 12:24 Ross Gardler a écrit : On 22/04/2010 00:54, Tim Williams wrote: On Mon, Dec 7, 2009 at 6:19 PM, Tim Williamswilliam...@gmail.com wrote: On Sun, Dec 6, 2009 at 9:38 PM, David Crossleycross...@apache.org wrote: Tim Williams wrote: reason I ask, is that we have FOR-1198 and FOR-796 both as blockers No such issue. Rather FOR-1108 and FOR-796. Arghh, typo, Thanks David. So, are we leaving dispatcher in the whiteboard for now? Hate to be a nag, but... are we leaving dispatcher in the whiteboard for the 0.9 release? It's complicated b/c we have [at least] two things working at odds here: 1) dispatcher has come to be in popular use despite its status and 2) being in the whiteboard, it wouldn't make it in the actual release. So, thoughts? I've wanted dispatcher in core since the 0.8 release for this very reason. However, now I'm only an observer here I'll refrain from arguing for or against, just settle with pointing out that I think it would be a mistake to leave it out of 0.9 unless it were to delay the release unreasonably (ahem). If it doesn't go in I would want to see a 0.10 within months with dispatcher in. I agree with you Ross, I think forrest needs a new release to make it clear that forrest is not dead... But we should also think about a R0.10 planned ASAP. Well, if the dispatcher is all that changed in such a release, we could do a 0.91 afterwards. I think there's another consideration that I didn't mention too. I feel irresponsible releasing software that we can't support and I'm concerned that this would be the case with the dispatcher. I have a difficult enough time now digging up Cocoon knowledge when questions come across but with dispatcher-related ones I have no clue. Maybe it's an unfounded concern, I dunno... --tim
[jira] Commented: (FOR-644) code-style cleanup for xml files
[ https://issues.apache.org/jira/browse/FOR-644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12861070#action_12861070 ] Tim Williams commented on FOR-644: -- It seems that this was done before the 0.8 release, is this just a house-keeping task that needs to be done prior to each release (e.g. in the same sense as license-checking)? code-style cleanup for xml files Key: FOR-644 URL: https://issues.apache.org/jira/browse/FOR-644 Project: Forrest Issue Type: Task Components: Other Affects Versions: 0.8, 0.9-dev Reporter: David Crossley Fix For: 0.9-dev We have much inconsistent whitespace in all of our files. This is known to cause trouble in a collaborative environment. See discussion at: http://marc.theaimsgroup.com/?t=11245090111 and http://marc.theaimsgroup.com/?t=11249561882 and various linked discussions. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (FOR-1177) where does forrest use Rhino
[ https://issues.apache.org/jira/browse/FOR-1177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Williams closed FOR-1177. - Resolution: Fixed I feel pretty good that this latest update to the Notices file complies with the MPL license. where does forrest use Rhino Key: FOR-1177 URL: https://issues.apache.org/jira/browse/FOR-1177 Project: Forrest Issue Type: Task Components: Other Reporter: David Crossley Assignee: Tim Williams Priority: Blocker Fix For: 0.9-dev While assessing the license situation for FOR-855 and FOR-857 ... one of the difficult cases is Rhino. Does someone know why we use Rhino and which part of Forrest? Did it just come along by accident with our addition of Cocoon, or is it actually being used? See: lib/core/rhino-1.6R2.jar and prior to that lib/core/rhino-1.6R1.jar -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Merging back the dispatcher
On Mon, Dec 7, 2009 at 6:19 PM, Tim Williams william...@gmail.com wrote: On Sun, Dec 6, 2009 at 9:38 PM, David Crossley cross...@apache.org wrote: Tim Williams wrote: reason I ask, is that we have FOR-1198 and FOR-796 both as blockers No such issue. Rather FOR-1108 and FOR-796. Arghh, typo, Thanks David. So, are we leaving dispatcher in the whiteboard for now? Hate to be a nag, but... are we leaving dispatcher in the whiteboard for the 0.9 release? It's complicated b/c we have [at least] two things working at odds here: 1) dispatcher has come to be in popular use despite its status and 2) being in the whiteboard, it wouldn't make it in the actual release. So, thoughts? --tim
