You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@rave.apache.org by "Ate Douma (Resolved) (JIRA)" <ji...@apache.org> on 2012/01/31 02:32:10 UTC

[jira] [Resolved] (RAVE-453) Duplicate jars encountered in rave-shindig

     [ https://issues.apache.org/jira/browse/RAVE-453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ate Douma resolved RAVE-453.
----------------------------

    Resolution: Fixed
    
> Duplicate jars encountered in rave-shindig
> ------------------------------------------
>
>                 Key: RAVE-453
>                 URL: https://issues.apache.org/jira/browse/RAVE-453
>             Project: Rave
>          Issue Type: Bug
>          Components: rave-shindig
>    Affects Versions: 0.7-INCUBATING
>            Reporter: Ate Douma
>            Assignee: Ate Douma
>             Fix For: 0.8-INCUBATING
>
>
> While checking up on the dependencies bundled with rave-shindig I noticed two duplicate (conflicting) jars:
> - json-20070829.jar (from shindig-server war) & json-20090211.jar (dependency from rave-core)
> - icu4j-4.8.1.1.jar (from shindig-server war) & icu4j-4.6.1.jar (dependency from rave-core)
> This fundamentally is *the* problem with maven war overlays: maven cannot check and align overlayed war internal dependencies.
> For this reason I already opened up an issue at Shindig: SHINDIG-1691 to help up better manage and use the shindig-server war similar to what we do with rave-portal ourselves.
> For the time being, I'll fix this issue by:
> a) bump our icu4j version (as defined as property in our root pom.xml) to newer version as used by Shindig itself
> b) add an extra maven-war-plugin configuration for rave-shindig to manually exclude the older json-20070829.jar from the shindig-server war 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira