Digging slightly deeper and playing with the runtime properties files... Removing the *auto_update_database=true* , will show the initialization wizard. Else will fail trying to update the database...
Still, I think the behavior changed. I've been using the same properties since liquibase first made appearance in OpenMRS 1.7 --- Regards, Saptarshi PURKAYASTHA My Tech Blog: http://sunnytalkstech.blogspot.com You Live by CHOICE, Not by CHANCE On 3 March 2012 02:47, Saptarshi Purkayastha <[email protected]> wrote: > ok, so after your email I've been retesting > > This is what I do after building trunk. > 1.) Create a new database > 2.) Create openmrs-runtime.properties > 3.) jetty:run on openmrs-webapp > > This is my log: http://pastebin.com/CG9DgAfp > This is my runtime-properties: http://pastebin.com/pcHDPk5J > > --- > Regards, > Saptarshi PURKAYASTHA > > My Tech Blog: http://sunnytalkstech.blogspot.com > You Live by CHOICE, Not by CHANCE > > > On 3 March 2012 01:13, Ben Wolfe <[email protected]> wrote: > >> FYI: I just tested this on trunk and if I have a runtime-properties file >> pointing to a database with no tables I am sent to the initialization >> wizard. >> >> Ben >> >> >> On Mon, Jan 30, 2012 at 4:10 PM, Saptarshi Purkayastha >> <[email protected]>wrote: >> >>> So if I want to see the installation wizard, there should be no >>> runtime.properties file >>> >>> This is different behavior from the earlier versions, where we can have >>> the runtime.properties file, but a blank database and it would run all the >>> changesets starting from schema, demo data and then update. >>> >>> --- >>> Regards, >>> Saptarshi PURKAYASTHA >>> >>> My Tech Blog: http://sunnytalkstech.blogspot.com >>> You Live by CHOICE, Not by CHANCE >>> >>> >>> On 31 January 2012 02:35, Saptarshi Purkayastha <[email protected]>wrote: >>> >>>> Yes, but shouldn't the liquibase update file be executed after schema >>>> creation and demo data?? >>>> I don't see the installation wizard anymore... >>>> >>>> --- >>>> Regards, >>>> Saptarshi PURKAYASTHA >>>> >>>> My Tech Blog: http://sunnytalkstech.blogspot.com >>>> You Live by CHOICE, Not by CHANCE >>>> >>>> >>>> On 31 January 2012 02:27, Wyclif Luyima <[email protected]> wrote: >>>> >>>>> I don't think this is a bug, this is the correct behaviour, the >>>>> liquibase update file should always be executed even during installation >>>>> to >>>>> add or update the core(required) tables in the DB >>>>> >>>>> 'Blank' database technically means include core tables and update them >>>>> but add no demo patient data. >>>>> >>>>> Wyclif >>>>> >>>>> On Mon, Jan 30, 2012 at 3:38 PM, Saptarshi Purkayastha < >>>>> [email protected]> wrote: >>>>> >>>>>> Dear devs, >>>>>> >>>>>> Is anyone else seeing trouble with new installations of OpenMRS? >>>>>> When I deploy OpenMRS into tomcat and create the >>>>>> openmrs-runtime.properties pointing to a blank MySQL database, it tries >>>>>> to >>>>>> run the liquibase-update-to-latest.xml. >>>>>> This should not be the case and should execute the schema-only, >>>>>> core-data liquibase xmls first. >>>>>> >>>>>> Can someone confirm this is a bug and a definite blocker. >>>>>> >>>>>> --- >>>>>> Regards, >>>>>> Saptarshi PURKAYASTHA >>>>>> >>>>>> My Tech Blog: http://sunnytalkstech.blogspot.com >>>>>> You Live by CHOICE, Not by CHANCE >>>>>> ------------------------------ >>>>>> Click here to >>>>>> unsubscribe<[email protected]?body=SIGNOFF%20openmrs-devel-l>from >>>>>> OpenMRS Developers' mailing list >>>>> >>>>> >>>>> >>>> >>> ------------------------------ >>> Click here to >>> unsubscribe<[email protected]?body=SIGNOFF%20openmrs-devel-l>from >>> OpenMRS Developers' mailing list >>> >> >> > _________________________________________ To unsubscribe from OpenMRS Developers' mailing list, send an e-mail to [email protected] with "SIGNOFF openmrs-devel-l" in the body (not the subject) of your e-mail. [mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l]
