Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Received-SPF: pass (hermes.apache.org: local policy)
From: "Eric Pugh" <epugh@upstate.com>
To: "'Jakarta Commons Developers List'" <commons-dev@jakarta.apache.org>
Subject: RE: [configuration]Site update of howtos
Date: Tue, 15 Mar 2005 22:07:02 -0000
Message-ID: <022a01c529ab$51699eb0$098315ac@sagunto>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
In-Reply-To: <42374565.5080701@t-online.de>
Importance: Normal

Over in Turbine land we have the advantage of a separate turbine-site
project.   We have generic site doucmentation, and then the maven
generated docs seperated by version:
/ generic site docs
/2.3
/2.3.1
/2.4-M1

And so on.

What we could do is have 
/commons/configuration/  <- current site docs symlinked to
/commons/configuration/1.0
/commons/configuration/1.1/ <-- new site docs
/commons/configuration/1.0/ <-- old site docs

And provide a link to the 1.1 and 1.0 from both projects....

Eric

-----Original Message-----
From: Oliver Heger [mailto:oliver.heger@t-online.de] 
Sent: Tuesday, March 15, 2005 8:28 PM
To: Jakarta Commons Developer List
Subject: [configuration]Site update of howtos


Our current site seems to be very confusing for our users as can be seen

in multiple postings on the user list. The main reason is probably the 
user guide (the howtos), which describes the latest version in SVN 
rather than the 1.0 release, which is used by most users.

I have now applied a quick and dirty fix for this situation: I manually 
uploaded the 1.0 howtos on the server. Then I created two index pages 
for the old and new howtos and linked to them in the main navigation 
bar, analogous as for the API docs. In the index page for the SVN howtos

there is an explicit warning that this may not be compatible with the 
latest released version.

This is of course only a temporary solution because it requires manual 
processing on the server. I don't know how we should deal with this 
problem. Would it make sense to store both the old and new howtos in the

xdocs and let maven generate it all? I guess that would be the easiest
way.

Oliver

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org