[EMAIL PROTECTED]: Project logging-log4j-chainsaw (in module logging-chainsaw) failed

[noreply]

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 [EMAIL PROTECTED]

Project logging-log4j-chainsaw has an issue affecting its community integration.
This issue affects 1 projects,
 and has been outstanding for 10 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- logging-log4j-chainsaw :  Chainsaw log viewer


Full details are available at:

http://vmgump.apache.org/gump/public/logging-chainsaw/logging-log4j-chainsaw/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -INFO- Failed with reason build failed
 -INFO- Failed to extract fallback artifacts from Gump Repository



The following work was performed:
http://vmgump.apache.org/gump/public/logging-chainsaw/logging-log4j-chainsaw/gump_work/build_logging-chainsaw_logging-log4j-chainsaw.html
Work Name: build_logging-chainsaw_logging-log4j-chainsaw (Type: Build)
Work ended in a state of : Failed
Elapsed: 8 secs
Command Line: java -Djava.awt.headless=true 
-Xbootclasspath/p:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/usr/local/gump/public/workspace/xml-xerces2/build/xercesImpl.jar
 org.apache.tools.ant.Main -Dgump.merge=/x1/gump/public/gump/work/merge.xml 
-Dbuild.sysclasspath=only -Dversion=23022006 chainsaw.jar 
[Working Directory: /usr/local/gump/public/workspace/logging-chainsaw]
CLASSPATH: 
/opt/jdk1.5/lib/tools.jar:/usr/local/gump/public/workspace/logging-chainsaw/classes:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/public/workspace/xml-commons/java/build/resolver.jar:/usr/local/gump/public/workspace/jakarta-oro/jakarta-oro-23022006.jar:/usr/local/gump/public/workspace/logging-log4j/dist/lib/log4j-23022006.jar:/usr/local/gump/public/workspace/logging-log4j/dist/lib/log4j-optional-23022006.jar:/usr/local/gump/public/workspace/logging-log4j/dist/lib/log4j-oro-23022006.jar:/usr/local/gump/public/workspace/logging-log4j/dist/lib/log4j-xml-23022006.jar:/usr/local/gump/public/workspace/jakarta-commons/vfs/target/commons-vfs-23022006.jar:/usr/local/gump/public/workspace/xstream/xstream-23022006.jar:/usr/local/gump/public/workspace/jmdns/lib/jmdns.jar:/usr/local/gump/public/workspace/jakarta-servletapi-4/lib/servlet.jar:/usr/local/gump/packages/jms1.1/lib/jms.jar:/usr/local/gump/packages/jmx-1_2_1-bin/lib/jmxri.jar:/usr/local/gump/packages/jmx-1_2_1-bin/lib/jmxtools.jar:/usr/local/gump/packages/javamail-1.3.2/mail.jar:/usr/local/gump/packages/javamail-1.3.2/lib/mailapi.jar
-
[javac] 
/x1/gump/public/workspace/logging-chainsaw/src/java/org/apache/log4j/chainsaw/LogUI.java:618:
 warning: [deprecation] AppenderSkeleton() in org.apache.log4j.AppenderSkeleton 
has been deprecated
[javac]   new AppenderSkeleton() {
[javac]   ^
[javac] 
/x1/gump/public/workspace/logging-chainsaw/src/java/org/apache/log4j/chainsaw/LogUI.java:626:
 warning: [deprecation] AppenderSkeleton() in org.apache.log4j.AppenderSkeleton 
has been deprecated
[javac] public boolean requiresLayout() {
[javac]^
[javac] 
/x1/gump/public/workspace/logging-chainsaw/src/java/org/apache/log4j/chainsaw/prefs/SettingsManager.java:155:
 warning: [deprecation] encode(java.lang.String) in java.net.URLEncoder has 
been deprecated
[javac] URLEncoder.encode(p.getNamespace() + 
".properties"));
[javac]   ^
[javac] 
/x1/gump/public/workspace/logging-chainsaw/src/java/org/apache/log4j/chainsaw/prefs/SettingsManager.java:247:
 warning: [deprecation] encode(java.lang.String) in java.net.URLEncoder has 
been deprecated
[javac]  
URLEncoder.encode(profileable.getNamespace()) + ".properties")));
[javac]^
[javac] 
/x1/gump/public/workspace/logging-chainsaw/src/java/org/apache/log4j/chainsaw/LogPanel.java:1190:
 warning: [deprecation] Date(java.lang.String) in java.util.Date has been 
deprecated
[javac] value = timestampExpressionFormat.format(new 
Date(table.getValueAt(row, column).toString()));
[javac] 

[EMAIL PROTECTED]: Project logging-log4j-chainsaw (in module logging-chainsaw) failed

[noreply]

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 [EMAIL PROTECTED]

Project logging-log4j-chainsaw has an issue affecting its community integration.
This issue affects 1 projects,
 and has been outstanding for 10 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- logging-log4j-chainsaw :  Chainsaw log viewer


Full details are available at:

http://vmgump.apache.org/gump/public/logging-chainsaw/logging-log4j-chainsaw/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -INFO- Failed with reason build failed
 -INFO- Failed to extract fallback artifacts from Gump Repository



The following work was performed:
http://vmgump.apache.org/gump/public/logging-chainsaw/logging-log4j-chainsaw/gump_work/build_logging-chainsaw_logging-log4j-chainsaw.html
Work Name: build_logging-chainsaw_logging-log4j-chainsaw (Type: Build)
Work ended in a state of : Failed
Elapsed: 8 secs
Command Line: java -Djava.awt.headless=true 
-Xbootclasspath/p:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/usr/local/gump/public/workspace/xml-xerces2/build/xercesImpl.jar
 org.apache.tools.ant.Main -Dgump.merge=/x1/gump/public/gump/work/merge.xml 
-Dbuild.sysclasspath=only -Dversion=23022006 chainsaw.jar 
[Working Directory: /usr/local/gump/public/workspace/logging-chainsaw]
CLASSPATH: 
/opt/jdk1.5/lib/tools.jar:/usr/local/gump/public/workspace/logging-chainsaw/classes:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/public/workspace/xml-commons/java/build/resolver.jar:/usr/local/gump/public/workspace/jakarta-oro/jakarta-oro-23022006.jar:/usr/local/gump/public/workspace/logging-log4j/dist/lib/log4j-23022006.jar:/usr/local/gump/public/workspace/logging-log4j/dist/lib/log4j-optional-23022006.jar:/usr/local/gump/public/workspace/logging-log4j/dist/lib/log4j-oro-23022006.jar:/usr/local/gump/public/workspace/logging-log4j/dist/lib/log4j-xml-23022006.jar:/usr/local/gump/public/workspace/jakarta-commons/vfs/target/commons-vfs-23022006.jar:/usr/local/gump/public/workspace/xstream/xstream-23022006.jar:/usr/local/gump/public/workspace/jmdns/lib/jmdns.jar:/usr/local/gump/public/workspace/jakarta-servletapi-4/lib/servlet.jar:/usr/local/gump/packages/jms1.1/lib/jms.jar:/usr/local/gump/packages/jmx-1_2_1-bin/lib/jmxri.jar:/usr/local/gump/packages/jmx-1_2_1-bin/lib/jmxtools.jar:/usr/local/gump/packages/javamail-1.3.2/mail.jar:/usr/local/gump/packages/javamail-1.3.2/lib/mailapi.jar
-
[javac] 
/x1/gump/public/workspace/logging-chainsaw/src/java/org/apache/log4j/chainsaw/LogUI.java:618:
 warning: [deprecation] AppenderSkeleton() in org.apache.log4j.AppenderSkeleton 
has been deprecated
[javac]   new AppenderSkeleton() {
[javac]   ^
[javac] 
/x1/gump/public/workspace/logging-chainsaw/src/java/org/apache/log4j/chainsaw/LogUI.java:626:
 warning: [deprecation] AppenderSkeleton() in org.apache.log4j.AppenderSkeleton 
has been deprecated
[javac] public boolean requiresLayout() {
[javac]^
[javac] 
/x1/gump/public/workspace/logging-chainsaw/src/java/org/apache/log4j/chainsaw/prefs/SettingsManager.java:155:
 warning: [deprecation] encode(java.lang.String) in java.net.URLEncoder has 
been deprecated
[javac] URLEncoder.encode(p.getNamespace() + 
".properties"));
[javac]   ^
[javac] 
/x1/gump/public/workspace/logging-chainsaw/src/java/org/apache/log4j/chainsaw/prefs/SettingsManager.java:247:
 warning: [deprecation] encode(java.lang.String) in java.net.URLEncoder has 
been deprecated
[javac]  
URLEncoder.encode(profileable.getNamespace()) + ".properties")));
[javac]^
[javac] 
/x1/gump/public/workspace/logging-chainsaw/src/java/org/apache/log4j/chainsaw/LogPanel.java:1190:
 warning: [deprecation] Date(java.lang.String) in java.util.Date has been 
deprecated
[javac] value = timestampExpressionFormat.format(new 
Date(table.getValueAt(row, column).toString()));
[javac] 

Re: Next 1.3alpha build

[Mark Womack]

Well, since gump doesn't give access to the generated test files, no. 
So, I am going to switch the appender to a console appender so we can
see the output in the gump test output when it reports the failure.

-Mark

On 2/22/06, Paul Smith <[EMAIL PROTECTED]> wrote:
> sounds good, any luck tracking down that intermittent test case issue?
>
> Paul
> On 23/02/2006, at 10:40 AM, Mark Womack wrote:
>
> > Unless there are objections, I am going to plan in doing the next 1.3
> > alpha build next Wednsday (3/1) instead of tonight.  I know there are
> > some things I want to get in before that.
> >
> > speak up if you'd rather see the build today,
> > thanks,
> > -mark
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[POLL] Base JDK version support for log4j 1.3?

[Mark Womack]

We have talked about this before, and I plan to poll the user list,
but I thought we could talk about it some more here first.

What base JDK version do we want to support for log4j 1.3?  > JDK 1.2?
 > JDK 1.3?

Cons:
- not as universal of an option for logging

Pros:
- can use more modern, builtin classes (like Scheduler) instead of
growing our own
- less testing and build maintenance

others?

comments?
-Mark

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [POLL] Base JDK version support for log4j 1.3?

[Jess Holle]

I'm sure I'm in the minority here, but 1.2.13 seems fine for "legacy" 
versions of Java, i.e. everything prior to Java 5.


I'd be fine with requiring Java 5 for log4j 1.3 and using the best 
concurrency, etc, utilities it has to offer.


--
Jess Holle

Mark Womack wrote:

We have talked about this before, and I plan to poll the user list,
but I thought we could talk about it some more here first.

What base JDK version do we want to support for log4j 1.3?  > JDK 1.2?
 > JDK 1.3?

Cons:
- not as universal of an option for logging

Pros:
- can use more modern, builtin classes (like Scheduler) instead of
growing our own
- less testing and build maintenance

others?

comments?
-Mark

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [POLL] Base JDK version support for log4j 1.3?

[Boris Unckel]

Mark Womack wrote:

What base JDK version do we want to support for log4j 1.3?  > JDK 1.2?
 > JDK 1.3?

+1 for version >= JDK 1.3
with javac set to source 1.3 and target 1.3

Reasons:
- JDK 1.2 legacy(!) users have log4j 1.2.13, stable, extensible
- slow adoption of new JDKs is already fulfilled, we are at JDK 
1.5stable and 1.6beta


Personally I would prefer source 1.4 and target 1.4

Regards
Boris


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [POLL] Base JDK version support for log4j 1.3?

[Boris Unckel]

Jess Holle wrote:
I'm sure I'm in the minority here, but 1.2.13 seems fine for "legacy" 
versions of Java, i.e. everything prior to Java 5.


I'd be fine with requiring Java 5 for log4j 1.3 and using the best 
concurrency, etc, utilities it has to offer.
Does Java5 have this market share? For technical reasons I would prefer 
always the latest stable version, but for a user

base mainly working with one release before...

Regards
Boris

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [POLL] Base JDK version support for log4j 1.3?

[Curt Arnold]

On Feb 23, 2006, at 11:31 AM, Jess Holle wrote:

I'm sure I'm in the minority here, but 1.2.13 seems fine for  
"legacy" versions of Java, i.e. everything prior to Java 5.


I'd be fine with requiring Java 5 for log4j 1.3 and using the best  
concurrency, etc, utilities it has to offer.



It would be difficult, at least, to retain compatibility with log4j  
1.2 and migrate to use of JDK 1.5 concurrency.  Minimizing and  
reworking concurrency concerns is a log4j 2.0 issue and that would  
seem to be the time to jump to JDK 1.5 in my opinion.


JDK 1.3 seems to be a reasonable target to me.  To support JDK 1.4 as  
a target, there would have to be some specific benefit identified.








-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [POLL] Base JDK version support for log4j 1.3?

[Yoav Shapira]

Hola,
Since 1.3 is so focused on backwards-compatibility, why even change
the JDK version?  OTOH, log4j 2.0, which will hopefully be free to do
more fun stuff, should be Java5 IMHO...

Yoav

On 2/23/06, Curt Arnold <[EMAIL PROTECTED]> wrote:
>
> On Feb 23, 2006, at 11:31 AM, Jess Holle wrote:
>
> > I'm sure I'm in the minority here, but 1.2.13 seems fine for
> > "legacy" versions of Java, i.e. everything prior to Java 5.
> >
> > I'd be fine with requiring Java 5 for log4j 1.3 and using the best
> > concurrency, etc, utilities it has to offer.
>
>
> It would be difficult, at least, to retain compatibility with log4j
> 1.2 and migrate to use of JDK 1.5 concurrency.  Minimizing and
> reworking concurrency concerns is a log4j 2.0 issue and that would
> seem to be the time to jump to JDK 1.5 in my opinion.
>
> JDK 1.3 seems to be a reasonable target to me.  To support JDK 1.4 as
> a target, there would have to be some specific benefit identified.
>
>
>
>
>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


--
Yoav Shapira
System Design and Management Fellow
MIT Sloan School of Management
Cambridge, MA, USA
[EMAIL PROTECTED] / www.yoavshapira.com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [POLL] Base JDK version support for log4j 1.3?

[Elias Ross]

On Thu, 2006-02-23 at 11:31 -0600, Jess Holle wrote:

> I'd be fine with requiring Java 5 for log4j 1.3 and using the best 
> concurrency, etc, utilities it has to offer.

Ah, "concurrency" -- my favorite Log4j word...  I can't really see what
Java 5 would provide in terms of better concurrency other than
standardized lock classes.

However, if you wanted, you could write your library as 1.5 then make it
run on 1.4:

http://retroweaver.sourceforge.net/



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [POLL] Base JDK version support for log4j 1.3?

[Andreas Fester]

Mark Womack wrote:
> We have talked about this before, and I plan to poll the user list,
> but I thought we could talk about it some more here first.
> 
> What base JDK version do we want to support for log4j 1.3?  > JDK 1.2?
>  > JDK 1.3?

I do not see any reason to support 1.2 anymore. 1.3 would be reasonable,
but I would even say 1.4 should be sufficient, given that 1.5/5.0 is
now available on all major platforms (including AIX ;-)) and 1.6/6.0 is
in beta stage...

Regards,

Andreas


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [POLL] Base JDK version support for log4j 1.3?

[Jess Holle]

The real question is how many people will not upgrade to the latest 
stable JVM yet want to upgrade to the latest (currently unstable) log4j.


By the time log4j 1.3 is released, I'm guessing Java 6 will be stable, 
making the question "how many won't upgrade to at least the version 
prior to latest yet want the latest log4j?"


Boris Unckel wrote:

Jess Holle wrote:
I'm sure I'm in the minority here, but 1.2.13 seems fine for "legacy" 
versions of Java, i.e. everything prior to Java 5.


I'd be fine with requiring Java 5 for log4j 1.3 and using the best 
concurrency, etc, utilities it has to offer.
Does Java5 have this market share? For technical reasons I would 
prefer always the latest stable version, but for a user

base mainly working with one release before...

Regards
Boris

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

svn commit: r380234 - /logging/chainsaw/trunk/build.xml

[psmith]

Author: psmith
Date: Thu Feb 23 13:49:49 2006
New Revision: 380234

URL: http://svn.apache.org/viewcvs?rev=380234&view=rev
Log:
Bit of a hack for gump.  The log4j main source code is not available during
a gump run, so I have set a 'gump' flag in the chainsaw gump run, which disables
generation of the JavaDoc for ALL receivers.

That's all I can think of doing for now, ideas appreciated.

Modified:
logging/chainsaw/trunk/build.xml

Modified: logging/chainsaw/trunk/build.xml
URL: 
http://svn.apache.org/viewcvs/logging/chainsaw/trunk/build.xml?rev=380234&r1=380233&r2=380234&view=diff
==
--- logging/chainsaw/trunk/build.xml (original)
+++ logging/chainsaw/trunk/build.xml Thu Feb 23 13:49:49 2006
@@ -163,10 +163,35 @@
 
   
 
-  
+   
+   
+   
+   
+   
+   
+ 
+   
+ 
+   
+ 
+ 
+   
+
+   
+
+   
   
   
-  
+  
 
   
 
@@ -176,27 +201,6 @@

  

-   
-
-
-  
-
-  
-
-  
-  
-   
-
-
   
   
 

Re: [POLL] Base JDK version support for log4j 1.3?

[Mark Womack]

Part of the equation is also the web application servers like JBoss,
etc.  They are all on 1.5/5 now, but they weren't for a while there.

-Mark

On 2/23/06, Jess Holle <[EMAIL PROTECTED]> wrote:
> The real question is how many people will not upgrade to the latest
> stable JVM yet want to upgrade to the latest (currently unstable) log4j.
>
> By the time log4j 1.3 is released, I'm guessing Java 6 will be stable,
> making the question "how many won't upgrade to at least the version
> prior to latest yet want the latest log4j?"
>
> Boris Unckel wrote:
> > Jess Holle wrote:
> >> I'm sure I'm in the minority here, but 1.2.13 seems fine for "legacy"
> >> versions of Java, i.e. everything prior to Java 5.
> >>
> >> I'd be fine with requiring Java 5 for log4j 1.3 and using the best
> >> concurrency, etc, utilities it has to offer.
> > Does Java5 have this market share? For technical reasons I would
> > prefer always the latest stable version, but for a user
> > base mainly working with one release before...
> >
> > Regards
> > Boris
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [POLL] Base JDK version support for log4j 1.3?

[Mark Womack]

I mentioned the Scheduler specifically, but we can start using more of
the "recent" standard jdk classes.  I think that is a plus.  And we
are focusing on backwards compatibility with our own api.

-Mark

On 2/23/06, Yoav Shapira <[EMAIL PROTECTED]> wrote:
> Hola,
> Since 1.3 is so focused on backwards-compatibility, why even change
> the JDK version?  OTOH, log4j 2.0, which will hopefully be free to do
> more fun stuff, should be Java5 IMHO...
>
> Yoav
>
> On 2/23/06, Curt Arnold <[EMAIL PROTECTED]> wrote:
> >
> > On Feb 23, 2006, at 11:31 AM, Jess Holle wrote:
> >
> > > I'm sure I'm in the minority here, but 1.2.13 seems fine for
> > > "legacy" versions of Java, i.e. everything prior to Java 5.
> > >
> > > I'd be fine with requiring Java 5 for log4j 1.3 and using the best
> > > concurrency, etc, utilities it has to offer.
> >
> >
> > It would be difficult, at least, to retain compatibility with log4j
> > 1.2 and migrate to use of JDK 1.5 concurrency.  Minimizing and
> > reworking concurrency concerns is a log4j 2.0 issue and that would
> > seem to be the time to jump to JDK 1.5 in my opinion.
> >
> > JDK 1.3 seems to be a reasonable target to me.  To support JDK 1.4 as
> > a target, there would have to be some specific benefit identified.
> >
> >
> >
> >
> >
> >
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>
> --
> Yoav Shapira
> System Design and Management Fellow
> MIT Sloan School of Management
> Cambridge, MA, USA
> [EMAIL PROTECTED] / www.yoavshapira.com
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [POLL] Base JDK version support for log4j 1.3?

[Paul Smith]

I'd be happy with JDK 1.4 for log4j 1.3, and go 1.5 for log4j 2?

Paul

On 24/02/2006, at 10:17 AM, Mark Womack wrote:


I mentioned the Scheduler specifically, but we can start using more of
the "recent" standard jdk classes.  I think that is a plus.  And we
are focusing on backwards compatibility with our own api.

-Mark

On 2/23/06, Yoav Shapira <[EMAIL PROTECTED]> wrote:

Hola,
Since 1.3 is so focused on backwards-compatibility, why even change
the JDK version?  OTOH, log4j 2.0, which will hopefully be free to do
more fun stuff, should be Java5 IMHO...

Yoav

On 2/23/06, Curt Arnold <[EMAIL PROTECTED]> wrote:


On Feb 23, 2006, at 11:31 AM, Jess Holle wrote:


I'm sure I'm in the minority here, but 1.2.13 seems fine for
"legacy" versions of Java, i.e. everything prior to Java 5.

I'd be fine with requiring Java 5 for log4j 1.3 and using the best
concurrency, etc, utilities it has to offer.



It would be difficult, at least, to retain compatibility with log4j
1.2 and migrate to use of JDK 1.5 concurrency.  Minimizing and
reworking concurrency concerns is a log4j 2.0 issue and that would
seem to be the time to jump to JDK 1.5 in my opinion.

JDK 1.3 seems to be a reasonable target to me.  To support JDK  
1.4 as

a target, there would have to be some specific benefit identified.







 
-

To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





--
Yoav Shapira
System Design and Management Fellow
MIT Sloan School of Management
Cambridge, MA, USA
[EMAIL PROTECTED] / www.yoavshapira.com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

svn commit: r380310 - in /logging/log4j/trunk: docs/chainsaw.html src/xdocs/chainsaw.xml

[psmith]

Author: psmith
Date: Thu Feb 23 18:35:55 2006
New Revision: 380310

URL: http://svn.apache.org/viewcvs?rev=380310&view=rev
Log:
Added documentation about how to configure ZeroConf stuff for one's application
including links to the stuff required.

Modified:
logging/log4j/trunk/docs/chainsaw.html
logging/log4j/trunk/src/xdocs/chainsaw.xml

Modified: logging/log4j/trunk/docs/chainsaw.html
URL: 
http://svn.apache.org/viewcvs/logging/log4j/trunk/docs/chainsaw.html?rev=380310&r1=380309&r2=380310&view=diff
==
--- logging/log4j/trunk/docs/chainsaw.html (original)
+++ logging/log4j/trunk/docs/chainsaw.html Thu Feb 23 18:35:55 2006
@@ -76,7 +76,8 @@
  Installation
  Getting Started
  Tutorial and User Manual
- 
+ ZeroConf - Zero Configuration
+ 
  

So what is it really?
  It's a 
GUI-based Log viewer. A picture tells a thousand words...
@@ -120,13 +121,37 @@


 This applies to 
distributions.
+   
ZeroConf - Zero Configuration
+Chainsaw has 
ZeroConf elements embedded within it, but you'll need to add a few things
+   to your application to enable your application.
+Download:
+
+   http://logging.apache.org/log4j/docs/webstart/chainsaw/log4j-zeroconf.zip";>log4j
 ZeroConf extension
+   http://sourceforge.net/projects/jmdns/";>JmDNS bundle
+   Add the log4j-zeroconf.jar and the 
jmdns.jar from these bundles and add them to your 
+   application's classpath. 
+   Modify your log4j configuration so that it use the 
ZeroConfSocketHubAppender.  Here is a complete log4j.xml file that you can use 
as a base:
+   
+
+
+
+
+
+
+
+
+
+   
+   
+   
  
 
   
-  
+
 
   
-   
 
+   
 
 
  
 

Modified: logging/log4j/trunk/src/xdocs/chainsaw.xml
URL: 
http://svn.apache.org/viewcvs/logging/log4j/trunk/src/xdocs/chainsaw.xml?rev=380310&r1=380309&r2=380310&view=diff
==
--- logging/log4j/trunk/src/xdocs/chainsaw.xml (original)
+++ logging/log4j/trunk/src/xdocs/chainsaw.xml Thu Feb 23 18:35:55 2006
@@ -40,7 +40,8 @@
  Installation
  Getting Started
  Tutorial and User Manual
- 
+ ZeroConf - Zero Configuration
+ 
  
 
 
@@ -100,6 +101,30 @@
 
-
+   
+   Chainsaw has ZeroConf elements embedded 
within it, but you'll need to add a few things
+   to your application to enable your application for 
ZeroConf.
+   Download:
+   
+   http://logging.apache.org/log4j/docs/webstart/chainsaw/log4j-zeroconf.zip";>log4j
 ZeroConf extension
+   http://sourceforge.net/projects/jmdns/";>JmDNS bundle
+   Add the log4j-zeroconf.jar and the 
jmdns.jar from these bundles and add them to your 
+   application's classpath. 
+   Modify your log4j configuration so that it use the 
ZeroConfSocketHubAppender.  Here is a complete log4j.xml file that you can use 
as a base:
+   
+
+
+
+
+
+
+
+
+
+ 

svn commit: r380313 - in /logging/chainsaw/trunk: src/java/org/apache/log4j/chainsaw/ src/java/org/apache/log4j/chainsaw/help/ src/java/org/apache/log4j/chainsaw/version/ zeroconf/org/apache/log4j/cha

[psmith]

Author: psmith
Date: Thu Feb 23 18:43:55 2006
New Revision: 380313

URL: http://svn.apache.org/viewcvs?rev=380313&view=rev
Log:
Activated the ZeroConf plugin, i've done testing locally and it appears to work 
very well.

Only thing now is for someone else to try it...

Modified:
logging/chainsaw/trunk/src/java/org/apache/log4j/chainsaw/LogUI.java

logging/chainsaw/trunk/src/java/org/apache/log4j/chainsaw/help/release-notes.html

logging/chainsaw/trunk/src/java/org/apache/log4j/chainsaw/version/VersionManager.java

logging/chainsaw/trunk/zeroconf/org/apache/log4j/chainsaw/zeroconf/ZeroConfPlugin.html

Modified: logging/chainsaw/trunk/src/java/org/apache/log4j/chainsaw/LogUI.java
URL: 
http://svn.apache.org/viewcvs/logging/chainsaw/trunk/src/java/org/apache/log4j/chainsaw/LogUI.java?rev=380313&r1=380312&r2=380313&view=diff
==
--- logging/chainsaw/trunk/src/java/org/apache/log4j/chainsaw/LogUI.java 
(original)
+++ logging/chainsaw/trunk/src/java/org/apache/log4j/chainsaw/LogUI.java Thu 
Feb 23 18:43:55 2006
@@ -477,15 +477,15 @@
 //pluginRegistry.addPlugin(cc);
 //cc.activateOptions();
 
-//try {
-//Class pluginClass = 
Class.forName("org.apache.log4j.chainsaw.zeroconf.ZeroConfPlugin");
-//Plugin plugin = (Plugin) pluginClass.newInstance();
-//pluginRegistry.addPlugin(plugin);
-//plugin.activateOptions();
-//MessageCenter.getInstance().getLogger().info("Looks like ZeroConf 
stuff is available... WooHoo!");
-//} catch (Throwable e) {
-//MessageCenter.getInstance().getLogger().error("Doesn't look like 
ZeroConf is available", e);
-//}
+try {
+Class pluginClass = 
Class.forName("org.apache.log4j.chainsaw.zeroconf.ZeroConfPlugin");
+Plugin plugin = (Plugin) pluginClass.newInstance();
+pluginRegistry.addPlugin(plugin);
+plugin.activateOptions();
+MessageCenter.getInstance().getLogger().info("Looks like ZeroConf 
stuff is available... WooHoo!");
+} catch (Throwable e) {
+MessageCenter.getInstance().getLogger().error("Doesn't look like 
ZeroConf is available", e);
+}
   }
 
   private void setupReceiverPanel() {

Modified: 
logging/chainsaw/trunk/src/java/org/apache/log4j/chainsaw/help/release-notes.html
URL: 
http://svn.apache.org/viewcvs/logging/chainsaw/trunk/src/java/org/apache/log4j/chainsaw/help/release-notes.html?rev=380313&r1=380312&r2=380313&view=diff
==
--- 
logging/chainsaw/trunk/src/java/org/apache/log4j/chainsaw/help/release-notes.html
 (original)
+++ 
logging/chainsaw/trunk/src/java/org/apache/log4j/chainsaw/help/release-notes.html
 Thu Feb 23 18:43:55 2006
@@ -10,6 +10,11 @@
 NOTE: The mechanism and format used to persist settings in Chainsaw is 
subject to change during this alpha phase.  If you are experiencing problems 
displaying events in Chainsaw, please delete everything in the 
$user.dir/.chainsaw directory.
 
 1.99.99
+24 February 2006
+
+Added ZeroConf plugin, allowing simple point-n-click connection to 
detected appenders.  See the ZeroConf tab inside
+Chainsaw.
+
 20 February 2006
 
 Using a different file name to load and save global settings (from 
chainsaw.xml to chainsaw.settings.xml).  NOTE:Users will need to 
re-apply their application-wide settings or copy chainsaw.xml to 
chainsaw.settings.xml.

Modified: 
logging/chainsaw/trunk/src/java/org/apache/log4j/chainsaw/version/VersionManager.java
URL: 
http://svn.apache.org/viewcvs/logging/chainsaw/trunk/src/java/org/apache/log4j/chainsaw/version/VersionManager.java?rev=380313&r1=380312&r2=380313&view=diff
==
--- 
logging/chainsaw/trunk/src/java/org/apache/log4j/chainsaw/version/VersionManager.java
 (original)
+++ 
logging/chainsaw/trunk/src/java/org/apache/log4j/chainsaw/version/VersionManager.java
 Thu Feb 23 18:43:55 2006
@@ -10,7 +10,7 @@
 
 private static final VersionManager instance = new VersionManager();
 
-private static final String VERSION_INFO = "1.99.99 (20 February 2006)";
+private static final String VERSION_INFO = "1.99.99 (24 February 2006)";
 
 public static final VersionManager getInstance() {
 return instance;

Modified: 
logging/chainsaw/trunk/zeroconf/org/apache/log4j/chainsaw/zeroconf/ZeroConfPlugin.html
URL: 
http://svn.apache.org/viewcvs/logging/chainsaw/trunk/zeroconf/org/apache/log4j/chainsaw/zeroconf/ZeroConfPlugin.html?rev=380313&r1=380312&r2=380313&view=diff
==
--- 
logging/chainsaw/trunk/zeroconf/org/apache/log4j/chainsaw/zeroconf/ZeroConfPlugin.html
 (original)
+++ 
logging/chainsaw/trunk/zeroconf/org/apache/log4j/chainsaw/zeroconf/ZeroConfPlugin.html
 Thu Feb 23 18:43:55 2006
@@ -31,9 +31,29 @@
 Interesting... So what do I need t

Chainsaw: New release, vote?

[Paul Smith]

Well, I've committed the last doco bits and pieces for ZeroConf and  
Chainsaw, and wouldn't mind a release to get some feedback.


Anyway, I'm obviously +1.  If Scott +1's it, is that enough  
votes.. ?Do we need a broader vote?  We haven't had a vote in the  
past, but maybe that's because no-one, including me, ever thought  
about it.


cheers,

Paul

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Chainsaw: New release, vote?

[Scott Deboy]

I'm +1.

I do want to commit a change to VFSLogFilePatternReceiver prior to the release 
(provide an optional GUI window for entering VFS username/password).

Scott Deboy
COMOTIV SYSTEMS
111 SW Columbia Street Ste. 950
Portland, OR  97201

Telephone:  503.224.7496
Cell:   503.997.1367
Fax:503.222.0185

[EMAIL PROTECTED]

www.comotivsystems.com



-Original Message-
From: Paul Smith [mailto:[EMAIL PROTECTED]
Sent: Thu 2/23/2006 6:49 PM
To: Log4J Developers List
Subject: Chainsaw: New release, vote?
 
Well, I've committed the last doco bits and pieces for ZeroConf and  
Chainsaw, and wouldn't mind a release to get some feedback.

Anyway, I'm obviously +1.  If Scott +1's it, is that enough  
votes.. ?Do we need a broader vote?  We haven't had a vote in the  
past, but maybe that's because no-one, including me, ever thought  
about it.

cheers,

Paul

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


<>-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Chainsaw: New release, vote?

[Paul Smith]

ok, cool, I can wait for that.  Now it's just up to the others... ?

Paul

On 24/02/2006, at 2:51 PM, Scott Deboy wrote:


I'm +1.

I do want to commit a change to VFSLogFilePatternReceiver prior to  
the release (provide an optional GUI window for entering VFS  
username/password).


Scott Deboy
COMOTIV SYSTEMS
111 SW Columbia Street Ste. 950
Portland, OR  97201

Telephone:  503.224.7496
Cell:   503.997.1367
Fax:503.222.0185

[EMAIL PROTECTED]

www.comotivsystems.com



-Original Message-
From: Paul Smith [mailto:[EMAIL PROTECTED]
Sent: Thu 2/23/2006 6:49 PM
To: Log4J Developers List
Subject: Chainsaw: New release, vote?

Well, I've committed the last doco bits and pieces for ZeroConf and
Chainsaw, and wouldn't mind a release to get some feedback.

Anyway, I'm obviously +1.  If Scott +1's it, is that enough
votes.. ?Do we need a broader vote?  We haven't had a vote in the
past, but maybe that's because no-one, including me, ever thought
about it.

cheers,

Paul

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Chainsaw: New release, vote?

[Jacob Kjome]

Chainsaw is still "alpha" or "beta", no?  I don't think any vote is 
needed.  However, if a vote is needed, count me as +1.


Jake

At 01:49 PM 2/24/2006 +1100, you wrote:
>Well, I've committed the last doco bits and pieces for ZeroConf and
>Chainsaw, and wouldn't mind a release to get some feedback.
>
>Anyway, I'm obviously +1.  If Scott +1's it, is that enough
>votes.. ?Do we need a broader vote?  We haven't had a vote in the
>past, but maybe that's because no-one, including me, ever thought
>about it.
>
>cheers,
>
>Paul
>
>-
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>  



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Chainsaw: New release, vote?

[Paul Smith]

On 24/02/2006, at 2:58 PM, Jacob Kjome wrote:



Chainsaw is still "alpha" or "beta", no?  I don't think any vote is  
needed.  However, if a vote is needed, count me as +1.


It'd be nice if there was no 'formal' vote required, but I'm cool  
either way.  I guess I'll be more diligent in at least giving the  
team a heads up with what's actually goiig on, rather than just being  
a rogue element deploying things willy nilly


Paul

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [POLL] Base JDK version support for log4j 1.3?

[Jacob Kjome]

For those not willing or able to move past JDK1.3, it seems like they'd 
also be unlikely to keep up with the latest versions of supporting 
libraries such as Log4j.  Since the 1.2.xx branch will always be there and 
still works just fine, I don't see any problem with moving to JDK1.4, as 
long as application code that had used 1.2.xx continues to work with 1.3.xx 
when the user makes the move to JDK1.4+.  A 2.xx release should definitely 
move to 1.5 after that, as long as there's a compelling reason to do so.


Jake

At 09:28 AM 2/23/2006 -0800, you wrote:
>We have talked about this before, and I plan to poll the user list,
>but I thought we could talk about it some more here first.
>
>What base JDK version do we want to support for log4j 1.3?  > JDK 1.2?
> > JDK 1.3?
>
>Cons:
>- not as universal of an option for logging
>
>Pros:
>- can use more modern, builtin classes (like Scheduler) instead of
>growing our own
>- less testing and build maintenance
>
>others?
>
>comments?
>-Mark
>
>-
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Chainsaw: New release, vote?

[Curt Arnold]

On Feb 23, 2006, at 8:49 PM, Paul Smith wrote:

Well, I've committed the last doco bits and pieces for ZeroConf and  
Chainsaw, and wouldn't mind a release to get some feedback.


Anyway, I'm obviously +1.  If Scott +1's it, is that enough  
votes.. ?Do we need a broader vote?  We haven't had a vote in  
the past, but maybe that's because no-one, including me, ever  
thought about it.


cheers,

Paul



Given the feedback on the recent log4j 1.3 alpha 8, how would you  
characterize the intended release?  It production quality to be  
placed on the primary dist and mirrors or alpha, beta or otherwise  
and placed on cvs.apache.org?


What versions of log4j would it work with?

Would you prefer Mark to do a build and place it for review or do you  
intend to do that?  A release vote would need a set of bits for us to  
give thumbs up or down.


Sorry not to be up on these things.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

svn commit: r380605 - in /logging/log4j/trunk: build.xml src/java/org/apache/log4j/xml/LogFileXMLReceiver.java src/java/org/apache/log4j/xml/LogFileXMLReceiverBeanInfo.java

[sdeboy]

Author: sdeboy
Date: Thu Feb 23 22:42:38 2006
New Revision: 380605

URL: http://svn.apache.org/viewcvs?rev=380605&view=rev
Log:
Initial commit: LogFileXMLReceiver

Added:
logging/log4j/trunk/src/java/org/apache/log4j/xml/LogFileXMLReceiver.java

logging/log4j/trunk/src/java/org/apache/log4j/xml/LogFileXMLReceiverBeanInfo.java
Modified:
logging/log4j/trunk/build.xml

Modified: logging/log4j/trunk/build.xml
URL: 
http://svn.apache.org/viewcvs/logging/log4j/trunk/build.xml?rev=380605&r1=380604&r2=380605&view=diff
==
--- logging/log4j/trunk/build.xml (original)
+++ logging/log4j/trunk/build.xml Thu Feb 23 22:42:38 2006
@@ -735,6 +735,7 @@
${stem}/xml/SAXErrorHandler.class,
 ${stem}/xml/UtilLoggingXMLDecoder.class,
 ${stem}/xml/XMLDecoder.class,
+   ${stem}/xml/LogFileXMLReceiver*.class,
${stem}/net/SMTPAppender.class,
${stem}/net/DefaultEvaluator.class,
${stem}/spi/TriggeringEventEvaluator.class,

Added: logging/log4j/trunk/src/java/org/apache/log4j/xml/LogFileXMLReceiver.java
URL: 
http://svn.apache.org/viewcvs/logging/log4j/trunk/src/java/org/apache/log4j/xml/LogFileXMLReceiver.java?rev=380605&view=auto
==
--- logging/log4j/trunk/src/java/org/apache/log4j/xml/LogFileXMLReceiver.java 
(added)
+++ logging/log4j/trunk/src/java/org/apache/log4j/xml/LogFileXMLReceiver.java 
Thu Feb 23 22:42:38 2006
@@ -0,0 +1,287 @@
+/*
+ * Copyright 1999,2004 The Apache Software Foundation.
+ * 
+ * Licensed 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.
+ */
+
+package org.apache.log4j.xml;
+
+import java.io.BufferedReader;
+import java.io.FileNotFoundException;
+import java.io.IOException;
+import java.io.InputStreamReader;
+import java.io.Reader;
+import java.net.MalformedURLException;
+import java.net.URL;
+import java.util.Collection;
+import java.util.Iterator;
+
+import org.apache.log4j.helpers.Constants;
+import org.apache.log4j.plugins.Receiver;
+import org.apache.log4j.rule.ExpressionRule;
+import org.apache.log4j.rule.Rule;
+import org.apache.log4j.spi.Decoder;
+import org.apache.log4j.spi.LoggingEvent;
+
+/**
+LogFileXMLReceiver will read an xml-formated log file and make the events in 
the log 
+file available to the log4j framework.  
+
+This receiver supports log files created using log4j's XMLLayout, as well 
as 
+java.util.logging XMLFormatter (via the org.apache.log4j.spi.Decoder 
interface).
+
+By default, log4j's XMLLayout is supported (no need to specify a decoder in 
that case).
+
+To configure this receiver to support java.util.logging's XMLFormatter, 
specify a
+'decoder' param of org.apache.log4j.xml.UtilLoggingXMLDecoder.
+
+Tailing -may- work, but not in all cases (try using a file:// URL).  If a 
process has a log file open,
+the receiver may be able to read and tail the file.  If the process closes the 
file and reopens the file, 
+the receiver may not be able to continue tailing the file.
+
+An expressionFilter may be specified.  Only events passing the expression 
will be forwarded to the log4j framework.
+
+Once the event has been "posted", it will be handled by the
+appenders currently configured in the LoggerRespository.
+
[EMAIL PROTECTED] Scott Deboy <[EMAIL PROTECTED]>
+
+  @since 1.3
+*/
+
+public class LogFileXMLReceiver extends Receiver {
+   private String fileURL;
+   private Rule expressionRule;
+   private String filterExpression;
+   private String decoder = "org.apache.log4j.xml.XMLDecoder";
+   private boolean tailing = false;
+
+   private Decoder decoderInstance;
+   private Reader reader;
+   private static final String FILE_KEY = "file";
+   private String host;
+   private String path;
+
+   /**
+* Accessor
+* 
+* @return file URL
+*/
+   public String getFileURL() {
+   return fileURL;
+   }
+
+   /**
+* Specify the URL of the XML-formatted file to process.
+* 
+* @param fileURL
+*/
+   public void setFileURL(String fileURL) {
+   this.fileURL = fileURL;
+   }
+
+   /**
+* Accessor
+* 
+* @return
+*/
+   public String getDecoder() {
+   return decoder;
+   }
+
+   /**
+* Specify the class 

Re: [POLL] Base JDK version support for log4j 1.3?

[Boris Unckel]

Good Morning,

Jacob Kjome wrote:


  For those not willing or able to move past JDK1.3, it seems like 
they'd also be unlikely to keep up with the latest versions of 
supporting libraries such as Log4j.  
  

+1 !!!


  Since the 1.2.xx branch will always be there and still works just 
fine, I don't see any problem with moving to JDK1.4, as long as 
application code that had used 1.2.xx continues to work with 1.3.xx 
when the user makes the move to JDK1.4+.  A 2.xx release should 
definitely move to 1.5 after that, as long as there's a compelling 
reason to do so. 
  

yes, exactly.
Full maintenance (Bug fixing, support, bug fix releases) for log4j 1.2.12 for JDK 1.2.x Users
Actual (trunk) release, compatible for application code with log4j 1.3 for JDK 1.4.x Users (source 1.4, target 1.4).

I have voted for JDK 1.3, but this was based on the argument of a user base.
Jacob's argumentation is more important to me than the absolute/relative count of potential users.
This is also based on my own experience: My company is not willing to move from 1.2.8 to 1.2.13 
due to the argument "never change a running system" and they have moved from IBM JDK 1.3.? to 1.4.2

Regards
Boris