You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by Diwaker Gupta <di...@gmail.com> on 2004/11/19 02:30:30 UTC
errors with text-output plugin
After most recent svn update, I get errors like these:
X [0] projects/index.txt
BROKEN: /home/diwaker/shared/forrest/site/content/xdocs/projects/linkmap-index.xml
(No such file or directory)
Also, it seems the build.xml file for plugins also has a problem.
There's a definition:
<property name="plugin.dir" value="${plugin-name}"/>
early on in build.xml, but the plugin-name property is not defined
until much later (eg, in the local-deploy target). Now the
local-deploy target uses ${plugin.dir} which subsitutes a literal
"${plugin-name}" and thus fails.
Simply using plugin-name instead of plugin.dir at all places will fix
this problem, since that is what eventually this substitution would
have achieved.
--
Diwaker Gupta
http://resolute.ucsd.edu/diwaker
Re: errors with text-output plugin
Posted by Rick Tessner <ri...@apache.org>.
Rick Tessner wrote:
> On Fri, 2004-11-19 at 01:40 +0000, Ross Gardler wrote:
>
>>Diwaker Gupta wrote:
>>
>>>After most recent svn update, I get errors like these:
>>>
>>>X [0] projects/index.txt
>>>BROKEN: /home/diwaker/shared/forrest/site/content/xdocs/projects/linkmap-index.xml
>>>(No such file or directory)
>>
>>Not sure about that one, that's Ricks baby :-)
>
>
> :)
>
> Yup, I'm suddenly seeing this too ... I've been trying to track down
> what happened here, but haven't had any luck yet. :(
>
> The odd thing is that some pages work, some don't and show that error.
> Hmmm ... will continue looking.
Okay, it looks like it's happening with any docs that have references to
site:* or ext:* (basically, refereencing anything in the site.xml).
ie. have things like <a href="site:somedoc">Some Doc</a>
Don't know why this stopped working, but I know what I'm looking for now. :)
--
Rick Tessner
rick@apache.org
Re: errors with text-output plugin
Posted by Rick Tessner <ri...@apache.org>.
On Fri, 2004-11-19 at 01:40 +0000, Ross Gardler wrote:
> Diwaker Gupta wrote:
> > After most recent svn update, I get errors like these:
> >
> > X [0] projects/index.txt
> > BROKEN: /home/diwaker/shared/forrest/site/content/xdocs/projects/linkmap-index.xml
> > (No such file or directory)
>
> Not sure about that one, that's Ricks baby :-)
:)
Yup, I'm suddenly seeing this too ... I've been trying to track down
what happened here, but haven't had any luck yet. :(
The odd thing is that some pages work, some don't and show that error.
Hmmm ... will continue looking.
> In the meantime you can simply cd into the plugin directory and do "ant
> local-deploy", that works.
Yup, that works. Thanks! If I solve the other problem above, I'll
take a crack at this ant config bit.
--
Rick Tessner <ri...@apache.org>
Re: errors with text-output plugin
Posted by Ross Gardler <rg...@apache.org>.
Diwaker Gupta wrote:
> After most recent svn update, I get errors like these:
>
> X [0] projects/index.txt
> BROKEN: /home/diwaker/shared/forrest/site/content/xdocs/projects/linkmap-index.xml
> (No such file or directory)
Not sure about that one, that's Ricks baby :-)
>
> Also, it seems the build.xml file for plugins also has a problem.
> There's a definition:
>
> <property name="plugin.dir" value="${plugin-name}"/>
>
> early on in build.xml, but the plugin-name property is not defined
> until much later (eg, in the local-deploy target). Now the
> local-deploy target uses ${plugin.dir} which subsitutes a literal
> "${plugin-name}" and thus fails.
>
> Simply using plugin-name instead of plugin.dir at all places will fix
> this problem, since that is what eventually this substitution would
> have achieved.
That was my doing, it did work the way you describe but I changed it
because each plugin now has a build file that needs to call the
local-deploy target. When that happens it passes in the plugin-name
property. The local-deploy needs to stay in the main build file as I
want to do a local-deploy-all target as well.
I do seem to have broken the interactive version of local-deploy though.
I'll fix it tomorrow (unless someone provides a patch before I get out
of bed).
In the meantime you can simply cd into the plugin directory and do "ant
local-deploy", that works.
Ross
Re: errors with text-output plugin
Posted by Ross Gardler <rg...@apache.org>.
Rick Tessner wrote:
> Diwaker Gupta wrote:
>
>> After most recent svn update, I get errors like these:
>>
>> X [0] projects/index.txt BROKEN:
>> /home/diwaker/shared/forrest/site/content/xdocs/projects/linkmap-index.xml
>>
>> (No such file or directory)
>
>
> I just committed a fix for this. The output.xmap for the plugins was
> being mounted a bit to early in the sitemap. I moved the <map:mount>
> down to where the other output formats get mounted and this appears to
> have resolved the problem.
>
> Hopefully this was the right thing to do. I'm not sure what the plan is
> for the mounting of the various plugin .xmap files and this was just a
> guess as to where the output one should go.
>
> Ross, could you cross-check this for me? Thanks Mr. Plugin Man! :)
Yeah, that seems to be the right place for it, but I must be losing my
title if others are correcting my mistakes :-)), or is it :-(
Note I have added a test framework to each plugin now. Just do ant test
in the plugin directory. This locally-deploys the plugin then builds the
plugin docs. This showed up another error with the plugin relating to my
recent extraction of the PDF stuff into a plugin.
It is now necessary to ether explicitly include the PDF plugin or to
disable the pdf link in skinconf.xml.
The fbit stuff that Thorsten is working on will remove this limitation.
Ross
Re: errors with text-output plugin
Posted by Rick Tessner <ri...@apache.org>.
Diwaker Gupta wrote:
> After most recent svn update, I get errors like these:
>
> X [0] projects/index.txt
> BROKEN: /home/diwaker/shared/forrest/site/content/xdocs/projects/linkmap-index.xml
> (No such file or directory)
I just committed a fix for this. The output.xmap for the plugins was
being mounted a bit to early in the sitemap. I moved the <map:mount>
down to where the other output formats get mounted and this appears to
have resolved the problem.
Hopefully this was the right thing to do. I'm not sure what the plan is
for the mounting of the various plugin .xmap files and this was just a
guess as to where the output one should go.
Ross, could you cross-check this for me? Thanks Mr. Plugin Man! :)
--
Rick Tessner
rick@apache.org