[jboss-dev] RE: Jdk1.4 vs jdk5

[Dimitris Andreadis]

I tried jbossxb 1.0.0.CR8 in jboss 4.2, that was compiled with jdk5, due
to jboss-test (imported by jbossxb) being compiled with jdk5.

So all 1.4 based testsuite builds of jbossas 4.2 break immediately due
to the jbossxb jdk5 compiled classes.
Do we need to just drop those builds?

Also, how to deal with the compatibility tests? The way we use client
libs from one jboss version against a running server of another version
(e.g. 4.2 client libs against 4.0 server) will not work, unless we run
the client with jdk5.

Is this what we are supposed to do? i.e. require all jboss 4.2 compiled
code to need a jdk5 runtime?

Do you see any other issue interoperating with older servers running on
jdk1.4 ?

> -----Original Message-----
> From: Scott M Stark 
> Sent: Thursday, January 11, 2007 9:03 PM
> To: Dimitris Andreadis
> Cc: JBoss.org development list; Scott M Stark; 
> jboss-as at redhat.com; Ryan Campbell
> Subject: Re: Jdk1.4 vs jdk5
> 
> libraries needing to be used under jdk14 must have a version for that.
> Why does jboss-test trigger a jdk14 issue as its not used by 
> jboss-4.0.x?
> 
> Dimitris Andreadis wrote:
> > With the switch to jdk5 for JBossAS 4.2 we are seeing more 
> cases where
> > jdk5 dependencies propagate, e.g.
> > 
> > jboss-test-1.0.0.GA build using 1.5 target -> jbossxb 1.0.0.CR8 -> 
> > jbossws 1.2.0.CR2 -> jbossAS.
> > 
> > So jbossAS with jdk1.4 testsuite runs are bound to fail, plus I 
> > presume we'll be start having problems with the 
> compatibility runs, e.g.
> > 
> > Jboss 4.0.x (jdk14) against JBoss 4.2.x (jdk15)
> > 
> > Jdk15 targeted jars won't be accepted on the 1.4 side.
> > 
> > How we want to deal with this?
> 
>