date:20060214

DO NOT REPLY [Bug 17862] - Version.getVersion() method requested

2006-02-14 Thread bugzilla

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=17862


[EMAIL PROTECTED] changed:

   What|Removed |Added

 CC||[EMAIL PROTECTED]




--- Additional Comments From [EMAIL PROTECTED]  2006-02-14 11:31 ---
For our in-house build scripts, we have a ant-based check that verifies that the
project.properties (a file) project version definition is equal to the one in
the java source-file _on release builds_. However, if you just do ordinary test
builds, this test isn't done. This test basically catches myself _every time_;
it is so difficult to remember to synch those! (And before that, I always
released code that had the wrong version altogether).
  (Also, on non-release-builds, the string "-POST" is added to all deliverables'
filenames (jars, and tar.gz), so that it is not possible to confuse a proper
release from a "test compiled" ("post" is supposed to mean that it is after the
1.3 release: 1.3-POST. You change to 1.4 when you build the 1.4 release, then
all test-builds after this gets 1.4-POST. Okay, enough already..).

BUT in regards to the version-string, here is another detail that one might want
to consider:

A public static final String LOG4J_VERSION = "1.3.15", and the method public
static getLog4jVersion() (return LOG4J_VERSION; } behaves slightly different in
an interesting way: accesses to the field from a user's code will be resolved
"statically" (as with e.g. an integer) _on compile time_, while the method will
always have to be resolved dynamically, e.g. link/run-time. This means that it
is possible, when a system starts up, to check whether it is running against the
version that it was compiled against - and also display this somewhere: "I was
compiled against 1.3.15, [and running on same|but is running on X]".
  The static field resolving of String is definately defined in the java
compiler specs (thus the "compiled against" is bound to work), but the
method-access I am slightly more uncertain about (the "I am running against
now"). The difference works for me, but I am not _certain_ that it isn't allowed
for a compiler to -statically inline- the method body, since the method body is
statical itself. The hunch is that it isn't allowed, since the method might
change in a future version, but so could the static string, and that is however
allowed to be inlined..
  It is very neat to be able to go to the "Monitor page" of a web-system and
have it list all these system libraries' compiled-against and running-on-now
versions.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

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

Re: log4j 1.3 alpha 8 release now available

2006-02-14 Thread paul womack

Mark Womack wrote:
This version contains many changes to bring it back to better
compatibility with log4j version 1.2.X, and more changes are planned for
the upcoming alpha9 release as well. Users are encouraged to test this
version with custom code that they have previously written for log4j
version 1.2.X and to report any issues to the log4j dev email list.

INCOMPATIBILITY and DOCUMENTATION OUT OF SYNC WITH CODE

In 1.2.8 I had extended PatternLayout to add 2 conversion
letters, giving me full stack dumps, and "terse" stack
dumps (instead of the always on, full stack dump
of PatternLayout).

Since the internal structure of PatterLayout
have changed, and I was using non-documented
internal classes, I have bought this on myself.
I have no complaints. But it provided good
results for coupla' years...

The overview doc for PatternLayout
http://www.qos.ch/logging/PatternLayout.jsp
speaks of facilities in PatternLayout
for adding new PatternConverters.

I would have been happy to alter my
code to use this (more official) approach.

Sadly, the facilities do not
appear to be present in the 1.3 alpha-8.

Intriguingly they were present in 1.3 alpha-1
http://72.14.207.104/search?q=cache:S_wrbFAOLogJ:logging.apache.org/log4j/docs/api-1.3/org/apache/log4j/PatternLayout.html+addConversionRule&hl=en&gl=uk&ct=clnk&cd=1&lr=lang_en&ie=UTF-8

I would (very much) like to use the documented method
for adding PatternConverter to Pattern Layout.

Any chance?

BugBear

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

Filter for Logger FQDN

2006-02-14 Thread Kariem Hussein

Hi,

As this is the first time sending mail to this dev-list, please do not
hesitate to tell me what I am doing wrong.

Based on the StringMatchFilter implementation a friend of mine (Bijan
Fathi) has created the attached LoggerMatchFilter. It uses the
logger's fqdn and acts similar to the StringMatchFilter.

Motivation:
In our project we use different appenders for different applications,
using a single log4j.xml (jboss, tclfilter). It was necessary to
filter loggers of a specific package, without interfering with other
appenders.

Strangely enough we could not find anything related, so we created this filter.

Was there already anything related we could have used? Is this approach ok?

Greetings,
Kariem
Index: log4j/src/java/org/apache/log4j/filter/LoggerMatchFilter.java
===
--- log4j/src/java/org/apache/log4j/filter/LoggerMatchFilter.java   
(revision 0)
+++ log4j/src/java/org/apache/log4j/filter/LoggerMatchFilter.java   
(revision 0)
@@ -0,0 +1,49 @@
+/*
+ * 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.filter;
+
+import org.apache.log4j.spi.Filter;
+import org.apache.log4j.spi.LoggingEvent;
+import org.apache.log4j.filter.StringMatchFilter;
+
+/**
+ * This is a very simple filter based on string matching on the logger fqdn.
+ * 
+ * @author Bijan Fathi
+ * @see StringMatchFilter
+ */
+public class LoggerMatchFilter extends StringMatchFilter {
+
+public int decide(LoggingEvent event) {
+String msg = event.fqnOfCategoryClass;
+
+if (msg == null || getStringToMatch() == null) {
+return Filter.NEUTRAL;
+}
+
+if (msg.indexOf(getStringToMatch()) == -1) {
+// string not found
+return Filter.NEUTRAL;
+}
+
+// we've got a match
+if (getAcceptOnMatch()) {
+return Filter.ACCEPT;
+}
+return Filter.DENY;
+}
+
+}











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

[Fwd: Re: log4j 1.3 alpha 8 release now available]

2006-02-14 Thread paul womack

INCOMPATIBILITY and DOCUMENTATION OUT OF SYNC WITH CODE

In 1.2.8 I had extended PatternLayout to add 2 conversion
letters, giving me full stack dumps, and "terse" stack
dumps (instead of the always on, full stack dump
of PatternLayout).

The overview doc for PatternLayout
http://www.qos.ch/logging/PatternLayout.jsp
speaks of facilities in PatternLayout
for adding new PatternConverters.

I would have been happy to alter my
code to use this (more official) approach.

Sadly, the facilities do not
appear to be present in the 1.3 alpha-8.

I would (very much) like to use the documented method
for adding PatternConverter to Pattern Layout.

Any chance?

BugBear

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

RE: log4j 1.3 alpha 8 release now available

2006-02-14 Thread Scott Deboy

Sorry I didn't discover this earlier but something went wrong with the alpha8 
build w/r/t LogFilePatternReceiver:

Exception in thread "Thread-0" java.lang.NoSuchMethodError: org.apache.log4j.spi
.ComponentBase.access$101(Lorg/apache/log4j/varia/LogFilePatternReceiver;)Lorg/a
pache/log4j/ULogger;
at org.apache.log4j.varia.LogFilePatternReceiver$1.run(LogFilePatternRec
eiver.java:803)
at java.lang.Thread.run(Unknown Source)

I don't get this when I run against a local build of SVN trunk - maybe it 
wasn't cleaned prior to the build?

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 womack [mailto:[EMAIL PROTECTED]
Sent: Tue 2/14/2006 3:00 AM
To: log4j-dev@logging.apache.org
Subject: Re: log4j 1.3 alpha 8 release now available

Mark Womack wrote:
> This version contains many changes to bring it back to better 
> compatibility with log4j version 1.2.X, and more changes are planned for 
> the upcoming alpha9 release as well. Users are encouraged to test this 
> version with custom code that they have previously written for log4j 
> version 1.2.X and to report any issues to the log4j dev email list. 

INCOMPATIBILITY and DOCUMENTATION OUT OF SYNC WITH CODE

In 1.2.8 I had extended PatternLayout to add 2 conversion
letters, giving me full stack dumps, and "terse" stack
dumps (instead of the always on, full stack dump
of PatternLayout).

Since the internal structure of PatterLayout
have changed, and I was using non-documented
internal classes, I have bought this on myself.
I have no complaints. But it provided good
results for coupla' years...

The overview doc for PatternLayout
http://www.qos.ch/logging/PatternLayout.jsp
speaks of facilities in PatternLayout
for adding new PatternConverters.

I would have been happy to alter my
code to use this (more official) approach.

Sadly, the facilities do not
appear to be present in the 1.3 alpha-8.

Intriguingly they were present in 1.3 alpha-1
http://72.14.207.104/search?q=cache:S_wrbFAOLogJ:logging.apache.org/log4j/docs/api-1.3/org/apache/log4j/PatternLayout.html+addConversionRule&hl=en&gl=uk&ct=clnk&cd=1&lr=lang_en&ie=UTF-8

I would (very much) like to use the documented method
for adding PatternConverter to Pattern Layout.

Any chance?

BugBear

-
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]

DO NOT REPLY [Bug 38617] - Support for custom levels without specifying classname

2006-02-14 Thread bugzilla

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=38617





--- Additional Comments From [EMAIL PROTECTED]  2006-02-14 17:16 ---
(In reply to comment #4)
> I don't see any mechanism that assigns a numerical level value an unrecognized
level.  How would log4j 
> know whether NOTICE where more or less significant than "ERROR", for example.
 In the current (less than 
> optimal) mechanism, that infomation is coded into the class.

I don't understand. How is this related to the issue I fix? It does not touch
the basic properties of a Level (or a Priority instance, for that matter). So
everything else remains working as it does now. Just create a Level instance as
one would do now. Then you already specify the numerical level.

I think you think I'm trying to solve a larger (or even different) issue.

The requested enhancement is not about not having to do any coding. You still
have to write some code that will construct a Level instance with a proper name,
numeric value and syslog-equivalent value.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

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

DO NOT REPLY [Bug 38580] - Reading log files using Chainsaw

2006-02-14 Thread bugzilla

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=38580





--- Additional Comments From [EMAIL PROTECTED]  2006-02-14 17:29 ---
Scott, Thanks for the feedback. 

I tried with conversionPattern
log4j.appender.FILE.layout.ConversionPattern=%d %p %c [%t] [%x] - %m%n  
and
logFormat:
TIMESTAMP LEVEL LOGGER [THREAD] [NDC] - MESSAGE

also tried with log4j.xml. But seems to be giving the same output as before. 

Basically I want to know if I can use Chainsaw to filter my log file based on 
NDC.

Thanks in advance.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

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

DO NOT REPLY [Bug 38580] - Reading log files using Chainsaw

2006-02-14 Thread bugzilla

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=38580


[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||INVALID




--- Additional Comments From [EMAIL PROTECTED]  2006-02-14 17:32 ---
Since this isn't a bug, let's move this conversation to the log4j-user mailing
list.  I'll send an email there.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

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

BoundedDailyRollingFileAppender

2006-02-14 Thread Erick Dovale


Hi there guys,
I was needing an appender to roll files daily and to maintain a maximun 
amount of log files like the RolliFileAppender does. There was the 
DailyRollingFileAppender that was able to roll files daily but do not 
have any functionality for the maximun number of files to keep. So I 
wrote this BoundedDailyRollingFileAppender that takes a number of files 
and delets the oldest log file when it is rolled if the max number of 
files is reached.
I just extended FileAppender and copied the whole content of the 
DailyRollingFileAppender and added a method to delete the file. I am 
willing to donate this class to log4j. I am using log4j-1.2.x

If you are ineterested please let me know how to proceed.

Thanks for a great product.

Erick.

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

DO NOT REPLY [Bug 38617] - Support for custom levels without specifying classname

2006-02-14 Thread bugzilla

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=38617





--- Additional Comments From [EMAIL PROTECTED]  2006-02-14 18:30 ---
Okay, I missed that you were expecting the caller to have registered "NOTICE" 
by creating a derived 
class prior to calling the configurator and misread the casts of the 
Priority.INFO et al which led me to 
think you might have been working on code where Priority extends Level instead 
of vice-versa.  

I'm concerned that the lazy initialization of the hashtable might present a 
threading issue.  It also 
continues to perpetuate the subclassing Level just to work around the protected 
constructor.  I also 
don't like joining the construction and registration actions (though I 
understand why those were done).

The NAME#classname is a bit ugly, but it does not require registration of the 
level prior to the 
configuration and it only uglifies the configuration file and the benefit of 
the patch doesn't seem to be 
sufficient to justify the potential ramifications (particularly in the 1.2.x 
branch) in my opinion.





  

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

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

DO NOT REPLY [Bug 38617] - Support for custom levels without specifying classname

2006-02-14 Thread bugzilla

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=38617





--- Additional Comments From [EMAIL PROTECTED]  2006-02-14 20:13 ---
(In reply to comment #6)
> Okay, I missed that you were expecting the caller to have registered "NOTICE"
by creating a derived 
> class prior to calling the configurator and misread the casts of the
Priority.INFO et al which led me to 
> think you might have been working on code where Priority extends Level instead
of vice-versa.  

Perhaps I should have been clearer on what my intensions were.

> I'm concerned that the lazy initialization of the hashtable might present a
threading issue.  It also 

The lazy initialization is indeed a bit ugly. I'll see if I can fix that. And
indeed it may present a threading issue. I didn't think of that yet.

> continues to perpetuate the subclassing Level just to work around the
protected constructor.  I also

How is the fact that Log4J requires subclassing Level relevant? I don't intend
to change that fact here, it's just a relatively minor improvement.

> don't like joining the construction and registration actions (though I
understand why those were done).

They could be separated. But then you lose some of the perceived elegance from
the perspective of the Log4J user...

> The NAME#classname is a bit ugly, but it does not require registration of the
level prior to the 
> configuration and it only uglifies the configuration file and the benefit of
the patch doesn't seem to be 
> sufficient to justify the potential ramifications (particularly in the 1.2.x
branch) in my opinion.

I disagree, because I have a practical issue here. The issue is that I don't
want to specify a class name in my Log4J settings, since the latter are
maintained by the IT Operations department. And class names are not in their
vocabulary.

Also, we provide them with documentation on log levels, but then one log level
is suddenly configured differently from all the others. That's inconsistent.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

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

DO NOT REPLY [Bug 38617] - Support for custom levels without specifying classname

2006-02-14 Thread bugzilla

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=38617


[EMAIL PROTECTED] changed:

   What|Removed |Added

  Attachment #17661|0   |1
is obsolete||




--- Additional Comments From [EMAIL PROTECTED]  2006-02-14 20:36 ---
Created an attachment (id=17692)
 --> (http://issues.apache.org/bugzilla/attachment.cgi?id=17692&action=view)
Patch that makes Level dynamically store and lookup Level instances by name,
with test case

I've improvement the patch. This time, the Hashtable is initialized by the
class initializer. However, I moved the ALL_LEVELS class field to class
Priority for this, because the latter is initialized before class Level, but it
constructs Level instances. So the Level constructor gets called before the
class initializer. This was the initial reason I introduced lazy
initialization.

Also, I've extended the test case to test some more situations.

I will think about registering levels explicitly. Perhaps I'll submit another
version of the patch for that.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

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

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

2006-02-14 Thread 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.
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
 -DEBUG- Extracted 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: 6 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=14022006 chainsaw.jar 
[Working Directory: /usr/local/gump/public/workspace/logging-chainsaw]
CLASSPATH: 
/opt/jdk1.4/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-14022006.jar:/usr/local/gump/public/workspace/logging-log4j/dist/lib/log4j-14022006.jar:/usr/local/gump/public/workspace/logging-log4j/dist/lib/log4j-optional-14022006.jar:/usr/local/gump/public/workspace/logging-log4j/dist/lib/log4j-oro-14022006.jar:/usr/local/gump/public/workspace/logging-log4j/dist/lib/log4j-xml-14022006.jar:/usr/local/gump/public/workspace/jakarta-commons/vfs/target/commons-vfs-14022006.jar:/usr/local/gump/public/workspace/xstream/xstream-14022006.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] import org.apache.log4j.TTCCLayout;
[javac] ^
[javac] 
/x1/gump/public/workspace/logging-chainsaw/src/java/org/apache/log4j/chainsaw/LogUI.java:617:
 warning: 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:625:
 warning: 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: 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: 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: 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

2006-02-14 Thread 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.
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
 -DEBUG- Extracted 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: 6 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=14022006 chainsaw.jar 
[Working Directory: /usr/local/gump/public/workspace/logging-chainsaw]
CLASSPATH: 
/opt/jdk1.4/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-14022006.jar:/usr/local/gump/public/workspace/logging-log4j/dist/lib/log4j-14022006.jar:/usr/local/gump/public/workspace/logging-log4j/dist/lib/log4j-optional-14022006.jar:/usr/local/gump/public/workspace/logging-log4j/dist/lib/log4j-oro-14022006.jar:/usr/local/gump/public/workspace/logging-log4j/dist/lib/log4j-xml-14022006.jar:/usr/local/gump/public/workspace/jakarta-commons/vfs/target/commons-vfs-14022006.jar:/usr/local/gump/public/workspace/xstream/xstream-14022006.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] import org.apache.log4j.TTCCLayout;
[javac] ^
[javac] 
/x1/gump/public/workspace/logging-chainsaw/src/java/org/apache/log4j/chainsaw/LogUI.java:617:
 warning: 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:625:
 warning: 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: 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: 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: Date(java.lang.String) in java.util.Date has been deprecated
[javac] value = timestampExpressionFormat.format(new 
Date(table.getValueAt(row, column).toString()));
[javac]

DO NOT REPLY [Bug 17862] - Version.getVersion() method requested

2006-02-14 Thread bugzilla

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=17862





--- Additional Comments From [EMAIL PROTECTED]  2006-02-14 23:07 ---
I see the following options for updating the version string:
1) Manually
2) Automatically from the build script

Considering the comment #8 from Endre Stølsvik, it indeed sounds like it's wise
to let it be done automatically.

Then I see the following options for locations for storing the version string:
a) in a static string in some class
b) in the Manifest.mf file, inside the JAR file
c) in a separate resource inside the JAR file

The last two options have multiple advantages over the former. As Mark Womack
mentions in comment #7 it avoids having to recompile code which is an issue
because it would normally make the system dependant on the javac dependency
algorithm, which is timestamp-based and may be tricky.

Also, the second and third option allows checking the version by just peeking at
the JAR file. That's an additional feature!

Option (b) has the advantage of being a standard approach. So assuming we can
get to this information, even on JDK 1.1, I suggest we choose this one.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

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

DO NOT REPLY [Bug 17862] - Version.getVersion() method requested

2006-02-14 Thread bugzilla

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=17862





--- Additional Comments From [EMAIL PROTECTED]  2006-02-15 00:10 ---
Re: comment #9: We do indeed also put the version information, and build date
(and are considering build-machine etc), in the manifest file.

I didn't quite get the point about "dependant on the javac dependency
algorithm".. If you simply _check_ that the versions match against some
project.properties-or-whatever file, then there won't be any timestamp. And did
you consider the somewhat strange but cool feature where your application code
can have its "compiled against version X of log4j" embedded in one of its class
files? .. the point is that if you later end up with a later version of log4j in
classpath, this can be caught by the application, and possibly mention it in
some log or similar.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

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

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

2006-02-14 Thread 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.
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
 -DEBUG- Extracted 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: 6 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=14022006 chainsaw.jar 
[Working Directory: /usr/local/gump/public/workspace/logging-chainsaw]
CLASSPATH: 
/opt/jdk1.4/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-14022006.jar:/usr/local/gump/public/workspace/logging-log4j/dist/lib/log4j-14022006.jar:/usr/local/gump/public/workspace/logging-log4j/dist/lib/log4j-optional-14022006.jar:/usr/local/gump/public/workspace/logging-log4j/dist/lib/log4j-oro-14022006.jar:/usr/local/gump/public/workspace/logging-log4j/dist/lib/log4j-xml-14022006.jar:/usr/local/gump/public/workspace/jakarta-commons/vfs/target/commons-vfs-14022006.jar:/usr/local/gump/public/workspace/xstream/xstream-14022006.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] import org.apache.log4j.TTCCLayout;
[javac] ^
[javac] 
/x1/gump/public/workspace/logging-chainsaw/src/java/org/apache/log4j/chainsaw/LogUI.java:617:
 warning: 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:625:
 warning: 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: 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: 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: 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

2006-02-14 Thread 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.
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
 -DEBUG- Extracted 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: 6 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=14022006 chainsaw.jar 
[Working Directory: /usr/local/gump/public/workspace/logging-chainsaw]
CLASSPATH: 
/opt/jdk1.4/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-14022006.jar:/usr/local/gump/public/workspace/logging-log4j/dist/lib/log4j-14022006.jar:/usr/local/gump/public/workspace/logging-log4j/dist/lib/log4j-optional-14022006.jar:/usr/local/gump/public/workspace/logging-log4j/dist/lib/log4j-oro-14022006.jar:/usr/local/gump/public/workspace/logging-log4j/dist/lib/log4j-xml-14022006.jar:/usr/local/gump/public/workspace/jakarta-commons/vfs/target/commons-vfs-14022006.jar:/usr/local/gump/public/workspace/xstream/xstream-14022006.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] import org.apache.log4j.TTCCLayout;
[javac] ^
[javac] 
/x1/gump/public/workspace/logging-chainsaw/src/java/org/apache/log4j/chainsaw/LogUI.java:617:
 warning: 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:625:
 warning: 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: 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: 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: Date(java.lang.String) in java.util.Date has been deprecated
[javac] value = timestampExpressionFormat.format(new 
Date(table.getValueAt(row, column).toString()));
[javac]

DO NOT REPLY [Bug 17862] - Version.getVersion() method requested

Re: log4j 1.3 alpha 8 release now available

Filter for Logger FQDN

[Fwd: Re: log4j 1.3 alpha 8 release now available]

RE: log4j 1.3 alpha 8 release now available

DO NOT REPLY [Bug 38617] - Support for custom levels without specifying classname

DO NOT REPLY [Bug 38580] - Reading log files using Chainsaw

DO NOT REPLY [Bug 38580] - Reading log files using Chainsaw

BoundedDailyRollingFileAppender

DO NOT REPLY [Bug 38617] - Support for custom levels without specifying classname

DO NOT REPLY [Bug 38617] - Support for custom levels without specifying classname

DO NOT REPLY [Bug 38617] - Support for custom levels without specifying classname

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

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

DO NOT REPLY [Bug 17862] - Version.getVersion() method requested

DO NOT REPLY [Bug 17862] - Version.getVersion() method requested

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

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

18 matches

Site Navigation

Mail list logo

Footer information