Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Developers List" <dev@commons.apache.org>
MIME-Version: 1.0
In-Reply-To: <D37C9A2B.45D7A%cnauroth@hortonworks.com>
References: <CACZkXPxH1ez5yX6FLRLV_KLRho77iGq6exULnrT9Aj2PmW4toQ@mail.gmail.com>
 <CAB917RJ62ZNjSXZCQVz_KPgrEZ660VEvagLGLRmcf74w1-oaBw@mail.gmail.com>
 <CAOGo0VYzTFfSx-vdsBAjf5579qaOoj-zCVbEMG6tenRL_1Wvcg@mail.gmail.com> <D37C9A2B.45D7A%cnauroth@hortonworks.com>
From: Matt Sicker <boards@gmail.com>
Date: Tue, 7 Jun 2016 17:48:07 -0500
Message-ID: <CACmp6koVzO9__RzWA6JPhQ+gZOJ6gDxgPu2ZQgcFM9K-Qp+Vrw@mail.gmail.com>
Subject: Re: [crypto] Logging dependency
To: Commons Developers List <dev@commons.apache.org>
Content-Type: multipart/alternative; boundary=001a11415f809c630c0534b7fbf8
archived-at: Tue, 07 Jun 2016 22:48:18 -0000

--001a11415f809c630c0534b7fbf8
Content-Type: text/plain; charset=UTF-8

No library depends on (or should depend on) log4j 1.x as it ties you to
log4j 1.x. Most projects have been using commons-logging or slf4j, but
commons-logging has been superseded by log4j 2.x. Which logging library is
actually used for configuration and the actual logging should be left to
the end user.

On 7 June 2016 at 17:41, Chris Nauroth <cnauroth@hortonworks.com> wrote:

> Could you please elaborate on the argument for not logging at all?  As a
> potential user of commons-crypto, I'll be reluctant to use it if it
> doesn't provide adequate diagnostic logging when something goes wrong.
>
> Regarding the choice of Log4J 2, this is also something that could prevent
> uptake.  For better or worse, I need to support applications that
> currently use Log4J 1, and therefore they will have an expectation that
> logging can be tuned through a Log4J 1 log4j.properties or log4j.xml file.
>  I am not aware of any way for Log4J 2 to provide backwards-compatibility
> with Log4J 1 configuration files.
>
> --Chris Nauroth
>
>
>
>
> On 6/7/16, 9:07 AM, "sebb" <sebbaz@gmail.com> wrote:
>
> >On 7 June 2016 at 16:42, Benedikt Ritter <britter@apache.org> wrote:
> >> Hello Gary,
> >>
> >> Gary Gregory <garydgregory@gmail.com> schrieb am Di., 7. Juni 2016 um
> >> 04:01 Uhr:
> >>
> >>> Hi All:
> >>>
> >>> IMO. if [crypto] is to have a dependency on a logging framework, it
> >>>should
> >>> be Log4j 2, not Commons Logging. Log4j 2 has an API module, which you
> >>>can
> >>> pair with any number of implementations: Log4j's own Core, JUL, SLF4J,
> >>>and
> >>> so on.
> >>>
> >>
> >> I agree, but I'd say a low level component like crypto should not do any
> >> logging at all.
> >>
> >
> >+1 to not logging
> >
> >>>
> >>> Gary
> >>>
> >>> --
> >>> E-Mail: garydgregory@gmail.com | ggregory@apache.org
> >>> Java Persistence with Hibernate, Second Edition
> >>> <http://www.manning.com/bauer3/>
> >>> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
> >>> Spring Batch in Action <http://www.manning.com/templier/>
> >>> Blog: http://garygregory.wordpress.com
> >>> Home: http://garygregory.com/
> >>> Tweet! http://twitter.com/GaryGregory
> >>>
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> >For additional commands, e-mail: dev-help@commons.apache.org
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>


-- 
Matt Sicker <boards@gmail.com>

--001a11415f809c630c0534b7fbf8--