> So the answer is Java 1.3

Danny also said "avalon dependancies may limit this to 1.4 for 2.1x versions
(head of cvs)" and "newer [than 2.0a3] releases will be compiled by 1.4."

So far I haven't had a problem running the CVS (2.1) release with JDK 1.3,
but I don't know if newer releases of the Avalon components will require
1.4.  As I understand it, so far there is not a requirement for JDK 1.4 in
either James or the Avalon components we depend upon.

However, as I understood your question, you want to know if/when it is OK to
start making use of JDK 1.4 capabilities in James.  That question doesn't
appear to be answered by TFM.

        --- Noel

-----Original Message-----
From: Peter M. Goldstein [mailto:[EMAIL PROTECTED]]
Sent: Sunday, August 11, 2002 5:47
To: 'James Developers List'; [EMAIL PROTECTED]
Subject: RE: Random Version Question Time

Danny et al,

Sorry about that.  Don't know how I missed it.  :)

So the answer is Java 1.3

--Peter

> -----Original Message-----
> From: Danny Angus [mailto:[EMAIL PROTECTED]]
> Sent: Sunday, August 11, 2002 2:06 AM
> To: James Developers List; [EMAIL PROTECTED]
> Subject: RE: Random Version Question Time
>
> pgoldstein wrote:
>
> > I'd like this detail to be someplace very obvious.  Is there a
> > consensus on this?
>
> RTFM
>
> Peter _read_ the james homepage http://jakarta.apache.org/james/index.html
> and you'll see it states "James requires Java 2 (either JRE 1.3 or 1.4
> as of 2.0a3)"
>
> James 2.0a3 will build and run under 1.3 or 1.4, I believe avalon
> dependancies may limit this to 1.4 for 2.1x versions (head of cvs)
> Serge hacked the db pool and build.xml to compile against the correct
> version of JDBC for the JDK version being used.
>
> Up to 2.0a3 binary releases made by me were compiled by 1.3, newer
> releases will be compiled by 1.4 on the principle that we should
> be using the latest stable JDK for releases where possible.
>
> d.


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to