My votes: - I would like 3rd party to be used for those that are not mavenized and do have source in the openmrs svn repository - I would like RELEASES for modules that have mavenized modules and are released - I would like SNAPSHOT for modules that have mavenized modules but are still under development
--- Regards, Saptarshi PURKAYASTHA My Tech Blog: http://sunnytalkstech.blogspot.com You Live by CHOICE, Not by CHANCE On 23 January 2012 22:09, Ben Wolfe <[email protected]> wrote: > I see addresshierarchy and serialization.xstream in the releases > repository. (xstream is then duplicated in the 3rd party too). > > I'd prefer we leave the releases for openmrs core files. Some modules are > considered to be authored and maintained by openmrs, but those might come > and go. I this we should just put all of them in the same place: 3rd party. > > Ben > > On Mon, Jan 23, 2012 at 9:35 AM, Mark Goodrich <[email protected]> wrote: > >> Is there a reason most of the module jars are being deployed to the >> “3rdparty” repo instead of the “releases” repo? >> **** >> >> ** ** >> >> If we do want them in the 3rd party repo, we should update this >> documentation accordingly:**** >> >> ** ** >> >> https://wiki.openmrs.org/display/docs/Managing+the+Maven+Repository**** >> >> ** ** >> >> Thanks, >> Mark**** >> >> ** ** >> >> ** ** >> ------------------------------ >> 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]
