Just an idea: don't forget the archetype plugin: https://docs.sonatype.com/display/NX/Nexus+Archetype+Plugin
Having it on r.a.o would be awesome. I can easily "downgrade" is to support Nexus 1.2.x (until 1.3 is not released). ~t~ On Fri, Feb 6, 2009 at 4:52 PM, Brian E. Fox <bri...@reply.infinity.nu>wrote: > I have thought about backing up the repo as well but haven't acted on it > for one main reason: the entire content of the apache repository is > replicated to central and then around the world to countless sites. There > isn't much to lose here that makes me overly concerned about replicating the > repo yet again. This is not true of the snapshot repo but losing that is > just an inconvenience. > > That's not to say we can't rsync the storage contents to yet another disk > inside of apache if we decide it's needed. > > -----Original Message----- > From: Jesse McConnell [mailto:jesse.mcconn...@gmail.com] > Sent: Friday, February 06, 2009 10:29 AM > To: Maven Developers List > Subject: Re: [vote] use repository.zones.apache.org as the new > staging/releasing location for Maven artifacts > > well might be a bit belated but I am +1 for this as well, bringing a > bit of order to the staging process is a good thing.. > > my only concern which I have written a number of responses to only to > just delete and not send is something that has been brought up a > number of times on the infra list... > > nexus brings a nice level of security to the repo practices that has > been missing but I am still a bit concerned on the artifacts on disk > from a recovery standpoint...I would feel more comfortable with it if > the artifact storage was backed by an scm...maybe not in this > particular instance for staging and promotion, but for the actual > repo...would be comforting to me. especially if we are starting to > move towards having tooling like nexus or archiva sitting over and > managing artifacts on a disk. Things like that symbolic link clean > issue that was just reported happen and having it backed by a backed > up scm would be comforting... > > my 2 cents, > jesse > > -- > jesse mcconnell > jesse.mcconn...@gmail.com > > > > On Fri, Feb 6, 2009 at 9:09 AM, Jason van Zyl <jvan...@sonatype.com> > wrote: > > > > On 6-Feb-09, at 12:23 AM, Ralph Goers wrote: > > > >> > >> On Feb 5, 2009, at 10:34 PM, Jason van Zyl wrote: > >> > >>> On 5-Feb-09, at 9:53 PM, Ralph Goers wrote: > >>> > >>>> I'm not sure why this needs a vote. Just do it. > >>>> > >>> > >>> This requires pulling all of the org.apache.maven.* artifacts into > Nexus > >>> and that's where they stay for this project because we can't keep > partial > >>> bits here and over on people. We are suggesting that projects at Apache > >>> decide on a per-project basis. So there are currently only two > solutions: > >>> use people or use Nexus. That's why Brian asked people. > >>>> > >> > >> I'm confused by your use of "people" in the last two sentences. The last > >> "people" could either mean infra or the folks on this list - it > obviously > >> isn't p.a.o. I saw all the traffic on Infra where Brian asked about > this > >> and was told how. No one objected that I saw when this was mentioned on > this > >> list several days ago. I realize you may not want to seem like you are > >> forcing this on anyone, but it seemed to me this was a done deal when > infra > >> told Brian to set it up in a zone. > >> > >> But if you want a +1 instead, consider this it. > >> > > > > It would be possible to support the staging without moving everything for > > Maven over into one location, but I would prefer to stick to concrete and > > currently the best (and only solution) for staging and promotion that > isn't > > painful is Nexus. So we did the staging and thought about how much work > it > > would be to support that and it's far simpler to just move everything for > > projects that want to use Nexus. I don't want to do a huge amount of work > > based on the theoretical possibility there will be another option anytime > in > > the near future. > > > >> Ralph > >> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > >> For additional commands, e-mail: dev-h...@maven.apache.org > >> > > > > Thanks, > > > > Jason > > > > ---------------------------------------------------------- > > Jason van Zyl > > Founder, Apache Maven > > jason at sonatype dot com > > ---------------------------------------------------------- > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
