forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ferdinand Soethe <ferdin...@apache.org>
Subject lm question for our docs
Date Mon, 22 May 2006 08:39:42 GMT
I have a problem in the release rotation of our docs that might be
solved elegantly using lm.

The problem is as follows: In site.xml we have this sections

<versions tab="docs">
    <overview label="Overview" href="versions/index.html"/>
    <v0.8 label="0.8-dev" href="site:v0.80//index"/>
    <v0.7 label="0.7 (current)" href="site:v0.70//index"/>
    <v0.6 label="0.6" href="site:v0.60//index"/>
  </versions>

to create the versioned docs subtabs.
When creating a new release we will change this to

<versions tab="docs">
    <overview label="Overview" href="versions/index.html"/>
    <v0.9 label="0.9-dev" href="site:v0.90//index"/>
    <v0.8 label="0.8 (current)" href="site:v0.80//index"/>
    <v0.7 label="0.7" href="site:v0.70//index"/>
  </versions>

basically rotating the version number one down.

The problem is that the published release package will not have a
docs_0_90-directory because it would just bloat the package to include an (at
this point) exact copy of 0.8-docs as 0.9-docs.

Soon after however, when the realease is announced, we will publish
the very same docs to our Website and by then will have a
0.9-directory.

So what I'd like to do is create a lm:map-entry that is used as href
in <v0.9 label="0.9-dev" href="site:v0.90//index"/> and works like
this:

if there is a 0.9 directory in the static pages, point to it
if there isn't, point to the same directory on the forrest website.

That way we won't have to touch site after building the release
candidate, simply do an svn-copy of the current dev docs to the new
dev docs.

Is that possible, is it a good idea, will it work?

Thanks,
Ferdinand









--
Ferdinand Soethe


Mime
View raw message