ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From erwin.de....@belgacom.be
Subject RE: copying files
Date Tue, 03 Jun 2003 13:28:34 GMT
Bertjan,

As long as there are no circular dependencies between your different
sources, you can use different javac tasks and thus define the desired
target/build directories.
If you have circular dependencies (as in your previous mails about the
multiple src locations), they will be much easier to handle in an ant script
when you put them together in 1 src tree.

Remark that you can still use the package names of your classes to put them
in different sub-folders of your common src tree, and the build results will
also have the same package/directory structure.

I think the mechanism with filelists etc is much too complex.

E.g. put gui1.java and gui2.java in the package "gui", base1 and base2 in
"base" etc. The end result is that you can use a common srcdir "src", and a
common destdir "build" and in side the build dir you will find all desired
sub-folders.

Cheers

Erwin

-----Original Message-----
From: Bertjan Broeksema [mailto:b.broeksema@home.nl]
Sent: 03 June 2003 15:21
To: Ant Users List
Subject: Re: copying files


Correction: the files in the tmp dir must be *.class files. And now they are

in the tmp dir, but i want the gui*.class files in the build/gui dir and the

same for the base*.class files.

> - src
>
>    |_ gui
>    |
>    |	|_ gui1.java
>    |	|_ fgui2.java
>    |	|_ filelist.txt
>    |
>    |_base
>    |
>    |	|_base1.java
>    |	|_base2.java
>    |	|_ filelist.txt
>
> - build
>
>    |_gui
>    |_base
>    |_tmp
>    |
>    |	|_ gui1.class
>    |	|_ fgui2.class
>    |	|_base1.class
>    |	|_base2.class


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

**** DISCLAIMER **** 
"This e-mail and any attachments thereto may contain information 
which is confidential and/or protected by intellectual property 
rights and are intended for the sole use of the recipient(s) named above. 
Any use of the information contained herein (including, but not limited to, 
total or partial reproduction, communication or distribution in any form) 
by persons other than the designated recipient(s) is prohibited. 
If you have received this e-mail in error, please notify the sender either 
by telephone or by e-mail and delete the material from any computer. 
Thank you for your cooperation."


Mime
View raw message