>
> 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?
> 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.
> * 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;
>
D:\Apache\Turbine\bin\src\org\apache\turbine\modules\screens\ImageServer.jav
> a:98: 'return' with value from void
> doOutput(org.apache.turbine.util.RunData).
> return null;
>
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
