You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-user@logging.apache.org by Jacob Kjome <ho...@visi.com> on 2004/02/25 06:51:42 UTC

update to install-chainsaw.xml + question

Wanted to let people know that I updated the install-chainsaw.xml to use 
the logging-log4j CVS module rather than jakarta-log4j, have it use the 
up-to-date 2.0.8 Jakarta-oro package, and added a commented out stub of 
<cvsgrab> listing all needed dependencies so that those behind a firewall 
can get the log4j CVS at work.

Note: I haven't updated the site.  I can't remember what that entails.  Can 
one of you other committers do that?

One other thing.  Has anyone else noticed that when you run "ant chainsaw" 
on the Log4j build that the attempt by Ant to delete the log4j and chainsaw 
jar files fails if they exist already?  I can't figure out why this would 
be.  I can delete them just fine on my own.  Nothing seems to have a handle 
to them.  I'm using Ant-1.6.1 and on both WinXP and Win2k.  Can anyone 
confirm this?


Jake


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


Re: update to install-chainsaw.xml + question

Posted by Jacob Kjome <ho...@visi.com>.
At 08:37 AM 3/1/2004 +1100, you wrote:
> > One other thing.  Has anyone else noticed that when you run "ant chainsaw"
> > on the Log4j build that the attempt by Ant to delete the log4j and 
> chainsaw
> > jar files fails if they exist already?  I can't figure out why this would
> > be.  I can delete them just fine on my own.  Nothing seems to have a 
> handle
> > to them.  I'm using Ant-1.6.1 and on both WinXP and Win2k.  Can anyone
> > confirm this?
>
>I have seen Ant do this from time to time, and it's not limited to the
>log4j module, it's happened to our project here at work.  I think it
>only happens on W32 AFAIK.  Usually it works the second time around.  It
>is strange.

Happens every time for me.  Does it work the second time for you, or are 
you running Linux so you can't test it?  I've never had this happen in one 
of my own builds.  Hmm... interesting.  Just tried it with Ant-1.5.3-1 and 
it works fine.  Looks like a bug in both Ant-1.6.0 and 1.6.1.  And what do 
you know, I searched bugzilla and found a bug report that matches this 
behavior...
http://issues.apache.org/bugzilla/show_bug.cgi?id=26108

Hopefully that can be fixed for Ant-1.6.2


Jake 


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


Re: update to install-chainsaw.xml + question

Posted by Paul Smith <pa...@lawlex.com.au>.
On Wed, 2004-02-25 at 16:51, Jacob Kjome wrote:
> Wanted to let people know that I updated the install-chainsaw.xml to use 
> the logging-log4j CVS module rather than jakarta-log4j, have it use the 
> up-to-date 2.0.8 Jakarta-oro package, and added a commented out stub of 
> <cvsgrab> listing all needed dependencies so that those behind a firewall 
> can get the log4j CVS at work.
> 

Thanks Jake, sorry this took me so long.  We've been struggling with a
version of Postgres that is allowing duplicate rows into a table even
with a primary key on it!

I have updated the website with your changes.

> Note: I haven't updated the site.  I can't remember what that entails.  Can 
> one of you other committers do that?
> 

At the moment it's a manual process of simply scp'ing the files to the
web server.

> One other thing.  Has anyone else noticed that when you run "ant chainsaw" 
> on the Log4j build that the attempt by Ant to delete the log4j and chainsaw 
> jar files fails if they exist already?  I can't figure out why this would 
> be.  I can delete them just fine on my own.  Nothing seems to have a handle 
> to them.  I'm using Ant-1.6.1 and on both WinXP and Win2k.  Can anyone 
> confirm this?

I have seen Ant do this from time to time, and it's not limited to the
log4j module, it's happened to our project here at work.  I think it
only happens on W32 AFAIK.  Usually it works the second time around.  It
is strange.

cheers,

Paul Smith


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