Thanks for much for the prompt, crisp, helpful information. I should go get the exception from the stack trace, but that would require that I restablish the test harness, so pardon me if I try to just get it almost correct.
01. I have the 3.1 RC running as a webapp under a Tomcat 5.5.17 on a Windows Server. It behaves fine. 02. I need, however, to write a CommentAuthenticator, so I follows the great example posted. 03. I restart, try to add a comment and -- probably for both of the methods of that Interface, but I don't ahve the stack trace -- I get java class version extensions. The class was compiled under JDK6. If I understand what you are saying, my problem is that I compiled on Java6, but Tomcat is running on a host with a Java5 runtime -- the incompatibility is NOT with the 1.4 basis of the Roller app. I will try to create those build and test conditions and let everyone know. If what you say is correct, I guess I have no need to worry about moving ahead with Roller. Thanks again, I will report results tomorrow. Anil Gangolli wrote: > > > Without trying to advocate for any stance, let me at least try to clarify > the current state of things. > > - The release is built with JDK 1.4 and source that is part of the release > is required to be compatible with 1.4. This only affects you if you plan > to > contribute code back to the project. > > - Given this, you can run on any JDK version 1.4 or higher. For example, > I > run my own site on JDK 1.5 and Tomcat 5.5. > > - You should be able to develop your own plugins and extensions using JDK > versions greater than 1.4 just fine as long as you then run the entire > thing > on equivalent or higher JDK versions. This doesn't require rebuilding or > touching Roller code. > > - You should also be able to build and run Roller sources yourself using > JDK > 1.5 or higher if you want if you do want to modify Roller code. > > The present stance is intentionally conservative, giving the greatest > flexibility to users, while putting additional burden on contributors to > write source code that compiles and runs in 1.4. > > For my own part, although everything else I am working on now is using > Java > 1.5 or higher (so personally I'd be fine with stepping up to it) I'm not > sure how many sites we'd be cutting out by requiring it. > > --a. > > > ----- Original Message ----- > From: "Terry Corbet" <[EMAIL PROTECTED]> > To: <[email protected]> > Sent: Friday, January 05, 2007 7:14 PM > Subject: Java Version > > >> >> There is a posting on the developers forum from last September in which >> folks >> talked about moving to Java 5. For reasons that may be valid within the >> Jakarta development environment, the discussion was simply dropped. >> Someone, however, indicated that they were able to deploy with a Java 5 >> runtime. >> >> Of course when I try to provide a CommentAuthenticator, all my >> development >> work left 1.4 at least three years ago, and with the most recent posts >> concerning forthcoming Java 7 features it is not even a question of >> whether >> or not one should be using Java 6 today. If there are compelling reasons >> why this project cannot be developed with currently-released SDKs, can >> someone please indicate if it is possible to provide plug-ins based on >> anything other than the 1.4 JDK? >> >> Acceptance of a fine body of software is being put aside because of this >> dependence upon way down-level tools. >> -- >> View this message in context: >> http://www.nabble.com/Java-Version-tf2929447s12275.html#a8190261 >> Sent from the Roller - User mailing list archive at Nabble.com. >> > > > -- View this message in context: http://www.nabble.com/Java-Version-tf2929447s12275.html#a8191339 Sent from the Roller - User mailing list archive at Nabble.com.
