You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by "Anthony W. Marino" <an...@AWMObjects.com> on 2002/05/20 17:14:27 UTC
JK2/Coyote Connector Testing Effort
(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: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: JK2/Coyote Connector Testing Effort
Posted by "Anthony W. Marino" <an...@AWMObjects.com>.
> 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 ant gets in the way, you should use the
> makefiles and autoconf.
>
> There is another project ( ant-contrib on sf.net ) doing tasks to compile
> C code with ant - the syntax is a bit different, but it could be used as
> well. After we're done with jk and this release, I'll spend some more time
> with the tasks trying to integrate/merge with those - any help would be
> great.
Now that's something that seems extremely interesting!
> The reason I'm interested in this - I think java is a more powerfull
> language than m4 and .sh, and it may be worth having a build system
> that most people can understand. I admit having troubles reading
> the libtool code ( and I have some .sh experience ), and not liking
> m4 too much.
>
> > Are you going to be gone for long??? Just have a good time, regardless
> > of what/where!
>
> I'll be back in 2 days ( unfortunately :-), I'm visiting few friends
> on the east coast.
>
>
I'm in NJ and it's been nice however on the chilly side as of late!!!
Later,
Anthony
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: JK2/Coyote Connector Testing Effort
Posted by co...@covalent.net.
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 ant gets in the way, you should use the
makefiles and autoconf.
There is another project ( ant-contrib on sf.net ) doing tasks to compile
C code with ant - the syntax is a bit different, but it could be used as
well. After we're done with jk and this release, I'll spend some more time
with the tasks trying to integrate/merge with those - any help would be
great.
The reason I'm interested in this - I think java is a more powerfull
language than m4 and .sh, and it may be worth having a build system
that most people can understand. I admit having troubles reading
the libtool code ( and I have some .sh experience ), and not liking
m4 too much.
> Are you going to be gone for long??? Just have a good time, regardless of
> what/where!
I'll be back in 2 days ( unfortunately :-), I'm visiting few friends
on the east coast.
Costin
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: JK2/Coyote Connector Testing Effort
Posted by "Anthony W. Marino" <an...@AWMObjects.com>.
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
> > (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 other, you can use the C
> module with any version of tomcat from tomcat3.2 ( up to coyote ).
>
> There are few build 'glitches' - I'll try to improve it as soon as
> I get back.
>
> > 2) Can Ant1.5b1 be used to build existing files?
>
> Any ant after 1.4 should work, as well as configure ( i.e. ant is not
> the only way to build jk ).
>
> 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 java rather than .sh or m4 ). However libtool/configure/make
> remain a solid solution.
>
> Costin
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: JK2/Coyote Connector Testing Effort
Posted by co...@covalent.net.
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 other, you can use the C
module with any version of tomcat from tomcat3.2 ( up to coyote ).
There are few build 'glitches' - I'll try to improve it as soon as
I get back.
> 2) Can Ant1.5b1 be used to build existing files?
Any ant after 1.4 should work, as well as configure ( i.e. ant is not
the only way to build jk ).
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 java rather than .sh or m4 ). However libtool/configure/make
remain a solid solution.
Costin
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>