diff --git a/src/site/site.xml b/src/site/site.xml index 667f746..ede4b25 100644 --- a/src/site/site.xml +++ b/src/site/site.xml @@ -1,64 +1,48 @@ - - - + Commons Logging /images/logo.png - http://commons.apache.org/logging/ + https://commons.apache.org/logging/ - - - - - - - - + + + + + + + + - - - - - - - - + + + + + + + + diff --git a/src/site/xdoc/building.xml b/src/site/xdoc/building.xml index 7484ecd..c2805a2 100644 --- a/src/site/xdoc/building.xml +++ b/src/site/xdoc/building.xml @@ -24,8 +24,8 @@ limitations under the License.

- Commons Logging uses Maven 2.0.x as its - primary build system. Ant can also be used. + Commons Logging uses Maven 2.0.x as its + primary build system. Ant can also be used.

@@ -56,7 +56,7 @@ limitations under the License.

Further details can be found in the - commons build instructions. + commons build instructions.

diff --git a/src/site/xdoc/download_logging.xml b/src/site/xdoc/download_logging.xml index 79ccd0d..2a07ede 100644 --- a/src/site/xdoc/download_logging.xml +++ b/src/site/xdoc/download_logging.xml @@ -88,7 +88,7 @@ limitations under the License.

- The KEYS + The KEYS link links to the code signing keys used to sign the product. The PGP link downloads the OpenPGP compatible signature from our main site. The MD5 link downloads the checksum from the main site. @@ -100,13 +100,13 @@ limitations under the License. - - + + - - + +
commons-logging-1.2-bin.tar.gzmd5pgpmd5pgp
commons-logging-1.2-bin.zipmd5pgpmd5pgp
@@ -114,13 +114,13 @@ limitations under the License. - - + + - - + +
commons-logging-1.2-src.tar.gzmd5pgpmd5pgp
commons-logging-1.2-src.zipmd5pgpmd5pgp
@@ -131,7 +131,7 @@ limitations under the License.

diff --git a/src/site/xdoc/guide.xml b/src/site/xdoc/guide.xml index 9ae418b..721cbb2 100644 --- a/src/site/xdoc/guide.xml +++ b/src/site/xdoc/guide.xml @@ -97,8 +97,8 @@ a specific logging implementation.

JCL provides thin-wrapper Log implementations for other logging tools, including -Log4J, -Avalon LogKit +Log4J, +Avalon LogKit (the Avalon Framework's logging infrastructure), JDK 1.4, and an implementation of JDK 1.4 logging APIs (JSR-47) for pre-1.4 systems. @@ -174,16 +174,16 @@ compatibility to pre-1.0 versions of this API, a system property

  • If the Log4J logging system is available in the application class path, use the corresponding wrapper class -(Log4JLogger). +(Log4JLogger).
  • If the application is executing on a JDK 1.4 system, use the corresponding wrapper class -(Jdk14Logger). +(Jdk14Logger).
  • Fall back to the default simple logging wrapper -(SimpleLog). +(SimpleLog).

    • @@ -217,7 +217,7 @@ is responsible for handling such issues.

    Log4J is a very commonly used logging implementation (as well as being the JCL primary default), so a few details are presented herein to get the developer/integrator going. -Please see the Log4J Home for more details +Please see the Log4J Home for more details on Log4J and it's configuration.

    @@ -388,8 +388,8 @@ In addition to the logging methods, the following are provided for code guards: The commons-logging.jar file includes the JCL API, the default LogFactory implementation and thin-wrapper Log implementations for -Log4J, -Avalon LogKit, +Log4J, +Avalon LogKit, the Avalon Framework's logging infrastructure, JDK 1.4, as well as an implementation of JDK 1.4 logging APIs (JSR-47) for pre-1.4 systems. @@ -784,7 +784,7 @@ for details. JCL is distributed with a very simple Log implementation named org.apache.commons.logging.impl.SimpleLog. This is intended to be a minimal implementation and those requiring a fully functional open source logging system are -directed to Log4J. +directed to Log4J.

    SimpleLog sends all (enabled) log messages, diff --git a/src/site/xdoc/index.xml b/src/site/xdoc/index.xml index e3fd5db..4fde42e 100644 --- a/src/site/xdoc/index.xml +++ b/src/site/xdoc/index.xml @@ -60,13 +60,13 @@ containing any code that is specific to the logging implementation used.

    Release Notes document the new features and bug fixes that have been included in the latest release.

    -

    The +

    The Javadoc API documents for the latest release are available online. In particular, you should read the package overview of the org.apache.commons.logging package. In addition, there is a (short) User Guide.

    -

    The Wiki site has +

    The Wiki site has the latest updates, an FAQ and much other useful information.

    Users needing to become experts or wanting to help develop JCL should @@ -79,7 +79,7 @@ This gives short introductions to topics such as advanced class loading.

    Binary and source distributions are available - here. + here.

    The main purpose of the 1.2 release is to drop support for Java 1.1.

    @@ -138,7 +138,7 @@ Binary and source distributions are available

    Regular builds of the current SVN HEAD code are made available. See the - wiki for details.

    + wiki for details.

    diff --git a/src/site/xdoc/issue-tracking.xml b/src/site/xdoc/issue-tracking.xml index 829a90c..ab10f27 100644 --- a/src/site/xdoc/issue-tracking.xml +++ b/src/site/xdoc/issue-tracking.xml @@ -50,14 +50,14 @@ limitations under the License.

    - Commons Logging uses ASF JIRA for tracking issues. - See the Commons Logging JIRA project page. + Commons Logging uses ASF JIRA for tracking issues. + See the Commons Logging JIRA project page.

    - To use JIRA you may need to create an account + To use JIRA you may need to create an account (if you have previously created/updated Commons issues using Bugzilla an account will have been automatically - created and you can use the Forgot Password + created and you can use the Forgot Password page to get a new password).

    @@ -65,13 +65,13 @@ limitations under the License. If you would like to report a bug, or raise an enhancement request with Commons Logging please do the following:
      -
    1. Search existing open bugs. +
    2. Search existing open bugs. If you find your issue listed then please add a comment with your details.
    3. Search the mailing list archive(s). You may find your issue or idea has already been discussed.
    4. Decide if your issue is a bug or an enhancement.
      5. -
    5. Submit either a bug report - or enhancement request.
      6. +
    6. Submit either a bug report + or enhancement request.

    @@ -86,15 +86,15 @@ limitations under the License.

    For more information on subversion and creating patches see the - Apache Contributors Guide. + Apache Contributors Guide.

    You may also find these links useful:

    diff --git a/src/site/xdoc/mail-lists.xml b/src/site/xdoc/mail-lists.xml index c5bf9b9..33f3ba3 100644 --- a/src/site/xdoc/mail-lists.xml +++ b/src/site/xdoc/mail-lists.xml @@ -49,7 +49,7 @@ limitations under the License.

    Commons Logging shares mailing lists with all the other - Commons Components. + Commons Components. To make it easier for people to only read messages related to components they are interested in, the convention in Commons is to prefix the subject line of messages with the component's name, for example: @@ -59,9 +59,9 @@ limitations under the License.

    Questions related to the usage of Commons Logging should be posted to the - User List. + User List.
    - The Developer List + The Developer List is for questions and discussion related to the development of Commons Logging.
    Please do not cross-post; developers are also subscribed to the user list. @@ -102,10 +102,10 @@ limitations under the License. Subscribe Unsubscribe Post - mail-archives.apache.org - markmail.org
    - www.mail-archive.com
    - news.gmane.org + mail-archives.apache.org + markmail.org
    + www.mail-archive.com
    + news.gmane.org @@ -120,10 +120,10 @@ limitations under the License. Subscribe Unsubscribe Post - mail-archives.apache.org - markmail.org
    - www.mail-archive.com
    - news.gmane.org + mail-archives.apache.org + markmail.org
    + www.mail-archive.com
    + news.gmane.org @@ -138,9 +138,9 @@ limitations under the License. Subscribe Unsubscribe read only - mail-archives.apache.org - markmail.org
    - www.mail-archive.com + mail-archives.apache.org + markmail.org
    + www.mail-archive.com @@ -155,9 +155,9 @@ limitations under the License. Subscribe Unsubscribe read only - mail-archives.apache.org - markmail.org
    - www.mail-archive.com + mail-archives.apache.org + markmail.org
    + www.mail-archive.com @@ -188,11 +188,11 @@ limitations under the License. Subscribe Unsubscribe read only - mail-archives.apache.org - markmail.org
    - old.nabble.com
    - www.mail-archive.com
    - news.gmane.org + mail-archives.apache.org + markmail.org
    + old.nabble.com
    + www.mail-archive.com
    + news.gmane.org diff --git a/src/site/xdoc/proposal.xml b/src/site/xdoc/proposal.xml index bd97a59..d725f3f 100644 --- a/src/site/xdoc/proposal.xml +++ b/src/site/xdoc/proposal.xml @@ -83,7 +83,7 @@ Non-goals: is selected at runtime).

  • Log4J (compile-time dependency only unless this Log implementation is selected at runtime)
    • -
  • Lumberjack +
  • Lumberjack (compile-time dependency only unless this Log implementation is selected at runtime)
    • diff --git a/src/site/xdoc/tech.xml b/src/site/xdoc/tech.xml index 581ff05..bf30a48 100644 --- a/src/site/xdoc/tech.xml +++ b/src/site/xdoc/tech.xml @@ -183,10 +183,10 @@ limitations under the License.

    @@ -217,7 +217,7 @@ limitations under the License.

    - (LangSpec 12.3.3) + (LangSpec 12.3.3) The bytecode representation of a class contains symbolic names for other classes referenced.

    @@ -227,7 +227,7 @@ limitations under the License.

    - (VMSpec 5.4.3) + (VMSpec 5.4.3) Resolution of a symbolic reference occurs dynamically at runtime and is carried out by the Java Virtual Machine. Resolution of a symbolic reference requires loading and linking of the new class.

    @@ -239,7 +239,7 @@ limitations under the License.

    - (VMSpec 2.17.2) + (VMSpec 2.17.2) Loading is the name given to the process by which a binary form of a class is obtained by the Java Virtual Machine. Java classes are always loaded and linked dynamically by the Java Virtual Machine @@ -256,12 +256,12 @@ limitations under the License.

    - (VMSpec 2.17.3) + (VMSpec 2.17.3) Linking is the name used for combining the binary form of a class into the Java Virtual Machine. This must happen before the class can be used.

    - (VMSpec 2.17.3) + (VMSpec 2.17.3) Linking is composed of verification, preparation and resolution (of symbolic references). Flexibility is allowed over the timing of resolution. (Within limit) this may happen at any time after preparation and before that reference is used. @@ -278,11 +278,11 @@ limitations under the License.

    - (VMSpec 2.17.2) + (VMSpec 2.17.2) The loading process is performed by a ClassLoader.

    - (VMSpec 5.3) + (VMSpec 5.3) A classloader may create a class either by delegation or by defining it directly. The classloader that initiates loading of a class is known as the initiating loader. The classloader that defines the class is known as the defining loader. @@ -297,7 +297,7 @@ limitations under the License.

    - (VMSPEC 5.3) + (VMSPEC 5.3) The bootstrap is the base ClassLoader supplied by the Java Virtual Machine. All others are user (also known as application) ClassLoader instances.

    @@ -312,12 +312,12 @@ limitations under the License.

    - (VMSpec 5.3) + (VMSpec 5.3) At runtime, a class (or interface) is determined by its fully qualified name and by the classloader that defines it. This is known as the class's runtime package.

    - (VMSpec 5.4.4) + (VMSpec 5.4.4) Only classes in the same runtime package are mutually accessible.

    @@ -334,7 +334,7 @@ limitations under the License.

    - (VMSpec 5.3) + (VMSpec 5.3) The classloader which defines the class (whose reference is being resolved) is the one used to initiate loading of the class referred to.

    @@ -352,10 +352,10 @@ limitations under the License.
    • - VMSpec The Java Virtual Machine Specification, Second Edition + VMSpec The Java Virtual Machine Specification, Second Edition
    • - LangSpec The Java Language Specification, Second Edition + LangSpec The Java Language Specification, Second Edition
    @@ -443,7 +443,7 @@ limitations under the License.

    The Javadoc for - + Thread.setContextClassLoader emphasizes the setting of the context classloader as an aspect of thread creation. However, in many applications the context classloader is not fixed at thread creation but @@ -508,7 +508,7 @@ limitations under the License. Again, this will cause difficulties.

    - Introduced in Java J2EE 1.3 + Introduced in Java J2EE 1.3 is a requirement for vendors to appropriately set the context classloader. Section 6.2.4.8 (1.4 text):

    @@ -569,19 +569,19 @@ above.