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:[EMAIL PROTECTED] >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: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] > > > > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
