Well, copy works great - it only copies files that changed. But in IF the files changed, I need to go to the place where all the java files are and delete ALL the java files. Because I really don't know what files will be generated, and as long as I don't copy new idl files it is okay to leave them, but as soon as a new idl is copied over (or a changed one) ... that is where I need to re-generate all the java again.
On Tue, Aug 12, 2008 at 6:27 PM, EJ Ciramella <[EMAIL PROTECTED]> wrote: > Maybe I'm still not understanding, but doesn't copy only copy over bits > that have changed? > > So you're copying the idl files to <somedirectory> and then from that > generating various java files? If the copy doesn't do anything, then > again, you'll have to test for the uptodate status of the idl files and > then and only then generate new java files. > > Did I miss again? > > -----Original Message----- > From: Evgeny [mailto:[EMAIL PROTECTED] > Sent: Tuesday, August 12, 2008 3:58 AM > To: user@ant.apache.org > Subject: Re: Uptodate working one way only > > No one replied, perhaps I did not make myself clear. > > I have a problem where I have a list of files scattered all over the > place .. the list is in a file. > Then I have no problems copying files with <mapper type="flatten"/> > and get a nice directory > with all those files copied into it. > > But there is an <exec> task that I run on these files, that generates > .java from .idl and the problem > is that each idl is generated into multiple java files. > > So when an idl file is copied with a new version, or a new idl file is > copied -- I need to clean the > generated files and generate everything fresh again. A process that > takes several minutes, and > I don't want to do this if no idl files were changed. > > So I thought using the <uptodate> task is most appropriate ... but > here is the catch, it works > the wrong way. I have a <fileset> from that list-in-a-file, and I have > a directory with all those > files copied -- and <uptodate> does not provide a solution comparing > one to another in a way > that I will know when a <copy> is going to be made. And <copy> does > not provide something > like the "property" attribute that <uptodate> has, though it works in > exactly the way I need. > > > Other than writing custom tasks for Ant that will give me the > usability of <uptodate> with the > functionality of <copy>, is there any other way that I am missing? > > > Regards, > Evgeny > > > On Wed, Aug 6, 2008 at 5:20 PM, Evgeny <[EMAIL PROTECTED]> wrote: >> Hi Ant users, >> >> I wish there was a way to use the uptodate task in the other >> direction, not check source against target but check target against >> source. Since my list of files in source comes from a list in a text >> file, and it's easy to use a mapping to map them to the place where >> they are copied to (aggregated). But I want to have a way to use >> antcall or something similar if there is anything needs to be copied, >> and it's almost impossible with the current uptodate task. >> >> Regards, >> Evgeny >> > > --------------------------------------------------------------------- > 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]
