Mailing-List: contact dev-help@myfaces.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "MyFaces Development" <dev@myfaces.apache.org>
Received-SPF: pass (hermes.apache.org: domain of craigmcc@gmail.com designates
 64.233.170.193 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=Bkk91CuYl9eiUhH0l9BKIMlyGvFsBfwF9ci1Vxh2V4oYlVIbwDV/TmCXryRJqEDYGGMz4AyN7Avxh5U/rIGZFgOHPRRhPbhBYVbnjVS796r4+Slx/duoFVlVsR7O/Oz6VD2oROxFMJtDa5yXaE+NbL4LdT1TnRgtgmN6SAAZzYc=
Message-ID: <f8b39ace050527090639caf62a@mail.gmail.com>
Date: Fri, 27 May 2005 09:06:40 -0700
From: Craig McClanahan <craigmcc@gmail.com>
Reply-To: craigmcc@apache.org
To: MyFaces Development <dev@myfaces.apache.org>,
	Sean Schofield <sean.schofield@gmail.com>
Subject: Re: Sorry for all the SVN commits
Cc: Matthias Wessendorf <mwessendorf@gmail.com>
In-Reply-To: <2387fbc505052706156d364012@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <2387fbc505052514286a385fdc@mail.gmail.com>
	 <f8b39ace0505262350586aae19@mail.gmail.com>
	 <71235db4050527030184331b2@mail.gmail.com>
	 <2387fbc505052706156d364012@mail.gmail.com>

On 5/27/05, Sean Schofield <sean.schofield@gmail.com> wrote:
> What if we want to automate the build of the javadoc?  Can we just
> publish them to the website through ant using scp?  I'd hate to lose
> the automated publishing of the javadoc.
>=20

That approach makes sense to me.  You might also think about
publishing the "latest and greatest" javadocs that correspond to each
nightly build, but also keep separately the docs that correspond to
each release (milestone or whatever) so that people can refer back to
it.

(hmm ... need to set up this sort of thing for Shale now, too ...)

> Perhaps I could publish to my home directory using ant and then have a
> cron script on minotaur that cleans out the javadoc periodcially and
> copies the new ones from my home dir.  I'm open to ideas here.
>=20
> BTW it turns out the javadoc differences were not due to timestamps
> but due to a different version of the JDK on the build machine.
>=20
> sean
>=20
> Sorry for adding to your email avalanche Craig :-(
>=20

One gets used to it :-).

Craig


> On 5/27/05, Matthias Wessendorf <mwessendorf@gmail.com> wrote:
> > sound reasonable to me, to store JavaDoc not inside of SVN.
> >
> > .Matthias
> >
> > On 5/27/05, Craig McClanahan <craigmcc@gmail.com> wrote:
> > > On 5/25/05, Sean Schofield <sean.schofield@gmail.com> wrote:
> > > > I just reran the build script (for the website) on a new build
> > > > machine.  Evidently we ran into a timestamp issue again.  The good
> > > > news is that the website build should be automated and if we only
> > > > build it on my machine we won't have all those extra commits.
> > >
> > > You also wouldn't have those commits if the javadoc files in question
> > > were simply installed on a standard web server somewhere and then
> > > pointed at by the website, rather than being part of the website buil=
d
> > > process.
> > >
> > > I've become convinced (and this last email flood, on top of a week's
> > > worth of other mail that just made it worse, reinforces this feeling)
> > > that committing Struts 1.0 javadocs to our source repository was a
> > > mistake.  I would encourage the MyFaces folks to reconsider this as
> > > well.
> > >
> > > Craig
> > >
> >
> >
> > --
> > Matthias Wessendorf
> >
>