[jboss-jira] [JBoss JIRA] Commented: (JBAS-8164) Move jboss-ha-server-* jars from common/lib to server/all/lib

[Scott Marlow (JIRA)]

    [ https://jira.jboss.org/browse/JBAS-8164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12538652#action_12538652 ] 

Scott Marlow commented on JBAS-8164:
------------------------------------

If we don't want to increase our image size (all + production share those small jars), we could also move the related clustering jars from server/all/lib to common/lib.  

Solving this jira might also help resolve an (unexplained) ClassCastException problem we hit on the Session_Ownership branch.  

> Move jboss-ha-server-* jars from common/lib to server/all/lib
> -------------------------------------------------------------
>
>                 Key: JBAS-8164
>                 URL: https://jira.jboss.org/browse/JBAS-8164
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Clustering
>    Affects Versions: 6.0.0.M3
>            Reporter: Paul Ferraro
>            Assignee: Scott Marlow
>             Fix For: 6.0.0.Final
>
>
> Currently, the build puts the following jars into common/lib:
> jboss-ha-server-api.jar
> jboss-ha-server-cache-jbc.jar
> jboss-ha-server-cache-spi.jar
> jboss-ha-server-core.jar
> This will likely cause classloader issues, especially for classes that extend/implement jbosscache or jgroups classes (e.g. CacheManager, ChannelFactory), since these jars reside in server/all/lib

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