logging-log4j-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Scott Deboy" <sde...@comotivsystems.com>
Subject RE: problems with chainsaw build
Date Thu, 16 Dec 2004 02:39:54 GMT
My mistake..

I didn't actually look, other than running 'ant chainsaw' and seeing logui in the jar.

Why you need to do a clean 1st is another question.


-----Original Message-----
From:	Paul Smith [mailto:psmith@aconex.com]
Sent:	Wed 12/15/2004 6:36 PM
To:	Log4J Users List
Cc:	
Subject:	Re: problems with chainsaw build
which may not build chainsaw (or all of chainsaw) if some libraries are 
missing (regexp is required ala jakarta-oro).

Andy McBride wrote:

> Hi,
> The 'jar' task depends on 'chainsaw.jar' which just jars up what is 
> there. 
> 'chainsaw.jar' target only depends on 'build', I think it also needs 
> to depend on 'build.chainsaw'
>
> Regards
>
> Andy
>
> On Thu, 16 Dec 2004 13:11:57 +1100
>  Paul Smith <psmith@aconex.com> wrote:
>
>> I'm a bit confused as to why "jar" _not_ but "chainsaw" is, because 
>> "chainsaw" depends on "jar" (at least I thought it did).
>>
>> Jacob Kjome wrote:
>>
>>> At 09:37 AM 12/15/2004 -0800, you wrote:
>>> >Curt,
>>> >
>>> >you need to run the 'chainsaw' target
>>> >
>>> >Scott
>>> >
>>>
>>> Scott, why would we allow the build to generate a chainsaw jar that 
>>> wasn't valid?  If "jar" is supposed to build all the jar artifacts 
>>> of the build, then the "chainsaw" target should be a dependency of 
>>> the "jar" target.  If we don't want to have this dependency, then 
>>> the chainsaw jar should not be built by running the "jar" target, 
>>> only the log4j jar.  My view of build files is that the user should 
>>> never, ever, be able to run something that doesn't produce a valid 
>>> result.  The build should take care of these dependencies relieving 
>>> the user of having to think about it.  Any other behavior is a bug.
>>>
>>>
>>> Jake
>>>
>>> >
>>> >-----Original Message-----
>>> >From:  Curt Arnold [mailto:carnold@apache.org]
>>> >Sent:  Wed 12/15/2004 8:55 AM
>>> >To:    Log4J Users List
>>> >Cc:
>>> >Subject:       Re: problems with chainsaw build
>>> >
>>> >On Dec 15, 2004, at 8:52 AM, Shai Simchi wrote:
>>> >
>>> >> thanks - i got it all figured out.
>>> >>
>>> >
>>> >Would be nice if you would share your resolution.  I just tried
>>> >building chainsaw from the CVS and am seeing the same problem.  If I
>>> >do:
>>> >
>>> >ant jar
>>> >
>>> >I get a log4j-chainsaw-1.3alpha-4.jar that does not contain the
>>> >org.apache.log4j.chainsaw.LogUI class.
>>> >
>>> >
>>> >---------------------------------------------------------------------
>>> >To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
>>> >For additional commands, e-mail: log4j-user-help@logging.apache.org
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >---------------------------------------------------------------------
>>> >To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
>>> >For additional commands, e-mail: log4j-user-help@logging.apache.org
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
>>> For additional commands, e-mail: log4j-user-help@logging.apache.org
>>>
>>>
>>>
>>
>> -- 
>>
>> *Paul Smith
>> *Software Architect
>>
>>     
>>
>> *Aconex
>> * 31 Drummond Street, Carlton, VIC 3053, Australia
>> *Tel: +61 3 9661 0200  *Fax: +61 3 9654 9946
>> Email: psmith@aconex.com  www.aconex.com**
>>
>> This email and any attachments are intended solely for the addressee. 
>> The contents may be privileged, confidential and/or subject to 
>> copyright or other applicable law. No confidentiality or privilege is 
>> lost by an erroneous transmission. If you have received this e-mail 
>> in error, please let us know by reply e-mail and delete or destroy 
>> this mail and all copies. If you are not the intended recipient of 
>> this message you must not disseminate, copy or take any action in 
>> reliance on it. The sender takes no responsibility for the effect of 
>> this message upon the recipient's computer system.**
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
>> For additional commands, e-mail: log4j-user-help@logging.apache.org
>>
>
> The information contained in this e-mail is intended only for the 
> person or
> entity to which it is addressed and may contain confidential and/or
> privileged material.  If You are not the intended recipient of this 
> e-mail,
> the use of this information or any disclosure, copying or distribution is
> Prohibited and may be unlawful.  If you received this in error, please
> contact the sender and delete the material from any computer.  The views
> expressed in this e-mail may not necessarily be the views of The PCMS 
> Group
> plc and should not be taken as authority to carry out any instruction
> contained.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-user-help@logging.apache.org
>
>
>

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






Mime
View raw message