ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lopez, William" <>
Subject RE: Jar error
Date Thu, 22 May 2003 13:06:00 GMT

Thanks for the advice. The reason I wanted to do that was due to the need to
have new classes available for the other subsequent compiles. So what I did
was have a temporary jar file with all the class files that could be needed
during compilation for these projects. As new/updated classes were compiled
I wanted to have them available [in the jar] for the other compilations. I
tried to accomplish this by breaking out each project, which contain
multiple packages (needed the temp jars because of these dependencies).
There are circular references in our application (in the process of removing
them...very painful)...the reason for the mad setup :-).


-----Original Message-----
From: Stefan Bodewig [] 
Sent: Wednesday, May 21, 2003 1:50 AM
Subject: Re: Jar error

On Mon, 19 May 2003, William Lopez <> wrote:

> ...I'm guessing that the previous task (compile) still has a "hold" of 
> the jar file (it is used in the classpath element of the compile 
> task).

Tip one would be "don't do that" - i.e. modify the jar you used before.  Tip
two would be to "fork" the compile task.


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message