Re: Chainsaw TODO's

[Paul Smith <ps...@aconex.com>]

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

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org

Re: Chainsaw TODO's

[Curt Arnold <ca...@apache.org>]

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.






---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org