View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20060106043641Lbuild.1146
BUILD COMPLETE-build.1146Date of build:01/06/2006 04:36:41Time to build:12 minutes 27 secondsLast changed:01/06/2006 03:04:49Last log entry:Turn off juddi
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20060106052218
BUILD FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-jboss-common.xml:179: The following error occurred while executing this line:
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20060106061849
BUILD FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-jboss-common.xml:179: The following error occurred while executing this line:
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20060106064908Lbuild.1147
BUILD COMPLETE-build.1147Date of build:01/06/2006 06:49:08Time to build:12 minutes 22 secondsLast changed:01/06/2006 06:41:30Last log entry:Extract
So which of these ejb3 tasks in the 404RC1 roadmap can be done?
http://jira.jboss.com/jira/secure/IssueNavigator.jspa?reset=truemode=hi
desorter/order=DESCsorter/field=priorityresolutionIds=-1pid=10030fi
xfor=12310378
Task JBAS-2603 EJB3 update
TaskJBAS-2604 Update
I think you should wait until we get a full PFD released of EJB3.
Emmanuel still has a bunch of work to do, as do Bill and I. Also, the
new Hibernate jars will not work with what EJB3 is in CVS.
Gavin King wrote:
OK, so. I am doing a tour in the second half of this month, speaking
about Seam
Scott M Stark wrote:
So which of these ejb3 tasks in the 404RC1 roadmap can be done?
http://jira.jboss.com/jira/secure/IssueNavigator.jspa?reset=truemode=hi
desorter/order=DESCsorter/field=priorityresolutionIds=-1pid=10030fi
xfor=12310378
Task JBAS-2603 EJB3 update
Task
I have assigned the installer issue to myself and will work on them this
weekend. I need a stable ejb3/hibernate set of binaries that can go into
4.0 to be able to produce a release, but these are not needed to fix the
installer issues.
The question is, can you have an ejb3 drop for 4.0 that
TaskJBAS-2604 Update the remoting version to a stable release
I'll have a 1.4.0 RC1 available for testing before tomorrow morning (if
no problems with this, will make the final next week).
---
This SF.net email is sponsored by:
Scott M Stark wrote:
I have assigned the installer issue to myself and will work on them this
weekend. I need a stable ejb3/hibernate set of binaries that can go into
4.0 to be able to produce a release, but these are not needed to fix the
installer issues.
The question is, can you have an
A component should be compatible with multiple versions, not just the
latest as this will break other uses of hibernate that cannot use
asm-3.0_beta. For example, from the tomcat 5.5.9 component-info.xml:
import componentref=apache-logging
compatible version=1.0.3/
Ok, I restored compatiblity to asm-1.5.3.
If hibernate is incompatible with asm-3.0_beta things will become
compilicated.
xxx
Thomas Diesler
Web Service Lead
JBoss Inc.
xxx
-Original Message-
From: Scott M Stark
Sent: Friday, January 06, 2006
If its incompatible then you would change it as you did. I believe its
really cglib that depends on the asm stuff so the dependencies are not
being expressed. Currently the cglib has no dependencies.
-Original Message-
From: Thomas Diesler
Sent: Friday, January 06, 2006 11:18 AM
To:
Another issue here is that there is no runtime dependency on the asm
jars in the retrotranslated output, so this is really an overzealous
dependency requirement. The retrotranslator stuff really needs to be
brought in as a jbossbuild component with a minimal runtime component
described in the
I created a JBossMC_2_0_0M1 mc release tag targeted for Feb 3 as the
next iteration of the mc. The main focus is to get the mc closer to a
state that we can start to port jboss5 to it. Any issues assigned to you
from this release should be considered a priority. Get back to me if you
can't get any
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/ejb3-4.0-testsuite?log=log20060106151715
BUILD FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-ejb3-4.0-testsuite.xml:82: Exit code: 1 See tests.log in Build Artifacts for details.Date of
Related to this issue:
Update the microcontainer release build to the agreed common format
http://jira.jboss.com/jira/browse/JBMICROCONT-54
we really should pull the mc out of jboss-head into its own project
module (jboss-mc) to simplify its development and better isolate it from
jboss5. jboss5
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/ejb3-head-testsuite?log=log20060106153957
BUILD FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-ejb3-head-testsuite.xml:82: Exit code: 1 See tests.log in Build Artifacts for details.Date of
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20060106160901
BUILD FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-jboss-common.xml:179: The following error occurred while executing this line:
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2-testsuite?log=log20060106162536
TESTS FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-jboss-common.xml:190: The following error occurred while executing this line:
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20060106171808
BUILD FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-jboss-common.xml:179: The following error occurred while executing this line:
HEM and annotations?
Gavin King wrote:
I am running JBoss AS 4.0.3SP1 with the latest Hibernate jars every day,
and it works smoothly.
-Original Message-
From: Bill Burke
Can the hibernate jars be updated in the 4.0 branch without breaking
the
ejb3 tests and seam?
annotations
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20060106181516
BUILD FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-jboss-common.xml:179: The following error occurred while executing this line:
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20060106194831
BUILD FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-jboss-common.xml:216: The following error occurred while executing this line:
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0-jdk-matrix?log=log20060106200156
BUILD FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-jboss-common.xml:179: The following error occurred while executing this line:
The change to the jbossxb classes has broken existing uses of org.jboss.xb.binding.GenericValueContainerand so cannot used as is. The jbossxb version used in 4.0 has to be binary compatible with the existing uses.A new compatible binary needs to be
Also, there cannot be snapshot version dependencies in the
4.0 branch build-thirdparty.xml:
componentref
name="jboss/jbossws" version="snapshot"/
componentref name="jboss/jbossxb"
version="snapshot"/
Such testing needs to happen in your workspace with a
subsequent tagged release of the
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-portal-2.0-testsuite?log=log20060107001339
TESTS FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-jboss-portal.xml:66: The following error occurred while executing this line:
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-portal-2.2-testsuite?log=log20060107001637
TESTS FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-jboss-portal.xml:66: The following error occurred while executing this line:
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-cache-testsuite?log=log20060107001937
BUILD TIMED OUTAnt Error Message:build timeoutDate of build:01/07/2006 00:19:37Time to build:Last changed:12/28/2005 10:48:11Last log entry:Add the 1.2.4SP1 changelog notes.
30 matches
Mail list logo
