i have java files in many packages. Such as com\pack1\pack2\pack3\ (java files here) com\pack1\pack2\ (java files here) com\pack1\ (java files here) ..... com\a\b\c\(java files here) com\a\b\(java files here) ..
I have to give an option to the end user to compile the source files(if she ever wants to do so). So I asked this ques in EE that how can i do this without using many javac statments and putting them in a batch file. i was suggested that i should use ant. Now I have managed to compile the source files using ant and copy other files(such as xml, xsl, jar etc) to the target directory. I do this by first navigating to the ant folder(which has build.xml file) and writing ant there. It compiles all those java files and puts them in build directory along with other needed files. What i want to know is how can i make the end user use this. Do i have to tell her to install ant, copy build.xml file there and the source dir and navigate to it and write ant or is there a better way of doing this?
Originally posted by Thomas Greene: What i want to know is how can i make the end user use this. Do i have to tell her to install ant, copy build.xml file there and the source dir and navigate to it and write ant or is there a better way of doing this?
If your user is not capable enough to use Ant, why is she interested in compiling your source code?
Anyway, if that's really what you want to do (let the user build your project without having to install Ant), you can always distribute Ant along with your application.