Bela and Ben,
I'd like to put forward an idea for JBoss Cache. However, first let me describe
what I'm doing.
I have a distributed application that uses JBoss Cache to distribute data to
all nodes. I'm using AOP for all cache access, synchronous replication,
transactions with read committed
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2-testsuite?log=log20050121002132Lbuild.54
BUILD COMPLETE-build.54Date of build:01/21/2005 00:21:32Time to build:70 minutes 13 secondsLast changed:01/20/2005 19:49:02Last log entry:Correct the
I already modify all jar manifests when a release is done to tag them with the
jboss release info. If a jar actually uses the version manifest (and few do)
its preserved, but the implementation headers are updated. Picking the
4.0.1/client/jacorb.jar at random:
| [EMAIL PROTECTED] client]$
Patches should be submitted to jira:
http://jira.jboss.com
Thanks.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3863036#3863036
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3863036
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0?log=log20050121014754Lbuild.327
BUILD COMPLETE-build.327Date of build:01/21/2005 01:47:54Time to build:45 minutes 7 secondsLast changed:01/21/2005 01:33:53Last log entry:Inserted sleep period to
101 - 105 of 105 matches
Mail list logo