first of all will javac -source 1.4 -target 1.4 always do the right thing?
And then i thing about the changes in StringBuilder/StringBuffer
I guess StringBuilder will not be used but StringBuffer will
And then i guess java 5 methods of StringBuffer will be used when appending
for example:
* @since 1.5
*/
public StringBuffer append(CharSequence s) {
what happens if the java 5 compiler uses that one for a specific object
because it is a CharSequence
in java 4 it would be linked to:
public synchronized StringBuffer append(Object obj) {
If you then run that on a java 4 jvm then i think you will get a abstract
method error.
This is just a wild guess and i didn't test it but i have seen things like
that when going from 1.3 to 1.4
append(StringBuffer) method
Are we really using a different jvm now on our Bamboo server? Last time i
checked it always did that with java 5
johan
On 2/5/07, Alastair Maw <[EMAIL PROTECTED]> wrote:
Hi Martijn,
You've evidently been bitten by this and have a set-up that fixes the
issue and works, and are therefore reluctant to change it. I respect
that and shall now politely stop haranguing you, even if I think I know
better. ;)
Regarding Bamboo going the way of Continuum, I'd like to note that if
people have their build environments set up incorrectly to link against
the wrong rt.jar version, then they have the potential to push JDK 5
code into the 1.4 codebase regardless of how Maven 2 is set up. One
simply doesn't run Maven 2 over the Wicket projects as a developer all
that much as the dependencies don't change that often.
It's also a pain having to set your JAVA_HOME and paths up specially
each time, so I'd guess most people don't tend to bother. Having a
continuous integration server that picks up these issues is therefore
useful and important regardless. Kudos to people for chasing licenses
and getting it all setting it up. :-)
Thanks,
Al
