Title: RE: Build problem with Tomcat

Hi John,

> > First, there are several files in the Turbine snapshot with
> > wrong file names. Most of the errors are with the extension
> > (empty, j, ja or jav instead of java), but a few were also
> > missing part of the basename.
>
> That is odd.  It has never been brought up before.  Are you
> talking about
> daily snapshots?  Did you look at any previous ones to see if
> they also were
> messed up?

This was on a daily snapshot, Apache-Turbine-20000717.tar.gz,
extracted with WinZip 6.3 SR1. I copied the file to a linux
machine and verified all the files had no problems; I guess I
hit a bug with this version of WinZip (scary thought). Anyway,
I downloaded the 0718 snapshot, and everything built Ok (modulo
the deprecated methods).

> > Second, I'm appending at the end of this message the errors
> > I get when issuing a "build-turbine jar". Anybody can share any
> > hints on what's going on? The errors fall into three categories:
> >
> > * Using deprecated methods.
>
> Turbine still supports jsdk 2.0.  Once it is decided to no
> longer support
> jsdk 2.0, we will change the code.

Does java have any conditional compilation features? I guess not...

> > * Using "return null" in methods declared as void.
> > * Using the non-existent method setContentType().
>
> Again, this is odd.  I have never seen errors like this. 
> These methods do
> not return null, they just return.
> For example on line 98 of ImageServer
> I do not see
> return null;
> in the code.  I see
> return;

Well, this is definitely odd. The file ImageServer.java, extracted
from the 0717 snapshot, has these lines:

     94         if ( image == null )
     95         {
     96             // should do more logging here
     97             Log.error( "ImageServer - image is null!" );
     98             return null;
     99         }

The same file, extracted from the 0718 snapshot, has these lines:

     94         if ( image == null )
     95         {
     96             // should do more logging here
     97             Log.error( "ImageServer - image is null!" );
     98             return;
     99         }

so something definitely changed here!


--
Gonzalo A. Diethelm
[EMAIL PROTECTED]
If this mail is in HTML format, blame Exchange Server: Q222508

Reply via email to