The missing JMSReceiver is because I did not have the j2ee jar at home
when I built it, and it silently dropped it from the build.
I will have to fix that tonight. Sorry about that. I wll also check the
issues that you have mentioned.
Paul
On Tue, 8 Jun 2004, Stephen Pain wrote:
Thanks -- it
you couldn't do me a huge favour and do this as a 'diff -u' could you?
(Unified diff), that way I can easily do this on my windows box inside the
ide.
I won't be able to redo the webstart till tonight (another 12 hours from
now) because I forgot to email myself certificate from home so I can do
Looking at our wiki, it seems to me that much of it either duplicates
the existing documentation in /docs/ or could be put to better use
under /src/xdocs.
The wiki is great for pages requiring user input. However, a wiki is
not well-suited for user documentation which requires some form of
quality
Log4j wiki pages are now editable.
http://wiki.apache.org/logging-log4j/Log4JProjectPages
http://wiki.apache.org/logging
If you are interested in a wiki for any other log4* project, please
ask infrastructure@ to set it up for you.
--
Ceki Gülcü
For log4j documentation consider "The complete lo
Oops, sent too fast. Chainsaw is built in the main Gump project (only other
one it log4j-test). So, my bad, I'll leave it.
regards,
Adam
- Original Message -
From: "Adam R. B. Jack" <[EMAIL PROTECTED]>
To: "Log4J Developers List" <[EMAIL PROTECTED]>
Sent: Tuesday, June 08, 2004 9:53 AM
S
Ok, I'll remove that dependency from the Gump descriptor. Thanks.
regards
Adam
- Original Message -
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, June 08, 2004 9:36 AM
Subject: cvs commit: logging-log4j build.xml
> sdeboy 2004/06/08 08:36:29
>
> Modified:.
sdeboy 2004/06/08 08:36:29
Modified:.build.xml
Log:
Moved compilation of logFilePatternReceiver from core to chainsaw to remove core ORO
dependency
Revision ChangesPath
1.104 +2 -1 logging-log4j/build.xml
Index: build.xml
Not quite related to what is said here, but...
>From a Gump perspective, I really like project separation (which is aided
by ant target and code dependency separation). Personally, I'd like the
chainsaw component out of the main logging (on Gump) project/build, since
folks only depend on (for com
> Thanks -- it works just fine!
I'm not convinced about that... a couple of bugs that had been fixed seem to have
reappeared! The receivers are now being duplicated again if I restart/refresh all, and
the restart doesn't seem to be working properly (ie, if I start chainsaw before I've
started
My most recent commit (adding an ExpressionRule dependency in LogFilePatternReceiver)
caused this.
I could move this out of core and add it in the Chainsaw target or somewhere else, I'm
fine with it.
I'd like to see support for something like my latest commit in all the receivers (the
ability
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 folk at [EMAIL PROTECTED]
Project log4j-tests has an issue affecting its community integration.
Project State : 'Failed
To whom it may satisfy...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact folk at [EMAIL PROTECTED]
Project logging-log4j *no longer* has an issue.
Project State : 'Success'
Full details are
Thanks -- it works just fine!
Asgeir
-Original Message-
From: Paul Smith [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 08, 2004 11:42 AM
To: Log4J Developers List
Subject: Re: Update Web Start?
I've managed to keep myself away from my Xbox and have compiled, built,
signed, and deployed
Here's the patch... still thinking about the Xbox!
If you could get this in and then include JMSReceiver in the webstart jar it would be
a big help (release notes now say that JMSReceiver is included, but I'm still getting
class not found).
Cheers,
Stephen
$ diff JMSReceiver.java.old JMSRecei
This is a question for Scott. I think his most recent commits added
this dependency but I am too lazy to check. In any case, looking at
the build.core target in build.xml, the org.apache.log4j.rule package
is part of the core build and apparently it needs ORO.
Scott, should we keep the rule package
I've managed to keep myself away from my Xbox and have compiled, built,
signed, and deployed the latest jars.
Apologise for the delay.
cheers,
Paul Smith
On Tue, 8 Jun 2004, Paul Smith wrote:
If I could just get my damn certificate installed properly on my new computer
I would have done this alr
If I could just get my damn certificate installed properly on my new
computer I would have done this already...
I'll again tonight when I get home.
cheers,
Paul
On Tue, 8 Jun 2004 [EMAIL PROTECTED] wrote:
Hello,
I've seen a number of commits for Chainsaw's release notes recently.
However, the Web
17 matches
Mail list logo
