forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gav...." <>
Subject Working - RE: Glossary Plugin FOR-755 - was RE: [jira] Updated: (FOR-639) define terminology for the various aspects of Dispatcher
Date Mon, 03 Apr 2006 13:31:02 GMT

> -----Original Message-----
> From: Ross Gardler []
> Sent: Monday, 3 April 2006 8:00 PM
> To:
> Subject: Re: Glossary Plugin FOR-755 - was RE: [jira] Updated: (FOR-639)
> define terminology for the various aspects of Dispatcher
> Thorsten Scherler wrote:
> > El lun, 03-04-2006 a las 17:00 +0800, Gav.... escribió:
> > ...
> >
> >>Definitely something wrong I think. I can put in deliberate mistakes,
> >>jargon, delete tags, close tags twice and it makes not a bit of
> difference.
> >>
> >>I can delete the input.xmap file altogether and it cares not, no
> difference,
> >>the site still builds fine and the glossary.xml file still displays only
> >>menus & tabs and no content.
> >
> >
> > Well that sounds like you should do a build clean (on forrest and your
> > plugin), since if you can have an invalid input.xmap that raises the
> > suspicion that an old (valid) one is being used (the already deployed
> > one).
> Yes, that sounds possible, you need to  do "ant local-deploy" inside the
> plugin dir every time you make a change to the plugin code, otherwise
> you will be using the old code. See the plugin How To doc.
> (actually, to be totally accurate you don't need to do "ant
> local-deploy" after a you clean build Forrest, as if the plugin is not
> present it will auto deploy)

Blimey, it does seem as though it helps, but to do it every time I made a
change was a bit tedious. However I found if I did not, some changes I made
would not be effective. I also had to ant local-deploy the projectInfo
plugin each time.

> One other thought, you have actually added the plugin name to
> haven't you?

Er, yep, was already there when doing an ant seedPlugin.

> > BTW I have not completely followed this thread because I do not have
> > much time for forrest ATM so you may have already stated whether you use
> > skins or the dispatcher?
> We've not got that far yet. Still trying to get the glossary file
> converted to XDoc.
> Ross

Well, I have had some success now :)

I have the plugin working now and the sample glossary.html file works just
fine. :)

But, (and there usually is a 'but' with me!), I have had to it using
workarounds otherwise I just could not get it to go.

1. Mentioned previously, 'glossary-v10.dtd' and 'glossary-v10.mod' MUST be
in the /xdocs/directory otherwise they are not found and it will not work.
If not there, error message is saying they are not found and is pointing to
the xdocs directory.

2. To get rid of another resource not found error message, I had to put
copyover.xsl into the /resources/stylesheets/ directory.

I would be happier if workaround 1. was solved, in fact I think it must
before it is accepted.

Workaround 2. may be a necessity I don't know.

If anyone has ideas as to why the above is happening I'm all ears.

Should I maybe send in a patch for what I have so you guys aren’t working


View raw message