Siphalor/tweed5-commons-logging
1
0
Fork 0
Code Activity

A few cosmetic changes. I think I prefer jar file to jarfile.

Browse Source 
git-svn-id: https://svn.apache.org/repos/asf/jakarta/commons/proper/logging/trunk@378372 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Robert Burrell Donkin
2006-02-16 21:55:45 +00:00
parent 22822656d2
commit d2b4d4a9aa
1 changed files with 10 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
RELEASE-NOTES.txt
View File

@@ -48,9 +48,9 @@ Jakarta Commons Logging wiki site:
== New Features == == New Features ==
* Jarfiles now have release-numbers embedded in the names, for easier management. * Jar files now have release-numbers embedded in the names, for easier management.
* New jarfile commons-logging-adapters-xxx.jar is now provided. This can be * New jar file commons-logging-adapters-xxx.jar is now provided. This can be
used to resolve class cast conflicts where parts of commons-logging are used to resolve class cast conflicts where parts of commons-logging are
deployed via different classloaders. It is not expected to be frequently deployed via different classloaders. It is not expected to be frequently
used; it is only necessary in situations where a container has deployed used; it is only necessary in situations where a container has deployed
@@ -87,7 +87,7 @@ Jakarta Commons Logging wiki site:
when a webapp was undeployed. An internal change fixes some situations where when a webapp was undeployed. An internal change fixes some situations where
that occurs (by using weak references); this requires no action on the part of that occurs (by using weak references); this requires no action on the part of
users of this library. In addition, a utility class ServletContextCleaner is users of this library. In addition, a utility class ServletContextCleaner is
provided in the jarfile which is expected to resolve this problem in all provided in the jar file which is expected to resolve this problem in all
situations; however it is necessary for an application to define this class as situations; however it is necessary for an application to define this class as
a ServletContextListener in the web.xml in order for this to be invoked. a ServletContextListener in the web.xml in order for this to be invoked.
@@ -143,7 +143,7 @@ Java 1.2 and later are supported. It may be possible to use this release with
java 1.1 but this has not been tested; the unit tests certainly don't run on java 1.1 but this has not been tested; the unit tests certainly don't run on
that version. that version.
== Distributed jarfiles == == Distributed Jar Files ==
File commons-logging-nn.jar is the one most people will want. It provides the File commons-logging-nn.jar is the one most people will want. It provides the
base implementation and adapters to a number of popular logging libraries. base implementation and adapters to a number of popular logging libraries.
@@ -151,19 +151,19 @@ base implementation and adapters to a number of popular logging libraries.
File commons-logging-adapters-nn.jar includes only the adapters to various File commons-logging-adapters-nn.jar includes only the adapters to various
concrete logging libraries. When commons-logging-nn.jar or concrete logging libraries. When commons-logging-nn.jar or
commons-logging-api-nn.jar is deployed in a container classpath, then this commons-logging-api-nn.jar is deployed in a container classpath, then this
adapters-only jarfile should be deployed in the webapp, not the complete JCL adapters-only jar file should be deployed in the webapp, not the complete JCL
distribution. This ensures that the core Log/LogFactory classes are only distribution. This ensures that the core Log/LogFactory classes are only
deployed via one classloader, thus avoiding "Log4JLogger does not implement Log" deployed via one classloader, thus avoiding "Log4JLogger does not implement Log"
and similar problems. and similar problems.
File commons-logging-api-nn.jar provides no adapters to external logging File commons-logging-api-nn.jar provides no adapters to external logging
libraries, just the internally implemented SimpleLog and NoOpLog classes. This libraries, just the internally implemented SimpleLog and NoOpLog classes. This
jarfile may be used as a declared dependency for projects that care about jar file may be used as a declared dependency for projects that care about
"transitive dependencies" and can't handle jarfiles such as commons-logging-nn.jar "transitive dependencies" and can't handle jar files such as commons-logging-nn.jar
which have "optional" dependencies depending on how they are used. In addition, which have "optional" dependencies depending on how they are used. In addition,
this jarfile can be useful for "rebundlers" of JCL who recompile the source-code this jar file can be useful for "rebundlers" of JCL who recompile the source-code
but who may not be able to recompile against the full set of supported adapters; but who may not be able to recompile against the full set of supported adapters;
such projects should be able to at least recreate an equivalent of this jarfile. such projects should be able to at least recreate an equivalent of this jar file.
== General Notes == == General Notes ==
@@ -188,7 +188,7 @@ website for details (http://jakarta.apache.org/commons).
deprecated for a long while. Replacement class Log4JLogger should be a completely deprecated for a long while. Replacement class Log4JLogger should be a completely
transparent replacement for all commons-logging users. transparent replacement for all commons-logging users.
* package.html files are no longer present in the jarfiles, removing nuisance * package.html files are no longer present in the jar files, removing nuisance
javadoc warnings when building javadoc for apps using jcl. javadoc warnings when building javadoc for apps using jcl.
* In several cases, LogConfigurationException objects were being wrapped in * In several cases, LogConfigurationException objects were being wrapped in