View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-testsuite-1.5?log=log20060328003314
TESTS FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-common.xml:235: The following error occurred while executing this line: /services/cruisecontrol/work/sc
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-testsuite-1.4?log=log20060328000417
BUILD FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-common.xml:224: The following error occurred while executing this line: /services/cruisecontrol/work/sc
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jbossweb?log=log20060327220036Lbuild.20
BUILD COMPLETE - build.20Date of build: 03/27/2006 22:00:36Time to build: 34 minutes 0 seconds
Unit Tests: (0) Total Errors and
There have been 10 revisions to the jboss-head version of
FieldAccessTransformer since the JBoss_AOP_1_3_5 tagged version. The
stopPrunning(boolean) method return type has changed from void to boolean,
and this is also a problem in the 1.3.5 release of aop. We probably need a
1.4.0 release o
Today, I've made more improvements on the ClassLeakage tool we used to discover
some of our leakages on redeployments.
Today, I decided to evaluate AOP, and I found this leak:
In a first window, I saw this (field dcl on JBossClassPool):
!--- FieldReference protected java.lang.ClassLoader [EMAIL
It looks like aop 1.3.4 is not compatible with javassist 3.2.0.CR1, but this is how I interpreted Kabir’s assent to the upgrade on Friday. _jars-cache: [mkdir] Created dir: /services/cruisecontrol/checkout/jboss-4.0-testsuite/testsuite/output/resources/META-INF [copy] Copying 9 files t
It looks like Branch_4_0 wasn't updated with JBossBuild_1_1_DR2 which
included your fix:
[EMAIL PROTECTED] work]$ md5sum jboss-head/tools/lib/jbossbuild.jar
fba87e22de426cc76eef7563f5c75cce jboss-head/tools/lib/jbossbuild.jar
[EMAIL PROTECTED] work]$ md5sum jboss-4.0/tools/lib/jbossbuild.jar
69bf
The problem seems to be that the Version class has not been updated with
the change I gave to Ruel a while back. When I apply this and rebuild
the jbossbuild.jar, the problem is seen to be an invalid 3.1RC2 version
specification coming from jboss/aop:
[synchronizeinfo] against newComponent: [EMAIL
I'm working on the installer stuff now.
> -Original Message-
> From: Dimitris Andreadis
> Sent: Monday, March 27, 2006 8:29 AM
> To: QA; jboss-development
> Cc: Thomas Diesler; Tom Elrod; Bill Burke; Brian Stansberry;
> Adrian Brock; Clebert Suconic; Scott M Stark; Ivelin Ivanov;
> St
I'm going to rollback until I can figure out this NPE.
-Original Message-
From: Ryan Campbell
Sent: Monday, March 27, 2006 2:57 PM
To: Scott M Stark; QA; 'jboss-development'
Subject: RE: thirdparty broken and build is throwning an NPE
Well, I'm working on upgrading javassist. That its t
Well, I'm working on upgrading javassist. That its throwing an NPE
instead of a more informative error is a separate problem.
-Original Message-
From: Ryan Campbell
Sent: Monday, March 27, 2006 2:54 PM
To: Scott M Stark; QA; 'jboss-development'
Subject: RE: thirdparty broken and build is
Yes, I'm working on this.
-Original Message-
From: Scott M Stark
Sent: Monday, March 27, 2006 2:51 PM
To: QA; 'jboss-development'
Subject: thirdparty broken and build is throwning an NPE
[synchronizeinfo] [10]: javassist
[synchronizeinfo] Checking currentComponentRef:
ComponentRef{id=ja
ant -verbose clean shows the NPE trace:
[synchronizeinfo] Creating a new version from string: 3.2.0.CR1 . This
version will be placed in a compatible.
setVersion, version=3.2.0.CR1
BUILD FAILED
C:\cvs\JBoss4.0\jboss-4.0.x\build\build.xml:937: The following error
occurred wh
ile executing this lin
[synchronizeinfo] [10]: javassist
[synchronizeinfo] Checking currentComponentRef:
ComponentRef{id=javassist,name=j
avassist,filename=component-info.xml,location=null,version=3.1RC2,compat
ibles=[C
[EMAIL PROTECTED],
version=3.1RC2}],component=null,importingComponent=Com
[EMAIL PROTECTED]/aop
atts=
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-seam-testsuite?log=log20060327101703
TESTS FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-seam-testsuite.xml:132: The following error occurred while executing this line: /services/cruisecontrol/wor
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-remoting-testsuite-1.5?log=log20060327075444
TESTS FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-remoting.xml:96: The following error occurred while executing this line: /services/cruisecontrol/wo
> Just to keep y'all up-to-date, I have one more piece of code
> to do before I cut the Hibernate release for use with 4.0.4.
> It'll be done today...
Great; I created a task to track the hibernate upgrade:
http://jira.jboss.com/jira/browse/JBAS-3009
--
Just to keep y'all up-to-date, I have one more piece of code to do
before I cut the Hibernate release for use with 4.0.4. It'll be done
today...
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Scott M Stark
Sent: Tuesday, March 21, 2006 12:38 AM
To: jbos
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-remoting-testsuite-1.4?log=log20060327072544
TESTS FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-remoting.xml:96: The following error occurred while executing this line: /services/cruisecontrol/wo
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-cache-testsuite?log=log20060327064318
TESTS FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-JBossCache.xml:86: The following error occurred while executing this line: /services/cruisecontrol/work/scripts/
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-testsuite-1.5?log=log20060327032641
TESTS FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-common.xml:235: The following error occurred while executing this line: /services/cruisecontrol/work/sc
21 matches
Mail list logo
