Someone from infra put the necessary credentials in ~/.m2/settings.xml at
my request.  I'll ask them to do that again.

In the future, rather than nuking all of ~/.m2/, you could just nuke
~/.m2/repository/, which would leave settings.xml in place.

Steve

On Sun, Jan 6, 2013 at 12:54 PM, Uwe Schindler <[email protected]> wrote:

> Hi,
>
> I think that's my fault maybe. I nuked ~/.m2, because the maven
> repositories were fucked up. Did I delete the upload key by this?
>
> Steven: How to fix this? We should place a backup for fast restoration in
> the home directory.
>
> -----
> Uwe Schindler
> H.-H.-Meier-Allee 63, D-28213 Bremen
> http://www.thetaphi.de
> eMail: [email protected]
>
>
> > -----Original Message-----
> > From: Uwe Schindler [mailto:[email protected]]
> > Sent: Sunday, January 06, 2013 6:49 PM
> > To: [email protected]
> > Subject: RE: [JENKINS-MAVEN] Lucene-Solr-Maven-trunk #729: POMs out of
> > sync
> >
> > It looks like Steven's upload certificate/key/whatever is no longer
> working.
> > HTTP error 401 is "access denied", he upload of the maven artifacts was
> > denied by the Apache Snapshot server. Maybe it is related to the LDAP
> > problem @ ASF?
> >
> > Uwe
> >
> > -----
> > Uwe Schindler
> > H.-H.-Meier-Allee 63, D-28213 Bremen
> > http://www.thetaphi.de
> > eMail: [email protected]
> >
> >
> > > -----Original Message-----
> > > From: Apache Jenkins Server [mailto:[email protected]]
> > > Sent: Sunday, January 06, 2013 6:45 PM
> > > To: [email protected]
> > > Subject: [JENKINS-MAVEN] Lucene-Solr-Maven-trunk #729: POMs out of
> > > sync
> > >
> > > Build: https://builds.apache.org/job/Lucene-Solr-Maven-trunk/729/
> > >
> > > No tests ran.
> > >
> > > Build Log:
> > > [...truncated 127 lines...]
> > >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [email protected] For additional
> > commands, e-mail: [email protected]
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

Reply via email to