Hey Stephen,
I was actually doing that, but it wasn't working. After much
playing around with the code, I discovered that there was in fact
classes being created in triplicate! And in differend packages/directory
structures to boot. In the end I just used the excludes attribute in the
javac task to exclude the offending classes in the generated code from
being compiled. So a simple solution to a problem I had made WAY too
complicated for myself. One of those days you end up going "Now why
didn't I think of that until now?"....
-----Original Message-----
From: Stephen McConnell [mailto:[EMAIL PROTECTED]
Sent: 09 August 2006 19:04
To: 'Ant Users List'
Subject: RE: Code synchronisation problem
> -----Original Message-----
> From: David Corley (AT/LMI) [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, 9 August 2006 6:42 PM
> To: Ant Users List
> Subject: Code synchronisation problem
>
> Hey,
> I have some "hand-written" classes and some idl-generated source
in
> two seperated directories. Some of the source in both of the
> directories has the same file/class name, and as I need to compile
> them together, I get "duplicate class" errors. What I would like to do
> is compare the "hand-written" source directory to the generated source
> directory, and where there are common files/names remove those files
> from only the generated source directory. I guess it's similar to the
> Ant <sync> task, but that task seems to work the other way around,
> i.e., the files in the target directory that DON'T match get removed.
Why not copy the generated sources to a new directory, then copy the
hand-written classes to the same directory using the overwrite option
then compile the consolidated collection?
/Steve.
---------------------------------------------------------------------
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]
