You shouldn't have to. I've got an automated test run that does the same and that succeeded before I committed the db change.
I do a clean before jetty:run but that shouldn't matter. Hugo Sent from my iPhone > On 14 mrt. 2014, at 18:25, Alena Prokharchyk <alena.prokharc...@citrix.com> > wrote: > > My master version is 384eeaf79261c3f744daa138369a424d3ef37295, so all the > fixes from remote are in my local repo. I observe the error after > executing the regular sequence of: > > mvn clean install -P developer,systemvm > mvn -P developer -pl developer -Ddeploydb > mvn -pl :cloud-client-ui jetty:run > > > Hugo, do I need to clean anything manually? > > Thanks, > Alena. > > >> On 3/14/14, 10:20 AM, "Nux!" <n...@li.nux.ro> wrote: >> >>> On 14.03.2014 17:15, Alena Prokharchyk wrote: >>> Observing following error on master after re-deploying the DB and >>> running clean maven build: >>> >>> [ERROR] Nested in >>> org.springframework.context.ApplicationContextException: Failed to >>> start bean 'cloudStackLifeCycle'; nested exception is >>> com.cloud.utils.exception.CloudRuntimeException: Database version >>> 4.5.0 is higher than management software version 4.4.0-SNAPSHOT: >>> com.cloud.utils.exception.CloudRuntimeException: Database version >>> 4.5.0 is higher than management software version 4.4.0-SNAPSHOT >>> >>> >>> Whoever increased the DB version to 4.5, could you please fix it? >>> >>> Thanks, >>> Alena. >> >> Hasn't "master" just become 4.5 after Hugo's cut earlier today? >> >> Lucian >> >> -- >> Sent from the Delta quadrant using Borg technology! >> >> Nux! >> www.nux.ro >
