Re: [JBoss-dev] ejb3 tests fail unless entire branch is built with jdk5

2006-03-31 Thread Bill Burke 
Why don't you have two installer distributions.  One built with JDK5 and 
includes EJB3, one without.


Bill

Scott M Stark wrote:

If the installer is built as it is for the 4.0.x dist with only the
aspects, ejb3 and ejb3x modules built with jdk5, the tests fail because
the ejb3/build-test.xml client.classpath is referring to
${jboss.dist}/client/jbossall-client.jar, but this jar does not contain
the ejb3 classes. It cannot for the 4.0.x dist so the tests need to be
referring to the module jdk5 client jars. The following has the majority
of the tests passing:

   path id=client.classpath
  path refid=apache.log4j.classpath/
  path refid=apache.logging.classpath/
  path refid=jboss.test.classpath/
  path refid=sun.servlet.classpath/
  pathelement path=${jboss.dist}/client/jbossall-client.jar/
  pathelement path=${module.output}/lib/jboss-ejb3-client.jar/
  pathelement path=${module.output}/lib/hibernate-client.jar/
  pathelement
path=${project.root}/aspects/output/lib/jboss-aspect-jdk50-client.jar/

   /path
 
I guess the ejb3 tests should be setting up a jboss-ejb3.dist that

mirrors what the installer has to do to integrate the ejb3 content into
the j2se1.4.2 compiled core and running against that.


Scott Stark
VP Architecture  Technology
JBoss Inc.
 



---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=kkid0944bid$1720dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development



--
Bill Burke
Chief Architect
JBoss Inc.


---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

RE: [JBoss-dev] ejb3 tests fail unless entire branch is built with jdk5

2006-03-31 Thread Scott M Stark 
Already dealt with, see:
http://www.jboss.com/index.html?module=bbop=viewtopict=80196 

 -Original Message-
 From: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] On 
 Behalf Of Bill Burke
 Sent: Friday, March 31, 2006 8:36 AM
 To: jboss-development@lists.sourceforge.net
 Subject: Re: [JBoss-dev] ejb3 tests fail unless entire branch 
 is built with jdk5
 
 Why don't you have two installer distributions.  One built 
 with JDK5 and includes EJB3, one without.
 
 Bill


---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnkkid0944bid$1720dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] ejb3 tests fail unless entire branch is built with jdk5

2006-03-29 Thread Scott M Stark 
If the installer is built as it is for the 4.0.x dist with only the
aspects, ejb3 and ejb3x modules built with jdk5, the tests fail because
the ejb3/build-test.xml client.classpath is referring to
${jboss.dist}/client/jbossall-client.jar, but this jar does not contain
the ejb3 classes. It cannot for the 4.0.x dist so the tests need to be
referring to the module jdk5 client jars. The following has the majority
of the tests passing:

   path id=client.classpath
  path refid=apache.log4j.classpath/
  path refid=apache.logging.classpath/
  path refid=jboss.test.classpath/
  path refid=sun.servlet.classpath/
  pathelement path=${jboss.dist}/client/jbossall-client.jar/
  pathelement path=${module.output}/lib/jboss-ejb3-client.jar/
  pathelement path=${module.output}/lib/hibernate-client.jar/
  pathelement
path=${project.root}/aspects/output/lib/jboss-aspect-jdk50-client.jar/

   /path
 
I guess the ejb3 tests should be setting up a jboss-ejb3.dist that
mirrors what the installer has to do to integrate the ejb3 content into
the j2se1.4.2 compiled core and running against that.


Scott Stark
VP Architecture  Technology
JBoss Inc.
 


---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnkkid0944bid$1720dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development