[
http://issues.apache.org/jira/browse/FOR-592?page=comments#action_12317380 ]
Gavin commented on FOR-592:
---
Ok , Thanks Guys for the info,
Now subscribed to the dev list.
Looking through some archives I see it has been brought up before (
[
http://issues.apache.org/jira/browse/FOR-604?page=comments#action_12317898 ]
Gavin commented on FOR-604:
---
Ok, I have made the changes needed. You can view it in action, I have uploaded
a basic site and at http://apache.minitutorials.com/samples/sample.html you
[
http://issues.apache.org/jira/browse/FOR-605?page=comments#action_12317899 ]
Gavin commented on FOR-605:
---
I removed the comment tags from the motd in /forrest/site-author/skinconf.xml
but it has made no difference.
Can you tell me how to enable motd so I can
[ http://issues.apache.org/jira/browse/FOR-604?page=all ]
Gavin updated FOR-604:
--
Attachment: basic.css.diff
The document-v* warning element does not get rendered properly
--
Key: FOR-604
[
http://issues.apache.org/jira/browse/FOR-604?page=comments#action_12317907 ]
Gavin commented on FOR-604:
---
I have attatched basic.css.diff for inclusion.
Thanks
Gav...
The document-v* warning element does not get rendered properly
[
http://issues.apache.org/jira/browse/FOR-578?page=comments#action_12318698 ]
Gavin commented on FOR-578:
---
Just to confirm that using index.es.xml does work as expected.
There may be confusion for some with this naming convension because when
looking in the
[
http://issues.apache.org/jira/browse/FOR-618?page=comments#action_12318699 ]
Gavin commented on FOR-618:
---
I am currently creating these issues,
basically just a summary taken from the two posts mentioned.
Maybe others could expand on them.
Gav...
Create
Deciding which view to use
--
Key: FOR-621
URL: http://issues.apache.org/jira/browse/FOR-621
Project: Forrest
Type: Improvement
Components: Views
Versions: 0.8-dev
Reporter: Gavin
Currently deciding which view to use is
[
http://issues.apache.org/jira/browse/FOR-624?page=comments#action_12318701 ]
Gavin commented on FOR-624:
---
For the most part, those that want pdf or text based alternatives, would do so
for offline reading, maybe printing them out for later perusal. In these
Packaging of views and themes
-
Key: FOR-622
URL: http://issues.apache.org/jira/browse/FOR-622
Project: Forrest
Type: Improvement
Components: Views
Versions: 0.8-dev
Reporter: Gavin
Priority: Minor
It was generally
Scope of themes
---
Key: FOR-625
URL: http://issues.apache.org/jira/browse/FOR-625
Project: Forrest
Type: Improvement
Components: Views
Versions: 0.8-dev
Reporter: Gavin
The current skinning system does not allow for skinning of formats
Configuration of views
--
Key: FOR-623
URL: http://issues.apache.org/jira/browse/FOR-623
Project: Forrest
Type: Improvement
Components: Views
Versions: 0.8-dev
Reporter: Gavin
Possibly too many configuration files for views.
Reusing Cocoon Portal Engine
Key: FOR-626
URL: http://issues.apache.org/jira/browse/FOR-626
Project: Forrest
Type: Improvement
Components: Views
Versions: 0.8-dev
Reporter: Gavin
A couple of the Forrest devs attended a
Confiuration of Forrest
---
Key: FOR-627
URL: http://issues.apache.org/jira/browse/FOR-627
Project: Forrest
Type: Improvement
Components: Core operations
Versions: 0.8-dev
Reporter: Gavin
Forrest's config files, as they stand
I18n Management
---
Key: FOR-628
URL: http://issues.apache.org/jira/browse/FOR-628
Project: Forrest
Type: Improvement
Components: Other
Versions: 0.8-dev
Reporter: Gavin
There is a problem with the current I18N support for content. At
[ http://issues.apache.org/jira/browse/FOR-605?page=all ]
Gavin updated FOR-605:
--
Attachment: forrest_faq.png
I am investigating this, and it seems there is doubled up use of margins and
padding in adjacent areas of the stylesheet. For instance the width of a
[ http://issues.apache.org/jira/browse/FOR-650?page=all ]
Gavin updated FOR-650:
--
Attachment: faq.xml.diff
This is the faq change to go with the MOTD changes in skinconf. Its just a
pointer to where the
MOTD is kept and its docs. This example could be enhanced
MOTD Needs to have a working example.
-
Key: FOR-650
URL: http://issues.apache.org/jira/browse/FOR-650
Project: Forrest
Type: Sub-task
Components: Skins (general issues)
Versions: 0.8-dev
Environment: All
Reporter:
[ http://issues.apache.org/jira/browse/FOR-650?page=all ]
Gavin updated FOR-650:
--
Attachment: skinconf.xml.diff
Updates MOTD so there is a out of the box working example ready to go. The
example also uses a new
FAQ entry in faq.xml to help show the way.
MOTD
[
http://issues.apache.org/jira/browse/FOR-605?page=comments#action_12320258 ]
Gavin commented on FOR-605:
---
I am now working on the CSS and will patch and go as I progress, this MOTD
issue will get sorted as a side effect of the revamp.
CSS enhancements needed
[ http://issues.apache.org/jira/browse/FOR-650?page=all ]
Gavin updated FOR-650:
--
Attachment: faq.xml.diff
Sorry, last update invalidated the xml due to duplicate id name (motd), renamed
second id to motd1.
MOTD Needs to have a working example.
CSS Style Sheets need cleanup and optimization
--
Key: FOR-652
URL: http://issues.apache.org/jira/browse/FOR-652
Project: Forrest
Type: Improvement
Components: Skins (general issues)
Versions: 0.8-dev
[ http://issues.apache.org/jira/browse/FOR-652?page=all ]
Gavin updated FOR-652:
--
Attachment: screen.css.diff
A start at making for a more fluid design. Some minor changes to improve
fluidity.
CSS Style Sheets need cleanup and optimization
[
http://issues.apache.org/jira/browse/FOR-605?page=comments#action_12320349 ]
Gavin commented on FOR-605:
---
FOR 652 has been created for general CSS enhancements. The first enhancement of
FOR 652 has been uploaded, if applied please see if the MOTD changes as
[
http://issues.apache.org/jira/browse/FOR-655?page=comments#action_12322690 ]
Gavin commented on FOR-655:
---
I have updated http://apache.minitutorials.com/xhtml2.html . I have also
created an xml version at http://apache.minitutorials.com/xhtml2.xml .
Both
[ http://issues.apache.org/jira/browse/FOR-655?page=all ]
Gavin updated FOR-655:
--
Attachment: xhtml2_subset.xml.diff
I have added all the rest of the sections mentioned in NKB's 'XHTML- lets do
it!' mail.
I have populated most of these new sections with content.
[
http://issues.apache.org/jira/browse/FOR-680?page=comments#action_12330806 ]
Gavin commented on FOR-680:
---
Hmm, that looks fine to me.
You can not nest ul ol nl etc inside of li.
li however must be inside of one of the above.
second level nesting etc is the
[ http://issues.apache.org/jira/browse/FOR-694?page=all ]
Gavin updated FOR-694:
--
Attachment: revisions.xmap.diff
I have changed what I can see, please check.
I note in this file a comment reads :
Example URL:
Target of LocationMap rewriteDemo causes build failure when target not available
Key: FOR-705
URL: http://issues.apache.org/jira/browse/FOR-705
Project: Forrest
Type: Bug
Components:
[
http://issues.apache.org/jira/browse/FOR-680?page=comments#action_12331646 ]
Gavin commented on FOR-680:
---
Looking at the source of [1] shows that jspwiki does normally created nested
bullets etc correctly, so I guess it is in the way we have implemented it.
[
http://issues.apache.org/jira/browse/FOR-680?page=comments#action_12331647 ]
Gavin commented on FOR-680:
---
Ok, I see the problem I think ,
In
%forrest_home\plugins\org.apache.forrest.plugin.input.wiki\resources\chaperon\stylesheets\wiki2xdoc.xsl
Bulleted
[ http://issues.apache.org/jira/browse/FOR-696?page=all ]
Gavin updated FOR-696:
--
Attachment: tabs.xmap.diff
Hopefully naming convension correct, I needed to update
locationmap-transforms.xml to add as there didnt seem to be a match.
Use locationmap in
[ http://issues.apache.org/jira/browse/FOR-696?page=all ]
Gavin updated FOR-696:
--
Attachment: locationmap-transforms.xml.diff
Use locationmap in tabs.xmap
Key: FOR-696
URL:
[ http://issues.apache.org/jira/browse/FOR-696?page=all ]
Gavin updated FOR-696:
--
Attachment: tabs.xmap.diff2
Missed a } from the first one, this fixes the first diff.
Use locationmap in tabs.xmap
Key: FOR-696
siteinfo-feedback contract returns multiple nested ahref declarations.
Key: FOR-743
URL: http://issues.apache.org/jira/browse/FOR-743
Project: Forrest
Type: Bug
Components: Views
Inline CSS produces extra unwanted url references - Views V2 -
--
Key: FOR-744
URL: http://issues.apache.org/jira/browse/FOR-744
Project: Forrest
Type: Bug
Components: Views
Versions: 0.8-dev
Coat Theme CSS Enhancements
---
Key: FOR-781
URL: http://issues.apache.org/jira/browse/FOR-781
Project: Forrest
Type: Improvement
Components: Skins (general issues)
Versions: 0.8-dev
Reporter: Gavin
Priority: Minor
[
http://issues.apache.org/jira/browse/FOR-790?page=comments#action_12362854 ]
Gavin commented on FOR-790:
---
This can be avoided by using onFocus inline for Form values instead of calling
the getBlank.js script.
A generic e.g to adapt :-
divlabel
[
http://issues.apache.org/jira/browse/FOR-803?page=comments#action_12365194 ]
Gavin commented on FOR-803:
---
Using Dispatcher rc1 I can see no performance lags when doing a forrest
run,forrest site,forrest -f bot.xml .
If anything, things are slightly quicker
[ http://issues.apache.org/jira/browse/FOR-811?page=all ]
Gavin updated FOR-811:
--
Attachment: pelt.fv.diff
pelt.screen.css.diff
siteinfo-credits.ft.diff
3 Attatchments go a way towards addressing this issue. There are still some
Dispatcher Build, Clean and Deploy Batch File for Windows
-
Key: FOR-831
URL: http://issues.apache.org/jira/browse/FOR-831
Project: Forrest
Type: Improvement
Components: Dispatcher (aka views)
Versions:
[
http://issues.apache.org/jira/browse/FOR-820?page=comments#action_12370503 ]
Gavin commented on FOR-820:
---
But we have to get it working yet, or did I miss that bit?
Around Line 667 of Pass2.java is being pointed to as the culprit, but as ever
with
[
http://issues.apache.org/jira/browse/FOR-811?page=comments#action_12370517 ]
Gavin commented on FOR-811:
---
There is a width problem concerning the tables in IE6, they are too wide making
the pages scrollable horizontally, it's fine in Firefox. There is a hack
[ http://issues.apache.org/jira/browse/FOR-831?page=all ]
Gavin updated FOR-831:
--
Attachment: builddispatcher.bat
Original file had 'build' , 'build clean' instructions in the wrong order. Now
corrected.
Dispatcher Build, Clean and Deploy Batch File for Windows
[ http://issues.apache.org/jira/browse/FOR-831?page=all ]
Gavin updated FOR-831:
--
Attachment: builddispatcher.bat
Updated batch file, original had the order of 'build' , 'build clean' instead
of the other way around.
Dispatcher Build, Clean and Deploy Batch
[
http://issues.apache.org/jira/browse/FOR-591?page=comments#action_12371889 ]
Gavin commented on FOR-591:
---
Another update note :
I have just added a comment (to COCOON-1574) to see how they are getting on, if
no near time frame for resolving it then maybe this
[
http://issues.apache.org/jira/browse/FOR-713?page=comments#action_12371890 ]
Gavin commented on FOR-713:
---
Was wondering if any conversions have been missed (remember the name changes of
'2' to '-to-' - html2document becomes html-to-document, and now with lm:
[
http://issues.apache.org/jira/browse/FOR-208?page=comments#action_12371918 ]
Gavin commented on FOR-208:
---
Second level tabs look fine now on main forrest.apache.org site, fine in
site-author, works fine in seed-sample (although color scheme not matching ,
the
[
http://issues.apache.org/jira/browse/FOR-834?page=comments#action_12372230 ]
Gavin commented on FOR-834:
---
Possibly related, comments in pelt.fv are causing whitespace in the resultant
output.
In this case though I think the comments are intended for dev use
[
http://issues.apache.org/jira/browse/FOR-755?page=comments#action_12372779 ]
Gavin commented on FOR-755:
---
I am working on getting this working, see
http://marc.theaimsgroup.com/?t=11438913811r=1w=2
Once done terms for
[ http://issues.apache.org/jira/browse/FOR-755?page=all ]
Gavin updated FOR-755:
--
Attachment: org.apache.forrest.plugin.input.glossary.zip
Zip file attached.
Glossary Input Plugin
-
Key: FOR-755
URL:
[ http://issues.apache.org/jira/browse/FOR-639?page=all ]
Gavin updated FOR-639:
--
Attachment: glossary.xml.add
Not sure you need an .add file, but I did to then create the .diff
define terminology for the various aspects of Dispatcher
[ http://issues.apache.org/jira/browse/FOR-639?page=all ]
Gavin updated FOR-639:
--
Attachment: glossary.xml.diff
site.xml.diff
glossary-to-document.xsl.diff
Glossary File added, not complete but a start.
Site.xml changed to
[
http://issues.apache.org/jira/browse/FOR-756?page=comments#action_12374186 ]
Gavin commented on FOR-756:
---
I have made a start and created the (input) plugin for this, now to configure
it.
Citations Plugin
Key: FOR-756
[
http://issues.apache.org/jira/browse/FOR-858?page=comments#action_12374488 ]
Gavin commented on FOR-858:
---
The 'see' elements is broken as it relys on the Citations Plugin. This is being
worked on currently. 'See' FOR-756 also.
glossary items with see for
[
http://issues.apache.org/jira/browse/FOR-595?page=comments#action_12374742 ]
Gavin commented on FOR-595:
---
Looking at the code it looks fixed to me.
title
xsl:choose
xsl:when test=@title!=''
xsl:value-of select=@title/
/xsl:when
[
http://issues.apache.org/jira/browse/FOR-595?page=comments#action_12374922 ]
Gavin commented on FOR-595:
---
I have an idea that may cure this but not sure of the 'how'.
What about we create a comment/comment element that when processed by
genericMarkup.ft ,
[
http://issues.apache.org/jira/browse/FOR-834?page=comments#action_12374923 ]
Gavin commented on FOR-834:
---
I have an idea that may cure this but not sure of the 'how'.
What about we create a comment/comment element that when processed by
genericMarkup.ft ,
[ http://issues.apache.org/jira/browse/FOR-595?page=all ]
Gavin updated FOR-595:
--
Sorry, last comment was for FOR-834, can it be removed from this one?
Hard-coded project name in input.projectinfo plugin
---
[
http://issues.apache.org/jira/browse/FOR-492?page=comments#action_12375069 ]
Gavin commented on FOR-492:
---
As far as I can see, all lines on Windows from a generated .html file all end
with CRLF.
Also I see no difference in the way comments are treated as
[ http://issues.apache.org/jira/browse/FOR-492?page=all ]
Gavin updated FOR-492:
--
Attachment: index.html
I wonder how those on other OS will be able to check this anyway, a screen shot
may be needed ?
Forgot to mention that link :
[
http://issues.apache.org/jira/browse/FOR-834?page=comments#action_12375100 ]
Gavin commented on FOR-834:
---
a working solution is provided at
http://marc.theaimsgroup.com/?l=forrest-devm=114544554025191w=2
A patch will be available if approved.
On another
[
http://issues.apache.org/jira/browse/FOR-834?page=comments#action_12375101 ]
Gavin commented on FOR-834:
---
a working solution is provided at
http://marc.theaimsgroup.com/?l=forrest-devm=114544554025191w=2
A patch will be available if approved.
On another
[ http://issues.apache.org/jira/browse/FOR-756?page=all ]
Gavin updated FOR-756:
--
Attachment: org.apache.forrest.plugin.input.citations.zip
Working version of Citations Plugin. Tested with 'Ant Test' and used a test
site using 'forrest run' and 'forrest site' .
[
http://issues.apache.org/jira/browse/FOR-858?page=comments#action_12375117 ]
Gavin commented on FOR-858:
---
Now that I have finished the Citations Plugin, I think there is a bit of
misunderstanding on the use of the 'see' element and 'cite'.
It looks to me like
[ http://issues.apache.org/jira/browse/FOR-639?page=all ]
Gavin updated FOR-639:
--
Component: Plugin: input.glossary
define terminology for the various aspects of Dispatcher
Key: FOR-639
[ http://issues.apache.org/jira/browse/FOR-639?page=all ]
Gavin updated FOR-639:
--
Attachment: glossary-v10.mod.diff
glossary-to-document.xsl.diff
glossary-v10.mod - added definitions element.
glossary-to-document.xsl - added definitions template ,
[
http://issues.apache.org/jira/browse/FOR-767?page=comments#action_12375847 ]
Gavin commented on FOR-767:
---
Looking at deploy.xml the build will fail if deploy is local :-
target name=deploy.local unless=build.failed description=FB: Deploy to a
local location
[ http://issues.apache.org/jira/browse/FOR-562?page=all ]
Gavin updated FOR-562:
--
Attachment: howto-buildPlugin.xml.diff
Changes applied as per Issue instructions.
Do we need to repeat the changes for the docs_0_80 version too ?
Update Plugins howto
[ http://issues.apache.org/jira/browse/FOR-851?page=all ]
Gavin updated FOR-851:
--
Attachment: voice-plugin.diff
Well, I tried a different way of making the diff file, so all changes are in
the one file rather than having a diff file for each file I
[
http://issues.apache.org/jira/browse/FOR-537?page=comments#action_12375880 ]
Gavin commented on FOR-537:
---
Ok, I see there are references to the 'three' plugin types further up the file,
but still remains references to sitemap.xmap also. I have corrected what I
[
http://issues.apache.org/jira/browse/FOR-211?page=comments#action_12377807 ]
Gavin commented on FOR-211:
---
Ok, I wonder if I can take a look at this, where should I start looking at ?
whole-site html and pdf: broken ext links
[
http://issues.apache.org/jira/browse/FOR-848?page=comments#action_12378211 ]
Gavin commented on FOR-848:
---
I am working on this and am making some progress.
The plugin has now been converted to use current Dispatcher.
I still need to get a 'notes' example
[ http://issues.apache.org/jira/browse/FOR-848?page=all ]
Gavin updated FOR-848:
--
Attachment: notetaking_plugin.diff
Attached diff file upgrades plugin to dispatcher.
The actual 'notes' part of it does not work atm.
See
[ http://issues.apache.org/jira/browse/FOR-635?page=all ]
Gavin updated FOR-635:
--
Attachment: fo.diff
added pathutils.xsl to fo directory, altered document-to-fo.xsl.
images not reproduced in PDFs, if sources are in xdocs/images directory
[ http://issues.apache.org/jira/browse/FOR-889?page=all ]
Gavin updated FOR-889:
--
Attachment: beforeUpgrade.txt
afterUpgrade.txt
Build Passes before upgrade, fails after upgrade.
Use by Ant of newer catalog entity resolver failing for Windows
[
http://issues.apache.org/jira/browse/FOR-635?page=comments#action_12413570 ]
Gavin commented on FOR-635:
---
Does somebody want to test this.
images not reproduced in PDFs, if sources are in xdocs/images directory
[ http://issues.apache.org/jira/browse/FOR-891?page=all ]
Gavin updated FOR-891:
--
Attachment: screen_2.css.diff
This revised patch fixes the errors ONLY - this will ensure that it passes CSS
compliance. The warnings remain however and will work through these as
[
http://issues.apache.org/jira/browse/FOR-891?page=comments#action_12415349 ]
Gavin commented on FOR-891:
---
No thanks, I'll send in a new patch shortly to hopefully close the Issue.
css-validator reports CSS errors and many warnings for pelt skin
[
http://issues.apache.org/jira/browse/FOR-876?page=comments#action_12415549 ]
Gavin commented on FOR-876:
---
I tried this and it works fine for me in a freshly seeded site.
pa href=lm:rewriteDemo/indexThis link is rewritten to
an offsite address/a
[
http://issues.apache.org/jira/browse/FOR-897?page=comments#action_12416746 ]
Gavin commented on FOR-897:
---
Hi Nico,
Had a quick look and the only error I can see at the moment is your file names
index.nl.xml is incorrectly named.
Try renaming it to
[
http://issues.apache.org/jira/browse/FOR-897?page=comments#action_12416748 ]
Gavin commented on FOR-897:
---
Ignore that sorry, looking at wrong naming convensions. index.nl.xml is correct.
Added dutch translations of menu, tabs and index.xml
[
http://issues.apache.org/jira/browse/FOR-897?page=comments#action_12416759 ]
Gavin commented on FOR-897:
---
Back Again,
Applied your patch locally to my system and to confirm, yes the space between
'' and 'a' in your index.nl.xml file makes all the difference,
[
http://issues.apache.org/jira/browse/FOR-822?page=comments#action_12416881 ]
Gavin commented on FOR-822:
---
I tested this using checkout 414415 and on a Dispatcher and i18n enabled
seed-sample site and these errors are now gone and it all seems to work fine
(as
[
http://issues.apache.org/jira/browse/FOR-785?page=comments#action_12417076 ]
Gavin commented on FOR-785:
---
Ok,
So I altered the DTD and moved project-name and project-description to the end.
This works fine and validates, have I missed something as to why we
[
http://issues.apache.org/jira/browse/FOR-209?page=comments#action_12417097 ]
Gavin commented on FOR-209:
---
If we are not fixing this for 0.7, this looked fixed to me in 0.8 - if everyone
agrees this issue should be closed.
Sjur or anykne, if any more visual
[
http://issues.apache.org/jira/browse/FOR-785?page=comments#action_12417244 ]
Gavin commented on FOR-785:
---
Yes, I changed the forrest-validate.skinconf to = true again before testing
(also you can 'forrest validate-skinconf' on the CLI.)
I will send a patch
[ http://issues.apache.org/jira/browse/FOR-785?page=all ]
Gavin updated FOR-785:
--
Attachment: dtdchanges.diff
dtdchanges.diff cures problems associated with plugins failing validation.
I am working through the plugins and have almost finished the main plugins.
[ http://issues.apache.org/jira/browse/FOR-785?page=all ]
Gavin updated FOR-785:
--
Attachment: enableValidatePlugins.diff
enableValidatePlugins turns all of the main plugins into
'forrest.validate.skinconf=true' except those that do not pass 'Ant Test' .
Other
[
http://issues.apache.org/jira/browse/FOR-488?page=comments#action_12417621 ]
Gavin commented on FOR-488:
---
Ok, so I guess this can be removed now then ?
Remove Zip Java components from Forrest
---
Key: FOR-488
[
http://issues.apache.org/jira/browse/FOR-203?page=comments#action_12418011 ]
Gavin commented on FOR-203:
---
I have tested this and it all seems to work fine. From what I understand of the
original problem it could be a case of misunderstanding of the
[
http://issues.apache.org/jira/browse/FOR-203?page=comments#action_12418013 ]
Gavin commented on FOR-203:
---
Also, I do not think this is a duplicate of FOR-208 .
2nd level tabs are not selected appropriately
-
[
http://issues.apache.org/jira/browse/FOR-203?page=comments#action_12418202 ]
Gavin commented on FOR-203:
---
I have tested the attachment now, and I still feel this is a user or
documentation error - or can someone tell me if this feature is required.
I mean,
Apachecon Images blurred due to resizing on the fly
---
Key: FOR-907
URL: http://issues.apache.org/jira/browse/FOR-907
Project: Forrest
Issue Type: Improvement
Components:
[ http://issues.apache.org/jira/browse/FOR-907?page=all ]
Gavin updated FOR-907:
--
Attachment: apache_con_asia_header.png
ASF-us-2006-web_masthead.jpg
apachecon.diff
Attached are resized to 150x50 versions of images and the diff to
[
http://issues.apache.org/jira/browse/FOR-285?page=comments#action_12421442 ]
Gavin commented on FOR-285:
---
Unless NKB can enlighten as to what this is and if it is still needed - I don't
see it as Incubator does not use Forrest - this could be
[
http://issues.apache.org/jira/browse/FOR-827?page=comments#action_12421443 ]
Gavin commented on FOR-827:
---
So, should this workaround be documented as the way to do it, then close the
issue, or does someone think there may be a better solution
[
http://issues.apache.org/jira/browse/FOR-731?page=comments#action_12421444 ]
Gavin commented on FOR-731:
---
The linked issue of which this is a workaround, has been scheduled for fix
version 0.9, so I guess this should follow suit.
empty
[ http://issues.apache.org/jira/browse/FOR-639?page=all ]
Gavin updated FOR-639:
--
Attachment: dispatcher.diff
Added dispatcher-glossary.xml to plugin, enabled glossary plugin.
define terminology for the various aspects of Dispatcher
[ http://issues.apache.org/jira/browse/FOR-639?page=all ]
Gavin updated FOR-639:
--
Attachment: glossary.xml.diff2
glossary.xml.diff2 removes dispatcher related terms, these are now in the
dispatcher-glossary.xml which resides in the dispatcher plugin instead.
1 - 100 of 415 matches
Mail list logo
