Nabble - Forrest

[jira] Subscription: FOR-open-with-patch

2009-11-29T04:30:22Z

Issue Subscription
Filter: FOR-open-with-patch (11 issues)
Subscriber: rgardler

Key Summary
FOR-412 use CSS for displaying list of Changes
https://issues.apache.org/jira/browse/FOR-412
FOR-752 Forrestbot "build" workstage creates spurious "build/webapp/WEB-INF/logs" directory
https://issues.apache.org/jira/browse/FOR-752
FOR-211 whole-site html and pdf: broken ext links
https://issues.apache.org/jira/browse/FOR-211
FOR-652 CSS Style Sheets need cleanup, optimization and better naming of elements
https://issues.apache.org/jira/browse/FOR-652
FOR-969 Add sensible site navigation in DOAP plugin
https://issues.apache.org/jira/browse/FOR-969
FOR-355 Improved PDF configurability (e.g., TOC, Page Numbers, logo)
https://issues.apache.org/jira/browse/FOR-355
FOR-998 [PATCH] Resolve empty cells.
https://issues.apache.org/jira/browse/FOR-998
FOR-311 OOo Headings bug causes Forrest to fail
https://issues.apache.org/jira/browse/FOR-311
FOR-934 i18n language override menu
https://issues.apache.org/jira/browse/FOR-934
FOR-280 gather index terms from documents to create index page with links
https://issues.apache.org/jira/browse/FOR-280
FOR-795 Navigation bars for easy access in long documents
https://issues.apache.org/jira/browse/FOR-795

From forum: Apache Forrest - Dev

Re: [Reminder] our forrestbot on zone server not running

2009-11-28T21:03:27Z

David Crossley wrote:
> Our forrestbot on the zone server is not running at the moment.
>
> See https://issues.apache.org/jira/browse/FOR-1179
> and the replies to this dev list.
>
> Other than monitor the infrastructure mail lists and #asfinfra
> and perhaps help, there is not much we can do.
>
> So be aware that it will not be alerting us to any issues.

The zone server, and hence our forrestbot, is back up.

-David

From forum: Apache Forrest - Dev

Re: [jira] Commented: (FOR-1179) zone server machine going to be updated OS soon: re-establish the forrestbot instance

2009-11-28T21:02:34Z

David Crossley wrote:

> Brian M Dube wrote:
> > David Crossley (JIRA) wrote:
> > > The zone machine update is not scheduled, as far as i know (i just heard it being talked about on one of the Infra lists).
> >
> > Is this happening? I haven't been able to access helios for at least a
> > day.
>
> I have not heard any further talk of this on the various infra mail lists.
>
> The Nagios monitoring
> http://apache.org/dev/#status
> shows "helios" as down, with the comment "nobody home".
>
> I don't understand, but it might be a reference to the
> lack of Solaris admins, which is one of the reasons for moving
> the zones server.

The "helios" machine is back up again, after a disk Array reboot.

-David

From forum: Apache Forrest - Dev

[jira] Commented: (FOR-1183) Forrestbar search of Jira issues broken, perhaps changed Jira search syntax

2009-11-24T01:50:39Z

[ https://issues.apache.org/jira/browse/FOR-1183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781842#action_12781842 ]

Gavin commented on FOR-1183:
----------------------------

Just to add, this is likely not a ForrestBar problem/bug, but we can work around it in ForrestBar if we wanted to, or wait for Atlassian to fix the issue (which would then be compounded by the fact we would have to wait for infra to then upgrade to include that fix)

> Forrestbar search of Jira issues broken, perhaps changed Jira search syntax
> ---------------------------------------------------------------------------
>
> Key: FOR-1183
> URL: https://issues.apache.org/jira/browse/FOR-1183
> Project: Forrest
> Issue Type: Bug
> Components: Tool: Forrestbar
> Reporter: David Crossley
>
> When searching our Jira Issues using Forrestbar, the upgraded ASF Jira now seems to intercede with "smart query". However, it seems to lose our search terms, and just finds all Forrest issues. Perhaps the Jira search syntax has changed.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

From forum: Apache Forrest - Dev

[jira] Commented: (FOR-1183) Forrestbar search of Jira issues broken, perhaps changed Jira search syntax

2009-11-24T01:48:39Z

[ https://issues.apache.org/jira/browse/FOR-1183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781840#action_12781840 ]

Gavin commented on FOR-1183:
----------------------------

aha, nice find! - Have you tripped up the search on more than one word, or just 'jxpath' ?

If you escape the word like '/jxpath' in your search then the smart search works just fine and the correct 4 issues are filtered. So, we may have found a bug, at least, after some searching I couldnt find no mention of this being a reserved word.

(You can do all sorts of cool things like searching for 'my open issues' and it will do just that, rather than searching for that text.)

Anyway, I filed a bug report at Atlassian, so we'll see what they come back with.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

From forum: Apache Forrest - Dev

Re: Blocking Issues

2009-11-24T01:21:07Z

On Tue, Nov 24, 2009 at 3:33 AM, Ross Gardler <rgardler@...> wrote:

> 2009/11/24 David Crossley <crossley@...>:
>> Ross Gardler wrote:
>>> David Crossley wrote:
>>> > Ross Gardler wrote:
>>> >> David Crossley wrote:
>>> >> > Ross Gardler wrote:
>>> >> >> Tim Williams wrote:
>>> >> >> >
>>> >> >> > FOR-855 verify the license situation prior to each release
>>> >> >> > - housekeeping
>>> >> >>
>>> >> >> I believe Davids work with RAT fixes this issue.
>>> >> >
>>> >> > No it does not. There is much more to the job that that.
>>> >>
>>> >> I meant that running RAT shows all licence headers are in place. we
>>> >> still need to do the housekeeping work that is normal due diligence on
>>> >> a release, of course.
>>> >
>>> > I meant that FOR-855 has much more than just the license header situation.
>>> > I have been working on it steadily for a long time now, and there is more
>>> > to do.
>>>
>>> OK, I should have reviewed the issue. I have no opinion on whether
>>> this is a blocker or not. I assumed that previous releases were
>>> legally sound (which I believe they were since we voted them through).
>>
>> We have cut corners on previous releases. Our top-level LICENSE.txt file
>> is not in line with agreed ASF best practice. It is supposed to display
>> relevant licenses for supporting products.
>
> Hmm.... not good.
>
> I wonder if this has occured as things have crept into plugins.
> Perhaps each plugin should have a licence.txt file and the build
> system should merge them together at build time.
>
>> Also all supporting product licenses need to be systematically reviewed.
>> Since the last release some things have been haphazardly added to SVN.
>> Also last time we could easily have missed some.
>
> I've tried to review every commit for such things. I hope others have
> been doing the same to catch the ones I miss. I'm pretty sure that a
> review of licences is already in the release workflow - if not it
> should be, for the reasons you give.
>
>>> Tim indicated that this was "housekeeping" which I took to mean the
>>> normal due diligence on a release.
>>
>> Yes, but i marked it as Blocker (same process as i did for the previous
>> releases) because a release should not be rolled until the situation is
>> suitable.
>
> I'm not saying it is not a blocker, I'm agreeing it is part of the
> required housekeeping of a release. In other words we are in agreement
> ;-)

Sorry, I might have inadvertently caused this confusion with my
imprecise wording, "housekeeping," which seems to have unintentionally
trivialized it. I meant it as in "a necessary part of the release
process" as opposed to, say, a "bug".

>> I will plod along with FOR-855 and FOR-857 while other people
>> attend to other things.
>
> Thank you. I'd like to say I'd help, but to be honest I doubt I'll
> find the time.

I'm going out of town for a week for our Thanksgiving holidays here in
America, I'll pick this up when I get back...
Thanks,
--tim

From forum: Apache Forrest - Dev

Re: Blocking Issues

2009-11-24T00:33:02Z

2009/11/24 David Crossley <crossley@...>:

> Ross Gardler wrote:
>> David Crossley wrote:
>> > Ross Gardler wrote:
>> >> David Crossley wrote:
>> >> > Ross Gardler wrote:
>> >> >> Tim Williams wrote:
>> >> >> >
>> >> >> > FOR-855 verify the license situation prior to each release
>> >> >> > - housekeeping
>> >> >>
>> >> >> I believe Davids work with RAT fixes this issue.
>> >> >
>> >> > No it does not. There is much more to the job that that.
>> >>
>> >> I meant that running RAT shows all licence headers are in place. we
>> >> still need to do the housekeeping work that is normal due diligence on
>> >> a release, of course.
>> >
>> > I meant that FOR-855 has much more than just the license header situation.
>> > I have been working on it steadily for a long time now, and there is more
>> > to do.
>>
>> OK, I should have reviewed the issue. I have no opinion on whether
>> this is a blocker or not. I assumed that previous releases were
>> legally sound (which I believe they were since we voted them through).
>
> We have cut corners on previous releases. Our top-level LICENSE.txt file
> is not in line with agreed ASF best practice. It is supposed to display
> relevant licenses for supporting products.

Hmm.... not good.

I wonder if this has occured as things have crept into plugins.
Perhaps each plugin should have a licence.txt file and the build
system should merge them together at build time.

> Also all supporting product licenses need to be systematically reviewed.
> Since the last release some things have been haphazardly added to SVN.
> Also last time we could easily have missed some.

I've tried to review every commit for such things. I hope others have
been doing the same to catch the ones I miss. I'm pretty sure that a
review of licences is already in the release workflow - if not it
should be, for the reasons you give.

>> Tim indicated that this was "housekeeping" which I took to mean the
>> normal due diligence on a release.
>
> Yes, but i marked it as Blocker (same process as i did for the previous
> releases) because a release should not be rolled until the situation is
> suitable.

I'm not saying it is not a blocker, I'm agreeing it is part of the
required housekeeping of a release. In other words we are in agreement
;-)

> I will plod along with FOR-855 and FOR-857 while other people
> attend to other things.

Thank you. I'd like to say I'd help, but to be honest I doubt I'll
find the time.

Ross

From forum: Apache Forrest - Dev

[jira] Commented: (FOR-1184) using unreleased code for some supporting products

2009-11-23T19:28:39Z

[ https://issues.apache.org/jira/browse/FOR-1184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781759#action_12781759 ]

David Crossley commented on FOR-1184:
-------------------------------------

There are also some other unreleased jars for some other
supporting products ...

lib/core/cocoon-2.1.12-dev and blocks
lib/core/commons-jci-r306555.jar
lib/core/commons-jxpath-1.2-r329470.jar (beware FOR-675, but that might be fixed with c-2.1)
lib/core/jcs-1.2.5-dev-20050313.jar
lib/core/jtidy-04aug2000r7-dev.jar
lib/core/rhino-1.6R2.jar
lib/core/xml-commons-resolver-1.2-dev-r395116.jar (see FOR-889)
lib/endorsed/jakarta-bcel-20040329.jar
plugins/org.apache.forrest.plugin.output.pdf/lib/cocoon-fop-ng-impl-special-SNAPSHOT.jar

tools/eclipse/plugins/org.apache.forrest.repository.daisy/lib/commons-httpclient-2.0-rc2.jar
tools/forrestbot/webapp/lib/osuser-1.0-dev.jar
whiteboard/forrest2/core/tools/ivy/repository/apache/commons-httpclient/jars/commons-httpclient-3.1-alpha1.jar
whiteboard/plugins/org.apache.forrest.plugin.output.htmlArea/tools/htmlArea_3.0-rc1.zip
whiteboard/plugins/rtf-output/WEB-INF/lib/jfor-0.7.2rc1.jar

> using unreleased code for some supporting products
> --------------------------------------------------
>
> Key: FOR-1184
> URL: https://issues.apache.org/jira/browse/FOR-1184
> Project: Forrest
> Issue Type: Task
> Components: Other
> Affects Versions: 0.9-dev
> Reporter: David Crossley
> Fix For: 0.9-dev
>
>
> After the last release, an issue was brought to our attention about using unreleased code from other projects.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

From forum: Apache Forrest - Dev

[jira] Commented: (FOR-1184) using unreleased code for some supporting products

2009-11-23T19:22:52Z

[ https://issues.apache.org/jira/browse/FOR-1184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781758#action_12781758 ]

David Crossley commented on FOR-1184:
-------------------------------------

Here is the last part of the discussion:
Date: 2007-12-13
Subject: Re: Unreleased Coccon Code in Forrest 0.8
http://thread.gmane.org/gmane.text.xml.forrest.devel/25170/focus=25218

At least we are now using the cocoon-2.1 release branch, but still a
development version.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

From forum: Apache Forrest - Dev

[jira] Created: (FOR-1184) using unreleased code for some supporting products

2009-11-23T19:20:42Z

using unreleased code for some supporting products
--------------------------------------------------

Key: FOR-1184
URL: https://issues.apache.org/jira/browse/FOR-1184
Project: Forrest
Issue Type: Task
Components: Other
Affects Versions: 0.9-dev
Reporter: David Crossley
Fix For: 0.9-dev

After the last release, an issue was brought to our attention about using unreleased code from other projects.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

From forum: Apache Forrest - Dev

[jira] Reopened: (FOR-1183) Forrestbar search of Jira issues broken, perhaps changed Jira search syntax

2009-11-23T19:18:44Z

[ https://issues.apache.org/jira/browse/FOR-1183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Crossley reopened FOR-1183:
---------------------------------

Hmmm, found a search which exhibits the problem (so re-opening).

Use Forrestbar to do the following search in "JIRA Issues" ...
jxpath

Whereas the following search is okay ...
xpath

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

From forum: Apache Forrest - Dev

Re: Blocking Issues

2009-11-23T18:22:31Z

Ross Gardler wrote:

> David Crossley wrote:
> > Ross Gardler wrote:
> >> David Crossley wrote:
> >> > Ross Gardler wrote:
> >> >> Tim Williams wrote:
> >> >> >
> >> >> > FOR-855 verify the license situation prior to each release
> >> >> > - housekeeping
> >> >>
> >> >> I believe Davids work with RAT fixes this issue.
> >> >
> >> > No it does not. There is much more to the job that that.
> >>
> >> I meant that running RAT shows all licence headers are in place. we
> >> still need to do the housekeeping work that is normal due diligence on
> >> a release, of course.
> >
> > I meant that FOR-855 has much more than just the license header situation.
> > I have been working on it steadily for a long time now, and there is more
> > to do.
>
> OK, I should have reviewed the issue. I have no opinion on whether
> this is a blocker or not. I assumed that previous releases were
> legally sound (which I believe they were since we voted them through).

We have cut corners on previous releases. Our top-level LICENSE.txt file
is not in line with agreed ASF best practice. It is supposed to display
relevant licenses for supporting products.

Also all supporting product licenses need to be systematically reviewed.
Since the last release some things have been haphazardly added to SVN.
Also last time we could easily have missed some.

> Tim indicated that this was "housekeeping" which I took to mean the
> normal due diligence on a release.

Yes, but i marked it as Blocker (same process as i did for the previous
releases) because a release should not be rolled until the situation is
suitable.

I will plod along with FOR-855 and FOR-857 while other people
attend to other things.

-David

From forum: Apache Forrest - Dev

[jira] Closed: (FOR-1183) Forrestbar search of Jira issues broken, perhaps changed Jira search syntax

2009-11-23T16:16:39Z

[ https://issues.apache.org/jira/browse/FOR-1183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Crossley closed FOR-1183.
-------------------------------

Resolution: Fixed

I checked again, and yes can confirm that it now works. Something at the Jira end must have changed.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

From forum: Apache Forrest - Dev

[jira] Updated: (FOR-630) Forrest strategy and direction

2009-11-23T15:50:39Z

[ https://issues.apache.org/jira/browse/FOR-630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Crossley updated FOR-630:
-------------------------------

Priority: Major (was: Critical)

I disagree. I see many items that are still relevant. But don't need to be addressed at the moment.

Anyway, i reduced the Issue Priority.

> Forrest strategy and direction
> ------------------------------
>
> Key: FOR-630
> URL: https://issues.apache.org/jira/browse/FOR-630
> Project: Forrest
> Issue Type: Task
> Components: Other
> Reporter: Ross Gardler
>
> Topics for discussion gathered at ApacheCon EU 2005.
> WARNING: Only reply to the general theme of this
> topics list. Please create separate threads for
> each specific topic.
> Actually we should be using Jira for some of this.
> How about discussing on the mailing list, and
> putting summaries into Jira.
> I have the scraps of paper that Nicola Ken wrote.
> Photographs are in:
> http://svn.apache.org/repos/asf/forrest/events/apachecon-eu-2005
> Ross helped me to interpret some of the sqwiggles,
> but there are still some obscure parts (marked
> with #? below). The items are raw, i have not tried
> to explain any or add others.
> List of topics is in no particular order and
> it is not complete. We spent maybe 15 minutes
> brainstorming. We had a first quick pass at
> assigning some priority.
> I don't understand NKBs priority symbols.
> Anyway some items where marked with
> circle ... [C]
> square ... [S]
> Then we went straight on to the top topic:
> "configuration" and spent the rest of the day.
> --------------
> * Create lenya/forrest publication.
> * [C] Naming convention for "views".
> * Roadmap specifically for views.
> * [S] i18n support with locationmap.
> * Locationmap - what is needed to complete it.
> * [C] Configuration |=> apache #? arrow apache #?
> * TraversableSource ...
> * Source resolving for locationmap.
> * [C] How views are interacting with locationmap?
> * [S] Documentation mismatch. Docs are distributed in
> various places: site, plugins, seed.
> * Block documentation for Cocoon (/Forrest).
> * [C] Pre-processing plugins.
> * Flow of the plugin process.
> plugins - locationmap / flow #? this line obscure #?
> * Memory profiling.
> * Better use of Jira.
> * [S] XHTML2 transition.
> * [S] Live Forrest for Apache.
> (a configuration usecase)
> * [S] New skins for views.
> * Views ... body="true|false" head="true|false"
> * The *.ft files in a plugin (one-to-many).
> * Move into Java -> 0.9.5 or when needed. #? no idea what #?
>
> * [C] View / doctypes.
> (view in view)
> * [C] Content directory.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

From forum: Apache Forrest - Dev

RE: State of dispatcher?

2009-11-23T06:17:43Z

On Mon, 2009-11-23 at 15:18 +0100, Thorsten Scherler wrote:

> On Mon, 2009-11-23 at 19:15 +1000, Gavin wrote:
> ...
> > > I will try a dry-run merge now and see what is coming out.
> >
> > Ah, this would be good, thanks Thorsten.
> >
> > To be honest I lost track of where I was supposed to be working when doing
> > dispatcher stuff, so continued with
> >
> > /trunk/whiteboard/plugins/*dispatcher
> > /trunk/whiteboard/plugins/*themes
> >
> > It would be good to have all this stuff merged, then we can look at the
> > state of the merger and decide if it can go into the release.
>
> The following release have been done in the trunk against the dispatcher
> after the creation of the branch:

I mean revisions!

> 733422
> 734387
> 734405
> 734546
> 734605
> 773472
> 795708
> 816460
> 816466
>
> The above committs have to be re-done by hand after the merge, or?
>
> I did:
> cd forrest/trunk/whiteboard
> svn merge -r 700363:HEAD
> https://svn.apache.org/repos/asf/forrest/branches/dispatcher_rewrite
>
> I will try to merge the above revision with the trunk.

...with the merged trunk.

salu2

>
> salu2
>
> >
> > Thanks
> >
> > Gav...
> >
> >
> > >
> > > salu2
> > >
> > > > --tim
> > > --
> > > Thorsten Scherler <thorsten.at.apache.org>
> > > Open Source Java <consulting, training and solutions>
> > >
> > > Sociedad Andaluza para el Desarrollo de la Sociedad
> > > de la Información, S.A.U. (SADESI)
> > >
> > >
> > >
> > >
> > > No virus found in this incoming message.
> > > Checked by AVG - www.avg.com
> > > Version: 8.5.425 / Virus Database: 270.14.71/2510 - Release Date: 11/17/09
> > > 19:26:00
> >

--
Thorsten Scherler <thorsten.at.apache.org>
Open Source Java <consulting, training and solutions>

Sociedad Andaluza para el Desarrollo de la Sociedad
de la Información, S.A.U. (SADESI)

From forum: Apache Forrest - Dev

RE: State of dispatcher?

2009-11-23T06:15:32Z

On Mon, 2009-11-23 at 19:15 +1000, Gavin wrote:
...

> > I will try a dry-run merge now and see what is coming out.
>
> Ah, this would be good, thanks Thorsten.
>
> To be honest I lost track of where I was supposed to be working when doing
> dispatcher stuff, so continued with
>
> /trunk/whiteboard/plugins/*dispatcher
> /trunk/whiteboard/plugins/*themes
>
> It would be good to have all this stuff merged, then we can look at the
> state of the merger and decide if it can go into the release.

The following release have been done in the trunk against the dispatcher
after the creation of the branch:

733422
734387
734405
734546
734605
773472
795708
816460
816466

The above committs have to be re-done by hand after the merge, or?

I did:
cd forrest/trunk/whiteboard
svn merge -r 700363:HEAD
https://svn.apache.org/repos/asf/forrest/branches/dispatcher_rewrite

I will try to merge the above revision with the trunk.

salu2

>
> Thanks
>
> Gav...
>
>
> >
> > salu2
> >
> > > --tim
> > --
> > Thorsten Scherler <thorsten.at.apache.org>
> > Open Source Java <consulting, training and solutions>
> >
> > Sociedad Andaluza para el Desarrollo de la Sociedad
> > de la Información, S.A.U. (SADESI)
> >
> >
> >
> >
> > No virus found in this incoming message.
> > Checked by AVG - www.avg.com
> > Version: 8.5.425 / Virus Database: 270.14.71/2510 - Release Date: 11/17/09
> > 19:26:00
>

--
Thorsten Scherler <thorsten.at.apache.org>
Open Source Java <consulting, training and solutions>

Sociedad Andaluza para el Desarrollo de la Sociedad
de la Información, S.A.U. (SADESI)

From forum: Apache Forrest - Dev

[jira] Commented: (FOR-630) Forrest strategy and direction

2009-11-23T01:24:39Z

[ https://issues.apache.org/jira/browse/FOR-630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781340#action_12781340 ]

Gavin commented on FOR-630:
---------------------------

I'd like to close this 4 year old critical issue.

It looks like everything has either been addressed or is not relevant any more.

> Forrest strategy and direction
> ------------------------------
>
> Key: FOR-630
> URL: https://issues.apache.org/jira/browse/FOR-630
> Project: Forrest
> Issue Type: Task
> Components: Other
> Reporter: Ross Gardler
> Priority: Critical
>
> Topics for discussion gathered at ApacheCon EU 2005.
> WARNING: Only reply to the general theme of this
> topics list. Please create separate threads for
> each specific topic.
> Actually we should be using Jira for some of this.
> How about discussing on the mailing list, and
> putting summaries into Jira.
> I have the scraps of paper that Nicola Ken wrote.
> Photographs are in:
> http://svn.apache.org/repos/asf/forrest/events/apachecon-eu-2005
> Ross helped me to interpret some of the sqwiggles,
> but there are still some obscure parts (marked
> with #? below). The items are raw, i have not tried
> to explain any or add others.
> List of topics is in no particular order and
> it is not complete. We spent maybe 15 minutes
> brainstorming. We had a first quick pass at
> assigning some priority.
> I don't understand NKBs priority symbols.
> Anyway some items where marked with
> circle ... [C]
> square ... [S]
> Then we went straight on to the top topic:
> "configuration" and spent the rest of the day.
> --------------
> * Create lenya/forrest publication.
> * [C] Naming convention for "views".
> * Roadmap specifically for views.
> * [S] i18n support with locationmap.
> * Locationmap - what is needed to complete it.
> * [C] Configuration |=> apache #? arrow apache #?
> * TraversableSource ...
> * Source resolving for locationmap.
> * [C] How views are interacting with locationmap?
> * [S] Documentation mismatch. Docs are distributed in
> various places: site, plugins, seed.
> * Block documentation for Cocoon (/Forrest).
> * [C] Pre-processing plugins.
> * Flow of the plugin process.
> plugins - locationmap / flow #? this line obscure #?
> * Memory profiling.
> * Better use of Jira.
> * [S] XHTML2 transition.
> * [S] Live Forrest for Apache.
> (a configuration usecase)
> * [S] New skins for views.
> * Views ... body="true|false" head="true|false"
> * The *.ft files in a plugin (one-to-many).
> * Move into Java -> 0.9.5 or when needed. #? no idea what #?
>
> * [C] View / doctypes.
> (view in view)
> * [C] Content directory.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

From forum: Apache Forrest - Dev

RE: State of dispatcher?

2009-11-23T01:15:33Z

> -----Original Message-----
> From: Thorsten Scherler [mailto:thorsten.scherler.ext@...]
> Sent: Thursday, 19 November 2009 8:37 PM
> To: dev@...
> Subject: Re: State of dispatcher?
>
> On Wed, 2009-11-18 at 19:51 -0500, Tim Williams wrote:
> > On Tue, Nov 17, 2009 at 11:51 PM, Brian M Dube <bdube@...> wrote:
> > > On Tue, Nov 17, 2009 at 4:33 PM, Tim Williams <williamstw@...>
> wrote:
> > >> Looking at our issues for 0.9 and attempting to answer recent
> question
> > >> about dispatcher got me poking around a bit more and trying to learn
> > >> where we're at. It's highlighted two questions:
> > >>
> > >> 1) Do we see dispatcher being in the 0.9 release or not (i.e. FOR-
> 796)?
> > >>
> > >> 2) Where exactly is the dispatcher? There is dispatcher in the
> > >> whiteboard/plugins and a branch that appears to still be somewhat
> > >> active after a long period of time. If it is still an active
> branch,
> > >> whether it makes it out of the whiteboard for release or not, it
> needs
> > >> to be merged with trunk soon I think.
> > >
> > > Is the recent activity in the branch more than cleanup that may have
> > > been found by a script? That's what my cursory look made me think of.
> >
> > I don't think so. It looks to me like the branch was created over 13
> > months ago and has not yet merged back into trunk. So, from what I
> > can tell, we have 3 different dispatcher related code-sets:
> >
> > /branches/dispatcher_rewrite
>
> This branch I have created to merge the two (actually three) following
> into one plugin.
>
> > /trunk/whiteboard/dispatcher
> > /trunk/whiteboard/plugins/*dispatcher
>
> /trunk/whiteboard/plugins/*themes
>
> is missing.
>
> The branch is tested and used by my client now over 6 month. I do not
> see any problems with it anymore and further there are some bugs fixed
> that had been reported as well from Vincent ( Server returned HTTP
> response code: 503 for URL: http://www.w3.org/TR/html4/loose.dtd). That
> is actually a bug in the resolver but it is fixed in the branch.
>
>
> >
> > >From what I can tell, the latest code is still in the branch. If this
> > is correct, beyond whether or not it goes into the 0.9 release, I
> > think it'd be "Really Good" if we merged it soon... the most
> > immediate concern is deciding whether it makes it into the release or
> > not though...
> >
>
> I will try a dry-run merge now and see what is coming out.

Ah, this would be good, thanks Thorsten.

To be honest I lost track of where I was supposed to be working when doing
dispatcher stuff, so continued with

/trunk/whiteboard/plugins/*dispatcher
/trunk/whiteboard/plugins/*themes

It would be good to have all this stuff merged, then we can look at the
state of the merger and decide if it can go into the release.

Thanks

Gav...

>
> salu2
>
> > --tim
> --
> Thorsten Scherler <thorsten.at.apache.org>
> Open Source Java <consulting, training and solutions>
>
> Sociedad Andaluza para el Desarrollo de la Sociedad
> de la Información, S.A.U. (SADESI)
>
>
>
>
> No virus found in this incoming message.
> Checked by AVG - www.avg.com
> Version: 8.5.425 / Virus Database: 270.14.71/2510 - Release Date: 11/17/09
> 19:26:00

From forum: Apache Forrest - Dev

[jira] Commented: (FOR-1183) Forrestbar search of Jira issues broken, perhaps changed Jira search syntax

2009-11-23T01:10:39Z

[ https://issues.apache.org/jira/browse/FOR-1183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781338#action_12781338 ]

Gavin commented on FOR-1183:
----------------------------

hmm, I just installed the released ForrestBar 0.8 and it seems to be working fine for me, on XP in Firefox 3.5.5

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

From forum: Apache Forrest - Dev

[jira] Commented: (FOR-1168) Sample pages that fail validation

2009-11-23T00:54:39Z

[ https://issues.apache.org/jira/browse/FOR-1168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781335#action_12781335 ]

Gavin commented on FOR-1168:
----------------------------

Does anyone have ideas as to where I can look to replace the + with a _ .
Also opinions welcome in whether this fix is suitable as suggested.

> 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.9-dev
>
>
> 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.

From forum: Apache Forrest - Dev

Re: Blocking Issues

2009-11-23T00:50:48Z

2009/11/23 David Crossley <crossley@...>:

> Ross Gardler wrote:
>> David Crossley wrote:
>> > Ross Gardler wrote:
>> >> Tim Williams wrote:
>> >> >
>> >> > FOR-855 verify the license situation prior to each release
>> >> > - housekeeping
>> >>
>> >> I believe Davids work with RAT fixes this issue.
>> >
>> > No it does not. There is much more to the job that that.
>>
>> I meant that running RAT shows all licence headers are in place. we
>> still need to do the housekeeping work that is normal due diligence on
>> a release, of course.
>
> I meant that FOR-855 has much more than just the license header situation.
> I have been working on it steadily for a long time now, and there is more
> to do.

OK, I should have reviewed the issue. I have no opinion on whether
this is a blocker or not. I assumed that previous releases were
legally sound (which I believe they were since we voted them through).
Tim indicated that this was "housekeeping" which I took to mean the
normal due diligence on a release.

>> >> > FOR-1177 where does forrest use Rhino
>> >>
>> >> Not a blocker
>> >
>> > Yes it is. At the moment i think that it might be using an
>> > unsuitable license.
>>
>> Why? Rhino is dual licensed under GPL and MPL. MPL is compatible, as
>> long as we have the relevant NOTICE file. What am I missing that you
>> are seeing?
>
> I will try to clarify it at FOR-1177. When our packaged version of
> Rhino was prepared, it was probably the old NPL-licensed one.

OK, so that's probably a blocker then - we need to update to the MPL version.

Ross

From forum: Apache Forrest - Dev

Re: Blocking Issues

2009-11-22T18:01:48Z

Ross Gardler wrote:

> David Crossley wrote:
> > Ross Gardler wrote:
> >> Tim Williams wrote:
> >> >
> >> > FOR-855 verify the license situation prior to each release
> >> > - housekeeping
> >>
> >> I believe Davids work with RAT fixes this issue.
> >
> > No it does not. There is much more to the job that that.
>
> I meant that running RAT shows all licence headers are in place. we
> still need to do the housekeeping work that is normal due diligence on
> a release, of course.

I meant that FOR-855 has much more than just the license header situation.
I have been working on it steadily for a long time now, and there is more
to do.

> >> > FOR-1177 where does forrest use Rhino
> >>
> >> Not a blocker
> >
> > Yes it is. At the moment i think that it might be using an
> > unsuitable license.
>
> Why? Rhino is dual licensed under GPL and MPL. MPL is compatible, as
> long as we have the relevant NOTICE file. What am I missing that you
> are seeing?

I will try to clarify it at FOR-1177. When our packaged version of
Rhino was prepared, it was probably the old NPL-licensed one.

-David

From forum: Apache Forrest - Dev

[jira] Commented: (FOR-1177) where does forrest use Rhino

2009-11-22T17:59:39Z

[ https://issues.apache.org/jira/browse/FOR-1177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781275#action_12781275 ]

David Crossley commented on FOR-1177:
-------------------------------------

To try to clarify ... Please see comments above at 12/Nov/09 ... i have a feeling that we still have the old NPL-licensed Rhino. Our svn log shows that lib/core/rhino-1.6R2.jar was added on 2005-12-09 while the referenced "Rhino now MPL/GPL" thread indicates that that happened around 2006-11-10.

> 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
> 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.

From forum: Apache Forrest - Dev

[jira] Subscription: FOR-open-with-patch

2009-11-22T04:30:41Z

From forum: Apache Forrest - Dev

Re: Blocking Issues

2009-11-21T06:26:24Z

2009/11/21 David Crossley <crossley@...>:
> Ross Gardler wrote:
>> Tim Williams wrote:
>> >
>> > FOR-855 verify the license situation prior to each release
>> > - housekeeping
>>
>> I believe Davids work with RAT fixes this issue.
>
> No it does not. There is much more to the job that that.

I meant that running RAT shows all licence headers are in place. we
still need to do the housekeeping work that is normal due diligence on
a release, of course.

>> > FOR-1177 ? ? ? ?where does forrest use Rhino
>>
>> Not a blocker
>
> Yes it is. At the moment i think that it might be using an
> unsuitable license.

Why? Rhino is dual licensed under GPL and MPL. MPL is compatible, as
long as we have the relevant NOTICE file. What am I missing that you
are seeing?

Ross

From forum: Apache Forrest - Dev

Re: Blocking Issues

2009-11-21T01:20:48Z

Ross Gardler wrote:
> Tim Williams wrote:
> >
> > FOR-855 verify the license situation prior to each release
> > - housekeeping
>
> I believe Davids work with RAT fixes this issue.

No it does not. There is much more to the job that that.

> > FOR-1177 ? ? ? ?where does forrest use Rhino
>
> Not a blocker

Yes it is. At the moment i think that it might be using an
unsuitable license.

-David

From forum: Apache Forrest - Dev

[jira] Updated: (FOR-971) The tables used to output Glossary information needs styling with CSS

2009-11-20T17:55:39Z

[ https://issues.apache.org/jira/browse/FOR-971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tim Williams updated FOR-971:
-----------------------------

Fix Version/s: (was: 0.9-dev)
0.10

> The tables used to output Glossary information needs styling with CSS
> ---------------------------------------------------------------------
>
> Key: FOR-971
> URL: https://issues.apache.org/jira/browse/FOR-971
> Project: Forrest
> Issue Type: Improvement
> Components: Plugin: input.glossary
> Affects Versions: 0.8
> Reporter: Gavin
> Fix For: 0.10
>
>
> I would like to align the table columns with percentage CSS like 20-60-20 to improve the look and readability.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

From forum: Apache Forrest - Dev

[jira] Updated: (FOR-1167) class attribute of body element in XDocs source is not included in generated HTML

2009-11-20T17:39:39Z

[ https://issues.apache.org/jira/browse/FOR-1167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tim Williams updated FOR-1167:
------------------------------

Component/s: (was: Skins (general issues))
Fix Version/s: (was: 0.9-dev)
0.10

With the last patch, this issue seems only to apply to dispatcher, so I've removed the 'skins' part of the component, and moving to .10.

> class attribute of body element in XDocs source is not included in generated HTML
> ---------------------------------------------------------------------------------
>
> Key: FOR-1167
> URL: https://issues.apache.org/jira/browse/FOR-1167
> Project: Forrest
> Issue Type: Bug
> Components: Plugin: internal.dispatcher, Plugin: themes.core
> Affects Versions: 0.9-dev
> Reporter: Brolin Empey
> Fix For: 0.10
>
> Attachments: FOR-1167-skins.patch
>
>
> Here is the body element of my XDocs source file:
> <body class="product_heading">
> The generated HTML does not include the class attribute.
> See <http://thread.gmane.org/gmane.text.xml.forrest.devel/27106>.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

From forum: Apache Forrest - Dev

[jira] Updated: (FOR-979) RSS - Description starts with the title, which makes unnecessary repeatitions

2009-11-20T17:35:39Z

[ https://issues.apache.org/jira/browse/FOR-979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tim Williams updated FOR-979:
-----------------------------

Fix Version/s: (was: 0.9-dev)
0.10

Pushing to .10, but it's not very clear what exactly this means. If anyone understands it, they should add a better description, steps to reproduce, what to look for, etc.

> RSS - Description starts with the title, which makes unnecessary repeatitions
> -----------------------------------------------------------------------------
>
> Key: FOR-979
> URL: https://issues.apache.org/jira/browse/FOR-979
> Project: Forrest
> Issue Type: Improvement
> Components: Plugin: input.projectInfo
> Affects Versions: 0.8
> Reporter: Cyriaque Dupoirieux
> Priority: Minor
> Fix For: 0.10
>
>
> The description of an item repeats the title which take lot a place in small frames (with aggregators such as Netvibes or Bloglines...)
> ex :
> Dispatcher improvment
> Dispatcher improvment by CD : Big work on...

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

From forum: Apache Forrest - Dev

[jira] Updated: (FOR-968) Embbed the Faq generation into a plugin instead of the core

2009-11-20T17:29:39Z

[ https://issues.apache.org/jira/browse/FOR-968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tim Williams updated FOR-968:
-----------------------------

Fix Version/s: (was: 0.9-dev)
0.10

> Embbed the Faq generation into a plugin instead of the core
> -----------------------------------------------------------
>
> Key: FOR-968
> URL: https://issues.apache.org/jira/browse/FOR-968
> Project: Forrest
> Issue Type: Improvement
> Components: Core operations, Plugins: Potential new
> Reporter: Cyriaque Dupoirieux
> Priority: Minor
> Fix For: 0.10
>
>

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

From forum: Apache Forrest - Dev

[jira] Updated: (FOR-533) Auto Generate plugins.xml entry

2009-11-20T17:27:40Z

[ https://issues.apache.org/jira/browse/FOR-533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tim Williams updated FOR-533:
-----------------------------

Fix Version/s: (was: 0.9-dev)
0.10

> Auto Generate plugins.xml entry
> -------------------------------
>
> Key: FOR-533
> URL: https://issues.apache.org/jira/browse/FOR-533
> Project: Forrest
> Issue Type: Improvement
> Components: Plugins (general issues)
> Reporter: Ross Gardler
> Priority: Minor
> Fix For: 0.10
>
>
> The information in the plugins.xml file would be better kept in the plugin directory and added to the plugins.xml file when deployed. This would reduce the amount of duplication in the plugins config files.
> All the necessary values are now in the plugin build.xml file.
> This change will require that the plugins.xml file be retrieved from the build directory rather than the plugins directory when building the plugin documentation pages. We will therefore need a fall back to retrieve this file from the network if it is not currently available - this can be done with the locationmap

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

From forum: Apache Forrest - Dev

[jira] Updated: (FOR-671) Layering error of HTML headings breaks rest of the page w/o warning

2009-11-20T17:25:40Z

[ https://issues.apache.org/jira/browse/FOR-671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tim Williams updated FOR-671:
-----------------------------

Fix Version/s: (was: 0.9-dev)
0.10

> Layering error of HTML headings breaks rest of the page w/o warning
> -------------------------------------------------------------------
>
> Key: FOR-671
> URL: https://issues.apache.org/jira/browse/FOR-671
> Project: Forrest
> Issue Type: Bug
> Components: Core operations
> Affects Versions: 0.7
> Environment: XP
> Reporter: Ferdinand Soethe
> Priority: Minor
> Fix For: 0.10
>
>
> Up to revision 280144 if you make Forrest display the following file as a skinned .html-file in Forrest, you'll only see the title. Only if you fix the layering error of the headings and make h2 into h1 will the rest of the page content show.
> If Forrest minds this layering error it should at least report it as an error, shoulnd't it?
> <?xml version="1.0" encoding="ISO-8859-1"?>
> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
> <html>
> <head>
> <title>Englisch</title>
> </head>
> <body class="Oberbereich">
> <h2>Kursthemen</h2>
> <ul class="Kursthemenliste">
> <li class="Kurstthemenlistenpunkt">
> <a class="Kursthemenliste_Listenpunkt" href="$KursthemaDateiname">Getting Started in Business (Abendkurs 1 x wöchentlich)
> </a>
> </li>
> <li class="Kurstthemenlistenpunkt">
> <a class="Kursthemenliste_Listenpunkt" href="$KursthemaDateiname">Getting Ahead in Business (Abendkurs 1 x wöchentlich)
> </a>
> </li>
> <li class="Kurstthemenlistenpunkt">
> <a class="Kursthemenliste_Listenpunkt" href="$KursthemaDateiname">Complaints, Reports and other Messages (Wochenendseminar)
> </a>
> </li>
> </ul>
> </body>
> </html>

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

From forum: Apache Forrest - Dev

[jira] Updated: (FOR-770) Locationmap logs should show which sitemap the request is coming from

2009-11-20T17:23:40Z

[ https://issues.apache.org/jira/browse/FOR-770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tim Williams updated FOR-770:
-----------------------------

Fix Version/s: (was: 0.9-dev)
0.10

Not going to happen for this release, pushing to .10.

> Locationmap logs should show which sitemap the request is coming from
> ---------------------------------------------------------------------
>
> Key: FOR-770
> URL: https://issues.apache.org/jira/browse/FOR-770
> Project: Forrest
> Issue Type: Improvement
> Components: Locationmap
> Affects Versions: 0.8, 0.9-dev
> Reporter: Ross Gardler
> Fix For: 0.10
>
>
> With the introduction of the locationmap it can be unclear which sitemap pipeline is handling a request. Prior to the locationmap, exceptions would tell us where in the sitemap we were working. However, this can sometimes get lost in the interaction with the locationmap.
> This makes it very difficult to debug some locationmap problems. For example, I recently had a situation in which the locationmap was being queried for "project.foo". In this hint the "project." part was being added by the sitemaps, but the error reported was not showing where. I knew this meant some match was intercepting the request before my plugin sitemap got hold of it, but the error messages would not tell me which. I had to trace the process manually, which took an age. In the end it was a catchall match in the raw.xmap
> If the LM logs could report where the request is coming from, I would have known in seconds what the problem was, rather than hours. We need a log entry something like:
> "Examining Locationmap for "project.foo" on behald of /raw.xmap (line XYZ)"

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

From forum: Apache Forrest - Dev

[jira] Updated: (FOR-144) define new format for skinconf.xml

2009-11-20T17:23:40Z

[ https://issues.apache.org/jira/browse/FOR-144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tim Williams updated FOR-144:
-----------------------------

Fix Version/s: (was: 0.9-dev)
0.10

Pushing off, need to consider how/if we deal with this once dispatcher is out of the whiteboard.

> define new format for skinconf.xml
> ----------------------------------
>
> Key: FOR-144
> URL: https://issues.apache.org/jira/browse/FOR-144
> Project: Forrest
> Issue Type: Task
> Components: Skins (general issues)
> Affects Versions: 0.7, 0.8
> Reporter: David Crossley
> Priority: Minor
> Fix For: 0.10
>
>
> We are attempting to define a new extensible skinconf format. Here is one thread where the discussion is happening (there were some other threads leading up to that).
> http://marc.theaimsgroup.com/?t=108315759100005

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

From forum: Apache Forrest - Dev

[jira] Updated: (FOR-250) only add the compliance logos if the html is valid

2009-11-20T17:21:39Z

[ https://issues.apache.org/jira/browse/FOR-250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tim Williams updated FOR-250:
-----------------------------

Fix Version/s: (was: 0.9-dev)
0.10

New feature being pushed to .10.

> only add the compliance logos if the html is valid
> --------------------------------------------------
>
> Key: FOR-250
> URL: https://issues.apache.org/jira/browse/FOR-250
> Project: Forrest
> Issue Type: New Feature
> Components: Core operations
> Affects Versions: 0.6
> Reporter: David Crossley
> Fix For: 0.10
>
>
> Currently the compliance logos are only applied to any page called "index.html". It would be nice if we could automatically determine if the final output was valid and apply the compliance logos accordingly.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

From forum: Apache Forrest - Dev