Can we guarantee that the 1.4 built version is bytecode compatable with 1.2? Its not nice whichever way around you do it.
How about build under 1.4, then use the jar to run the test cases against under 1.2?
FWIW, I have done this both ways with current sources -- build w/ 1.4, run tests using 1.2 and vice versa. Both work for me. I also ran 1.4-compiled tests on 1.3 and that worked as well. I did this earlier today thinking that I might see performance differences, but I did not (i.e., the 1.2-compiled code seems to run as fast under 1.4 as the 1.4 compiled version. <disclaimer> This is based on just 2 runs with each config so is by no means scientific. Also, our unit tests are obviously not performance tests </disclaimer>).
Phil
Stephen
----- Original Message ----- From: "Henri Yandell" <[EMAIL PROTECTED]>
On Sat, 16 Aug 2003, Stephen Colebourne wrote:built
+1 to RC3
BTW, is there a problem with building with 1.2.2 if our javadoc has been optimised for 1.4? The javadoc compiler has changed. Can the docs be
using 1.4 instead?
Ack. So we want a 1.2 built jar and a 1.4 built javadoc?
Maybe I should just go ahead and use 1.4 to distribute. While I could merge a 1.4 and 1.2 set of builds, it wouldn't be something the user could repeat with the -src jar.
Hen
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
