Re: Chainsaw harmonization, branding, etc.

>
> I used the assembly:assembly plug to create a distribution, however  
> the descriptor (src/assembly/bin.xml) needs to be tweaked to drop  
> out non-re-distributable jars.  Hopefully, all the non-re- 
> distributable jars  are not essential to operation, at least not on  
> JDK 1.5. Currently, you can do java -jar on apache-chainsaw.jar and  
> the app launches.  I added the main-class and path entries to the  
> chainsaw jar, wouldn't do that on a library jar but hopefully is a  
> good thing for an application jar.
>

I've never found that main-class much use because of the external  
reference to jars.  Personally I like the appassembler distribution  
that maven can build, plus the Mac-specific one.

The external referenced jars are the crux of the problem with  
Chainsaw.  Out-of-the-box, Chainsaw is useful for socket-based  
operations and local file reading.  For JMS, DB, and VFS style  
operations, the 3rd-party requirements make it a tricky distribution  
problem.

Which exactly are the non-redistributable jars?  Xstream and jmdns  
are the only listed dependencies in the pom, both of which are ASL  
licensed.  JSch (for ssh-based stuff like vfs) used to LGPL but is  
now BSD licensed, but we don't actually need to depend on that per-se  
(they can go in the plugins directory).

> I will probably need to get my head around the distribution  
> mechanisms.  I think we do need a classic distribution tarball that  
> is farmed out to the distribution mirrors.  Keeping the WebStart is  

Re: Chainsaw TODO's

On 30/06/2007, at 7:15 AM, Curt Arnold wrote:

> There is a splash screen that shows Chainsaw history.  That should  
> be integrated into src/changes/changes.xml.
>
Is this is the Release Notes section you're referring to?  Yes I  
think tracking the changes in changes.xml is probably best from now  
on.  If there's a way to generate from this an html file that is  
'injected' into the generate-sources phase of maven, then Chainsaw  
can ship with a HTML copy of that file.

> I placed an empty development roadmap in src/site/apt/roadmap.apt.

thanks.

Paul

Re: Chainsaw harmonization, branding, etc.

On Jul 1, 2007, at 5:27 PM, Paul Smith wrote:

>>
>> I used the assembly:assembly plug to create a distribution,  
>> however the descriptor (src/assembly/bin.xml) needs to be tweaked  
>> to drop out non-re-distributable jars.  Hopefully, all the non-re- 
>> distributable jars  are not essential to operation, at least not  
>> on JDK 1.5. Currently, you can do java -jar on apache-chainsaw.jar  
>> and the app launches.  I added the main-class and path entries to  
>> the chainsaw jar, wouldn't do that on a library jar but hopefully  
>> is a good thing for an application jar.
>>
>
> I've never found that main-class much use because of the external  
> reference to jars.

The combo of Main-Class and Class-Path in there currently does allow  
the jar to be double-clicked and successfully launch after the  
tarball is expanded.  It does seem desirable in addition to the others.

> Personally I like the appassembler distribution that maven can  
> build, plus the Mac-specific one.
>
> The external referenced jars are the crux of the problem with  
> Chainsaw.  Out-of-the-box, Chainsaw is useful for socket-based  
> operations and local file reading.  For JMS, DB, and VFS style  
> operations, the 3rd-party requirements make it a tricky  
> distribution problem.
>

Re: Chainsaw TODO's

On Jul 1, 2007, at 5:29 PM, Paul Smith wrote:

>
> On 30/06/2007, at 7:15 AM, Curt Arnold wrote:
>
>> There is a splash screen that shows Chainsaw history.  That should  
>> be integrated into src/changes/changes.xml.
>>
> Is this is the Release Notes section you're referring to?  Yes I  
> think tracking the changes in changes.xml is probably best from now  
> on.  If there's a way to generate from this an html file that is  
> 'injected' into the generate-sources phase of maven, then Chainsaw  
> can ship with a HTML copy of that file.
>

Yes.  I think it could be generated and placed in the assembled jar.   
I'm not sure if generate-sources is the best phase, but that could be  
worked out.

Also the Help/About should say that the product is brought to you by  
the Apache Software Foundation or the Apache Logging Services Project  
instead of the Log4j team.

Re: log4j 1.2.15 and companion release candidates

On Jun 28, 2007, at 1:03 AM, Scott Deboy wrote:

> I pulled everything about 2 weeks ago and ran everything through  
> Chainsaw.
>
> The backported receivers which set properties on events (all of the  
> new network appenders) are throwing NPEs - around the property  
> setting code if I recall.
>
> We should do something about that - by either supporting properties  
> or preventing the NPEs.
>

Any chance you could recreate the test and provide stack traces or a  
description on how to reproduce the observed problem?  Pretty much  
stalled on addressing it until then.

Re: Chainsaw harmonization, branding, etc.

>

> I don't think we can redistribute activation.jar, jms-1.1.jar,  
> jmxri-1.2.1.jar, jmxtools-1.2.1.jar and mail-1.4.jar which are  
> currently included in the generated tarball and zip archive.  They  
> are in the assembly since they are referenced by log4j, but they  
> can be suppressed.
>

None of those should be shipped anyway.  Chainsaw either does not use  
them, or need to be placed in the plugins directory alongside the  
driver-specific jar (in the case of the jms one). We'd also want to  
specifically exclude the VFS, DB and JMS Receivers from the  
distribution for the same reason, hence the need for some customized  
Receiver distribution for Chainsaw only.

>>

>> We might as well be consistent with a tarball distro, but I'm not  
>> sure that's what the users would want to use.  For non-webstart  
>> operations I actually think letting the user use Maven to build  
>> the complete distribution including all dependencies is actually  
>> probably the most pain-free for a user.
>
> That would require Maven and a JDK where the current tarball can be  
> launched with just a JRE and tar.

yes true.  I was originally thinking that there was more jars that  
need to be distributed than can normally be with an Apache  
distribution (LGPL etc).  Given that the VFS and jmdns bits and bobs  

Bug report for Log4j [2007/07/01]

+---------------------------------------------------------------------------+
| Bugzilla Bug ID                                                           |
|     +---------------------------------------------------------------------+
|     | Status: UNC=Unconfirmed NEW=New         ASS=Assigned                |
|     |         OPN=Reopened    VER=Verified    (Skipped Closed/Resolved)   |
|     |   +-----------------------------------------------------------------+
|     |   | Severity: BLK=Blocker     CRI=Critical    MAJ=Major             |
|     |   |           MIN=Minor       NOR=Normal      ENH=Enhancement       |
|     |   |   +-------------------------------------------------------------+
|     |   |   | Date Posted                                                 |
|     |   |   |          +--------------------------------------------------+
|     |   |   |          | Description                                      |
|     |   |   |          |                                                  |
|  569|Ver|Cri|2001-02-09|fully qualified class name used as category name c|
|13099|Opn|Nor|2002-09-27|DOMConfigurator ignores category factory setting  |
|14350|New|Enh|2002-11-07|Patch to substitute variables in the log4j.configu|
|15585|Ver|Maj|2002-12-20|log4j does not show Class Name, Method, or Line Nu|
|16280|Opn|Min|2003-01-21|Error Message always logged to log4j when calling |
|17498|New|Nor|2003-02-27|Logging inconsistencies using DailyRollingFileAppe|
|17531|Ass|Min|2003-02-28|PropertyConfigurator.configureAndWatch() don't res|
|17887|Opn|Maj|2003-03-11|RollingFileAppender does not work for 10 threads  |
|20395|New|Enh|2003-06-01|PreparedStatementAppender Enhancement             |
|22894|Opn|Nor|2003-09-02|Single backslash not accepted in File param value |
|22934|Opn|Nor|2003-09-04|org.apache.log4j.jmx is not compatible with JMX 1.|
|23329|Ass|Maj|2003-09-22|<logger> element in XML config should support reso|
|25106|Opn|Enh|2003-12-01|Support XInclude in XML configuration scripts     |
|25107|New|Enh|2003-12-01|OptionConverter.getSystemProperty() does not allow|
|25355|New|Enh|2003-12-09|allow to require "TLS/SSL only" for outgoing mails|
|25747|New|Enh|2003-12-24|more explanations when hitting "WARN No appenders |
|26084|New|Nor|2004-01-13|Log Event detail panel does not show special chara|

DO NOT REPLY [Bug 42789] New: - Chainsaw can't remember filter expressions between restarts

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=42789>.
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=42789

           Summary: Chainsaw can't remember filter expressions between
                    restarts
           Product: Log4j
           Version: unspecified
          Platform: Other
        OS/Version: other
            Status: NEW
          Severity: normal
          Priority: P2
         Component: chainsaw
        AssignedTo: log4j-dev <at> logging.apache.org
        ReportedBy: isurues <at> gmail.com

When a user shuts down Chainsaw, it doesn't remember the filter expressions
specified in the 'Refine focus on' combo box. So the user have to specify the
expressions whenever he restarts Chainsaw. This can be really inconvenient for a
user who use several filter expressions for different tabs with so many log
events coming in...

--

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------

DO NOT REPLY [Bug 42789] - Chainsaw can't remember filter expressions between restarts

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=42789>.
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=42789

------- Additional Comments From isurues <at> gmail.com  2007-07-02 00:28 -------
Created an attachment (id=20425)
 --> (http://issues.apache.org/bugzilla/attachment.cgi?id=20425&action=view)
Making chainsaw remember filter expressions between restarts

In this patch, I have made the required changes to the LogPanel class in order
to make chainsaw remember filter expressions between restarts. I used the same
XML file which is currently used to remember LogPanel configurations to save
the filter expressions. And I added a button to clear the selected expression
on the combo box such that the cleared expression is no longer remembered by
Chainsaw.

--

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

GSoC project - task 2 - Making chainsaw remember filter expressions