You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by Ross Gardler <rg...@wkwyw.net> on 2002/11/08 00:31:31 UTC
Something is breraking my build
I have been moving a project from an earlier version of Forrest and have
come across a very strange problem. Unfortunately, I cannot reliably
reproduce it yet, I'm trying to find out if anyonw else has come across it.
Twice I have built the project up from scratch in this way:
created a seed project
copied across the source files
Edited skinconf.xml accordingly
Built site
Everything is OK except SVG serilaistation (as expected)
Then I go on to the following:
copy forrest sitemap to src/documentation
add SVG serialisation to sitemap
build site
SVG serialisation still not working
This is where I get a bit hazy as to what I have done as there are a
number of changes to my sitemap and image files etc in order to get the
SVG to work. But in both cases the same thing has happened, eventually
the site won;t build complaining of a missing index.html.
Of course the first thing I have done to rectify the problem is ensur
that I haven't broken the sitemap, so I remove my custom one. But this
makes no difference. I have checked that my xdocs are still OK (they
are) and that they are copied into the context directory (they are).
Everything seems normal except it won't build.
The tail of the output from forrest is copied below. Has anyone seen
this behaviour before, is it too late at night for me to see what on
earth I am doing wrong?
Ross
Forrest output
--------------
<snip/>
check-contentdir:
ensure-content:
validate-xdocs:
5 file(s) have been successfully validated.
...validated xdocs
validate-skins-stylesheets:
validate-skins:
validate-stylesheets:
validate:
copy-conf:
copy-sitemap:
copy-xdocs:
Copying 55 files to
/home/rgardler/projects/saafe/research/build/tmp/context/content/xdocs
copy-stylesheets:
copy-images:
Copying 32 files to
/home/rgardler/projects/saafe/research/build/tmp/context/resources/images
copy-schema:
copy-content:
copy-lib:
copy-classes:
copy-skins:
copy-skinconf:
Copying 1 file to /home/rgardler/projects/saafe/research/build/tmp/context
copy-status:
project-context:
prepare-context:
-prepare-classpath:
-site:
Deleting directory /home/rgardler/projects/saafe/research/build/tmp/work
Created dir: /home/rgardler/projects/saafe/research/build/tmp/work
Setup... done.
Initializing... ready, let's go :-)
* [0]
-> [broken link] index.html <-
disposing... done.
Re: Skin validation
Posted by Jeff Turner <je...@apache.org>.
On Fri, Nov 08, 2002 at 05:53:14PM +1100, David Crossley wrote:
> Jeff, where did you get the brilliant
> src/resources/schema/relaxng/xslt.rng
It's James Clark's:
http://thaiopensource.com/relaxng/
linked to from the RNG home page.
> I would like to use it elsewhere, but not
> sure of its origin. Do we need to credit
> anyone with developing it?
I'll add a README to the directory.
--Jeff
> --David
>
>
Re: build-time validation of core config
Posted by Jeff Turner <je...@apache.org>.
On Mon, Nov 11, 2002 at 01:37:20PM +1100, David Crossley wrote:
> Recent changes now provide for build-time validation of
> the core Forrest configuration files.
> * all skinconf.xml
> * all sitemap.xmap
> * all XSL stylesheets
Good stuff, thanks. I copied the sitemap validation into
forrest.build.xml as well, so all projects have their sitemaps validated:
validate-sitemap:
Error at URL "file:/tmp/testsite/src/documentation/sitemap.xmap", line
number 104, column number 46: attribute "cheesy" not allowed at this
point; ignored
BUILD FAILED
file:/home/jeff/apache/xml/xml-forrest/build/dist/shbat/bin/../forrest.build.xml:742:
Validation failed, messages should have been provided.
--Jeff
>
> --David
Re: Skin validation
Posted by David Crossley <cr...@indexgeo.com.au>.
Jeff, where did you get the brilliant
src/resources/schema/relaxng/xslt.rng
I would like to use it elsewhere, but not
sure of its origin. Do we need to credit
anyone with developing it?
--David
build-time validation of core config
Posted by David Crossley <cr...@indexgeo.com.au>.
Recent changes now provide for build-time validation of
the core Forrest configuration files.
* all skinconf.xml
* all sitemap.xmap
* all XSL stylesheets
This shows up an error with the new editor sitemap, so
this is commented-out for now.
src/resources/editor/editor.xmap
It uses an attribute for its map:pipeline called cacheable="true"
However, according to Cocoon there is no such attribute.
Rather it uses named pipelines. Does anyone know how to
properly express that? Then we can switch on validation of
all sitemaps.
--David
Re: Skin validation
Posted by David Crossley <cr...@indexgeo.com.au>.
Jeff Turner wrote:
> David Crossley wrote:
<snip/>
>
> > We are working on the same sort of thing at cocoon-dev, build-time
> > validation of core config files.
>
> Oh yes.. currently, forrest.build.xml doesn't validate user sitemaps. Is
> the cocoon RNG sitemap schema in a decent state?
It is at a basic state, and yes, working. The rules
needed to be simplified to get things started. Now they
can be tightened. I will bring that to Forrest soon.
--David
Re: Skin validation
Posted by Jeff Turner <je...@apache.org>.
On Fri, Nov 08, 2002 at 04:59:56PM +1100, David Crossley wrote:
> Jeff Turner wrote:
> > David Crossley wrote:
> <snip/>
> >
> > > Should i add a general validation target into the top-level
> > > xml-forrest/build.xml that does various validation of Forrest's core
> > > stylesheets and config files? It may better belong at that level -
> > > forrest-shbat/forrest.build.xml is getting quite full.
> >
> > Yes, that's probably the best solution..
> > Only, because validation requires Ant 1.6, one couldn't build Forrest
> > with 'ant' anymore. Everyone would need to use build.{sh,bat}.
> >
> > +1 despite that.. it can always be fixed later.
>
> The RELAX NG validation with Jing would work. That is what i intended
> to use. Great, i will proceed.
Good, thanks
> We are working on the same sort of thing at cocoon-dev, build-time
> validation of core config files.
Oh yes.. currently, forrest.build.xml doesn't validate user sitemaps. Is
the cocoon RNG sitemap schema in a decent state?
--Jeff
> --David
>
>
Re: Skin validation
Posted by David Crossley <cr...@indexgeo.com.au>.
Jeff Turner wrote:
> David Crossley wrote:
<snip/>
>
> > Should i add a general validation target into the top-level
> > xml-forrest/build.xml that does various validation of Forrest's core
> > stylesheets and config files? It may better belong at that level -
> > forrest-shbat/forrest.build.xml is getting quite full.
>
> Yes, that's probably the best solution..
> Only, because validation requires Ant 1.6, one couldn't build Forrest
> with 'ant' anymore. Everyone would need to use build.{sh,bat}.
>
> +1 despite that.. it can always be fixed later.
The RELAX NG validation with Jing would work. That
is what i intended to use. Great, i will proceed.
We are working on the same sort of thing at cocoon-dev,
build-time validation of core config files.
--David
Re: Skin validation
Posted by Jeff Turner <je...@apache.org>.
On Fri, Nov 08, 2002 at 03:34:34PM +1100, David Crossley wrote:
> Jeff Turner wrote:
> > David Crossley wrote:
> <snip/>
>
> > > Ah i see. I am not using a project-specific skin.
> > >
> > > I was wanting it to do validation of the main
> > > forrest-site skin, etc. both during 'build.sh docs'
> > > and the 'forrest' build ... i was trying some mods to
> > > the "forrest-site" and "basic" skins.
> > >
> > > I will keep looking. It must be a strange setting of
> > > the forrest.validate.* properties.
> >
> > Oh.. no, it deliberately doesn't validate those, on the assumption that
> > Forrest wouldn't distribute broken stylesheets, and having every user
> > validate them would slow things down. If you think it's a good idea, we
> > can add a forrest.validate.internal.skins (or something) property.
>
> I was wondering if that might be the issue.
> Yes, i think that it is vitally important to validate
> the "internal" skins, as well as all config files,
> and xdocs, and sitemaps, and stuff. Otherwise how do
> we *know* that we are not distributing broken stuff.
We Forrest committers are immune to the stupid mistakes that users make!
;)
> I presumed that during "build docs" Forrest is treating
> itself as yet another project. So i presumed that it would
> therefore validate its own stuff (the targets do get called).
> I now gather that this is not so.
If Forrest had a custom skin in src/documentation/skins, it would get
validated.
> Yes, i agree that every user should not need to do this every time.
> However, if they are working on core Forrest stuff (i.e. a developer)
> then we want them to validate before sending patches.
>
> Should i add a general validation target into the top-level
> xml-forrest/build.xml that does various validation of Forrest's core
> stylesheets and config files? It may better belong at that level -
> forrest-shbat/forrest.build.xml is getting quite full.
Yes, that's probably the best solution..
Only, because validation requires Ant 1.6, one couldn't build Forrest
with 'ant' anymore. Everyone would need to use build.{sh,bat}.
+1 despite that.. it can always be fixed later.
--Jeff
> --David
>
>
Re: Skin validation
Posted by David Crossley <cr...@indexgeo.com.au>.
Jeff Turner wrote:
> David Crossley wrote:
<snip/>
> > Ah i see. I am not using a project-specific skin.
> >
> > I was wanting it to do validation of the main
> > forrest-site skin, etc. both during 'build.sh docs'
> > and the 'forrest' build ... i was trying some mods to
> > the "forrest-site" and "basic" skins.
> >
> > I will keep looking. It must be a strange setting of
> > the forrest.validate.* properties.
>
> Oh.. no, it deliberately doesn't validate those, on the assumption that
> Forrest wouldn't distribute broken stylesheets, and having every user
> validate them would slow things down. If you think it's a good idea, we
> can add a forrest.validate.internal.skins (or something) property.
I was wondering if that might be the issue.
Yes, i think that it is vitally important to validate
the "internal" skins, as well as all config files,
and xdocs, and sitemaps, and stuff. Otherwise how do
we *know* that we are not distributing broken stuff.
I presumed that during "build docs" Forrest is treating
itself as yet another project. So i presumed that it would
therefore validate its own stuff (the targets do get called).
I now gather that this is not so.
Yes, i agree that every user should not need to do this
every time. However, if they are working on core Forrest
stuff (i.e. a developer) then we want them to validate
before sending patches.
Should i add a general validation target into the top-level
xml-forrest/build.xml that does various validation of
Forrest's core stylesheets and config files? It may better
belong at that level - forrest-shbat/forrest.build.xml
is getting quite full.
--David
Skin validation (Re: Something is breraking my build)
Posted by Jeff Turner <je...@apache.org>.
On Fri, Nov 08, 2002 at 02:54:09PM +1100, David Crossley wrote:
> Jeff Turner wrote:
> > David Crossley wrote:
> > ...
> > > > They will with recent versions of Forrest, which validate skin XSLTs.
> > >
> > > I know that Forrest intends to, but i wonder if it is
> > > actually doing this validation. We should see the message:
> > > ...validated stylesheet
> >
> > yes..
> >
> > > from the Ant target 'validate-stylesheets:'
> >
> > validate-skins-stylesheets
> >
> > > However, i am not seeing it with my build. Also, i tried to
> > > deliberately break a stylesheet, but i do not see a validation error. I
> > > am currently investigating this.
> >
> > Works for me with a custom skin in src/documentation/skins/*:
> >
> > validate-skins-stylesheets:
> > Error at URL
> > "file:/tmp/testproj/src/documentation/skins/blueness/xslt/html/site2xhtml.xsl",
> > line number 29, column number 13: element "foo" from namespace
> > "http://www.w3.org/1999/XSL/Transform" not allowed in this context
>
> Ah i see. I am not using a project-specific skin.
>
> I was wanting it to do validation of the main
> forrest-site skin, etc. both during 'build.sh docs'
> and the 'forrest' build ... i was trying some mods to
> the "forrest-site" and "basic" skins.
>
> I will keep looking. It must be a strange setting of
> the forrest.validate.* properties.
Oh.. no, it deliberately doesn't validate those, on the assumption that
Forrest wouldn't distribute broken stylesheets, and having every user
validate them would slow things down. If you think it's a good idea, we
can add a forrest.validate.internal.skins (or something) property.
--Jeff
> --David
>
>
Re: Something is breraking my build
Posted by David Crossley <cr...@indexgeo.com.au>.
Jeff Turner wrote:
> David Crossley wrote:
> ...
> > > They will with recent versions of Forrest, which validate skin XSLTs.
> >
> > I know that Forrest intends to, but i wonder if it is
> > actually doing this validation. We should see the message:
> > ...validated stylesheet
>
> yes..
>
> > from the Ant target 'validate-stylesheets:'
>
> validate-skins-stylesheets
>
> > However, i am not seeing it with my build. Also, i tried to
> > deliberately break a stylesheet, but i do not see a validation error. I
> > am currently investigating this.
>
> Works for me with a custom skin in src/documentation/skins/*:
>
> validate-skins-stylesheets:
> Error at URL
> "file:/tmp/testproj/src/documentation/skins/blueness/xslt/html/site2xhtml.xsl",
> line number 29, column number 13: element "foo" from namespace
> "http://www.w3.org/1999/XSL/Transform" not allowed in this context
Ah i see. I am not using a project-specific skin.
I was wanting it to do validation of the main
forrest-site skin, etc. both during 'build.sh docs'
and the 'forrest' build ... i was trying some mods to
the "forrest-site" and "basic" skins.
I will keep looking. It must be a strange setting of
the forrest.validate.* properties.
--David
Re: Something is breraking my build
Posted by Jeff Turner <je...@apache.org>.
On Fri, Nov 08, 2002 at 02:15:27PM +1100, David Crossley wrote:
...
> > They will with recent versions of Forrest, which validate skin XSLTs.
>
> I know that Forrest intends to, but i wonder if it is
> actually doing this validation. We should see the message:
> ...validated stylesheet
yes..
> from the Ant target 'validate-stylesheets:'
validate-skins-stylesheets
> However, i am not seeing it with my build. Also, i tried to
> deliberately break a stylesheet, but i do not see a validation error. I
> am currently investigating this.
Works for me with a custom skin in src/documentation/skins/*:
validate-skins-stylesheets:
Error at URL
"file:/tmp/testproj/src/documentation/skins/blueness/xslt/html/site2xhtml.xsl",
line number 29, column number 13: element "foo" from namespace
"http://www.w3.org/1999/XSL/Transform" not allowed in this context
--Jeff
> --David
>
>
>
Re: Something is breraking my build
Posted by David Crossley <cr...@indexgeo.com.au>.
On Fri, 2002-11-08 at 13:46, Jeff Turner wrote:
> On Fri, Nov 08, 2002 at 10:45:45AM +1100, Peter Donald wrote:
> > On Fri, 8 Nov 2002 10:31, Ross Gardler wrote:
> > > This is where I get a bit hazy as to what I have done as there are a
> > > number of changes to my sitemap and image files etc in order to get the
> > > SVG to work. But in both cases the same thing has happened, eventually
> > > the site won;t build complaining of a missing index.html.
> > >
> > > Of course the first thing I have done to rectify the problem is ensur
> > > that I haven't broken the sitemap, so I remove my custom one. But this
> > > makes no difference. I have checked that my xdocs are still OK (they
> > > are) and that they are copied into the context directory (they are).
> > > Everything seems normal except it won't build.
> > >
> > > The tail of the output from forrest is copied below. Has anyone seen
> > > this behaviour before, is it too late at night for me to see what on
> > > earth I am doing wrong?
> >
> > That happened to me all the time when I broke one of the xslt sheets. Make
> > sure that all your xslts are valid. The content xmls, skinconfig and sitemap
> > should be validated for you. However the xslts (and supporting resources?)
> > will not give you a warning if they are broken.
>
> They will with recent versions of Forrest, which validate skin XSLTs.
I know that Forrest intends to, but i wonder if it is
actually doing this validation. We should see the message:
...validated stylesheet
from the Ant target 'validate-stylesheets:'
However, i am not seeing it with my build. Also, i tried
to deliberately break a stylesheet, but i do not see a
validation error. I am currently investigating this.
--David
Re: Something is breraking my build
Posted by Jeff Turner <je...@apache.org>.
On Fri, Nov 08, 2002 at 10:45:45AM +1100, Peter Donald wrote:
> On Fri, 8 Nov 2002 10:31, Ross Gardler wrote:
> > This is where I get a bit hazy as to what I have done as there are a
> > number of changes to my sitemap and image files etc in order to get the
> > SVG to work. But in both cases the same thing has happened, eventually
> > the site won;t build complaining of a missing index.html.
> >
> > Of course the first thing I have done to rectify the problem is ensur
> > that I haven't broken the sitemap, so I remove my custom one. But this
> > makes no difference. I have checked that my xdocs are still OK (they
> > are) and that they are copied into the context directory (they are).
> > Everything seems normal except it won't build.
> >
> > The tail of the output from forrest is copied below. Has anyone seen
> > this behaviour before, is it too late at night for me to see what on
> > earth I am doing wrong?
>
> That happened to me all the time when I broke one of the xslt sheets. Make
> sure that all your xslts are valid. The content xmls, skinconfig and sitemap
> should be validated for you. However the xslts (and supporting resources?)
> will not give you a warning if they are broken.
They will with recent versions of Forrest, which validate skin XSLTs.
--Jeff
Re: Something is breraking my build
Posted by Peter Donald <pe...@apache.org>.
On Fri, 8 Nov 2002 10:31, Ross Gardler wrote:
> This is where I get a bit hazy as to what I have done as there are a
> number of changes to my sitemap and image files etc in order to get the
> SVG to work. But in both cases the same thing has happened, eventually
> the site won;t build complaining of a missing index.html.
>
> Of course the first thing I have done to rectify the problem is ensur
> that I haven't broken the sitemap, so I remove my custom one. But this
> makes no difference. I have checked that my xdocs are still OK (they
> are) and that they are copied into the context directory (they are).
> Everything seems normal except it won't build.
>
> The tail of the output from forrest is copied below. Has anyone seen
> this behaviour before, is it too late at night for me to see what on
> earth I am doing wrong?
That happened to me all the time when I broke one of the xslt sheets. Make
sure that all your xslts are valid. The content xmls, skinconfig and sitemap
should be validated for you. However the xslts (and supporting resources?)
will not give you a warning if they are broken.
--
Cheers,
Peter Donald
----------------------------------------------
Money is how people with no talent keep score.
----------------------------------------------
Re: Something is breraking my build
Posted by Jeff Turner <je...@apache.org>.
On Fri, Nov 08, 2002 at 02:07:13PM +0000, Ross Gardler wrote:
> Ross Gardler wrote:
> >
> >
> >Jeff Turner wrote:
> >
> >>On Fri, Nov 08, 2002 at 12:19:39PM +0000, Ross Gardler wrote:
> >>Could you perhaps send me (offlist) a tgz of the breaking project?
> >
> >
> >I'll do a whole new one using the process above (just in case I missed
> >somehting in the CVS update) and send it to you in a few minutes.
>
> Hmmm...
>
> I just tried to reproduce this again and couldn't. This means either I
> missed something in the CVS update or I am just being especially stupid
> today (or most likely both).
:/ .. well we'll soon be able to validate project sitemaps, which should
eliminate a class of weird errors.
> Anyway, it seems to work now, thanks to everyone for their help and
> applogies for being one of "those stupid users".
We love all our users ;P
--Jeff
> Ross
>
Re: Something is breraking my build
Posted by Ross Gardler <ro...@saafe.org>.
Ross Gardler wrote:
>
> Anyway, it seems to work now, thanks to everyone for their help and
> applogies for being one of "those stupid users".
It happened again, it seems to be intermittent, perhaps I'm not so
stupid afterall!
This time I'm not editing the sitemap (although I do have an unmodified
copy of it and the forrest-site skins in my src and resources/skins
directories). I changed the trail settings in
skinconf.xml and rebuilt the site. I still had the old trail settings
(pointing to apache sites), so I deleted the build directory and reran
forrest. I'm now back to the samr error (broken link to index.html).
I'll try and reproduce it in a project I can send (to Jeff off list) for
diagnosis.
Ross
Re: Something is breraking my build
Posted by Ross Gardler <rg...@wkwyw.net>.
Ross Gardler wrote:
>
>
> Jeff Turner wrote:
>
>> On Fri, Nov 08, 2002 at 12:19:39PM +0000, Ross Gardler wrote:
>> Could you perhaps send me (offlist) a tgz of the breaking project?
>
>
> I'll do a whole new one using the process above (just in case I missed
> somehting in the CVS update) and send it to you in a few minutes.
Hmmm...
I just tried to reproduce this again and couldn't. This means either I
missed something in the CVS update or I am just being especially stupid
today (or most likely both).
Anyway, it seems to work now, thanks to everyone for their help and
applogies for being one of "those stupid users".
Ross
Re: Something is breraking my build
Posted by Ross Gardler <rg...@wkwyw.net>.
Jeff Turner wrote:
> On Fri, Nov 08, 2002 at 12:19:39PM +0000, Ross Gardler wrote:
>
>>Ross Gardler wrote:
>
> ....
>
>>Here is a precise log of what I have done:
>>
>>mkdir tmp
>>cd tmp
>>forrest seed
>>forrest
>>
>>- Build succesful
>>
>>cp /ext/openSource/xml-forrest/src/resources/conf/sitemap.xmap
>>./src/documentation/
>>forrest
>>
>>- Build succesful
>>
>>In src/documentation/sitemap.xmap I commented out the root element, thus
>>breaking the sitemap.
>>
>>
>>forrest now outputs:
>>
>>Setup... done.
>>Iniitializing... ready, let's go :-)
>> * [0]
>>-> [broken link] index.html <-
>>
>>OK, so fix the problem, by uncommenting the root element of the sitemap.
>>
>>forrest gives same results.
>>
>>So delete all the cache info:
>>
>>rm -Rf build
>>
>>forrest still does the same.
>
>
> That is really weird. I went through exactly what you've describe with a
> clean rebuilt Forrest, and the post-fix build worked. In fact I didn't
> even need the rm -Rf build.
>
> Are you sure you have all of Forrest? Ie, updated with 'cvs up -dP'?
Just did this to make sure, only one file was different:
src/resources/fesh-site/forrest.properties, which was the addition of
the (commented out) avalon skin.
>
> Could you perhaps send me (offlist) a tgz of the breaking project?
I'll do a whole new one using the process above (just in case I missed
somehting in the CVS update) and send it to you in a few minutes.
Ross
Re: Something is breraking my build
Posted by Jeff Turner <je...@apache.org>.
On Fri, Nov 08, 2002 at 12:19:39PM +0000, Ross Gardler wrote:
> Ross Gardler wrote:
....
> Here is a precise log of what I have done:
>
> mkdir tmp
> cd tmp
> forrest seed
> forrest
>
> - Build succesful
>
> cp /ext/openSource/xml-forrest/src/resources/conf/sitemap.xmap
> ./src/documentation/
> forrest
>
> - Build succesful
>
> In src/documentation/sitemap.xmap I commented out the root element, thus
> breaking the sitemap.
>
>
> forrest now outputs:
>
> Setup... done.
> Iniitializing... ready, let's go :-)
> * [0]
> -> [broken link] index.html <-
>
> OK, so fix the problem, by uncommenting the root element of the sitemap.
>
> forrest gives same results.
>
> So delete all the cache info:
>
> rm -Rf build
>
> forrest still does the same.
That is really weird. I went through exactly what you've describe with a
clean rebuilt Forrest, and the post-fix build worked. In fact I didn't
even need the rm -Rf build.
Are you sure you have all of Forrest? Ie, updated with 'cvs up -dP'?
> Do I need to delete stuff in the forrest directory as well? If so
> shouldn't this be handled by the build process.
There is no state info stored in under the shbat distribution. The idea
is that it's copied in /usr/local or somewhere read-only and never
touched again. This can be verified with chmod -R -w {shbat dir}.
Could you perhaps send me (offlist) a tgz of the breaking project?
--Jeff
> Ross
>
Re: Something is breraking my build
Posted by Ross Gardler <rg...@wkwyw.net>.
Ross Gardler wrote:
> I have tried deleting the build directory and runnng forrest again, but
> no joy. I think this may be related in some way but I am still able to
> seed a new project and build that, so I don't think the problem is in
> the Forrest stuff, rather it is in my project somewhere.
>
> I will start the whole migration thing again from scratch and see if I
> can reproduce this error. Maybe I can be a little clearer about the
> final steps.
With all your help, I've managed to narrow the problem down. I don't
have a solution, but I can reproduce the problem reliably...
I started again, this time working with only a seed project. It seems
that what I have done is broken the sitemap. Fair enough, a broken
sitemap shouldn't work (but a better error would help). Anyway, I should
be able to get back to a working project once the sitemap is corrected
but I can't.
Here is a precise log of what I have done:
mkdir tmp
cd tmp
forrest seed
forrest
- Build succesful
cp /ext/openSource/xml-forrest/src/resources/conf/sitemap.xmap
./src/documentation/
forrest
- Build succesful
In src/documentation/sitemap.xmap I commented out the root element, thus
breaking the sitemap.
forrest now outputs:
Setup... done.
Iniitializing... ready, let's go :-)
* [0]
-> [broken link] index.html <-
OK, so fix the problem, by uncommenting the root element of the sitemap.
forrest gives same results.
So delete all the cache info:
rm -Rf build
forrest still does the same.
Do I need to delete stuff in the forrest directory as well? If so
shouldn't this be handled by the build process.
Ross
Re: Something is breraking my build
Posted by Ross Gardler <rg...@wkwyw.net>.
David Crossley wrote:
> Ross Gardler wrote:
> <snip/>
>
>>-site:
>>Deleting directory /home/rgardler/projects/saafe/research/build/tmp/work
>>Created dir: /home/rgardler/projects/saafe/research/build/tmp/work
>>
>>Setup... done.
>>Initializing... ready, let's go :-)
>> * [0]
>>-> [broken link] index.html <-
>>
>>disposing... done.
>
>
> This may be off target, but i saw a similar problem with
> Cocoon. See this workaround ...
> http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=103501324917674
>
> By the way, why is there not a 'clean' target in Forrest build.
The symptoms are the same, but the cause seems to be different. This
thread provides two workaraounds, one is to comment out the SVG
serializer stuff, which does not work. The other is to:
build.sh clean
build.sh
build.sh site
The middle build builds cocoon itself and the thread indicates that this
may be a problem with cocoon blocks, which are only a part of the the
2.1 CVS branch. Is Forrest using the 2.1 branch?
I have tried deleting the build directory and runnng forrest again, but
no joy. I think this may be related in some way but I am still able to
seed a new project and build that, so I don't think the problem is in
the Forrest stuff, rather it is in my project somewhere.
I will start the whole migration thing again from scratch and see if I
can reproduce this error. Maybe I can be a little clearer about the
final steps.
Ross
Re: Something is breraking my build
Posted by David Crossley <cr...@indexgeo.com.au>.
Ross Gardler wrote:
<snip/>
>
> -site:
> Deleting directory /home/rgardler/projects/saafe/research/build/tmp/work
> Created dir: /home/rgardler/projects/saafe/research/build/tmp/work
>
> Setup... done.
> Initializing... ready, let's go :-)
> * [0]
> -> [broken link] index.html <-
>
> disposing... done.
This may be off target, but i saw a similar problem with
Cocoon. See this workaround ...
http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=103501324917674
By the way, why is there not a 'clean' target in Forrest build.
--David
Re: Something is breraking my build
Posted by Ross Gardler <rg...@wkwyw.net>.
Jeff Turner wrote:
> On Thu, Nov 07, 2002 at 11:31:31PM +0000, Ross Gardler wrote:
>
<snip/>
>
>>add SVG serialisation to sitemap
>>build site
>>
>>SVG serialisation still not working
>
>
> Btw, there's a section in your-project.html about adding SVG.
Yes, I was following that but it didn;t work. However, I'll revisit this
problem when I can get the site to build again - probably just some
stupid mistake on my part.
>>This is where I get a bit hazy as to what I have done as there are a
>>number of changes to my sitemap and image files etc in order to get the
>>SVG to work. But in both cases the same thing has happened, eventually
>>the site won;t build complaining of a missing index.html.
>>
>>Of course the first thing I have done to rectify the problem is ensur
>>that I haven't broken the sitemap, so I remove my custom one. But this
>>makes no difference.
>
>
> I gather you don't have a custom skin, so changing the sitemap was the
> only change..? Did you delete the whole build/ directory after changing
> the sitemap? I suspect the build process caches bad stuff in build/tmp
> or somewhere. Also, the build apparently no longer overwrites
> build/site/. I'm not sure exactly how that works.
I had a custom skin in the original project, but have not yet brought
that across into the new one. So, yes, I am only changing the sitemap. I
have deleted the whole build structure to ensure there is no cacheing
issues.
>
>
>>I have checked that my xdocs are still OK (they
>>are) and that they are copied into the context directory (they are).
>>Everything seems normal except it won't build.
>>
>>The tail of the output from forrest is copied below. Has anyone seen
>>this behaviour before, is it too late at night for me to see what on
>>earth I am doing wrong?
>
>
> Have a look at build/tmp/context/WEB-INF/logs/error.log. It should
> contain useful stuff.
error.log is empty. I have checked the sitemap.log and it confirms that
I am using the forrest-site skin.
Ross
>
>
> --Jeff
>
>
>
>>Ross
>>
>
Re: Something is breraking my build
Posted by Jeff Turner <je...@apache.org>.
On Thu, Nov 07, 2002 at 11:31:31PM +0000, Ross Gardler wrote:
> I have been moving a project from an earlier version of Forrest and have
> come across a very strange problem. Unfortunately, I cannot reliably
> reproduce it yet, I'm trying to find out if anyonw else has come across it.
>
> Twice I have built the project up from scratch in this way:
>
> created a seed project
> copied across the source files
> Edited skinconf.xml accordingly
> Built site
>
> Everything is OK except SVG serilaistation (as expected)
>
> Then I go on to the following:
>
> copy forrest sitemap to src/documentation
Btw, the sitemap->skin stylesheets changed last week, from {dir} and
{resources} to a single {path}. This had the effect of fubar'ing
everyone's custom sitemaps or custom skins (unless both were overridden),
and sparked the thread about backwards-compat.
> add SVG serialisation to sitemap
> build site
>
> SVG serialisation still not working
Btw, there's a section in your-project.html about adding SVG.
> This is where I get a bit hazy as to what I have done as there are a
> number of changes to my sitemap and image files etc in order to get the
> SVG to work. But in both cases the same thing has happened, eventually
> the site won;t build complaining of a missing index.html.
>
> Of course the first thing I have done to rectify the problem is ensur
> that I haven't broken the sitemap, so I remove my custom one. But this
> makes no difference.
I gather you don't have a custom skin, so changing the sitemap was the
only change..? Did you delete the whole build/ directory after changing
the sitemap? I suspect the build process caches bad stuff in build/tmp
or somewhere. Also, the build apparently no longer overwrites
build/site/. I'm not sure exactly how that works.
> I have checked that my xdocs are still OK (they
> are) and that they are copied into the context directory (they are).
> Everything seems normal except it won't build.
>
> The tail of the output from forrest is copied below. Has anyone seen
> this behaviour before, is it too late at night for me to see what on
> earth I am doing wrong?
Have a look at build/tmp/context/WEB-INF/logs/error.log. It should
contain useful stuff.
--Jeff
> Ross
>