[ jetty-Bugs-1200255 ] errors when compiling jetty-4.2.19, jetty-4.2.24 with jikes

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[ jetty-Bugs-1200255 ] errors when compiling jetty-4.2.19, jetty-4.2.24 with jikes

SourceForge.net
Bugs item #1200255, was opened at 2005-05-11 23:48
Message generated for change (Comment added) made by gregwilkins
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=107322&aid=1200255&group_id=7322

Category: None
Group: None
Status: Open
>Resolution: Postponed
Priority: 5
Submitted By: Joshua Nichols (nichoj)
Assigned to: Nobody/Anonymous (nobody)
Summary: errors when compiling jetty-4.2.19, jetty-4.2.24 with jikes

Initial Comment:
I'm working on packaging Jetty for Gentoo Linux. The
new Java policy is to build from source when possible,
and we offer the ability to compile using jikes.

So, when I attempt to run with jetty-4.2.19 (most
recent packaged in Portage), or the most recent 4.2.24:
ant  -Dbuild.compiler=jikes clean classes

I get many warnings to the effect of:
    [javac]
/tmp/jetty-4.2.24/src/org/mortbay/servlet/Forward.java:46:33:46:36:

Lexical Warning: The use of "enum" as an identifier is
deprecated, as it will be a keyword once -source 1.5 is
implemented.

In addition to one build error:
    [javac]
/tmp/jetty-4.2.24/src/org/mortbay/http/HttpServer.java:1464:37:1464:
50: Semantic Error: The static type
org.mortbay.http.HttpServer$ComponentEventListener"
must use a qualified name to access the non-static
member type
"org.mortbay.http.HttpServer$ComponentEvent" of the
enclosing type "org.mortbay.http.HttpServer".

Both of these are very simple to fix. For the enum
warning, the variable just needs to be named something
else. For the semantic error, the reference to
ComponentEvent needs to be changed to
HttpServer.ComponentEvent.

----------------------------------------------------------------------

>Comment By: Greg Wilkins (gregwilkins)
Date: 2005-05-12 08:52

Message:
Logged In: YES
user_id=44062

I think both of these have been fixed in Jetty 5.   If you
are doing a new package, then I really think that Jetty 5
(the stable release) should be the target.

If you really really really want a Jetty 4 release, I will
make the fixes

----------------------------------------------------------------------

Comment By: Joshua Nichols (nichoj)
Date: 2005-05-11 23:50

Message:
Logged In: YES
user_id=1216866

I also forgot to mention that were also warnings like:
    [javac]
/tmp/jetty-4.2.24/src/org/mortbay/http/DigestAuthenticator.java:72:1
9:73:32: Semantic Warning: This switch block can fall
through to the next case. Did you forget a break statement?

But I was not sure if this was the desired behavior, so
didn't attempt to fix it.


----------------------------------------------------------------------

You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=107322&aid=1200255&group_id=7322


-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_id=7393&alloc_id=16281&op=click
_______________________________________________
jetty-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/jetty-discuss