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 (asf.osuosl.org: domain of phil.steitz@gmail.com designates
 64.233.162.194 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:in-reply-to:mime-version:content-type:references;
        b=hCdLD+I34srQCvn0bAxSAmXZMbBjJ1jD+5w9dPfetj6M5wpaLBd8w7JCOi7M/HFrguM2xjBPLLnO4ZEeYC2rAGmIMEHx4upqDv5FS+98Fapu8W1tnZyC8AGc0utMkvSWVFgM6+OWzawHGYUaGimMvif6PpcXnLq315J3q4a7tQk=
Message-ID: <8a81b4af050911133060619f40@mail.gmail.com>
Date: Sun, 11 Sep 2005 13:30:29 -0700
From: Phil Steitz <phil.steitz@gmail.com>
Reply-To: phil.steitz@gmail.com
To: Jakarta Commons Developers List <commons-dev@jakarta.apache.org>
Subject: Re: [commons-build] Site build problem
In-Reply-To: <43248FFB.5040401@apache.org>
Mime-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_8526_13213743.1126470629584"
References: <1c661f2f05090118553501ffbe@mail.gmail.com>
	 <554CD11B-1D4F-439D-BEBB-0B3753705535@mac.com>
	 <30AFA56A-6E49-4DEE-8F36-70DC4D6B90F8@mac.com>
	 <1c661f2f050903010255fee6e@mail.gmail.com>
	 <1c661f2f05090911066f21fa5a@mail.gmail.com>
	 <1c661f2f05090914524f42b194@mail.gmail.com>
	 <001b01c5b59e$77b618d0$0200a8c0@DELL1800>
	 <8a81b4af050910081569c0f391@mail.gmail.com>
	 <8a81b4af050911130616652b50@mail.gmail.com>
	 <43248FFB.5040401@apache.org>

------=_Part_8526_13213743.1126470629584
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On 9/11/05, Brett Porter <brett@apache.org> wrote:
>=20
> Hi Phil.
>=20
> Phil Steitz wrote:
>=20
> >There does not appear to be a reasonable way to make our customized
> >site.jslwork with both pre- and post-
> >1.9 versions of the maven xdoc plugin. The best solution is to upgrade t=
o
> >1.9+ before generating commons sites. I also just fixed a problem in
> >commons-site.jsl that we preventing the date being displayed, so before
> >generating commons sites, you should svn up commons-build.
> >
> >
> That's a shame - I would have thought at least one of those solutions
> would have worked.


The problem is that we have decoupled the site builds from commons-build -=
=20
the individual projects reference commons-site.jsl directly.=20

Probably the most effective thing to do in this case is to put a check
> into commons-build/maven.xml to make sure the latest plugin is being
> used. That could be used to select the JSL to use (current or previous),
> but it might be better to recommend a consistent version (especially if
> some start requiring the i18n or other features, for example).


Given the current setup above, unless I am missing something, all of the=20
maven.xml's would have to be modified to check, I guess this is possible.

Is there any way to get commons-site.jsl to check?

Thanks for your help on this and any ideas that you have on how to improve=
=20
the setup.=20

If you can see an any way to eliminate the dependency on the fmt library=20
from commons-site.jsl without breaking site generation or to sneak it in=20
somehow without breaking xdoc <1.9, that would also be great.=20

Phil

------=_Part_8526_13213743.1126470629584--