Curt Arnold | 1 Aug 2009 06:28
Picon
Favicon

Re: Is anybody home? :-D

We've discussed the javac target option previously, setting target=1.2  
does not indicate that only methods in the JDK 1.2's class library are  
used, it means to output byte-code that adheres to that particular  
JVM's byte code format.  The target setting was intentional.  I'm not  
aware of any significant improvement that would come from bumping it.   
I definitely would not want to bump it on log4j itself.

I think the reason for bumping one of the companions to using log4j  
1.2.16 instead of 15 is that we were having class loading issues when  
UnrecognizedElementHandler (which is used to support nested content in  
user defined appenders et al) was defined both in log4j.jar and in the  
companion.  I think the interface was removed from the companion and  
the minimal version was bumped.
Antonio Petrelli | 1 Aug 2009 11:49
Picon

Re: Is anybody home? :-D

2009/8/1 Curt Arnold <carnold <at> apache.org>:
> We've discussed the javac target option previously, setting target=1.2

Just a note, in companion component the target is 1.1, the source is 1.2.

> does
> not indicate that only methods in the JDK 1.2's class library are used, it
> means to output byte-code that adheres to that particular JVM's byte code
> format.

You're right, in fact the only problem is inside Eclipse, since it is
saying that the environment that I use (J2SE 1.2 over a Java SE 6)
gives me compile errors due to "restrictions in the use of some
classes", such as DOM classes.

> The target setting was intentional.  I'm not aware of any
> significant improvement that would come from bumping it.  I definitely would
> not want to bump it on log4j itself.

Why not on the companions, then? Java 5 is at the end-of-life, while
Java 6 is mature, why not jumping *at least* into Java 5?

Antonio
Curt Arnold | 1 Aug 2009 15:17
Picon
Favicon

Re: Is anybody home? :-D


On Aug 1, 2009, at 4:49 AM, Antonio Petrelli wrote:

> 2009/8/1 Curt Arnold <carnold <at> apache.org>:
>> We've discussed the javac target option previously, setting  
>> target=1.2
>
> Just a note, in companion component the target is 1.1, the source is  
> 1.2.
>
>> does
>> not indicate that only methods in the JDK 1.2's class library are  
>> used, it
>> means to output byte-code that adheres to that particular JVM's  
>> byte code
>> format.
>
> You're right, in fact the only problem is inside Eclipse, since it is
> saying that the environment that I use (J2SE 1.2 over a Java SE 6)
> gives me compile errors due to "restrictions in the use of some
> classes", such as DOM classes.
>
>>  The target setting was intentional.  I'm not aware of any
>> significant improvement that would come from bumping it.  I  
>> definitely would
>> not want to bump it on log4j itself.
>
> Why not on the companions, then? Java 5 is at the end-of-life, while
> Java 6 is mature, why not jumping *at least* into Java 5?
>
(Continue reading)

bugzilla | 3 Aug 2009 08:08
Picon
Favicon

Bug report for Log4j [2009/08/02]

+---------------------------------------------------------------------------+
| Bugzilla Bug ID                                                           |
|     +---------------------------------------------------------------------+
|     | Status: UNC=Unconfirmed NEW=New         ASS=Assigned                |
|     |         OPN=Reopened    VER=Verified    (Skipped Closed/Resolved)   |
|     |   +-----------------------------------------------------------------+
|     |   | Severity: BLK=Blocker CRI=Critical  REG=Regression  MAJ=Major   |
|     |   |           MIN=Minor   NOR=Normal    ENH=Enhancement TRV=Trivial |
|     |   |   +-------------------------------------------------------------+
|     |   |   | Date Posted                                                 |
|     |   |   |          +--------------------------------------------------+
|     |   |   |          | Description                                      |
|     |   |   |          |                                                  |
|13099|Opn|Nor|2002-09-27|DOMConfigurator ignores category factory setting  |
|17887|Opn|Maj|2003-03-11|RollingFileAppender does not work for 10 threads  |
|20395|Inf|Enh|2003-06-01|PreparedStatementAppender Enhancement             |
|23329|New|Enh|2003-09-22|<logger> element in XML config should support reso|
|26084|Inf|Nor|2004-01-13|Log Event detail panel does not show special chara|
|27363|Inf|Enh|2004-03-02|JNI based SyslogAppender                          |
|27367|Inf|Enh|2004-03-02|NetSendAppender                                   |
|28647|Ass|Enh|2004-04-28|Add "Flush on Level" capability to FileAppender   |
|29244|Inf|Nor|2004-05-27|Preserve XML content in log messages when using XM|
|29304|New|Nor|2004-05-30|Starting XMLSocketAppender from config file       |
|29305|New|Nor|2004-05-30|Chainsaw doesn't see locationinfo from XMLSocketRe|
|29735|New|Nor|2004-06-22|Receiver list display error  when receiver has no |
|30055|New|Nor|2004-07-12|Problem with registering Appenders with the same n|
|30407|Inf|Maj|2004-07-30|Externally rolled file problem                    |
|30888|New|Maj|2004-08-27|Chainsaw mixes files in same panel                |
|30890|New|Min|2004-08-27|Newly opened log file should get focus            |
|30892|New|Min|2004-08-27|Log files cannot be closed                        |
(Continue reading)

carnold | 4 Aug 2009 11:23
Picon
Favicon

[GUMP <at> vmgump]: Project logging-log4j-12-tests (in module logging-log4j-12) failed

To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at general <at> gump.apache.org.

Project logging-log4j-12-tests has an issue affecting its community integration.
This issue affects 1 projects,
 and has been outstanding for 8 runs.
The current state of this project is 'Failed', with reason 'Build Timed Out'.
For reference only, the following projects are affected by this:
    - logging-log4j-12-tests :  Fast and flexible logging package for Java

Full details are available at:
    http://vmgump.apache.org/gump/public/logging-log4j-12/logging-log4j-12-tests/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were provided:
 -INFO- Made directory [/srv/gump/public/workspace/logging-log4j-12/tests/classes]
 -INFO- Failed with reason build timed out

The following work was performed:
http://vmgump.apache.org/gump/public/logging-log4j-12/logging-log4j-12-tests/gump_work/build_logging-log4j-12_logging-log4j-12-tests.html
Work Name: build_logging-log4j-12_logging-log4j-12-tests (Type: Build)
Work ended in a state of : Failed
Elapsed: 60 mins
Command Line: /usr/lib/jvm/java-6-sun/bin/java -Djava.awt.headless=true
-Xbootclasspath/p:/srv/gump/public/workspace/xml-xerces2/build/xercesImpl.jar
org.apache.tools.ant.Main -Dgump.merge=/srv/gump/public/gump/work/merge.xml
(Continue reading)

carnold | 5 Aug 2009 04:38
Picon
Favicon

svn commit: r801049 - in /logging/log4j/trunk: examples/lf5/InitUsingXMLPropertiesFile/ src/changes/ src/main/java/org/apache/log4j/xml/ src/main/javadoc/org/apache/log4j/xml/examples/ src/performance/java/org/apache/log4j/performance/xml/

Author: carnold
Date: Wed Aug  5 02:38:09 2009
New Revision: 801049

URL: http://svn.apache.org/viewvc?rev=801049&view=rev
Log:
bug 42842: Create a public identifier for log4j.dtd

Modified:
    logging/log4j/trunk/examples/lf5/InitUsingXMLPropertiesFile/example.xml
    logging/log4j/trunk/src/changes/changes.xml
    logging/log4j/trunk/src/main/java/org/apache/log4j/xml/Log4jEntityResolver.java
    logging/log4j/trunk/src/main/java/org/apache/log4j/xml/XMLLayout.java
    logging/log4j/trunk/src/main/javadoc/org/apache/log4j/xml/examples/sample1.xml
    logging/log4j/trunk/src/main/javadoc/org/apache/log4j/xml/examples/sample2.xml
    logging/log4j/trunk/src/main/javadoc/org/apache/log4j/xml/examples/sample3.xml
    logging/log4j/trunk/src/main/javadoc/org/apache/log4j/xml/examples/sample4.xml
    logging/log4j/trunk/src/main/javadoc/org/apache/log4j/xml/examples/sample5.xml
    logging/log4j/trunk/src/performance/java/org/apache/log4j/performance/xml/logging1.xml

Modified: logging/log4j/trunk/examples/lf5/InitUsingXMLPropertiesFile/example.xml
URL: http://svn.apache.org/viewvc/logging/log4j/trunk/examples/lf5/InitUsingXMLPropertiesFile/example.xml?rev=801049&r1=801048&r2=801049&view=diff
==============================================================================
--- logging/log4j/trunk/examples/lf5/InitUsingXMLPropertiesFile/example.xml (original)
+++ logging/log4j/trunk/examples/lf5/InitUsingXMLPropertiesFile/example.xml Wed Aug  5 02:38:09 2009
 <at>  <at>  -1,5 +1,5  <at>  <at> 
 <?xml version="1.0" encoding="UTF-8" ?>
-<!DOCTYPE log4j:configuration SYSTEM "log4j.dtd">
+<!DOCTYPE log4j:configuration PUBLIC "-//APACHE//DTD LOG4J 1.2//EN" "log4j.dtd">
 <!--
(Continue reading)

bugzilla | 5 Aug 2009 04:43
Picon
Favicon

DO NOT REPLY [Bug 42842] Create a PUBLIC identifier for the log4j DTD

https://issues.apache.org/bugzilla/show_bug.cgi?id=42842

--- Comment #2 from Curt Arnold <carnold <at> apache.org> 2009-08-04 19:43:07 PDT ---
There is no code in log4j that outputs a XML declaration.  There was only one
place that could consume (the entity resolver that previously assumed that any
system identifier ending with 'log4j.dtd' was our DTD.  I modified it to also
recognize '-//APACHE//DTD LOG4J 1.2//EN" as identifying the current log4j.dtd. 
Should have no negative effect on any other public identifiers users have used
to identify the log4j.dtd.

Committed 801049.

--

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
bugzilla | 5 Aug 2009 05:00
Picon
Favicon

DO NOT REPLY [Bug 42842] Create a PUBLIC identifier for the log4j DTD

https://issues.apache.org/bugzilla/show_bug.cgi?id=42842

Curt Arnold <carnold <at> apache.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
         Resolution|                            |FIXED

--

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
bugzilla | 5 Aug 2009 05:05
Picon
Favicon

DO NOT REPLY [Bug 46226] log4j.properties not using the right log level

https://issues.apache.org/bugzilla/show_bug.cgi?id=46226

Curt Arnold <carnold <at> apache.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID

--- Comment #1 from Curt Arnold <carnold <at> apache.org> 2009-08-04 20:05:30 PDT ---
Most likely there is another log4j.properties or log4j.xml on the class path. 
Sure you have figured it out or have forgotten it by now. log4j-user would have
been the right place for it.  Closing as INVALID.

--

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
Curt Arnold | 5 Aug 2009 05:16
Picon
Favicon

Marking org.apache.log4j.RollingFileAppender and DRFA as deprecated?

I'm planning on spending a few hours each night on log4j to finally  
cut a log4j 1.2.16.

There are a decent number of bugs regarding  
org.apache.log4j.RollingFileAppender or  
org.apache.log4j.DailyRollingFileAppender.  I'll look at the bug  
reports and see if there are any simple, low-risk fixes, but not sure  
that there will be.  org.apache.log4j.rolling.RollingFileAppender has  
some problems, but not as many as the org.apache.log4j RFA's.

Is it time to mark org.apache.log4j.RFA and DRFA as deprecated and  
suggest that users migrate to the RFA's in the extras companion?

Gmane