Hi Evanthika, We need to copy the Ant script to root folder if we are doing migration in windows OS, since there is an Ant bug . We will document this clearly in our 1.7.1 doc.. We have plan not to ship migration scripts with distribution rather will host them in svn..(we will discuss about this come up with a proper plan for our next major release..) Thanks.
On 29 July 2014 09:58, Evanthika Amarasiri <[email protected]> wrote: > Hi Ratha, > > Could you kindly look into this issue? Seems like these fixes are not > included in the 1.7.1 packs. The migration works only when you copy the > Main.java & build.xml given in the JIRA it seems. > > Regards, > Evanthika > > > On Mon, Jul 28, 2014 at 3:49 PM, Chalitha Waldeniyage <[email protected]> > wrote: > >> Hi, >> >> >> While Migrating API manager 1.6.0 to 1.7.0 following issues have been >> found. >> >> 1) You need to apply main.java and build.xml with reference [1] for it to >> work correctly.It should be shipped as built in for API manager 1.7.1. >> >> 2) In case lot of tenants are there (ex: 100) , you need to update the >> rxts for each tenant manually .In addtion to that you need to run swagger >> and resource migration for each tenant. >> >> For the latter it can be scripted but for the scenario where you update >> the rxt, do we expect the user to do this manually or should we provide >> them with the script? >> >> >> >> >> [1] - https://wso2.org/jira/browse/APIMANAGER-2529 >> >> >> >> >> >> >> Thanks, >> -- >> *Chalitha Maheshwari* >> Software Engineer-QA, >> WSO2 Inc. >> >> *E-mail:* [email protected] >> *Mobile: *+94710 411 112 >> >> _______________________________________________ >> Dev mailing list >> [email protected] >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > -- -Ratha mobile: (+94)755906608
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
