Yes, you are right. We will disable
the head/jdk1.4 runs.
From:
jboss-development-bounces@lists.jboss.org
[mailto:jboss-development-bounces@lists.jboss.org] On Behalf Of Scott M Stark
Sent: Friday, July 28, 2006 9:08
AM
To: JBoss.org development list
Subject: RE: [JBoss-dev] jdk5 byte
code in jboss-4.0 dependency
This is the head testsuite build
using jdk1.4, not jboss-4.0.x. Its getting to the point of not being worth
running head with jdk1.4. Any libraries that are supposed to be jdk1.4
compatible would either have to have a jboss-.4.x integration or their own validation.
From:
jboss-development-bounces@lists.jboss.org
[mailto:jboss-development-bounces@lists.jboss.org] On Behalf Of Ryan Campbell
Sent: Friday, July 28, 2006 4:56
AM
To:
jboss-development@lists.jboss.org
Subject: [JBoss-dev] jdk5 byte code
in jboss-4.0 dependency
Importance: High
When trying to compile jboss-4.0 w/ java 1.4
/services/cruisecontrol/checkout/jboss-head-testsuite-1.4/aop/src/main/org/jboss/aop/Advisor.java:72: cannot access org.jboss.repository.spi.MetaDataContext
bad class file: /services/cruisecontrol/checkout/jboss-head-testsuite-1.4/thirdparty/jboss/microcontainer/lib/jboss-container.jar(org/jboss/repository/spi/MetaDataContext.class)
class file has wrong version 49.0, should be 48.0
Please remove or make sure it appears in the correct subdirectory of the classpath.
import org.jboss.repository.spi.MetaDataContext;