tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jean-frederic clere <jfrederic.cl...@fujitsu-siemens.com>
Subject Re: Building modapp for Tomcat4.0 and apache1_3.23
Date Thu, 11 Apr 2002 15:21:35 GMT
GOMEZ Henri wrote:
>>Ok, so then don't destroy MY build by introducing shit around 
>>the CVS tree,
>>moving files along and NOT patching what I've done before... 
>>Thanks JF for
>>doing that, but I'm still not able to build the java code interactively
>>without passing thru ANT...
> 
> 
> You could notice that I avoided to touch anything in webapp, since
> JF does a great maintenance job there ;)

I have tried to find some time for it...

> 
> 
>>>if ant build files could works, let use it.
>>
>>No, because then we will have TWO stupid build systems to 
>>track and debug.
> 
> 
> Why should you get only one way to do something. Two builds
> methods are fine till there is people to update and maintain them.
> 
> 
>>>I'm like you and use exotic OS, OS/400, where
>>>autoconf/automake/libtool didn't works (yet ?).
>>
>>If autoconf/libtool doesn't work, then you can't even build 
>>APR, you can't
>>build Apache, therefore you don't f***ing need mod_webapp, k?
> 
> 
> On AS/400, APR and Apache 2.0 are build by IBM, from snapshots
> with in-house cross-compiling tools, so they don't have to build
> them on AS/400.

The libtool does not support EBCDIC...
I have started to patch the 1.4.2 to compile APR and httpd-2.0 on our BS2000 
EBCDIC mainframes may be you could reuse something.

> 
> Apache 2.0 is present on AS/400 as a standard component. 
> Currently you have on recent AS/400 something derived from 2.0.18 beta.
> 
> The sad thing is that IBM didn't report the AS/400 specific patches
> they apply to a snapshot back to ASF.
> 
> Now that 2.0.35 is GA, they will certainly make a new release.
> 
> 
>>>Each tool in java which could replace them is a
>>>big plus for me ;)
>>
>>Each tool which can replace them and is a PITA to maintain, or requires
>>hyperknowledges of XML and tagets, build properties and such, whose
>>configuration file is 40 lines to do what I do in 3 lines of 
>>shell script
>>will always be a HUGE -1 from me...
> 
> 
> So why are we using ant in jakarta instead of smaller makefiles ?)
> 
> ant is a great tool and it will be a PITA to avoid using it
> when it's a valid alternative to old like autoconf/automake/libtool/m4.
> 
> ant is ASF after all and run on all OS, so it's a good reason to use
> it when possible. jkant (in jtc) is a good example of native-interaction
> module which boost ant...
> 
> 
> 
> --
> To unsubscribe, e-mail:   <mailto:tomcat-dev-unsubscribe@jakarta.apache.org>
> For additional commands, e-mail: <mailto:tomcat-dev-help@jakarta.apache.org>
> 
> 
> 




--
To unsubscribe, e-mail:   <mailto:tomcat-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:tomcat-dev-help@jakarta.apache.org>


Mime
View raw message