Nick, great work on preparing the release! Awesome! I just woke up and will
verify today.
-Remko

Ralph, get well soon!
-Remko


On Sunday, February 9, 2014, Nick Williams <nicho...@nicholaswilliams.net>
wrote:

> Turns out my email address in Sonatype is not correct (it's just my Apache
> ID, "nickwilliams," instead of my Apache email address). This is why I
> couldn't get the notification. I "hacked" a previous release vote to point
> the links to the rc1 release repository. I've emailed Infra to get my email
> address corrected, since it's read-only in Sonatype.
>
> Nick
>
> On Feb 8, 2014, at 2:52 PM, Christian Grobmeier wrote:
>
> > On 8 Feb 2014, at 21:12, Nick Williams wrote:
> >
> >> Almost done. In the vote email, I'm supposed to, "Provide a list of the
> artifacts by copying from the email sent from the Nexus Repository." I
> didn't get an email from the Nexus Repository. Perhaps that only went to
> the PMC? Can someone forward that email to me privately?
> >
> > I haven't seen an email to the PMC. If it would be sent to private it
> would need to go to public anyway as this is not confidential.
> >
> > Great you have made it, thanks! I am going to vote tomorrow.
> >
> >
> >
> >
> >> Nick
> >>
> >> On Feb 8, 2014, at 1:17 PM, Christian Grobmeier wrote:
> >>
> >>> On 8 Feb 2014, at 20:11, Nick Williams wrote:
> >>>> On Feb 8, 2014, at 1:06 PM, Christian Grobmeier wrote:
> >>>>> OK, so just confirming you want me to do:
> >>>>> svn delete
> https://svn.apache.org/repos/asf/logging/log4j/log4j2/tags/log4j-2.0-rc1/
> >>>>
> >>>> Correct. Please delete that.
> >>>
> >>> OK, its done.
> >>>
> >>>>> I would prefer to give you the permissions, if there are any to give.
> >>>>> I will look around, maybe i find a hint.
> >>>>
> >>>> Some Googling reveals that I need to edit ~/.m2/settings.xml and add
> my repository username and password to it. Why it can't just PROMPT me for
> my username and password is beyond me. I'll update the wiki with more info
> after all of this. Just delete that tag and I'll make another attempt.
> >>>
> >>> Please also note my other mail - you may need additional -D params
> duplicating password info.
> >>>
> >>> And yes, updating the wiki is always welcome.
> >>>
> >>>>
> >>>> Nick
> >>>>
> >>>>>
> >>>>>
> >>>>> Cheers
> >>>>> Christian
> >>>>>
> >>>>>
> >>>>>>
> >>>>>> Nick
> >>>>>>
> >>>>>> On Feb 8, 2014, at 12:13 PM, Nick Williams wrote:
> >>>>>>
> >>>>>>> Christian was right. The distribution POM was still referring to
> log4j-core-osgi-nosql-mongo and log4j-core-osgi-nosql-couch. I've fixed
> that. Continuing the release...
> >>>>>>>
> >>>>>>> N
> >>>>>>>
> >>>>>>> On Feb 8, 2014, at 12:11 PM, Ralph Goers wrote:
> >>>>>>>
> >>>>>>>> When you run the build you should have just had to hit enter a
> bunch of times to set they version.  I have never gotten messages like
> below when releasing.
> >>>>>>>>
> >>>>>>>> Sent from my iPad
> >>>>>>>>
> >>>>>>>> On Feb 8, 2014, at 9:02 AM, Nick Williams <
> nicho...@nicholaswilliams.net> wrote:
> >>>>>>>>
> >>>>>>>>> The wiki does NOT have enough info on this...
> >>>>>>>>>
> >>>>>>>>> I got the following error that prevent release from proceeding
> (and forced me to have to revert a bunch of staged changes):
> >>>>>>>>>
> >>>>>>>>> [INFO] [ERROR] Failed to execute goal on project
> log4j-distribution: Could not resolve dependencies for project
> org.apache.logging.log4j:log4j-distribution:pom:2.0-rc1: The following
> artifacts could not be resolved:
> org.apache.logging.log4j.osgi:log4j-core-osgi-nosql-couch:jar:2.0-rc1,
> org.apache.logging.log4j.osgi:log4j-core-osgi-nosql-mongo:jar:2.0-rc1:
> Could not find artifact
> org.apache.logging.log4j.osgi:log4j-core-osgi-nosql-couch:jar:2.0-rc1 in
> oracleReleases (http://download.oracle.com/maven) -> [Help 1]
> >>>>>>>>>
> >>>>>>>>> This was after having received a bunch of prompts I wasn't
> expecting. I'm not sure I responded to them all correctly. Can anyone tell
> me what I should do next?
> >>>>>>>>>
> >>>>>>>>> [INFO] Checking dependencies and plugins for snapshots ...
> >>>>>>>>> There are stil

Reply via email to