View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-cache-testsuite?log=log20060422011853
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-remoting-testsuite-1.5?log=log20060421231027
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/jbossweb?log=log20060421220025Lbuild.37
BUILD COMPLETE - build.37Date of build: 04/21/2006 22:00:25Time to build: 10 minutes 43 seconds
Unit Tests: (0) Total Errors an
The issue was that I had a pre-existing thirdparty with an old javassist
and I think the synchronization was looking at other component
dependencies before synchronizing javassist with the current
build-thirdparty.xml which has a newer javassit. It might have been a
timestamp problem. No point in l
It looks like whatever component in your workspace that is requiring
javassist 3.1RC2 is out of date. I don't see any components that
require it when I do a fresh checkout and build. I'm not sure how it is
possible to get into a "partially" updated repository state though.
I would make sure the
Yes that's it. I guess javassist has been updated and some component is
referencing it before javassist itself has been synchronized?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ruel
Loehr
Sent: Friday, April 21, 2006 2:28 PM
To: jboss-development@list
No, I only have one in build-thirdparty.xml:
I think the error message really is saying that something else already
wanted javassist 3.1RC2, but that aop wants 3.2.0.CR1. I'll have to look
at the build code I guess.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
It looks like it is something local to your workspace.
Does the following command yield any hits?
find thirdparty -name "component-info.xml" | xargs grep '3.1RC2'
Ruel Loehr
JBoss QA
-
512-342-7840 ext 2011
Yahoo: ruelloehr
Skype: ruelloehr
AOL: dokoruel
-Orig
Is your build-thirdparty.xml and jboss/aop/component-info.xml defining
the javaassist version to be 3.2.0.CR1?
Looks like you may have multiple lines of javaassist definitions in your
build-thirdparty.xml
Scott M Stark wrote:
I'm having trouble tracking down the cause of this javassist ver
I'm having trouble tracking down the cause of this javassist version
problem:
[synchronizeinfo] Checking currentComponentRef:
ComponentRef{id=javassist,name=j
avassist,filename=component-info.xml,location=null,version=3.2.0.CR1,com
patibles
[EMAIL PROTECTED],
version=3.2.0.CR1}],component=null,imp
Hi Julien/Chris
If you need to check whether I bugfix works for you in
jboss-4.0.x, please follow the process documented here:
http://wiki.jboss.org/wiki/Wiki.jsp?page=JBWSFAQBuildAndInstall
cheers
-thomas
Sorry about the crappy HTML post. My bad.
Same post again, sorry about the duplication.
Jboss-serialization is now dependent on trove.jar.
I used that to solve circular dependencies, and it was way better to use
TIntObjectHashMap and TObjectIntHashMap.
And jboss-serialization is included into
Jboss-serialization is now dependent on trove.jar.
I used that to solve circular dependencies, and it was way
better to use TIntObjectHashMap and TObjectIntHashMap.
And jboss-serialization is included into /client/jboss-all.jar.
So, what should I do before GA? Basically I have thr
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jbpm-sybase-testsuite?log=log20060421063019
BUILD TIMED OUTAnt Error Message: build timeoutDate of build: 04/21/2006 06:30:19Time to build: Last changed: 04/20/2006 03:10:08Last log entry: seam pageflow update. Changed type of Pr
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-cache-testsuite?log=log20060421092907
TESTS FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-JBossCache.xml:86: The following error occurred while executing this line: /services/cruisecontrol/work/scripts/
A given instance of JaasSecurityManager never has its domainCache reset.
Its set only on creation of JaasSecurityManager by the
JaasSecurityManagerService when a lookup does not have an existing
binding. This cannot be seen from the given JaasSecurityManager code
fragment though.
-Original Me
Yes, that's pretty much it. If you want to guarantee ordering you'll
have to do it with some intelligent interface between transactional
participants and the backend "datastore" (queue in this case). Or, use
JBossTS ;-)
Mark.
Tim Fox wrote:
Thanks.
This means that if I create 2 JMS XASessi
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-remoting-testsuite-1.5?log=log20060421060831
TESTS FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-remoting.xml:96: The following error occurred while executing this line: /services/cruisecontrol/wo
Thanks.
This means that if I create 2 JMS XASessions, enlist them in a global
tx, then receive messages 1, 2, 3 with session 1, and messages 4, 5, 6
in session2, then rollback the global tx, the messages will end up back
in the queue, but for some transaction managers the order in the queue
w
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jbpm-oracle-testsuite?log=log20060421050152
TESTS FAILEDAnt Error Message: /home/cruisecontrol/work/scripts/build-jbpm-db-matrix.xml:100: The following error occurred while executing this line: /home/cruisecontrol/work/scripts/bui
That's me. Sorry. Fixed now.
Bill Burke wrote:
org/jboss/ejb/plugins/EntityInstanceCache.java
I'm commenting out the line until someboyd who broke it fixes it.
---
Using Tomcat but need to do more? Need to support web services, security?
Ge
No, there's no guaranteed order (it can be different between transaction
instances and between commit phases). None of the standards provide for
it (going back beyond X/Open), and in fact that's one of the reasons
synchronizations were introduced as a separate protocol (to guarantee
ordering).
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jbpm-hsqldb-testsuite?log=log20060421041910
TESTS FAILEDAnt Error Message: /home/cruisecontrol/work/scripts/build-jbpm-db-matrix.xml:85: The following error occurred while executing this line: /home/cruisecontrol/work/scripts/buil
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-remoting-testsuite-1.4?log=log20060421030951
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/jbpm-mysql-testsuite?log=log20060421012621
TESTS FAILEDAnt Error Message: /home/cruisecontrol/work/scripts/build-jbpm-db-matrix.xml:92: The following error occurred while executing this line: /home/cruisecontrol/work/scripts/build
25 matches
Mail list logo
