blob: e027bc406c93ee3f96244110172e86191b59ff65 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
|
SPELL=jakarta-commons-logging
VERSION=1.0.2
SOURCE=${SPELL##*-}-${VERSION}-src.tar.gz
SOURCE_DIRECTORY=$BUILD_DIRECTORY/${SPELL#*-}-${VERSION}-src
SOURCE_URL[0]=http://www.apache.org/dist/${SPELL//-/\/}/source/$SOURCE
SOURCE_URL[1]=http://archive.apache.org/dist/commons/${SPELL##*-}/source/$SOURCE
SOURCE_HASH=sha512:acabf10b27965cffc71bc920e6643fb66d555b827bd4387c65c8d6c08a9ea79644041321958935da310583567212d46691c925ef2d1879629a8bc473148cf1b2
LICENSE[0]=APACHE
WEB_SITE=http://jakarta.apache.org/commons/logging.html
KEYWORDS="java"
ENTERED=20030326
SHORT="Jakarta-Commons Logging Component."
cat << EOF
There is a great need for debugging and logging information inside of
Commons components
such as HTTPClient and DBCP. However, there are many logging APIs out there
and it is
difficult to choose among them.
The Logging package is an ultra-thin bridge between different logging
libraries. Commons
components may use the Logging API to remove compile-time and run-time
dependencies on
any particular logging package, and contributors may write Log implementations
for the
library of their choice.
EOF
|