Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <dev@tomcat.apache.org>
Received-SPF: neutral (herse.apache.org: 72.17.152.163 is neither permitted
 nor denied by domain of wltjr@gentoo.org)
Subject: Re: Building the Jasper compiler
From: "William L. Thomson Jr." <wltjr@gentoo.org>
To: Tomcat Developers List <dev@tomcat.apache.org>
In-Reply-To: <583461.64072.qm@web38904.mail.mud.yahoo.com>
References: <583461.64072.qm@web38904.mail.mud.yahoo.com>
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature"; boundary="=-VsbTR1TYBPrzF7IFgAOh"
Organization: Gentoo
Date: Mon, 12 Feb 2007 15:50:51 -0500
Message-Id: <1171313451.19169.14.camel@wlt.obsidian-studios.com>
Mime-Version: 1.0

--=-VsbTR1TYBPrzF7IFgAOh
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Mon, 2007-02-12 at 10:21 -0800, M Coffee wrote:
> Could I ask again for a reference to instructions on how to build the
> Jasper compiler?  The Building.txt that comes with it does not work
> for me (Win2K, jdk 1.5, ant 1.7.0).

It's not going to be on windows, but on Gentoo we will have a
tomcat-jasper package. There was a jakarta-tomcat-jasper, that was old
based on 5.0.28 sources, and I punted it from the tree since no one was
using it. It's purpose was for Jetty, since Jetty uses Tomcat's Jasper.

I had to rip out the guts, and make a build.xml specifically for
tomcat-servlet-api. I will be doing the same at some point for
tomcat-jasper. So if no one else responds with info, check the Gentoo
viewcvs/svn for either the tree, or one of our java overlays in a few
weeks. Presently I have no motivation to work on the package, but will
see about it over the upcoming weeks.

Once I do, you can take the build.xml and it should work on windows or
etc.

> Or, would you let me know if it is not possible to build the Jasper
> compiler except through the Tomcat build?

I am sure it's possible, but might be some steps involved. I would
recommend looking at the existing build.xml for anything specific to
jasper and rip that out and put into it's own build.xml. You will need
to make your own compiling target, and omit any stuff that is not
necessary to compiling or building jasper.

> I have been able to compile individual classes in jasper, so that's
> what I've been doing, and patching the working jar I have.  But I'd
> rather be following an ant build process, just to be sure that all of
> the environment is being referenced correctly.

Their used to be multiple build.xml's. Which on one level was nice for
splitting up the package. But on another made some things really a pain.
I much prefer the single build.xml to multiple.

> Is there a mailing list just for Jasper that I should be sending this
> question to?

It's my understanding through past comments on this list that Jasper is
an integral port of Tomcat. It was developed for Tomcat, it will change
along with Tomcat versions. So this would be the right list and place,
unless things have changed ;)

--=20
William L. Thomson Jr.
Gentoo/Java

--=-VsbTR1TYBPrzF7IFgAOh
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQBF0NMrPrChP8zZLyYRAhdgAKC5Tq5JU3AeTtNO51L4VhKOjY4JSQCg5yB0
fipLoQxU5Ngai58QGRNsGzM=
=KyyS
-----END PGP SIGNATURE-----

--=-VsbTR1TYBPrzF7IFgAOh--