Looks like you're right, I do have the power. I created a "modules" repo in nexus. Mark, can you update the wiki docs?
I don't see an easy way to move files in nexus. They will need to be reuploaded. Any module files in pre-release should go into the snapshots repo as Saptarshi suggests. Ben On Tue, Jan 24, 2012 at 9:43 AM, Michael Downey <[email protected]> wrote: > I feel this is pretty good and kind of aligns with our SVN (and > perhaps GitHub) model. As far as I know Ben you should be able to just > create the repository via the UI. > > Michael > > On Tue, Jan 24, 2012 at 9:35 AM, Ben Wolfe <[email protected]> wrote: > > If its easy to do, then yes, I think adding a "modules" repo seems the > most > > correct. Any reason not to do that? Do we need an ITSM ticket for that? > > > > "modules" - all omod files: openmrs supported, volunteer supported, > > mavenized, or unmavenized > > "releases" - openmrs core jar and war files > > "3rd party" - all non-mavenized libraries we need to host somewhere (old > > versions of liquibase, customized hibernate, etc) > > > > The automatic push from module.openmrs.org repository to the nexus maven > > repo is a good project to list here: > > https://wiki.openmrs.org/display/projects/Unassigned+Projects (This > project > > would be easy with our current custom repo, not sure how possible if we > > switch to something mainstream) > > > > Ben > > > > > > On Tue, Jan 24, 2012 at 8:59 AM, Mark Goodrich <[email protected]> > wrote: > >> > >> I would support a modules peer to releases. I see the reasoning for > >> separating the two, but 3rd party doesn't seem quite accurate. > >> ________________________________ > >> From: Michael Downey > >> Sent: 1/24/2012 8:07 AM > >> > >> To: [email protected] > >> Subject: Re: [OPENMRS-DEV] maven module releases -- 3rd party repo vs > >> Releases repo > >> > >> Personally I see "releases" akin to our Sourceforge mirrors. Basically > all > >> add-on modules are 3rd party developments, although the few core modules > >> owned by the core team could be debatable. > >> > >> The alternative could be creating a "modules" peer to "releases". > >> > >> Michael > >> > >> On Tuesday, January 24, 2012, Rowan Seymour <[email protected]> > >> wrote: > >> > I say anything uploaded to modules.openmrs.org and mavenized should > be > >> > automatically deployed to RELEASES. > >> > Do we actually need SNAPSHOT module artifacts? > >> > > >> > On 23 January 2012 19:04, Saptarshi Purkayastha <[email protected]> > >> > wrote: > >> >> > >> >> 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 > >> >>>> “3rd party” 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 from OpenMRS Developers' mailing list > >> >> > >> >> ________________________________ > >> >> Click here to unsubscribe from OpenMRS Developers' mailing list > >> > > >> > > >> > -- > >> > Rowan Seymour > >> > tel: +250 783835665 > >> > http://twitter.com/rowanseymour > >> > > >> > > >> > >> -- > >> > >> Best regards, > >> > >> Michael Downey > >> OpenMRS Community Infrastructure Team > >> [email protected] - http://openmrs.org/ > >> ________________________________ > >> Click here to unsubscribe from OpenMRS Developers' mailing list > >> ________________________________ > >> Click here to unsubscribe from OpenMRS Developers' mailing list > > > > > > > > -- > > Best regards, > > Michael Downey > OpenMRS Community Infrastructure Team > [email protected] - http://openmrs.org/ > > _________________________________________ > > 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] > _________________________________________ 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]
