To purge the local repo we have a jenkins plugin that can be used : https://wiki.jenkins-ci.org/display/JENKINS/Maven+Repo+Cleaner+Plugin (note that these days I have a doubt that it doesn't have a bug thus if we are using it at Apache too it could help us to stabilize it :-) )
For real HTTP proxy I'm not sure we could do something. The solution might be to have the good http header to not put these binaries in cache but I don't think that Nexus has such feature. This was a problem that shouldn't occur before because URLs were changing if we restaged something For MRMs they shouldn't be use to cache such group/repo excepted if they have the ability to update released binaries (I'm not sure for Nexus users). For local repo, it doesn't change, we have to purge it manually. On Wed, Nov 30, 2011 at 6:49 AM, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > purge local repo and any caching proxies in between that is > > - Stephen > > --- > Sent from my Android phone, so random spelling mistakes, random nonsense > words and other nonsense are a direct result of using swype to type on the > screen > On 30 Nov 2011 05:16, "Stephen Connolly" <stephen.alan.conno...@gmail.com> > wrote: > > > yep... now all we need is a way to easily purge if the vote is cancelled > > > > - Stephen > > > > --- > > Sent from my Android phone, so random spelling mistakes, random nonsense > > words and other nonsense are a direct result of using swype to type on > the > > screen > > On 30 Nov 2011 00:24, "Barrie Treloar" <baerr...@gmail.com> wrote: > > > >> On Wed, Nov 30, 2011 at 9:33 AM, Benson Margulies < > bimargul...@gmail.com> > >> wrote: > >> >> Are you able to give an overview or point me at the docs I haven't > >> read yet. > >> > > >> > So, whenever we stage a release, Nexus creates a private repository > >> > just for that one release of that one item. That's the URL sent around > >> > in release votes. You can put that URL into a <repository>, but once > >> > the release is promoted, it goes away. > >> > > >> > What Brian set up is a virtual repository that aggregates all the > >> > private repos of this kind for things in our groupId > >> > (org.apache.maven). So, if you add a <repository> with that URL, and > >> > pending releases are visible to you. > >> > > >> > This enables a number of interesting things. First, if you put that in > >> > your settings.xml, you can now do tests of any Maven release up for a > >> > vote without having to manually configure the url of the vote thread. > >> > > >> > Second, an RM can stage a release of a shared component, and then go > >> > ahead and modify something else to use it, and stage a release of > >> > *that*. > >> > >> Sweet thanks. > >> Having to muck around with settings.xml for release votes is painful for > >> me. > >> Being behind a firewall makes it annoying. > >> I can set this up once and forget about it. > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > >> For additional commands, e-mail: dev-h...@maven.apache.org > >> > >> >
