Hi Kasun, Yes, we need to include a fix, but the component being fixed is coming from svn (4.2.0 based one). Since components are not getting released from svn anymore, we have to release the fixed component from Git. The plan was to create a separate branch on carbon-mediation to keep the fixed component and related features.
On Tuesday, May 26, 2015, Kasun Indrasiri <ka...@wso2.com> wrote: > Can you elaborate please.. Do you want to include a fix to > carbon-mediation? > > On Tue, May 26, 2015 at 6:07 PM, Amila De Silva <ami...@wso2.com > <javascript:_e(%7B%7D,'cvml','ami...@wso2.com');>> wrote: > >> Hi, >> >> To resolve the issue mentioned in >> [1], org.wso2.carbon.mediator.bam.config needs to be patched. Since this >> component resides only on svn, it needs to get released from repo [2]. >> >> [1] https://wso2.org/jira/browse/APIMANAGER-3611 >> [2] https://github.com/wso2/carbon-mediation >> -- >> *Amila De Silva* >> >> WSO2 Inc. >> mobile :(+94) 775119302 >> >> >> _______________________________________________ >> Dev mailing list >> Dev@wso2.org <javascript:_e(%7B%7D,'cvml','Dev@wso2.org');> >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > Kasun Indrasiri > Software Architect > WSO2, Inc.; http://wso2.com > lean.enterprise.middleware > > cell: +94 77 556 5206 > Blog : http://kasunpanorama.blogspot.com/ > -- *Amila De Silva* WSO2 Inc. mobile :(+94) 775119302
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
