Mailing-List: contact cxf-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cxf-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of bimargulies@gmail.com
 designates 72.14.246.241 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
        b=dZrsb9LaOYiMtfvF4zGqH4PXnx0NhSz6fZgGBqlcSQlFoPN8XljEze+Cf7Y+/66TIsL9PfgCD50g2NzevIul1nEoVVfAcQIGNVbfNulsgunmbrzVrPKkse+Dsm74S6R5kWGIFwz6BOBRxbQB8d2ZuIHdqu0ssax2K1GByc70g1I=
Message-ID: <61b5d9410804091251t2ffea2a7x55287025142a3f56@mail.gmail.com>
Date: Wed, 9 Apr 2008 15:51:06 -0400
From: "Benson Margulies" <bimargulies@gmail.com>
To: cxf-dev@incubator.apache.org
Subject: Re: IBM jdk "issue"
In-Reply-To: <200804091454.33755.dkulp@apache.org>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_109_31428945.1207770666970"
References: <200804091454.33755.dkulp@apache.org>

------=_Part_109_31428945.1207770666970
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Let's create all the files. It's convenient to have them there to edit when
you want to customize the logging.

On Wed, Apr 9, 2008 at 2:54 PM, Daniel Kulp <dkulp@apache.org> wrote:

>
> I'm playing around with the latest IBM 1.6 JDK cause I think we can now
> support it since there is a version of SAAJ built in that actually
> works.
>
> However, I've run into a minor "snag".   For every test, we have it
> configured to look for target/test-classes/logging.properties for the
> logging properties.   However, that file doesn't exist for almost all
> our cases.   Sun just ignores it and pretty much doesn't log anything.
> IBM, however, spits out a stack trace and then sets the warning level to
> WARNING.   It's non-fatal, but it does result in a stack trace printed
> for each module (and probably a bunch in systest, haven't gotten that
> far yet).
>
> Options:
> 1) Document it as a "known issue" with building with the IBM jdk.
>
> 2) Add a suitable logging.properties files to EVERY module.
>
> 3) Don't set a "java.util.logging.config.file" and just allow the info
> level stuff to spit out on Sun.  (lots of stuff, although less with the
> work Benson and Glen have done)
>
> Others?   Thoughts?
>
> --
> J. Daniel Kulp
> Principal Engineer, IONA
> dkulp@apache.org
> http://www.dankulp.com/blog
>

------=_Part_109_31428945.1207770666970--