diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 22d84a5..a261465 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -25,7 +25,7 @@ | commons-build-plugin/trunk/src/main/resources/commons-xdoc-templates | +======================================================================+ | | - | 1) Re-generate using: mvn commons:contributing-md | + | 1) Re-generate using: mvn commons-build:contributing-md | | | | 2) Set the following properties in the component's pom: | | - commons.jira.id (required, alphabetic, upper case) | @@ -51,47 +51,65 @@ Getting Started + Make sure you have a [JIRA account](https://issues.apache.org/jira/). + Make sure you have a [GitHub account](https://github.com/signup/free). + If you're planning to implement a new feature it makes sense to discuss your changes on the [dev list](https://commons.apache.org/mail-lists.html) first. This way you can make sure you're not wasting your time on something that isn't considered to be in Apache Commons Logging's scope. -+ Submit a ticket for your issue, assuming one does not already exist. ++ Submit a [Jira Ticket][jira] for your issue, assuming one does not already exist. + Clearly describe the issue including steps to reproduce when it is a bug. + Make sure you fill in the earliest version that you know has the issue. -+ Fork the repository on GitHub. ++ Find the corresponding [repository on GitHub](https://github.com/apache/?query=commons-), +[fork](https://help.github.com/articles/fork-a-repo/) and check out your forked repository. Making Changes -------------- -+ Create a topic branch from where you want to base your work (this is usually the master/trunk branch). ++ Create a _topic branch_ for your isolated work. + * Usually you should base your branch on the `master` branch. + * A good topic branch name can be the JIRA bug id plus a keyword, e.g. `LOGGING-123-InputStream`. + * If you have submitted multiple JIRA issues, try to maintain separate branches and pull requests. + Make commits of logical units. + * Make sure your commit messages are meaningful and in the proper format. Your commit message should contain the key of the JIRA issue. + * e.g. `LOGGING-123: Close input stream earlier` + Respect the original code style: + Only use spaces for indentation. - + Create minimal diffs - disable on save actions like reformat source code or organize imports. If you feel the source code should be reformatted create a separate PR for this change. - + Check for unnecessary whitespace with git diff --check before committing. -+ Make sure your commit messages are in the proper format. Your commit message should contain the key of the JIRA issue. -+ Make sure you have added the necessary tests for your changes. + + Create minimal diffs - disable _On Save_ actions like _Reformat Source Code_ or _Organize Imports_. If you feel the source code should be reformatted create a separate PR for this change first. + + Check for unnecessary whitespace with `git diff` -- check before committing. ++ Make sure you have added the necessary tests for your changes, typically in `src/test/java`. + Run all the tests with `mvn clean verify` to assure nothing else was accidentally broken. Making Trivial Changes ---------------------- +The JIRA tickets are used to generate the changelog for the next release. + For changes of a trivial nature to comments and documentation, it is not always necessary to create a new ticket in JIRA. In this case, it is appropriate to start the first line of a commit with '(doc)' instead of a ticket number. + Submitting Changes ------------------ -+ Sign the [Contributor License Agreement][cla] if you haven't already. ++ Sign and submit the Apache [Contributor License Agreement][cla] if you haven't already. + * Note that small patches & typical bug fixes do not require a CLA as + clause 5 of the [Apache License](https://www.apache.org/licenses/LICENSE-2.0.html#contributions) + covers them. + Push your changes to a topic branch in your fork of the repository. -+ Submit a pull request to the repository in the apache organization. ++ Submit a _Pull Request_ to the corresponding repository in the `apache` organization. + * Verify _Files Changed_ shows only your intended changes and does not + include additional files like `target/*.class` + Update your JIRA ticket and include a link to the pull request in the ticket. +If you prefer to not use GitHub, then you can instead use +`git format-patch` (or `svn diff`) and attach the patch file to the JIRA issue. + + Additional Resources -------------------- + [Contributing patches](https://commons.apache.org/patches.html) -+ [Apache Commons Logging JIRA project page](https://issues.apache.org/jira/browse/LOGGING) ++ [Apache Commons Logging JIRA project page][jira] + [Contributor License Agreement][cla] + [General GitHub documentation](https://help.github.com/) -+ [GitHub pull request documentation](https://help.github.com/send-pull-requests/) ++ [GitHub pull request documentation](https://help.github.com/articles/creating-a-pull-request/) + [Apache Commons Twitter Account](https://twitter.com/ApacheCommons) -+ #apachecommons IRC channel on freenode.org ++ `#apache-commons` IRC channel on `irc.freenode.net` [cla]:https://www.apache.org/licenses/#clas +[jira]:https://issues.apache.org/jira/browse/LOGGING diff --git a/NOTICE.txt b/NOTICE.txt index 53257af..67d7715 100644 --- a/NOTICE.txt +++ b/NOTICE.txt @@ -1,6 +1,5 @@ Apache Commons Logging -Copyright 2003-2023 The Apache Software Foundation +Copyright 2001-2023 The Apache Software Foundation This product includes software developed at The Apache Software Foundation (https://www.apache.org/). - diff --git a/README.md b/README.md index caad61a..de5a25f 100644 --- a/README.md +++ b/README.md @@ -25,7 +25,7 @@ | commons-build-plugin/trunk/src/main/resources/commons-xdoc-templates | +======================================================================+ | | - | 1) Re-generate using: mvn commons:readme-md | + | 1) Re-generate using: mvn commons-build:readme-md | | | | 2) Set the following properties in the component's pom: | | - commons.componentid (required, alphabetic, lower case) | @@ -42,40 +42,53 @@ ---> Apache Commons Logging =================== -[![Java CI](https://github.com/apache/commons-logging/actions/workflows/maven.yml/badge.svg)](https://github.com/apache/commons-logging/actions/workflows/maven.yml) -[![Maven Central](https://maven-badges.herokuapp.com/maven-central/commons-logging/commons-logging/badge.svg?gav=true)](https://maven-badges.herokuapp.com/maven-central/commons-logging/commons-logging/?gav=true) -[![CodeQL](https://github.com/apache/commons-logging/actions/workflows/codeql-analysis.yml/badge.svg)](https://github.com/apache/commons-logging/actions/workflows/codeql-analysis.yml) -Apache Commons Logging is a thin adapter allowing configurable bridging to other, well known logging systems. +[![Java CI](https://github.com/apache/commons-logging/actions/workflows/maven.yml/badge.svg)](https://github.com/apache/commons-logging/actions/workflows/maven.yml) +[![Coverage Status](https://codecov.io/gh/apache/commons-logging/branch/master/graph/badge.svg)](https://app.codecov.io/gh/apache/commons-logging) +[![Maven Central](https://maven-badges.herokuapp.com/maven-central/commons-logging/commons-logging/badge.svg?gav=true)](https://maven-badges.herokuapp.com/maven-central/commons-logging/commons-logging/?gav=true) +[![Javadocs](https://javadoc.io/badge/commons-logging/commons-logging/1.3.0.svg)](https://javadoc.io/doc/commons-logging/commons-logging/1.3.0) +[![CodeQL](https://github.com/apache/commons-logging/actions/workflows/codeql-analysis.yml/badge.svg)](https://github.com/apache/commons-logging/actions/workflows/codeql-analysis.yml) +[![OpenSSF Scorecard](https://api.securityscorecards.dev/projects/github.com/apache/commons-logging/badge)](https://api.securityscorecards.dev/projects/github.com/apache/commons-logging) + +Apache Commons Logging is a thin adapter allowing configurable bridging to other, + well known logging systems. Documentation ------------- More information can be found on the [Apache Commons Logging homepage](https://commons.apache.org/proper/commons-logging). -The [Javadoc](https://commons.apache.org/proper/commons-logging/javadocs/api-release) can be browsed. +The [Javadoc](https://commons.apache.org/proper/commons-logging/apidocs) can be browsed. Questions related to the usage of Apache Commons Logging should be posted to the [user mailing list][ml]. -Where can I get the latest release? ------------------------------------ +Getting the latest release +-------------------------- You can download source and binaries from our [download page](https://commons.apache.org/proper/commons-logging/download_logging.cgi). -Alternatively, you can pull it from the central Maven repositories: +Alternatively, you can pull it from the central Maven repositories: ```xml commons-logging commons-logging - 1.2 + 1.3.0 ``` +Building +-------- + +Building requires a Java JDK and [Apache Maven](https://maven.apache.org/). +The required Java version is found in the `pom.xml` as the `maven.compiler.source` property. + +From a command shell, run `mvn` without arguments to invoke the default Maven goal to run all tests and checks. + Contributing ------------ -We accept Pull Requests via GitHub. The [developer mailing list][ml] is the main channel of communication for contributors. +We accept Pull Requests via GitHub. The [developer mailing list](https://commons.apache.org/mail-lists.html) is the main channel of communication for contributors. There are some guidelines which will make applying PRs easier for us: + No tabs! Please use spaces for indentation. -+ Respect the code style. ++ Respect the existing code style for each file. + Create minimal diffs - disable on save actions like reformat source code or organize imports. If you feel the source code should be reformatted create a separate PR for this change. + Provide JUnit tests for your changes and make sure your changes don't break any existing tests by running ```mvn```. @@ -84,20 +97,24 @@ You can learn more about contributing via GitHub in our [contribution guidelines License ------- -This code is under the [Apache License v2](https://www.apache.org/licenses/LICENSE-2.0). +This code is licensed under the [Apache License v2](https://www.apache.org/licenses/LICENSE-2.0). See the `NOTICE.txt` file for required notices and attributions. -Donations ---------- -You like Apache Commons Logging? Then [donate back to the ASF](https://www.apache.org/foundation/contributing.html) to support the development. +Donating +-------- +You like Apache Commons Logging? Then [donate back to the ASF](https://www.apache.org/foundation/contributing.html) to support development. Additional Resources -------------------- + [Apache Commons Homepage](https://commons.apache.org/) + [Apache Issue Tracker (JIRA)](https://issues.apache.org/jira/browse/LOGGING) ++ [Apache Commons Slack Channel](https://the-asf.slack.com/archives/C60NVB8AD) + [Apache Commons Twitter Account](https://twitter.com/ApacheCommons) + `#apache-commons` IRC channel on `irc.freenode.org` -[ml]:https://commons.apache.org/mail-lists.html +Apache Commons Components +------------------------- + +Please see the [list of components](https://commons.apache.org/components.html) diff --git a/RELEASE-NOTES.txt b/RELEASE-NOTES.txt index 2197ca5..7f91c19 100644 --- a/RELEASE-NOTES.txt +++ b/RELEASE-NOTES.txt @@ -1,7 +1,74 @@ Apache Commons Logging - Version 1.2 + Version 1.3.0 RELEASE NOTES +The Apache Commons Logging team is pleased to announce the release of Apache Commons Logging 1.3.0. + +Apache Commons Logging is a thin adapter allowing configurable bridging to other, +well known logging systems. + +This is a feature and maintenance release. Java 8 or later is required. + +Changes in this version include: + +New features: +o Add support for Log4j API and SLF4J #177. Thanks to Piotr P. Karwasz. +o Deprecate org.apache.commons.logging.impl.WeakHashtable without replacement. Thanks to Piotr P. Karwasz. +o LOGGING-188: Deprecate and disable `Jdk13LumberjackLogger` and `Log4JLogger`. Thanks to Piotr P. Karwasz. +o LOGGING-173: Deprecate and disable `AvalonLogger` and `LogKitLogger`. Thanks to SingingBush. +o LOGGING-165: Add Automatic-Module-Name Manifest Header for Java 9 compatibility. + +Fixed Bugs: +o LOGGING-163: BufferedReader is not closed properly. Thanks to Kaloyan Spiridonov. +o LOGGING-177: Remove redundant initializer #46 Thanks to Arturo Bernal. +o Use a weak reference for the cached class loader #71. Thanks to Jakob van Kruijssen, Bruno P. Kinoshita, Gary Gregory. +o Add more entries to .gitignore file #25. Thanks to xiaozhiliaoo. +o Minor Improvements #34. Thanks to Arturo Bernal. +o [StepSecurity] ci: Harden GitHub Actions #145. Thanks to step-security-bot, Gary Gregory. +o LOGGING-185: Replace custom code with `ServiceLoader` call. Thanks to Piotr P. Karwasz. +o Fix possible NPEs in LogFactoryImpl. Thanks to Gary Gregory. +o LOGGING-185: Fix failing tests #180. Thanks to Piotr P. Karwasz. +o Deprecate LogConfigurationException.cause in favor of getCause(). Thanks to Gary Gregory. +o Fix SpotBugs [ERROR] High: Found reliance on default encoding in org.apache.commons.logging.LogFactory.initDiagnostics(): new java.io.PrintStream(OutputStream) [org.apache.commons.logging.LogFactory] At LogFactory.java:[line 1205] DM_DEFAULT_ENCODING. Thanks to Gary Gregory. +o Fix SpotBugs [ERROR] Medium: Class org.apache.commons.logging.impl.WeakHashtable defines non-transient non-serializable instance field queue [org.apache.commons.logging.impl.WeakHashtable] In WeakHashtable.java SE_BAD_FIELD. Thanks to Gary Gregory. +o Set java.logging as optional module #183. Thanks to Piotr P. Karwasz. +o Fix SpotBugs [ERROR] Medium: Switch statement found in org.apache.commons.logging.impl.SimpleLog.log(int, Object, Throwable) where default case is missing [org.apache.commons.logging.impl.SimpleLog] At SimpleLog.java:[lines 505-522] SF_SWITCH_NO_DEFAULT. Thanks to Gary Gregory. +o Deprecate org.apache.commons.logging.impl.Jdk13LumberjackLogger.dummyLevel without replacement. Thanks to Gary Gregory. + +Changes: +o Bump Java from 6 to 8. Thanks to Gary Gregory. +o Bump actions/cache from 2 to 3.0.10 #50, #77, #95, #98, #107, #110. Thanks to Dependabot, Gary Gregory. +o Bump actions/checkout from 2.3.1 to 3.1.0, #24, #63, #75, #109. Thanks to Dependabot, Gary Gregory. +o Bump actions/setup-java from 1.4.0 to 3.5.1 #21. Thanks to Dependabot, Gary Gregory. +o Bump junit from 3.8.1 to 5.9.1 Vintage #23, #38. Thanks to Dependabot, Gary Gregory. +o Bump clirr-maven-plugin from 2.2.2 to 2.8 #14. Thanks to Dependabot. +o Bump findbugs-maven-plugin from 2.5.2 to 3.0.5 #8. Thanks to Dependabot. +o Bump maven-failsafe-plugin from 2.12 to 3.0.0-M7 #31, #91. Thanks to Dependabot, Gary Gregory. +o Bump spotbugs-surefire-plugin from 2.22.2 to 3.0.0-M5. Thanks to Gary Gregory. +o Bump maven-dependency-plugin from 2.4 to 3.5.0 #29, #79, #117, #131. Thanks to Dependabot. +o Bump maven-pmd-plugin from 3.3 to 3.19.0 #28, #90, #100, #103. Thanks to Dependabot. +o Bump maven-assembly-plugin from 2.5 to 3.4.2 #30, #94, #96. Thanks to Dependabot. +o Bump servlet-api from 2.3 to 2.5 #27. Thanks to Dependabot. +o Bump maven-checkstyle-plugin from 2.7 to 3.2.1 #35, #101, #130. Thanks to Gary Gregory, Dependabot. +o Bump spotbugs-maven-plugin from 4.1.4 to 4.7.2.1 #33, #70, #78, #93, #97, #102, #112. Thanks to Dependabot. +o Bump spotbugs from 4.5.3 to 4.7.3 #81, #87, #92, #104, #115. Thanks to Dependabot. +o Bump commons-parent from 52 to 65 #82, #106, #122, #126, #143. Thanks to Dependabot, Gary Gregory. +o Bump github/codeql-action from 1 to 2 #86. Thanks to Dependabot. + + +Historical list of changes: https://commons.apache.org/proper/commons-logging/changes-report.html + +For complete information on Apache Commons Logging, including instructions on how to submit bug reports, +patches, or suggestions for improvement, see the Apache Commons Logging website: + +https://commons.apache.org/proper/commons-logging/ + +============================================================================= + +Apache Commons Logging +Version 1.2 +RELEASE NOTES + The Apache Commons Logging team is pleased to announce the release of Apache Commons Logging 1.2 @@ -28,4 +95,4 @@ Historical list of changes: http://commons.apache.org/proper/commons-logging/cha For complete information on Apache Commons Logging, including instructions on how to submit bug reports, patches, or suggestions for improvement, see the Apache Commons Logging website: -http://commons.apache.org/proper/commons-logging/ \ No newline at end of file +http://commons.apache.org/proper/commons-logging/ diff --git a/src/changes/changes.xml b/src/changes/changes.xml index 19cdb4a..9e47eb9 100644 --- a/src/changes/changes.xml +++ b/src/changes/changes.xml @@ -43,7 +43,7 @@ The type attribute can be add,update,fix,remove. Release Notes - + Add support for Log4j API and SLF4J #177. diff --git a/src/changes/release-notes.vm b/src/changes/release-notes.vm index 65e162e..2c58859 100644 --- a/src/changes/release-notes.vm +++ b/src/changes/release-notes.vm @@ -14,9 +14,9 @@ ## KIND, either express or implied. See the License for the ## specific language governing permissions and limitations ## under the License. - ${project.name} - Version ${version} - RELEASE NOTES +${project.name} +Version ${version} +RELEASE NOTES The ${developmentTeam} is pleased to announce the release of ${project.name} ${version} @@ -106,4 +106,6 @@ Historical list of changes: ${project.url}changes-report.html For complete information on ${project.name}, including instructions on how to submit bug reports, patches, or suggestions for improvement, see the ${project.name} website: -${project.url} \ No newline at end of file +${project.url} + +============================================================================= diff --git a/src/site/xdoc/download_logging.xml b/src/site/xdoc/download_logging.xml index 2a07ede..110e880 100644 --- a/src/site/xdoc/download_logging.xml +++ b/src/site/xdoc/download_logging.xml @@ -26,15 +26,28 @@ limitations under the License. | commons-build-plugin/trunk/src/main/resources/commons-xdoc-templates | +======================================================================+ | | - | 1) Re-generate using: mvn commons:download-page | + | 1) Re-generate using: mvn commons-build:download-page | | | | 2) Set the following properties in the component's pom: | - | - commons.componentid (required, alphabetic, lower case) | + | - commons.componentid (required, alphabetic, lower case) | | - commons.release.version (required) | - | - commons.binary.suffix (optional) | + | - commons.release.name (required) | + | - commons.binary.suffix (optional) | | (defaults to "-bin", set to "" for pre-maven2 releases) | + | - commons.release.desc (optional) | + | - commons.release.subdir (optional) | + | - commons.release.hash (optional, lowercase, default sha512) | + | | + | - commons.release.[234].version (conditional) | + | - commons.release.[234].name (conditional) | + | - commons.release.[234].binary.suffix (optional) | + | - commons.release.[234].desc (optional) | + | - commons.release.[234].subdir (optional) | + | - commons.release.[234].hash (optional, lowercase, [sha512])| | | | 3) Example Properties | + | (commons.release.name inherited by parent: | + | ${project.artifactId}-${commons.release.version} | | | | | | math | @@ -46,17 +59,17 @@ limitations under the License. Download Apache Commons Logging - Commons Documentation Team + Apache Commons Documentation Team

We recommend you use a mirror to download our release - builds, but you must verify the integrity of + builds, but you must verify the integrity of the downloaded files using signatures downloaded from our main distribution directories. Recent releases (48 hours) may not yet - be available from the mirrors. + be available from all the mirrors.

@@ -88,39 +101,44 @@ limitations under the License.

- 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. + It is essential that you + verify the integrity + of downloaded files, preferably using the PGP signature (*.asc files); + failing that using the SHA512 hash (*.sha512 checksum files). +

+

+ The KEYS + file contains the public PGP keys used by Apache Commons developers + to sign releases.

-
+
- - - + + + - - - + + +
commons-logging-1.2-bin.tar.gzmd5pgpcommons-logging-1.3.0-bin.tar.gzsha512pgp
commons-logging-1.2-bin.zipmd5pgpcommons-logging-1.3.0-bin.zipsha512pgp
- - - + + + - - - + + +
commons-logging-1.2-src.tar.gzmd5pgpcommons-logging-1.3.0-src.tar.gzsha512pgp
commons-logging-1.2-src.zipmd5pgpcommons-logging-1.3.0-src.zipsha512pgp
@@ -131,7 +149,7 @@ limitations under the License.

diff --git a/src/site/xdoc/issue-tracking.xml b/src/site/xdoc/issue-tracking.xml index ab10f27..4eea72f 100644 --- a/src/site/xdoc/issue-tracking.xml +++ b/src/site/xdoc/issue-tracking.xml @@ -26,7 +26,7 @@ limitations under the License. | commons-build-plugin/trunk/src/main/resources/commons-xdoc-templates | +======================================================================+ | | - | 1) Re-generate using: mvn commons:jira-page | + | 1) Re-generate using: mvn commons-build:jira-page | | | | 2) Set the following properties in the component's pom: | | - commons.jira.id (required, alphabetic, upper case) | @@ -43,35 +43,35 @@ limitations under the License. --> - Commons Logging Issue tracking - Commons Documentation Team + Apache Commons Logging Issue tracking + Apache Commons Documentation Team -
+

- Commons Logging uses ASF JIRA for tracking issues. - See the Commons Logging JIRA project page. + Apache Commons Logging uses ASF JIRA for tracking issues. + See the Apache 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).

If you would like to report a bug, or raise an enhancement request with - Commons Logging please do the following: + Apache 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.

@@ -80,21 +80,21 @@ limitations under the License.
  • the more information you provide, the better we can help you
  • test cases are vital, particularly for any proposed enhancements
    • -
  • the developers of Commons Logging are all unpaid volunteers
    • +
  • the developers of Apache Commons Logging are all unpaid volunteers

- For more information on subversion and creating patches see the - Apache Contributors Guide. + For more information on creating patches see the + 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 33f3ba3..01fdacc 100644 --- a/src/site/xdoc/mail-lists.xml +++ b/src/site/xdoc/mail-lists.xml @@ -26,7 +26,7 @@ limitations under the License. | commons-build-plugin/trunk/src/main/resources/commons-xdoc-templates | +======================================================================+ | | - | 1) Re-generate using: mvn commons:mail-page | + | 1) Re-generate using: mvn commons-build:mail-page | | | | 2) Set the following properties in the component's pom: | | - commons.componentid (required, alphabetic, lower case) | @@ -41,15 +41,15 @@ limitations under the License. --> - Commons Logging Mailing Lists - Commons Documentation Team + Apache Commons Logging Mailing Lists + Apache Commons Documentation Team

- Commons Logging shares mailing lists with all the other - Commons Components. + Apache Commons Logging shares mailing lists with all the other + 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: @@ -58,24 +58,29 @@ limitations under the License.

- Questions related to the usage of Commons Logging should be posted to the - User List. + Questions related to the usage of Apache Commons Logging should be posted to the + User List.
- The Developer List - is for questions and discussion related to the development of Commons Logging. + The Developer List + is for questions and discussion related to the development of Apache Commons Logging.
Please do not cross-post; developers are also subscribed to the user list. +
+ You must be subscribed to post to the mailing lists. Follow the Subscribe links below + to subscribe.

- Note: please don't send patches or attachments to any of the mailing lists. - Patches are best handled via the Issue Tracking system. - Otherwise, please upload the file to a public server and include the URL in the mail. + Note: please don't send patches or attachments to any of the mailing lists; + most of the lists are set up to drop attachments. + Patches are best handled via the Issue Tracking system. + If you have a GitHub account, most components also accept PRs (pull requests). + Otherwise, please upload the file to a public server and include the URL in the mail.

-
+

- Please prefix the subject line of any messages for Commons Logging + Please prefix the subject line of any messages for Apache Commons Logging with [logging] - thanks!

@@ -96,16 +101,17 @@ limitations under the License. Commons User List

- Questions on using Commons Logging. + Questions on using Apache Commons Logging.

Subscribe Unsubscribe Post - mail-archives.apache.org - markmail.org
- www.mail-archive.com
- news.gmane.org + + lists.apache.org + + + www.mail-archive.com @@ -114,16 +120,17 @@ limitations under the License. Commons Developer List

- Discussion of development of Commons Logging. + Discussion of development of Apache Commons Logging.

Subscribe Unsubscribe Post - mail-archives.apache.org - markmail.org
- www.mail-archive.com
- news.gmane.org + + lists.apache.org + + + www.mail-archive.com @@ -138,9 +145,11 @@ limitations under the License. Subscribe Unsubscribe read only - mail-archives.apache.org - markmail.org
- www.mail-archive.com + + lists.apache.org + + + www.mail-archive.com @@ -149,15 +158,17 @@ limitations under the License. Commons Commits List

- Only for e-mails automatically generated by the source control sytem. + Only for e-mails automatically generated by the source control system.

Subscribe Unsubscribe read only - mail-archives.apache.org - markmail.org
- www.mail-archive.com + + lists.apache.org + + + www.mail-archive.com @@ -185,14 +196,14 @@ limitations under the License. General announcements of Apache project releases.

- Subscribe - Unsubscribe + Subscribe + Unsubscribe read only - mail-archives.apache.org - markmail.org
- old.nabble.com
- www.mail-archive.com
- news.gmane.org + + lists.apache.org + + + www.mail-archive.com