Parent Directory
| 
Revision Log
| Links to HEAD: | (view) (annotate) |
| Sticky Revision: |
Provide commons.home as an alias for jakarta.home
Replace tab characters with spaces. No other changes.
Moving to TLP
Moving back :)
Moving to TLP
Use the new location of the Maven 1 repository.
Use source.version and target.version when compiling test classes.
Change key of servlet api jar from "servletapi" to "servlet-api". The maven2 tests pull this jar from the maven2 repository, and in there the jarfile has a different name from the jarfile in the maven1 repo where ant pulls it from :-(.
Exclude LogFactoryImpl anonymous inner classes from adapter jar that shouldn't be included.
Update license info using script update-AL20.pl, as per http://www.apache.org/legal/src-headers.html
Updated to next SNAPSHOT
Final preparations for JCL 1.1 Release
Preparations for Release candidate 11
Preparations for release candidate 10
Preparing for release candidate 9.
Preparing for release candidate 8
Made logkit tests optional. Moved pathable tests into optional log4j section since they rely on that implementation.
Restored JDK14 to API jar. This is for drop in backwards compatibility for Tomcat.
Preparations for release candidate 7.
Upgraded version in preparation for new release candidate.
Tab->space conversions only.
* Make LogKit lib available to unit tests * Fix minor documentation error re running specific tests * Add documentation on enabling diagnostics during tests * replace tabs with spaces
Preparing for release candidate 5.
After some consideration removed the indexes. JCL isn't signed and so anyone using it in an applet would need to rejar and sign in any case. They can index at the same time. Probably safer this way.
Update to number RC4
Consolidated source and javadocs into single jar.
Adds index lists to jar files. Contributed by Boris Unckel. Issue #38499.
Updated version ready for next release candidate.
Comment out some remains from the log4j 1.3 build. Add notes to put them back again if/when the build uses log4j 1.3.
Added a warning message that is shown if maven site:generate has not been run.
Updated script so that target dist does not fail when maven site:generate has not been run.
Added source and javadoc archives for IDEs to distribution build.
Updated dist method to reflect modern practice. Added optional isolated compilation for releases (requires a pre-1.4 JVM to run the ant tasks and the executable.javac1.4 build property to be set). Artifacts are built in new subdirectory with file ending standardisation. Ant lacks a svn task so will consider whether the source artifacts should also be created by dist.
Default target is now 'all' and target 'all' now runs the unit tests.
Removed javadoc target. Use maven for documentation including javadocs.
Removed properties used by the now-removed optional build.
Decided that it's better to include suffix for release candidates.
Exclude LogFactoryImpl from adapters jar; it doesn't do any harm but will never be used as the default implementation is always loaded via the LogFactory classloader.
Upgraded version number in preparation for cutting first candidate
Exclude jdk14 logger from api jar Include WeakHashtable in api jar Make ant dependencies used in build be the same as those in the maven project.xml file.
Expose servletapi.jar as a "logical lib" for unit tests
Fixes for javadoc building. Add build instructions.
Remove WeakHashtable classes from the commons-logging-adapters jarfile.
Fixes due to Log4J12Logger being renamed back to Log4JLogger and Log4J13Logger being removed.
Moved optional distribution into contrib.
log4j tests now all work fine with <batchtest> so remove special case code for log4j.
Fail the build if any unit test fails. Also removed some redundant stuff.
Added getlibs task to automatically download all dependencies.
Minor tweak to unit testing stuff.
Massive removal of custom test targets now most tests support the PathableTestSuite stuff.
Update the test.pathable target. Note that the optional ant junit task is now used in this file - see comments at head of file for details.
Add adapters jar to list of logical jars available to unit test code.
Changes due to testcase classes now controlling their own classpaths. * The Wrapper class is no longer used. * The log4j tests run with log4j13 in the classpath have been removed for now; will implement this via another mechanism in the near future. Note that there are expected to be more cleanups applied to this file in the near future.
Need to include discovery as dependency for any target that tries to test xxx.present variables.
Add dependency on prepare targets for new compile targets, so that if they are run independently the destination dirs will exist.
Improve warning messages for missing libs (thanks to Dennis Lundberg).
Split compile target into separate pieces in order to assist gump. Target compile-only is now: show-lib-presence,compile-non-log4j,compile-log4j12,compile-log4j13,build-jar
Change version# to 1.1-dev
Split Log4JLogger into Log4J12Logger and Log4J13Logger
The created jarfiles now have the version# embedded in their names, so the test wrapper class can't just hard-wire their names any more. Instead, we pass the jarfile names in from the build.xml file as system properties.
Minor cleanups.
Add an implementation of ServletContextListener for use in avoiding memory leaks in webapps.
Add version into jarname as done by maven, eg commons-logging-1.x.x.jar
Create commons-logging-adapters.jar file in dist target.
Exclude package.html files from the jar files.
Ensure class files generated are compatible with 1.1 JVMs (although we only support 1.2+ at the moment).
svn:keywords correction
Updated HEAD version.
Fixed bug in distribution build. Issue 33323. Contributed by Brian Stansberry.
LogFactory's Hashtable implementation (used to store LogFactoryImpl by classloader) can now be subclassed. This will default to WeakHashtable when this is present on the classpath, Hashtable otherwise. The implementation class can be specified by a system property. Based on a contribution by Brian Stansberry.
Added new optional subcomponent consisting of non-core implementations. Initial contents MemoryLog, a log implementation intended for use when unit testing. Issue #27663. Contributed by Joerg Schaible.
New test case for simple log date time setting
Added optional tests for Log4JLogger against 1.2.x
Tweak the release notes to include the last enhancement. Update version number to 1.0.4 in both build.xml and MANIFEST.MF (in the original Ant based build mechanisms, we used to use filter replacement so you only had to change this in one place; is there some technique to regain that benefit that works with both Ant and Maven?).
remove usersguide.html to fix gump build (patch from Antoine L�vy-Lambert)
Changed build script so that the javadocs contain the license boilerplate and also that the NOTICE file is copied to the dist directory (as well as the LICENSE file).
Finish migration to the new Apache License (version 2.0): * Add updated LICENSE.txt and new NOTICE.txt files. * Add license header to currently unlicensed text files (html, xml, properties).
Add support for Lumberjack (a project that supports JSR-47 compatible logging on a JDK 1.2 or JDK 1.3 system). PR: Bugzilla #21455. Submitted By: Vince Eagen <vince256 at comcast.net>
Make o.a.c.l.impl.SimpleLog Serializable. Add more comprehensive unit tests for SimpleLog, including the ability to serialize and deserialize instances. This work will form the basis for making similar changes to the other Log implementations (and their corresponding test cases).
Modified build script so that user guide is copied into distribution.
Made implementation of AvalonLogger more robust (avoiding NPEs when nulls are passed in) together with a testcase. Improved build by compiling tests for only those optional components whose dependencies are present. Submitted by Neeme Praks.
Added AvalonLogger which wraps the logger used by the Avalon framework. Also added an optional dependency on avalon-framework.jar. Added better warnings to build about which loggers are going to be created.
Updated to reflect 1.0.3 release
Preparations for 1.0.3 release
Include the release notes in the distribution.
Wrapper: - Refactor the setup of class loaders so that it is clearer what is going on - For the Log4J tests, add the custom Appender implementation to whichever class loader Log4J is put in - Set and reset the thread context class loader to more accurately simulate the environment of a servlet container. build.xml: - Implement the multi-classloader test scenarios for Log4J, equivalent to those for JDK 1.4. We now have a robust testing environment to catch any possible regressions when modifying the functionality (such as ripping out Log4jFactory, as discussed on COMMONS-DEV). I don't have time to do the corresponding test scenarios for Avalon LogKit, but anyone who wants to do so is welcome to create them.
Copy LICENSE.txt file into distribution, and make sure it is included in the JAR files, without going to the directory above the top-level directory. This will make it easier to build commons-logging from source distros.
When copying MANIFEST.MF files for the JAR files, use the one that has already been filtered to get the right version number in it.
Cosmetic changes, and correct copyright dates. Add simple overview with pointer to the real documentation, and a package.html for the o.a.c.l.impl package. Bring various documentation points up to date with the actual current functionality.
Add basic tests for Log4J. Still need to add the multi-classloader scenarios.
Add test scenarios where two levels of class loader hierarchies are created - one exactly like the default configuration of Tomcat 4.1 (with c-l placed inside the webapp) and one where you put c-l in the parent class loader (in place of commons-logging-api.jar) so webapps do not have to.
Add a more thorough set of unit tests for using JDK 1.4 logging. Right now,
the tests run when everything is in the system class loader -- need to add
execution wrappers for two-tier class loaders where:
* commons-logging.jar is in the parent and test execution is in the child
* commons-logging-api.jar is in the parent and test execution plus
commons-logging.jar is in the child
to simulate container environments like that you get running inside Tomcat.
Later on, we'll want an analogous set of tests for Log4J.
Avoid breaking the build when a developer has "commons-logging.jar" set in a build.properties file already.
That's what was breaking the build in tomcat5.
Update the build process to skip all the Log4J implementation classes if Log4J is not present. PR: Bugzilla #16358 Submitted by: Jeremias Maerki <jeremias at apache.org>
Avoid name clashes on local property names "commons-logging-api.jar" and
"commons-logging.jar" which will not work correctly for any developer who
has such properties defined in a "${user.home}/build.properties" file.
A small change that allows the quick build of commons-logging jars.
The way I use it is:
<ant dir="${cvs.base}/jakarta-commons/logging" target="compile-only" >
<property name="commons-logging-api.jar" location="${build.dir}/lib/commons-logging-api.jar" />
<property name="commons-logging.jar" location="${build.dir}/lib/commons-logging.jar" />
<property name="build.home" value="${build.dir}" />
</ant>
If it brakes something or any other problem - please let me know.
Version 1.0.2
Update version number back for development.
Update version number for release tagging.
o maven goodies PR: Obtained from: Submitted by: Reviewed by:
Add the simple logger to the '-api' jar. It seems all is working fine now, including the log4j JMX stuff in the default config ( adding the 'setName()' sovled the problems )
Build commons-logging-api.jar, with no logger adapters. This will allow the logger and the adapters to sit in the WEB-INF ( and multiple loggers to be used ), while having commons-logging in the root classloader. ( this in turns allow various components that are loaded with the root loader to log ).
Few small (?) fixes: - for JDK1.4, include the correct class/method. This uses a hack to extract the information from the stack trace - probably slow, but it's better to get the correct information. - for log4j, check if log4j is initialized ( by checking if any appenders are present ). Set a default configuration if it is not initialized.
Reset version number for development. Update copyright year (so that it will be right the next time).
Update version number for release build.
Include the classpath in the available check.
Fix conditional compilation. The official distribution must include support for all loggers, for development it should be enough to have one.
Update to reflect the move of the JDK14Logger class
Add logkit.jar to "test.classpath" as well as "compile.classpath".
A few more tweaks to the STATUS file, add the MANIFEST.MF file for the META-INF directory of the JAR file.
LogKit wrapper initial commit
Add a new Log implementation for JDK 1.4 (or later) logging. Default behavior of LogSource.getInstance() is now: * If Log4J is available, return an instance of Log4JCategoryLog * If JDK 1.4 is available, return an instance of Jdk14Logger * Otherwise, return an instance of NoOpLogger As before, this default behavior can be overridden with a system property, or by calling LogSource.setLogImplementation(), as described in the package Javadocs.
Add "META-INF/LICENSE.txt" for digester and logging also.
Migrate the "logging" package from jakarta-commons-sandbox.
This form allows you to request diffs between any two revisions of this file. For each of the two "sides" of the diff, enter a numeric revision.
| apache@apache.org | ViewVC Help |
| Powered by ViewVC 1.1.2 |