You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by "Craig R. McClanahan" <cr...@apache.org> on 2004/02/29 00:27:52 UTC
[logging] Current Status and Release Planning
I've converted [logging] to the new Apache License 2.0, brought the
documentation up to date with current changes, created provisional release
notes for a 1.0.4 maintenance release, and applied the patch included with the
last outstanding open bug report against [logging]. Please download tonight's
(20040229) nightly build and help me test the new bits to make sure I didn't
break anything along the way.
This is the last call for any issues you'd like to see addressed in a 1.0.4
maintenance release of [logging]. The best way to raise such issues is with
bug reports (or enhancement requests) in our issue tracking system
(http://issues.apache.org/bugzilla), or by posting comments and questions on
the COMMONS-DEV (or COMMONS-USER) mailing list
Barring the need for major changes, I'm planning on posting a release candidate
for this release on Wednesday (March 3, 2004) and calling for a release vote on
it shortly thereafter.
Craig McClanahan
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [logging] Current Status and Release Planning
Posted by "Craig R. McClanahan" <cr...@apache.org>.
Quoting Dennis Lundberg <de...@mdh.se>:
> I've been diffing the 1.0.3 release and the nightly from 20040229. I
> thought that I would try the Lumberjack logging, but I can't see how it
> could possibly work.
It would work if you also provided a JSR-47 compliant implementation of the
java.util.logging API classes that leveraged this underlying logging
implementation, as Lumberjack was originally reported to include.
> Here's a code snippet from LogFactoryImpl:
>
> /**
> * Is <em>JDK 1.3 with Lumberjack</em> logging available?
> */
> protected boolean isJdk13LumberjackAvailable() {
> try {
> loadClass("java.util.logging.Logger");
> loadClass("org.apache.commons.logging.impl.Jdk13LumberjackLogger");
> return (true);
> } catch (Throwable t) {
> return (false);
> }
> }
>
> In a pre 1.4 environment the line
> loadClass("java.util.logging.Logger");
> is going to throw an exception, isn't it? I mean all the Lumberjack
> classes are in the com.redstarhacker.lumberjack package.
>
>
> On another note the version-numbers in build.xml and project.xml should
> be changed to 1.0.4 before the release.
>
They will be - thanks for the reminder.
> --
> Dennis Lundberg
>
Craig
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [logging] Current Status and Release Planning
Posted by Dennis Lundberg <de...@mdh.se>.
I've been diffing the 1.0.3 release and the nightly from 20040229. I
thought that I would try the Lumberjack logging, but I can't see how it
could possibly work. Here's a code snippet from LogFactoryImpl:
/**
* Is <em>JDK 1.3 with Lumberjack</em> logging available?
*/
protected boolean isJdk13LumberjackAvailable() {
try {
loadClass("java.util.logging.Logger");
loadClass("org.apache.commons.logging.impl.Jdk13LumberjackLogger");
return (true);
} catch (Throwable t) {
return (false);
}
}
In a pre 1.4 environment the line
loadClass("java.util.logging.Logger");
is going to throw an exception, isn't it? I mean all the Lumberjack
classes are in the com.redstarhacker.lumberjack package.
On another note the version-numbers in build.xml and project.xml should
be changed to 1.0.4 before the release.
--
Dennis Lundberg
Craig R. McClanahan wrote:
> I've converted [logging] to the new Apache License 2.0, brought the
> documentation up to date with current changes, created provisional release
> notes for a 1.0.4 maintenance release, and applied the patch included with the
> last outstanding open bug report against [logging]. Please download tonight's
> (20040229) nightly build and help me test the new bits to make sure I didn't
> break anything along the way.
>
> This is the last call for any issues you'd like to see addressed in a 1.0.4
> maintenance release of [logging]. The best way to raise such issues is with
> bug reports (or enhancement requests) in our issue tracking system
> (http://issues.apache.org/bugzilla), or by posting comments and questions on
> the COMMONS-DEV (or COMMONS-USER) mailing list
>
> Barring the need for major changes, I'm planning on posting a release candidate
> for this release on Wednesday (March 3, 2004) and calling for a release vote on
> it shortly thereafter.
>
> Craig McClanahan
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [logging] Current Status and Release Planning
Posted by robert burrell donkin <ro...@blueyonder.co.uk>.
hi dennis
thanks for the spot :)
i agree that this is a problem but i need to find out what the status
is of the master website conversion before i can finish the
mavenization work. once this work is finished, these documents will be
removed.
- robert
On 29 Feb 2004, at 01:02, Dennis Lundberg wrote:
> Now that guide.xml and proposal.xml exist in xdocs, shouldn't
> usersguide.html and PROPOSAL.html be removed? Or do we need to switch
> to the mavenized site first?
>
> As it is now, guide.xml and usersguide.html is not in sync. A bunch of
> typos have been fixed in guide.xml but not in usersguide.xml.
>
> --
> Dennis Lundberg
>
>
> Craig R. McClanahan wrote:
>> I've converted [logging] to the new Apache License 2.0, brought the
>> documentation up to date with current changes, created provisional
>> release
>> notes for a 1.0.4 maintenance release, and applied the patch included
>> with the
>> last outstanding open bug report against [logging]. Please download
>> tonight's
>> (20040229) nightly build and help me test the new bits to make sure I
>> didn't
>> break anything along the way.
>> This is the last call for any issues you'd like to see addressed in a
>> 1.0.4
>> maintenance release of [logging]. The best way to raise such issues
>> is with
>> bug reports (or enhancement requests) in our issue tracking system
>> (http://issues.apache.org/bugzilla), or by posting comments and
>> questions on
>> the COMMONS-DEV (or COMMONS-USER) mailing list Barring the need for
>> major changes, I'm planning on posting a release candidate
>> for this release on Wednesday (March 3, 2004) and calling for a
>> release vote on
>> it shortly thereafter.
>> Craig McClanahan
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [logging] Current Status and Release Planning
Posted by Dennis Lundberg <de...@mdh.se>.
Now that guide.xml and proposal.xml exist in xdocs, shouldn't
usersguide.html and PROPOSAL.html be removed? Or do we need to switch to
the mavenized site first?
As it is now, guide.xml and usersguide.html is not in sync. A bunch of
typos have been fixed in guide.xml but not in usersguide.xml.
--
Dennis Lundberg
Craig R. McClanahan wrote:
> I've converted [logging] to the new Apache License 2.0, brought the
> documentation up to date with current changes, created provisional release
> notes for a 1.0.4 maintenance release, and applied the patch included with the
> last outstanding open bug report against [logging]. Please download tonight's
> (20040229) nightly build and help me test the new bits to make sure I didn't
> break anything along the way.
>
> This is the last call for any issues you'd like to see addressed in a 1.0.4
> maintenance release of [logging]. The best way to raise such issues is with
> bug reports (or enhancement requests) in our issue tracking system
> (http://issues.apache.org/bugzilla), or by posting comments and questions on
> the COMMONS-DEV (or COMMONS-USER) mailing list
>
> Barring the need for major changes, I'm planning on posting a release candidate
> for this release on Wednesday (March 3, 2004) and calling for a release vote on
> it shortly thereafter.
>
> Craig McClanahan
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [logging] Current Status and Release Planning
Posted by robert burrell donkin <ro...@blueyonder.co.uk>.
committed. many thanks.
- robert
On 29 Feb 2004, at 01:32, Dennis Lundberg wrote:
> Here are a couple of patches:
> 1. In project.xml the license has to come after the xml declaration,
> otherwise maven refuses to run
> 2. A couple of missing </li> in proposal.xml prevented "maven site"
> from working
>
> --
> Dennis Lundberg
>
>
> Craig R. McClanahan wrote:
>> I've converted [logging] to the new Apache License 2.0, brought the
>> documentation up to date with current changes, created provisional
>> release
>> notes for a 1.0.4 maintenance release, and applied the patch included
>> with the
>> last outstanding open bug report against [logging]. Please download
>> tonight's
>> (20040229) nightly build and help me test the new bits to make sure I
>> didn't
>> break anything along the way.
>> This is the last call for any issues you'd like to see addressed in a
>> 1.0.4
>> maintenance release of [logging]. The best way to raise such issues
>> is with
>> bug reports (or enhancement requests) in our issue tracking system
>> (http://issues.apache.org/bugzilla), or by posting comments and
>> questions on
>> the COMMONS-DEV (or COMMONS-USER) mailing list Barring the need for
>> major changes, I'm planning on posting a release candidate
>> for this release on Wednesday (March 3, 2004) and calling for a
>> release vote on
>> it shortly thereafter.
>> Craig McClanahan
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
> Index: project.xml
> ===================================================================
> RCS file: /home/cvspublic/jakarta-commons/logging/project.xml,v
> retrieving revision 1.13
> diff -u -r1.13 project.xml
> --- project.xml 28 Feb 2004 22:10:53 -0000 1.13
> +++ project.xml 29 Feb 2004 01:23:40 -0000
> @@ -1,5 +1,5 @@
> +<?xml version="1.0" encoding="UTF-8"?>
> <!--
> -
> Copyright 2001-2004 The Apache Software Foundation.
>
> Licensed under the Apache License, Version 2.0 (the "License");
> @@ -13,10 +13,8 @@
> 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.
> -
> -->
>
> -<?xml version="1.0" encoding="UTF-8"?>
>
> <project>
> <extend>../commons-build/project.xml</extend>
> Index: xdocs/proposal.xml
> ===================================================================
> RCS file: /home/cvspublic/jakarta-commons/logging/xdocs/proposal.xml,v
> retrieving revision 1.3
> diff -u -r1.3 proposal.xml
> --- xdocs/proposal.xml 28 Feb 2004 23:20:57 -0000 1.3
> +++ xdocs/proposal.xml 29 Feb 2004 01:26:23 -0000
> @@ -75,11 +75,11 @@
> <ul>
> <li>Java Development Kit (Version 1.1 or later)</li>
> <li>Avalon Framework (compile-time dependency only unless this Log
> - implementation is selected at runtime)
> + implementation is selected at runtime)</li>
> <li>Avalon LogKit (compile-time dependency only unless this Log
> - implementation is selected at runtime)
> - <li>JDK 1.4 (compile-time dependency only unless this log
> implementation
> - is selected at runtime).
> + implementation is selected at runtime)</li>
> + <li>JDK 1.4 (compile-time dependency only unless this Log
> implementation
> + is selected at runtime)</li>
> <li>Log4J (compile-time dependency only unless this Log
> implementation is selected at runtime)</li>
> <li><a
> href="http://sourceforge.net/projects/lumberjack/">Lumberjack</a>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [logging] Current Status and Release Planning
Posted by Dennis Lundberg <de...@mdh.se>.
Here are a couple of patches:
1. In project.xml the license has to come after the xml declaration,
otherwise maven refuses to run
2. A couple of missing </li> in proposal.xml prevented "maven site" from
working
--
Dennis Lundberg
Craig R. McClanahan wrote:
> I've converted [logging] to the new Apache License 2.0, brought the
> documentation up to date with current changes, created provisional release
> notes for a 1.0.4 maintenance release, and applied the patch included with the
> last outstanding open bug report against [logging]. Please download tonight's
> (20040229) nightly build and help me test the new bits to make sure I didn't
> break anything along the way.
>
> This is the last call for any issues you'd like to see addressed in a 1.0.4
> maintenance release of [logging]. The best way to raise such issues is with
> bug reports (or enhancement requests) in our issue tracking system
> (http://issues.apache.org/bugzilla), or by posting comments and questions on
> the COMMONS-DEV (or COMMONS-USER) mailing list
>
> Barring the need for major changes, I'm planning on posting a release candidate
> for this release on Wednesday (March 3, 2004) and calling for a release vote on
> it shortly thereafter.
>
> Craig McClanahan
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>