These are now publishing to the Snapshots repository on our nightly builds. I am concerned about growth of the size of the repository, though. I'd like to create a scheduled task in Nexus to remove old snapshots from the Snapshots repository. Three questions:
1. Is this OK? 2. How many do we need (in terms of days and/or N versions)? 3. Do we need to keep snapshots for released versions? Michael On Thursday, December 1, 2011 at 11:09 AM, Mark Goodrich wrote: > Michael-- > > I'd like to be able to do something like this within my HFE pom and have > Maven be able to locate it: > > <dependency> > <groupId>org.openmrs.api</groupId> > <artifactId>openmrs-api</artifactId> > <version>trunk-SNAPSHOT<version> > <type>jar</type> > <scope>provided</scope> > </dependency> > > I wouldn't need these to be archived... just have the most recently jars > posted to maven repo nightly, overwriting the jars from the night before. > > Mark > > -----Original Message----- > From: [email protected] [mailto:[email protected]] On Behalf Of Michael Downey > Sent: Thursday, December 01, 2011 10:27 AM > To: [email protected] > (mailto:[email protected]) > Subject: Re: [OPENMRS-DEV] Daily trun snapshot posted to Openmrs Maven repo? > > Hi Mark, > > On Thu, Dec 1, 2011 at 10:25 AM, Mark Goodrich <[email protected] > (mailto:[email protected])> wrote: > > I see there is a "Snapshots" repository on the Openmrs Maven repo. Would it > > be possible to automatically post the current Openmrs trunk nightly build to > > this repo (or is this already being done and I'm missing it)? I'll like to > > run the Html Form Entry against the most recent trunk build (to test out > > TRUNK-2015). I could built trunk myself and post it to my local Maven repo, > > but if it happened automatically it would be a great help facilitating > > testing. > > > > > FYI, we're already archiving nightly builds on SourceForge. Are you > saying that you need it to be in the repository to test? I'm wary of > maintaining two archives but if it's a bona fide requirement we can > look at what additional resources would be necessary to maintain them. > > Michael _________________________________________ 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]
