[jboss-jira] [JBoss JIRA] Commented: (JBAS-2251) Fix JBoss Cache / AS integration issues

[Brian Stansberry (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBAS-2251?page=comments#action_12397817 ] 
            
Brian Stansberry commented on JBAS-2251:
----------------------------------------

Here is the current comparison of common dependencies between JBC/PojoCache 2.1.0.CR3 vs. AS trunk:

jgroups.jar:                    2.6.1             vs.  2.6.1
jboss-aop 2.0.0.CR3:  2.0.0.CR3    vs.  2.0.0.CR3
jboss-javaee:               5.0.0.Beta3  vs.  5.0.0.Beta3Update1
jboss-common-core:  2.2.1.GA      vs.  2.2.3.GA
commons-logging:     1.0.4.GA      vs.  1.1.0.jboss

JBC no longer depends on anything produced by AS trunk.  The first two dependencies are the critical ones and are aligned.  The latter 3 are minor, but you can see there is drift.  If that drift was causing a problem, we'd see it in the AS testsuite, so it's OK.

Remaining work I still want to do on this next week is to add a "JBossAS" profile to the JBC/PojoCache pom.xml files where I specify the AS dependencies rather than the standard JBC ones.  We can then execute the JBC testsuite with that profile to look for issues.  Doing that is more to set up a system to ensure that things don't break down the road; I don't have any concern at all about the current alignment.

I want to keep this JIRA open until that is done.  By I don't see any reason why the current state of this should be considered as not meeting criteria for a 5.0.0.BETA4 release.

> Fix JBoss Cache / AS integration issues
> ---------------------------------------
>
>                 Key: JBAS-2251
>                 URL: http://jira.jboss.com/jira/browse/JBAS-2251
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: JBoss Cache
>            Reporter: Adrian Brock
>         Assigned To: Brian Stansberry
>            Priority: Minor
>             Fix For: JBossAS-5.0.0.Beta4
>
>
> The JBossCache standalone build includes:
> jboss-aop.jar (ok - should be standalone project)
> jboss-common.jar (ok - should be standalone project(s))
> jboss-j2ee.jar (TransactionManager interfaces)
> jboss-jmx.jar (only for JBossNotificationBroadcasterSupport leaking from jboss-system.jar?)
> jboss-minimal.jar (for MarshalledValue, etc.)
> jboss-system.jar (for ServiceMBeanSupport)
> We are heading for a fall on this (not to mention the other thirdparty jars that could get out-of-sync)
> Some of this will probably have to wait until we have the proper federated build.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira