On Sat, Dec 5, 2009 at 6:35 PM, Ruwan Linton <[email protected]> wrote: > Milinda Pathirage wrote: > > We don't need to keep old version. Because its already already in the > > maven repo. > Good point, then why do we need saxon 9.x it is also there on the repo > unless we introduce a new version of saxon we do not need that as well. > > Milinda, we might need to fix issue (like imports and exports) and do a > wso2v2 version of the orbit saxon-8.9 please do not remove that till we > test the ESB with the 9.x verison. > If doing a change I think we have to do it in the latest version and if we are working on trunk we should change the places where we use that particular orbit bundle and update them to new version. Otherwise things might go wrong.
Regards Lahiru > > BTW: what exactly is the version of Saxon that you are using in BPS? > > Thanks, > Ruwan > > > > Thanks, > > Milinda > > > > On Sat, Dec 5, 2009 at 12:06 PM, Ruwan Linton <[email protected] > > <mailto:[email protected]>> wrote: > > > > Milinda Pathirage wrote: > > > Hi devs, > > > > > > We have multiple orbit bundles for different version of same third > > > party library. For example we have saxon 9.x version for bps and > 8.9 > > > for ESB. Also we have two bundles for rhino and another two for > > axiom. > > > I think we can remove those older versions from orbit because we > > > published old versions in to maven repo and no need to keep two > > > versions in orbit. Is it ok to remove old versions and keep newest > > > version only? > > We need to test the ESB with the new version of the saxon before > > removing it. > > > > Thanks, > > Ruwan > > > > > > thanks > > > Milinda > > > > > > -- > > > Milinda Pathirage > > > Product Manager, Business Process Server - WSO2 Inc > > > Blog: http://blog.mpathirage.com > > > > > > ------------------------------------------------------------------------ > > > > > > _______________________________________________ > > > Carbon-dev mailing list > > > [email protected] <mailto:[email protected]> > > > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > > > > > -- > > Ruwan Linton > > Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb > > WSO2 <http://wso2.org/esb%0AWSO2> Inc.; http://wso2.org > > email: [email protected] <mailto:[email protected]>; cell: +94 77 341 3097 > > blog: http://blog.ruwan.org > > > > > > > > _______________________________________________ > > Carbon-dev mailing list > > [email protected] <mailto:[email protected]> > > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > > > > > > -- > > Milinda Pathirage > > Product Manager, Business Process Server - WSO2 Inc > > Blog: http://blog.mpathirage.com > > ------------------------------------------------------------------------ > > > > _______________________________________________ > > Carbon-dev mailing list > > [email protected] > > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > -- > Ruwan Linton > Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb > WSO2 <http://wso2.org/esb%0AWSO2> Inc.; http://wso2.org > email: [email protected]; cell: +94 77 341 3097 > blog: http://blog.ruwan.org > > > > _______________________________________________ > Carbon-dev mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > -- Lahiru Gunathilake Software Engineer - WSO2 Inc.
_______________________________________________ Carbon-dev mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
