On Tue, 22 Jan 2002, Ted Husted wrote:
> Date: Tue, 22 Jan 2002 05:56:56 -0500
> From: Ted Husted <[EMAIL PROTECTED]>
> Reply-To: Struts Developers List <[EMAIL PROTECTED]>
> To: Struts Developers List <[EMAIL PROTECTED]>
> Subject: Re: Struts Next
>
> Martin Cooper wrote:
> >
> > ----- Original Message -----
> > From: "Ted Husted" <[EMAIL PROTECTED]>
> > To: "Struts Developers List" <[EMAIL PROTECTED]>
> > Sent: Monday, January 21, 2002 3:52 AM
> > Subject: Re: Struts Next
> >
> > > Right now, we're exploding the struts-documentation WAR to create the
> > > Web site.
> >
> > Having worked with the Anakia way (a la commons and site2) a little bit now,
> > I have to say that I like that web site update process much better than our
> > exploding war file. It's simpler and quicker. I wonder what other folks
> > think about migrating to this process at some point?
> >
> > This would also release us from the one-to-one mapping we currently have
> > between what's bundled with the release (i.e. struts-documentation.war) and
> > what's on the public web site. (See below.)
>
> I don't think it's really an "Anakia" issue, just a matter of whether we
> check in the html files that are generated by the Digester, and then
> check those out again at the Web site.
>
I personally don't care for that aspect of the way jakarta-site2 works --
I'd rather see us check in only the XML source files, and run the
generator on daedalus directly to create the HTML pages. Other than that,
I'm fine with the concept of decoupling the web site content from the
struts-documentation WARs (as long as we mirror both the latest official
release docs and the currently nightly docs on the web site as well).
The only potential cost of this is that we have to maintain "duplicate"
content for the web site pages, to some extent. If the web site page is
filled with hyperlinks to the relevant stuff instead of repeating it all,
this should not be that big a problem -- but it's something to keep in
mind.
> Something that I set up for myself is a build-website target in the
> build.xml. With that and a build-doc script and batch file, we'd be at
> the same place site2 is.
>
I like this -- but let's run "ant build-website" on daedalus instead of
your development machine :-).
> But then there would be a definite 1:1 mapping between the nightly build
> and the current website, unless we set it to check out a branch, but
> that seems like a long term maintenance hassle.
>
How about a one-page website with:
Latest news
Links to resources
Link to 1.0.1 doc bundle and downloads
Link to HEAD doc bundle and downloads
Links to Bugzilla:
Query 1.0 branch bugs
Query HEAD branch bugs
Submit a new bug
... other stuff as needed ...
This minimizes our maintenance hassles, decouples things as desired, and
lets both current-release users and HEAD branch users get what they need.
(NOTE: One of the things I'm also cooking up is a consolidated Javadocs
for all the Commons packages - this will be a useful link off the Struts
pages as well)
Craig
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
