I believe this is a classic package conflict issue for which we don't have a solution yet in the platform. We run into the same issue when deploying other third party bundles, and up until now our solution has been to merge the jars using some tool (generally a Maven script).
Thanks, Hiranya On Mon, May 14, 2012 at 2:38 PM, Kasun Gajasinghe <[email protected]> wrote: > Hi, > > The recommended subversion implementation for svn-based deployment > synchronizer is the svnkit. If svnkit is not available, the svn adapter > svnclient uses the default mechanism which contain lot of issues. > But the provided solution doesn't work. > > As seen in [1], svnkit should be picked up by svnclient if the said jars > are copied to the relevant locations. But as said in a later comment in > this issue, it doesn't work. *Seems there are issues when making a orbit > bundle from plain jars. *Though the provided solution works, it's kind of > a hack. > > Is there a proper solution for this? > > [1] > https://wso2.org/jira/browse/ESBJAVA-950?focusedCommentId=51602&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_51602 > > Thanks, > --KasunG > > -- > *Kasun Gajasinghe* > Software Engineer; > Development Technologies Team, WSO2 Inc.; http://wso2.com , > *email: **kasung AT spamfree wso2.com** cell: **+94 (77) 678-0813* > *linked-in: *http://lk.linkedin.com/in/gajasinghe* > * > *blog: **http://blog.kasunbg.org* <http://blog.kasunbg.org>* > twitter: **http://twitter.com/kasunbg* <http://twitter.com/kasunbg>* > * > > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Hiranya Jayathilaka Senior Technical Lead; WSO2 Inc.; http://wso2.org E-mail: [email protected]; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
