I could live with having bundled modules only in the standalone and none (except logic) in the war only download. However, we're putting omods into svn in the 1.x.x branches, so /not/ including it in the war would be less scriptable.
Ben On Tue, Feb 21, 2012 at 6:50 PM, Darius Jazayeri <[email protected]>wrote: > You're correct that this isn't right. > > Logic is the only *core* module. But we bundle a larger set of modules > that are generally useful, but I don't remember if these are included in > the release branch or just added when the release is built. Either it's > supposed to include the full list, or none-but-logic. > > With 1.8 we bundled (in addition to logic): > > - Form Entry > - HTML Form Entry > - XForms > - Reporting Compatibility (we'll unbundle this when Reporting > replicates the functionality of Cohort Builder and Data Exports) > - Reporting > - Serialization.Xstream (to support reporting) > - HTML Widgets (to support reporting) > > In the 1.9 pre-releases we've included all of those except for Form Entry, > because there isn't yet a version that's 1.9-compatible. And we're > intending to include Patient Flags, though I don't see that in the 1.9 Beta > release notes. I don't know what happened there. > > @Daniel: make sure we include Patient Flags in the RC... > > To speak to the broader question, it does seem like we should be releasing > two different distributions, one with "useful bundled modules" and one > minimal with just the WAR. Are the scenarios for these identical to the > current standalone versus enterprise WAR downloads? I could buy the > argument for that, rather than have 3 separate downloads (standalone, > war-with-bundled-modules, just-the-war). > > -Darius > > > On Tue, Feb 21, 2012 at 3:03 PM, Dave Thomas <[email protected]> wrote: > >> Hi. It seems like the bundled modules in the 1.9 branch are: >> >> logic >> reporting >> reportingCompatibility >> xforms >> >> I don't think this is right. I sort of thing that only logic should be >> bundled. Reporting doesn't work without its two support modules >> (htmlwidgets, xstream), so you have a permanent error in your admin/manage >> modules page, and I don't think that reportingCompatiblity or xforms should >> be bundled -- what if I don't want them, especially reportingCompatibility? >> >> Is there a decision history here that i missed? >> >> d >> ------------------------------ >> 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]
