I currently have a project where I have a couple of jar files sitting in lib/ . I naively used an ANT build file to copy (obviously with fileset..todir blah) across the binary jar files to some other deploy directory. This resulted in corrupted jars.
I am sure taht other people came across the same issue and was wondering how did you get pass this? Is there some common practice.?
Your input is greatly appreciated.
Thanks
This message was edited 1 time. Last update was at by Bear Bibeault
I did read the copy specifications. I was hoping to get an idea of how do others people move binaries around in Ant in their projects. I am planning to break my copy task into two one with filter and the other without. That is the only way I can think of (not very clean in my view).
I did read the copy specifications. I was hoping to get an idea of how do others people move binaries around in Ant in their projects. I am planning to break my copy task into two one with filter and the other without. That is the only way I can think of (not very clean in my view).
I ran into the same problem long ago, but mixing binary and text files (if you can avoid it) is itself not a very clean approach. You're better off keeping 2 directories, one for the text (filtered) items, and one for the binary files, and doing 2 copies.
Yes, it makes the build.xml file (and directory structure) slightly more complex, but it makes the overall project structure more straighforward.
One thing that using J2EE frameworks has taught me is that less files doesn't necessarily make a project simpler to work with. Otherwise I'd still be cramming everything into logic on JSPs.
A lot the of modern-day software development platforms are designed to permit parcelling out work to those with the best aptitude for it. A lot of modern-day business is predicated on making one person do all the work, regardless of aptitude.
0
