Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Developers List" <dev@commons.apache.org>
Received-SPF: pass (nike.apache.org: domain of thomas.neidhart@gmail.com
 designates 74.125.82.46 as permitted sender)
Message-ID: <53B9A5DB.1030905@gmail.com>
Date: Sun, 06 Jul 2014 21:39:07 +0200
From: Thomas Neidhart <thomas.neidhart@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux i686;
 rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Commons Developers List <dev@commons.apache.org>
Subject: Re: [VOTE] Release Logging 1.2 based on RC2
References: <53B845EE.1010402@gmail.com> <53B97E98.2030809@gmail.com>
In-Reply-To: <53B97E98.2030809@gmail.com>
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: 7bit

On 07/06/2014 06:51 PM, Phil Steitz wrote:
> Release contents, release notes look good.
> Sigs and hashes are good.
> Tested ant build with OSX jdk 1.7.0_55, 1.8.0_05, Linux 1.6.0_43,
> 1.5.0_22-b03, 1.4.2_19-b04
> maven OSX Jdk 1.7.0_55, 1.8.0_05
> All jdks Oracle.
> 
> I did not test the site build (all tests above are "clean test").
> 
> Two non-blocking nits to improve future releases:
> * There is no sources jar in the binary distro
> * "well-known" should be hyphenated in the release notes
> 
> +1

@all: to run the unit tests for logging one has to call the following:

 mvn clean verify

This has also been added to the README.txt.

The reason being that the tests use custom classloading to test various
scenarios and require that the logging jars have been built before
running the tests.

Thomas

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