gpo.zugaina.org

Search Portage & Overlays:

dev-java/log4j-api

API for Java's Apache Log4j

Screenshots

  • log4j-api-2.2
    ~amd64
    test elibc_FreeBSD doc source elibc_FreeBSD

    View      Download      Browse     License: Apache-2.0   
    Overlay: java (layman)

ChangeLog

commit 3a12a5661c66b909b9043c4e4a1288dca91a3512
Author: James Le Cuirot <chewi@gentoo.org>
Date: Fri Apr 29 22:49:37 2016 +0100

Fix metadata in line with GLEP 67

This should shut Travis up.

commit c3a9f0793b0465b1d176a41ac8025103e496b912
Author: Andreas Sturmlechner <andreas.sturmlechner@gmail.com>
Date: Sun Aug 9 02:29:33 2015 +0200

Update/cleanup header for the git migration in main tree

again courtesy of kde overlay

Package-Manager: portage-2.2.20

commit 2b054699a7381d9d2e6e1b80fe01c01485c342cf
Author: Andreas Sturmlechner <andreas.sturmlechner@gmail.com>
Date: Fri Aug 7 00:06:26 2015 +0200

[metadata] Drop old ChangeLogs

commit 7d5ad545aee8e180b78efb2516d1c671edbf109a
Author: Johannes Huber <johu@gentoo.org>
Date: Mon Jul 20 23:50:58 2015 +0200

Use thin manifests

commit c8f323c7b01f0ce95570f38cc00e11e1a87b2b51
Author: James Le Cuirot <chewi@gentoo.org>
Date: Fri Mar 6 23:34:12 2015 +0000

The new Log4j is far more modular than version 1. This API component
is required by the core component. I have tried to get the tests
passing but I keep getting class cast exceptions and I can't figure
out why. Even swapping in the upstream jars doesn't work. Perhaps
Maven does some trickery that I'm not aware of.

Package-Manager: portage-2.2.18
Manifest-Sign-Key: 9C6D7DE4