Curt Arnold wrote:
I assume the infrastructure team is pretty adept at migrating Bugzilla
databases. I wouldn't do it in the middle of a iteration but at the
next alpha might be ok.
It is also documented at
http://nagoya.apache.org/wiki/apachewiki.cgi?JIRABugzillaMigration
--
Sincerely,
Asgei
hoju2004/12/14 22:30:10
Modified:.build.xml
src/java/org/apache/log4j/filter MDCMatchFilter.java
src/java/org/apache/log4j/servlet
InitShutdownController.java
ServletContextLogAppender.java
Remove
On Dec 14, 2004, at 9:32 PM, Paul Smith wrote:
I put a proposal to move log4j over to JIRA a while back, but it did
not seem to go down well. We've been using JIRA here at work for a
while now, and I get so frustrated with any Bugzilla I have to deal
with now.
But I'll support whatever this co
I put a proposal to move log4j over to JIRA a while back, but it did not
seem to go down well. We've been using JIRA here at work for a while
now, and I get so frustrated with any Bugzilla I have to deal with now.
But I'll support whatever this community wants. I understand that it is
a distr
On Dec 14, 2004, at 7:27 PM, Andy McBride wrote:
Do all apache projects use this bugzilla? I know its very functional
but... give me a nice jira interface anyday (free for open-source
projects I believe).
If anyone has any info on getting a simple summary report out of
bugzilla (preferably a
At 05:10 PM 12/14/2004 -0800, you wrote:
>Well, maybe you guys have had to solve this kind of problem before. I want
>to have the log home directory in one place for jboss and another place for
>tomcat. So, I was mucking with some code to set the log home base
>directory. The mechanism I fellbac
On Tue, 14 Dec 2004 17:10:44 -0800
Mark Womack <[EMAIL PROTECTED]> wrote:
Well, maybe you guys have had to solve this kind of
problem before. I want
to have the log home directory in one place for jboss and
another place for
tomcat.
I've never hit this requirement yet, I tend to log to a
fil
On Tue, 14 Dec 2004 16:35:13 -0800 (PST)
Yoav Shapira <[EMAIL PROTECTED]> wrote:
Hi,
As of this afternoon, my work has shrunk the number of
open issues from 206 to
99.
Wow! Could we keep this quiet please... if my boss finds
out he's going to want to know why I can only fix five a
day :-)
Well, maybe you guys have had to solve this kind of problem before. I want
to have the log home directory in one place for jboss and another place for
tomcat. So, I was mucking with some code to set the log home base
directory. The mechanism I fellback to was looking at the system
properties. I
Hi,
No problem. This checking is expected and welcome, not just from you but from
other committers as well. Bugs and issues that I thought were border-line I
tried to mark as such, either in the code or in the commit remarks.
This is also why I made the commits have a one-to-one relationship wit
Hi,
As of this afternoon, my work has shrunk the number of open issues from 206 to
99. There are a ton more that are either easy to do or irrelevant and can be
closed as such. There are also several issues which are simply good (not
trivial, not irrelevant) and would be nice additions to log4j.
Hi,
It's fairly pointless to rely on getServerInfo and similar approaches: it's one
of the first things security-conscious server administrators customize or
spoof, as that's a recommended best practice.
Class-name-based detections (e.g. Class.forName("org.apache.catalina.foo.bar")
for Tomcat) are
psmith 2004/12/14 13:06:08
Modified:src/java/org/apache/log4j/chainsaw/plugins
PluginClassLoaderFactory.java
Log:
Fix JDK 1.3 compatability.
Revision ChangesPath
1.5 +2 -2
logging-log4j/src/java/org/apache/log4j/chainsaw/plugins/Plugin
Also, does anyone know if there is a way to
programmatically detect the web
container the web app is running under? I am seeing a
need to have
different behavior between JBoss and Tomcat, and I was
just wondering if
there is a standard way to detect this.
-Mark
Mark,
The ServletContext has
psmith 2004/12/14 13:56:36
Modified:src chainsawWebStart.jnlp chainsaw.bat
Log:
these 2 changes are just because we're now at alpha-4.
Revision ChangesPath
1.4 +2 -2 logging-log4j/src/chainsawWebStart.jnlp
Index: chainsawWebStart.jnlp
=
Hi,
I used to get regular emails with a summary of open log4j
bugs but I don't seem to have received one for quite a
while.
Has something changed with the bugzilla config since the
move to logging.apache.org or is it just me not seeing
them?
It's a shame as it gave a good view of the qual
So, I have had the opportunity at my job to integrate and
use the o.a.log4j.servlet classes in the sandbox. And I have to say that
the initialization related classes (InitContextListener,
InitShutdownController) really rock! Many thanks to Jake for focusing on
these classes and making the
yoavs 2004/12/14 13:01:41
Modified:docs HISTORY.txt
src/java/org/apache/log4j/net SocketHubAppender.java
Log:
Bugzlla 28682.
Revision ChangesPath
1.17 +2 -0 logging-log4j/docs/HISTORY.txt
Index: HISTORY.txt
===
HUGE apologies for the delay here.
From CVS Head, the key classes are:
org.apache.log4j.chainsaw.LogUI - this is the 'startup' class that
contains the main(...) method, as well as a static method,
createChainsawGUI(ApplicationPreferenceModel, Action), that is designed
so that one could create
Hello Yoav,
Thanks for the recent flurry of bug fixes. With your permission, I
will go over the bug fixes one by one, checking that the bug fix
suggested by the user should really be applied. Obviously, only fixes
which are problematic will be reverted. Thus, this verification
process will inherent
Hi,
The setOption method of org.apache.log4j.pattern.DatePatternConverter consults
helpers.AbsoluteDateTimeFormat to figure out a pattern and then creates a
java.text.SimpleDateFormat formatter to use. Why doesn't DatePatternConverter
create an instance of AbsoluteDateTimeFormat instead?
I was lo
yoavs 2004/12/14 12:27:12
Modified:docs HISTORY.txt
src/java/org/apache/log4j/pattern PatternParser.java
src/java/org/apache/log4j/rolling
TimeBasedRollingPolicy.java
Log:
Changed converter register accessors to take/return
I finally got around to fixing this, sorry for the delay.
Paul Smith wrote:
When I remove the JDBC jar to avoid that part of the build I get the
next error:
chainsawCheck:
[echo] Chainsaw dependant libraries present.
build.chainsaw:
[javac] Compiling 119 source files to
C:\Java\code\j
Webstart Link:
http://logging.apache.org/log4j/docs/webstart/chainsaw/chainsawWebStart.jnlp
Standalone bundle:
http://logging.apache.org/log4j/docs/webstart/chainsaw/chainsaw-bundle.zip
regards to all,
Paul Smith
-
To unsubscribe,
yoavs 2004/12/14 13:11:04
Modified:docs HISTORY.txt
src/java/org/apache/log4j PropertyConfigurator.java
Log:
Bugzilla 28464.
Revision ChangesPath
1.18 +2 -0 logging-log4j/docs/HISTORY.txt
Index: HISTORY.txt
===
yoavs 2004/12/14 12:50:39
Modified:.build.properties.sample build.xml
docs HISTORY.txt
Log:
Bugzilla 26658.
Revision ChangesPath
1.19 +4 -1 logging-log4j/build.properties.sample
Index: build.properties.sample
=
At 07:41 PM 12/14/2004, Mark Womack wrote:
The fact that 200 projects were affected in Gump is a Gump problem, not a
log4j problem.
Gump is reportedly being improved to avoid the recent observed massive
breakdown. However, when 200 projects start blaming log4j, then things
become much less obvious.
On Wednesday 15 December 2004 02:41, Mark Womack wrote:
> If there are that many projects in there, all dependent on
> each other in a multitude of ways, it amazes me that Gump ever completes a
> nightly build of all the projects. I like Gump, I support it, but I am not
> going to take special ac
yoavs 2004/12/14 10:57:11
Modified:docs HISTORY.txt
src/java/org/apache/log4j/pattern PatternConverter.java
Log:
Bugzilla 17377.
Revision ChangesPath
1.14 +1 -0 logging-log4j/docs/HISTORY.txt
Index: HISTORY.txt
===
yoavs 2004/12/14 10:47:35
Modified:docs HISTORY.txt
src/java/org/apache/log4j/net SMTPAppender.java
Log:
Bugzilla 20985.
Revision ChangesPath
1.13 +12 -9 logging-log4j/docs/HISTORY.txt
Index: HISTORY.txt
===
I agree with Niclas. Unless there is something else going on here, his
suggestion was appropriate. I just did not take any action because I
figured Yoav would fix it the right way when he had a chance. It didn't
look like there were any other dependencies, but hey, I haven't been keeping
track o
At 04:48 PM 12/14/2004, Niclas Hedhman wrote:
On Tuesday 14 December 2004 22:57, Ceki Gülcü wrote:
My sincerest apologies. Of course, Log4J are entitled to "fuck up" from time
to time. That is not something I want to undermine, and if it came across
like that, then I am truly sorry.
Niclas, there i
Niclas et al.,
IMHO, the kind of urgent pleas as the one by Niclas (quoted below) are
quite inappropriate. We, the log4j developers, have the right to
occasionally fuck up like every one else. The fact that a small typo
affects 200 projects should tell you that something is wrong with
ceki2004/12/14 05:42:25
Modified:examples/tiny-webapp/Tata/src/WEB-INF web.xml
Removed: examples/tiny-webapp/Tata/src/resources log4j.xml
Log:
Web-app specific config files should be named differently than log4j.xml
Revision ChangesPath
1.4 +8 -0
log
ceki2004/12/14 05:42:14
Modified:examples/tiny-webapp INSTALL.txt
Log:
Web-app specific config files should be named differently than log4j.xml
Revision ChangesPath
1.3 +20 -28logging-log4j/examples/tiny-webapp/INSTALL.txt
Index: INSTALL.txt
=
ceki2004/12/14 05:38:32
Added: examples/tiny-webapp/Tata/src/resources tata-log4j.xml
Log:
Web-app specific config files should be named differently than log4j.xml
Revision ChangesPath
1.1
logging-log4j/examples/tiny-webapp/Tata/src/resources/tata-
Hi,
This would be my doing -- sorry about that. I swear it built cleanly from
scratch before I committed it. Will go fix...
Yoav
--- [EMAIL PROTECTED] wrote:
> To whom it may engage...
>
> This is an automated request, but not an unsolicited one. For
> more information please visit h
37 matches
Mail list logo
