> > > On Wed, Jun 13, 2012 at 1:26 PM, Frank Zhang > > > <frank.zh...@citrix.com> > > > wrote: > > > > I still have some concerns about using ant. > > > > As we are removing those apache incompatible jars from source > > > > code, > > > there build process would break as those jars are compilation > > dependencies. > > > > Speaking for Ant(not maven), how other projects handle this? Do we > > need > > > to put those jar to somewhere and pull it before compiling? Then we > > are > > > doing what maven did. > > > > Jnetcap is one of them. BuildRequires is not enough, it won't work for > > developers who only uses ant > > Write a "ant get-dependency" which grab those apache incompatible jars > from somewhere else(we can host these jar files).
That what I said, we are doing what maven already did > > > > > > > > > Whats the specific dependency concerns wrt compilation (that > > > probably needs to be a new thread)? We can use BuildRequires for any > > dependency > > > (or the debian equivalent) > > > > > > Speaking as a packager, I really dislike Maven's method of handling > > > dependencies, and desperately hope we avoid that. > > > > > > --David