1
0
Files
tweed5-commons-logging/src/changes/changes.xml

85 lines
3.4 KiB
XML

<?xml version="1.0"?>
<!--
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
The ASF licenses this file to You under the Apache License, Version 2.0
(the "License"); you may not use this file except in compliance with
the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-->
<!--
This file is also used by the maven-changes-plugin to generate the release notes.
Useful ways of finding items to add to this file are:
1. Add items when you fix a bug or add a feature (this makes the
release process easy :-).
2. Do a JIRA search for tickets closed since the previous release.
3. Use the report generated by the maven-changelog-plugin to see all
SVN commits. TBA how to use this with SVN.
To generate the release notes from this file:
mvn changes:announcement-generate -Prelease-notes [-Dchanges.version=nn]
then tweak the formatting if necessary
and commit
The <action> type attribute can be add,update,fix,remove.
-->
<document xmlns="http://maven.apache.org/changes/1.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/changes/1.0.0 http://maven.apache.org/xsd/changes-1.0.0.xsd">
<properties>
<title>Release Notes</title>
</properties>
<body>
<release version="1.1.2" date="In SVN" description="Bug fixes.">
<action type="update" issue="LOGGING-138">
In case of a discovery failure now also the stacktrace of the cause will be
added to the diagnostic message.
</action>
<action type="fix" issue="LOGGING-132">
Jdk14Logger now correctly uses the specified logger name.
</action>
<action type="update" issue="LOGGING-133">
Change scope of Jdk14Logger.log(Level, String, Throwable) to protected, allowing
subclasses to modify the logging output.
</action>
<action type="fix" issue="LOGGING-146">
Properly synchronize access to protected static field LogFactory.nullClassLoaderFactory.
</action>
<action type="fix" issue="LOGGING-119">
Prevent potential deadlock scenario in WeakHashtable.
</action>
<action type="fix" issue="LOGGING-130">
Potential missing privileged block for class loader.
</action>
<action type="fix" issue="LOGGING-145">
LogFactoryImpl.setAttribute - possible NPE.
</action>
<action type="fix" issue="LOGGING-142">
Log4JLogger uses deprecated static members of Priority such as INFO.
</action>
<action type="fix" issue="LOGGING-128">
Static analysis suggests a number of potential improvements.
</action>
<action type="fix" issue="LOGGING-147">
SimpleLog.log - unsafe update of shortLogName.
</action>
<action type="fix" issue="LOGGING-148">
LogFactory.diagnosticPrefix and diagnosticsStream could be final.
</action>
</release>
</body>
</document>