Found a workaround for this, we forgot to put db folder (including all its scripts) under jetty client webapp folder. For me, it is under <root>/client/target/cloud-client-ui-4.1.0-SNAPSHOT/WEB-INF/lib. Our maven script may need a fix for this.
Thanks -min On 10/25/12 4:25 PM, "Min Chen" <[email protected]> wrote: > >Hi Edison, >On Master branch, running MS using mvm failed to upgrade my database: > >INFO [cloud.upgrade.DatabaseUpgradeChecker] (main:) DB version = 2.2.14 >Code Version = 4.1.0-SNAPSHOT >INFO [cloud.upgrade.DatabaseUpgradeChecker] (main:) Database upgrade >must be performed from 2.2.14 to 4.1.0-SNAPSHOT >WARN [utils.script.Script] (main:) Unable to find script >db/schema-2214to30.sql >ERROR [utils.component.ComponentLocator] (main:) Problems with running >checker:DatabaseUpgradeChecker >com.cloud.utils.exception.CloudRuntimeException: Unable to find >db/schema-2214to30.sql >at >com.cloud.upgrade.dao.Upgrade2214to30.getPrepareScripts(Upgrade2214to30.ja >va:62) > >I used to encounter this problem on 4.0 branch on windows, where I just >need to move >{tomcat.home}/webapps/client/WEB-INF/lib/db/db/*.* to one level up to >{tomcat.home}/webapps/client/WEB-INF/lib/db, >But this workaround is no longer working anymore since we are using jetty >now. Any solution to this issue? I am running my MS from Mac OS. > >Thanks >-min >
