tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Danno Ferrin <>
Subject Re: nightly build scripts (was: IllegalAccessError and Tags)
Date Thu, 03 Feb 2000 18:23:10 GMT
Ok, I thought that this issue was fixed but apparently it isn't.  The
two most recent nightly build zips and the 3_1M1 zip and gz from off of
the directories still have this
problem.  This is a process bug that has been around for upwards of two
months now and we need to get it fixed.  

I have never been able to create this bug by any other way than to get
the binaries form the web site, I can always build it clean.  What needs
to be done?  If need I can put my builds out there on the site via a
cron job on my Linux box (I might need to read the howtos for
dynamically raising the ppp connection).  Is this being caused by old or
dirty builds visible in the class path?

--Danno wrote:
> Danno Ferrin wrote:
> >More follow-up on this for the build process....
> >
> >Where are the tomcat zips being made?  After seeing this error on two
> >(or more...) different binary releases it leads me to believe that this
> >error is being introduced by someting that can be changed and not by
> >random occurrence.  Is the compiler jikes or the 1.3ea compiler?  Is
> >there an old xml jar in the extensions?  If it happens more than once it
> >can be nailed down.
> The 3.1_M1 builds were done on Linux using the IBM 1.1.8 JDK.  I used 1.1.8
> because I felt that the output of this would run on the most platforms.
> It took me a while to notice it, but the servlet-2.2.0.jar which was
> actually checked into the jakarta-tools CVS tree was bad, and caused
> illegal access errors such as these (if I recall correctly, the class names
> were different).    I rebuild servlet-2.2.0.jar and checked it in, but
> people don't tend refresh jakarta-tools on any regular basis.
> I do not rebuild project-x.  In fact, I am not even aware of where the
> source to this is.
> - Sam Ruby
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

View raw message