Carsten Ziegeler wrote:
Stephen McConnell wrote:
Farr, Aaron wrote:
-----Original Message----- From: Carsten Ziegeler [mailto:[EMAIL PROTECTED]
I mean "compiling with a JDK 1.3" and not "compiling with a JDK 1.4 with target (or source) 1.3" :) So, if Magic is the one
starting the
compilation, then yes, you have to start Magic with JDK 1.3. Otherwise you may run exactly into the trap.
But have we identified any actual code for which the JDK
version would
matter? For example, the StringBuffer 'bug'?
Nobody has done an audit that I'm aware of.
We have StringBuffer usage throughout the code (Studio, Cornerstone Connection, Scheduler and Store, a couple of tutorials, the composition model, framework, LogKit, lots in repository, several util packages, and Magic itself). It's going to take a while to verify all this but I suspect there will not be a problem.
Perhaps we are safe as noone complained - or noone is using JDK 1.3 :)
Anyways, my own suggestion is: if you support JDK 1.3, then use it to compile.
JDK 1.2 is supported.
I'm inclined to agree with you that a dist under 1.3 is probably a better move - but I don't think it will happen fast. We are still bringing everything back into sync. following the reorg and the changes to the magic site stuff will involve adding external dependencies (which is a real PITA) - and there are also some pressing items related to the JMX and HTTP facilities that need to be closed.
However - we are now aware of the potential issue.
Cheers, Steve.
Carsten
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--
|---------------------------------------| | Magic by Merlin | | Production by Avalon | | | | http://avalon.apache.org | |---------------------------------------|
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
