Take 4.
New artifacts have been uploaded.Signed with my key 70C9C3D0, created
2010-02-17. Change file has an anticipated release date of November 19th.
Vote will be open at least 72 hours unless pulled.
On Nov 13, 2010, at 2:53 AM, Curt Arnold wrote:
I've prepared a release candidate
Confirmed md5, sha signatures of binaries, ran mvn install for both tar.gz
and zip, rat:check looks good, went through the site and everything looks
good.
+1
Thanks Curt!
Scott
On Mon, Nov 15, 2010 at 7:10 PM, Curt Arnold carn...@apache.org wrote:
Take 4.
New artifacts have been uploaded.
I had no in-depth checks, but surfed on the website and checked keys.
Everything looks good to me
Here is a small encoding problem on the website:
http://svn.apache.org/repos/asf/logging/site/trunk/docs/log4j/companions/extras/roadmap.html
but i think its somehow related to svn and no blocker.
+1
Thanks for the check.
The build currently uses an old RAT plugin since the latest does not appear to
support exceptions and we need them for reference log outputs, etc.
The 360 failed licenses seems to be a misreporting in the log since rat.txt
shows about that number of Apache Licenses. The
I've prepared a release candidate for review and voting. The artifacts can be
downloaded from
http://people.apache.org/builds/logging/repo/log4j/apache-log4j-extras/1.1.
The staged documentation can be viewed at
Hi Curt
mvn rat:check bombed due to (360!) failed licenses...a while back, I went
through the process of cleaning up rat warnings (
http://svn.apache.org/viewvc?view=revisionrevision=956195) ...so maybe this
is a local environment problem?
The .zip and .tar.gz won't build via mvn install, since
