We could potentially do a build (it would be hard), but then you wouldn't have a single binary. Personally I think its easier at this point to include backport. Once there is a much larger usage of JDK5 we could migrate and then provide the backport as a separate build.
Paul
On 2/23/06, Steve Loughran <[EMAIL PROTECTED]> wrote:
Paul Fremantle wrote:
> Steve
>
> The answer is that there is no single set of imports that we can use in Java
> that uses backport if its there in JDK 1.4 and the in-built JDK 5 stuff
> otherwise.
>
> So we had to either fix Axis2 to be JDK5+ only, or use backport. We chose
> backport for the widest acceptance. However, they are in their own
> namespace, so in JDK5 you are using the backport lib not the JDK stuff.
> Eventually we can do a global rename and create a JDK5+ only version.
There is no way to do a 1.4 and a 1.5 build and switch to the right impl
on demand?
> I started writing a rant against Sun's strategy but I figured no-one would
> be interested so I've deleted it.
Oh, but I agree with it, even if is still unwritten.
--
Paul Fremantle
VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
http://bloglines.com/blog/paulfremantle
[EMAIL PROTECTED]
"Oxygenating the Web Service Platform", www.wso2.com
