> -----Original Message-----
> From: Gary Gregory
> Sent: Saturday, January 29, 2011 22:31
> To: Commons Developers List
> Subject: RE: Releasing commons-parent
> 
> I am trying to logon to Nexus and I get:
> 
> Nexus returned an error: ERROR 503: Service Temporarily Unavailable
> 
> Can anyone else get in?

And now from "Logging in" to "Nexus returned an error: ERROR 502: Bad Gateway"

Anyone else seeing this?

Gary

> 
> Gary
> 
> > -----Original Message-----
> > From: sebb [mailto:seb...@gmail.com]
> > Sent: Friday, January 28, 2011 17:41
> > To: Commons Developers List
> > Subject: Re: Releasing commons-parent
> >
> > IIRC I did a couple of previous releases, mainly using the Nexus page.
> >
> > In fact I used that to create the the artifacts for the VOTE thread -
> > you should be able to see them in the archives - it was early July
> > 2010.
> >
> > Once the vote pased, I just released the Nexus artifacts.
> >
> > On 28 January 2011 22:34, Gary Gregory <ggreg...@seagullsoftware.com>
> > wrote:
> > > Well, I'm going to give up for today :( Half of
> > http://wiki.apache.org/commons/CreatingReleases does not apply for a
> site-
> > less project or Maven returns errors. Very frustrating. Would the person
> > who created 17 update the wiki? I am happy to do the release, but the
> > process is non-trivial...
> > >
> > > Thanks,
> > > Gary
> > >
> > >> -----Original Message-----
> > >> From: sebb [mailto:seb...@gmail.com]
> > >> Sent: Friday, January 28, 2011 16:04
> > >> To: Commons Developers List
> > >> Subject: Re: Releasing commons-parent
> > >>
> > >> On 28 January 2011 20:13, Gary Gregory <ggreg...@seagullsoftware.com>
> > >> wrote:
> > >> >> -----Original Message-----
> > >> >> From: Rahul Akolkar [mailto:rahul.akol...@gmail.com]
> > >> >> Sent: Friday, January 28, 2011 14:50
> > >> >> To: Commons Developers List
> > >> >> Subject: Re: Releasing commons-parent
> > >> >>
> > >> >> On Fri, Jan 28, 2011 at 1:57 PM, Gary Gregory
> > >> >> <ggreg...@seagullsoftware.com> wrote:
> > >> >> >> -----Original Message-----
> > >> >> >> From: Gary Gregory [mailto:ggreg...@seagullsoftware.com]
> > >> >> >> Sent: Friday, January 28, 2011 13:56
> > >> >> >> To: Commons Developers List
> > >> >> >> Subject: Releasing commons-parent
> > >> >> >>
> > >> >> >> Well, I am digging around for instructions on publishing
> commons-
> > >> parent
> > >> >> and
> > >> >> >> I am not sure if what I am seeing on various apache pages
> applies
> > to
> > >> >> >> commons-parent which is not the same kind of project as other
> > commons
> > >> >> >> projects.
> > >> >> >>
> > >> >> >> Any tips please?
> > >> >> >
> > >> >> > I should have asked, is it as simple as calling mvn deploy:deploy
> > >> >> >
> > >> >> > ?
> > >> >> >
> > >> >> <snip/>
> > >> >>
> > >> >> Use the release plugin, scroll down to "Releasing commons-parent
> pom"
> > >> >> on this page:
> > >> >>
> > >> >>   http://wiki.apache.org/commons/CreatingReleases
> > >> >
> > >> > Ah! Thank you for the link.
> > >> >
> > >> > I read: " It is a good idea to check your settings.xml that it
> > contains
> > >> the corresponding server entries for the repositories and websites
> > defined
> > >> in the commons parent pom. If you have a different user name on your
> box
> > >> than on people.apache.org you local user name will be used for
> > >> authentication. Therefore the authentication will fail and after a few
> > >> retries your are locked out from people.apache.org for a day - which
> in
> > >> turn makes cutting a release rather lengthy. In theory you could also
> > >> provide your password in the server section below but this unsafe and
> > did
> > >> not work in my case."
> > >> >
> > >> > My apache ID and my user name on my Windows box is ggregory but my
> > >> password is obviously not the same.
> > >> >
> > >> > So... how where does my Apache password live? In settings.xml? "did
> > not
> > >> work in my case"
> > >>
> > >> See also:
> > >>
> > >> http://wiki.apache.org/commons/UsingNexus
> > >>
> > >> > Thank you,
> > >> > Gary
> > >> >
> > >> >>
> > >> >> -Rahul
> > >> >>
> > >> >> -------------------------------------------------------------------
> --
> > >> >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> > >> >> For additional commands, e-mail: dev-h...@commons.apache.org
> > >> >
> > >> >
> > >> > --------------------------------------------------------------------
> -
> > >> > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> > >> > For additional commands, e-mail: dev-h...@commons.apache.org
> > >> >
> > >> >
> > >>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> > >> For additional commands, e-mail: dev-h...@commons.apache.org
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> > > For additional commands, e-mail: dev-h...@commons.apache.org
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> > For additional commands, e-mail: dev-h...@commons.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Reply via email to