[jira] Commented: (FOR-392) deploy of deleted files

[ http://issues.apache.org/jira/browse/FOR-392?page=comments#action_12358477 ] Dave Brondsema commented on FOR-392: Ant has a task, but that's only for local copies. I guess it would be hard to implement for all types of deploys. I had origi

Re: problem with docs at forrest.apache.org/docs/dev/

lease the plugins with each major version. When that becomes insufficient (e.g. if a plugin takes off and makes its own major changes & releases within one forrest release), we can tackle it again. I think in that case, the plugin should be documented seperately from the main forrest docs and it can say what versions of forrest it is compatible with. -- Dave Brondsema : [EMAIL PROTECTED] http://www.brondsema.net : personal http://www.splike.com : programming http://csx.calvin.edu : student org

Re: problem with docs at forrest.apache.org/docs/dev/

David Crossley wrote: David Crossley wrote: David Crossley wrote: David Crossley wrote: Dave Brondsema wrote: /docs/dev/ nested below /docs/ seems weird. I think it would be better to host the current stable release at a url like: /docs/0.7/. This would also permit us to keep documentation for

Re: svn commit: r158748 - forrest/trunk/docs-author/skinconf.xml

David Crossley wrote: Dave Brondsema wrote: /docs/ doesn't work if these docs are standalone (e.g on my machine). Yeah, sorry. I knew it would make a broken link for local docs, but thought that it was more important to get the website happening at this stage. Good point. Now that I think

Re: merging separate sets of generated docs, default tabs

David Crossley wrote: Dave Brondsema wrote: Ok. What about href="/docs"? I think because it is a 'href' it would keep it from failing the build, and it would still be relative. That should work. I woder why we didn't think of that before. Maybe it was all getting confu

Re: svn commit: r158748 - forrest/trunk/docs-author/skinconf.xml

t/trunk/docs-author/skinconf.xml Wed Mar 23 00:21:34 2005 @@ -111,6 +111,21 @@ + + v0.7 + +This is documentation for the current release v0.7 + + /docs/ + /docs/ doesn't work if these docs are standalone (e.g on my machine). -- Dave Brondsema : [EMAIL PROTECTED] http

Re: better use of Jira for Forrest

Quoting Ross Gardler <[EMAIL PROTECTED]>: > Dave Brondsema wrote: > > Quoting David Crossley <[EMAIL PROTECTED]>: > > > > > >>Done. That clarifies the Roadmap. > >> > >>Do any people out in the Forrest dev community > >>

Re: better use of Jira for Forrest

ich are not worth spending time on. The problem, of course, would be to coordinate such a day, especially given our geographical spread. It doesn't have to be simultaneous work, though. We could even do a week of bug-squashing. -- Dave Brondsema : [EMAIL PROTECTED] http://www.brondsema

Re: [JIRA] Created: (FOR-470) docs and fresh-site samples for "raw content" need update

est way to answer this would be to update the documentation instead of just replying :-) -- Dave Brondsema : [EMAIL PROTECTED] http://www.splike.com : programming http://csx.calvin.edu : student org http://www.brondsema.net : personal signature.asc Description: OpenPGP digital signature

Re: better use of Jira for Forrest

n. Good idea. I just tested by moving 0.7 to 0.7-dev ... hooray. I will do that over the weekend unless someone stops me. --David +1 Good ideas, guys. -- Dave Brondsema : [EMAIL PROTECTED] http://www.splike.com : programming http://csx.calvin.edu : student org http://www.brondsema.net : personal signa

Re: problem with docs at forrest.apache.org/docs/dev/

unless of course the issues in question is new to the dev version). That will keep all of our archived links good. -- Dave Brondsema : [EMAIL PROTECTED] http://www.splike.com : programming http://csx.calvin.edu : student org http://www.brondsema.net : personal signature.asc Description: OpenPGP digital signature

Re: planning for 0.7 release

(like plugin documentation; and maybe plugin versioning) seem like they are very important to get done before the release. Ross has done a lot on the plugins, but even if we help, what if we don't have these done before the release date? What would you guys think of postponing the release un

Re: merging separate sets of generated docs, default tabs (Was: svn commit: r157791)

content/xdocs/tabs.xml?view=diff&r1=157778&r2=157779 == --- forrest/trunk/docs-author/content/xdocs/tabs.xml (original) +++ forrest/trunk/docs-author/content/xdocs/tabs.xml Wed Mar 16 09:46:03 2005 @@ -36,8 +36,6 @@ - -

Re: Writer Output plugin

ou mentioned on [EMAIL PROTECTED] would be good to get in SVN even if they aren't complete. If you put them in the whiteboard, then we know that they aren't finished, but others can see them and help. -- Dave Brondsema : [EMAIL PROTECTED] http://www.splike.com : programming http://csx.calv

Re: Hugo ? - Open Writer Plugin.

Ferdinand Soethe wrote: Dave Brondsema wrote: DB> The OO.o plugin does not properly handle headers, so you may encounter DB> other weird issues too. I think things work best if you have an ordered DB> heirarchy of headings, like this: DB> heading1 DB> heading2 DB> headin

Re: [pmc] JIRA admins

David Crossley wrote: Dave Brondsema wrote: David Crossley wrote: What do you want to add? I can do it. Plugin: htmlArea Plugin: wiki Done. --David Also, please: Plugin: pdf-output -- Dave Brondsema : [EMAIL PROTECTED] http://www.splike.com : programming http://csx.calvin.edu : student org http

Re: [pmc] JIRA admins

David Crossley wrote: Dave Brondsema wrote: Can the cocoondev JIRA admin set up all PMC members to have administrative rights on Forrest? Not until we move it to the ASF infrastructure. I'd like to add some more component categories for our plugins right now. What do you want to add? I c

[pmc] JIRA admins

Can the cocoondev JIRA admin set up all PMC members to have administrative rights on Forrest? I'd like to add some more component categories for our plugins right now. -- Dave Brondsema : [EMAIL PROTECTED] http://www.splike.com : programming http://csx.calvin.edu : student org

Re: Hugo ? - Open Writer Plugin.

nter other weird issues too. I think things work best if you have an ordered heirarchy of headings, like this: heading1 heading2 heading2 heading2 heading3 heading2 heading1 heading2 and not jump from 1 to 3 for example because the stylesheet doesn't know how to create proper s out of that. --

Re: planning for 0.7 release

will. +1 I propose that we move it forward a few days - how about 2005-05-22 ? We can still celebrate NKB. That's a few months, by my calendar. How about 2005-03-29? -- Dave Brondsema : [EMAIL PROTECTED] http://www.splike.com : programming http://csx.calvin.edu : student org http://ww

Re: [heads-up] forrest website updated

Quoting Ross Gardler <[EMAIL PROTECTED]>: > David Crossley wrote: > > Dave Brondsema wrote: > > > >>Because 0.6 docs are not split, things are pretty confusing. I > >>speculate it might be worth it to get a 0.7 release out the door > >>prima

Re: [heads-up] forrest website updated

rectory. That adds the 0.7-dev technical docs. 4) 'svn commit' 5) the cron job will do 'svn update' on the server. Alternatively, you can do it manually ssh cvs.apache.org; cd /www/forrest.apache.org; svn update Anyway, would someone with fresh eyes please look at the site. --D

Re: svn commit: r154167 - forrest/trunk/site-author/content/xdocs/site.xml

wierd. In general (i.e. 0.7+) there will be a build.xml for each version and therefore none at f.a.org/build.html So this sort of thing is only temporary. Once 0.7 is released, 0.6 docs won't be online and we can remove this. -- Dave Brondsema : [EMAIL PROTECTED] http://www.splike.com :

Re: running multiple forrestbots

David Crossley wrote: Dave Brondsema wrote: David Crossley wrote: Dave Brondsema wrote: David Crossley wrote: I suddenly realised the issue with "cocoon-trunk". It needs to run its 'build docs' before running 'forrest'. It generates some extra source documentation b

Re: [VOTE] Forrest Project Guidelines

Dave Brondsema wrote: (I'm making this a new thread, so it doesn't get lost... -Dave) I reckon that the draft guidelines are now ready. The ASF Board Resolution that created the Forrest project http://www.apache.org/foundation/records/minutes/2004/board_minutes_2004_05_26.txt as

[VOTE] Forrest Project Guidelines

(I'm making this a new thread, so it doesn't get lost... -Dave) I reckon that the draft guidelines are now ready. The ASF Board Resolution that created the Forrest project http://www.apache.org/foundation/records/minutes/2004/board_minutes_2004_05_26.txt assigned our PMC the task of creating

Re: [Proposal] forrestbot at apache.org

David Crossley wrote: Dave Brondsema wrote: David Crossley wrote: I suddenly realised the issue with "cocoon-trunk". It needs to run its 'build docs' before running 'forrest'. It generates some extra source documentation before forrest starts. There is a global para

Re: [Proposal] forrestbot at apache.org

ocoon-trunk builds running, so i am currently finding a way to avoid that. --David -- Dave Brondsema : [EMAIL PROTECTED] http://www.splike.com : programming http://csx.calvin.edu : student org http://www.brondsema.net : personal signature.asc Description: OpenPGP digital signature

Re: site: link construct broken in aggragated PDFs?

ue FOR-147). Unfortunately there's no easy fix. -- Dave Brondsema : [EMAIL PROTECTED] http://www.splike.com : programming http://csx.calvin.edu : student org http://www.brondsema.net : personal signature.asc Description: OpenPGP digital signature

Re: [OT] Re: Enhancing status.xml

#x27;ll make it optional for people who don't want reserved filenames bothering them. -- Dave Brondsema : [EMAIL PROTECTED] http://www.splike.com : programming http://csx.calvin.edu : student org http://www.brondsema.net : personal signature.asc Description: OpenPGP digital signature

Re: Enhancing status.xml

). What your describing seems like you might as well just use a real issue tracker. -- Dave Brondsema : [EMAIL PROTECTED] http://www.splike.com : programming http://csx.calvin.edu : student org http://www.brondsema.net : personal signature.asc Description: OpenPGP digital signature

finishing the site/docs split

I hope to start again on those sometime, but if anyone wants to give it a shot, please go ahead and try. -- Dave Brondsema : [EMAIL PROTECTED] http://www.splike.com : programming http://csx.calvin.edu : student org http://www.brondsema.net : personal signature.asc Description: OpenPGP digital signature

Re: SVN Inconsitent Line Endings

have to comma-seperate your include list. > > Ayone got any ideas? > I'd say we should find out why the HTML is generated with inconsistent line endings in the first place. -- Dave Brondsema : [EMAIL PROTECTED] http://www.brondsema.net : personal http://www.splike.com : programming http://csx.calvin.edu : student org

Re: strange error looking for skins in wrong place

hat is wrong? > > Aha! That error message was the sound of Forrest stumbling over > the old sitemap.xmap that Cocoon uses for its documentation as webapp. > This reminds me that sooner or later we should start documenting a "contract" of what a project's sitemap.xm