Any ant after 1.4 should work, as well as configure ( i.e. ant is not
the only way to build jk ).
I'm still working on autoconf support for jk2 and make files
The current ant tasks for building C work reasonably well - and
I think it's a good idea ( for some reasons I prefer to write
logic in
On Mon, 20 May 2002, Anthony W. Marino wrote:
Costin,
I've experienced all kinds of build problems using Ant however it's
what I prefer to use and I'll pass along the changes when finished.
Ant is what I prefer to use, but the final goal is to make it easy for
people to build mod_jk -
(TC4.1.2/JK2/Apache2)
1) Is it required that for a mod_jk2.so build/distribution that the entire set
of coyote jars also be distributed when the build is based on a new j-t-c
download from cvs?
2) Can Ant1.5b1 be used to build existing files?
Thank You,
Anthony
--
To unsubscribe, e-mail:
On Mon, 20 May 2002, Anthony W. Marino wrote:
(TC4.1.2/JK2/Apache2)
1) Is it required that for a mod_jk2.so build/distribution that the entire set
of coyote jars also be distributed when the build is based on a new j-t-c
download from cvs?
The C and java sides are independent of each
Costin,
I've experienced all kinds of build problems using Ant however it's what I
prefer to use and I'll pass along the changes when finished.
Are you going to be gone for long??? Just have a good time, regardless of
what/where!
Thank You and Have A Nice Evening!
Anthony
On Mon, 20 May 2002, Anthony W. Marino wrote:
Costin,
I've experienced all kinds of build problems using Ant however it's what I
prefer to use and I'll pass along the changes when finished.
Ant is what I prefer to use, but the final goal is to make it easy for
people to build mod_jk - if
