On 16 June 2006 at 11:07, Tim Ellison <[EMAIL PROTECTED]> wrote: > I just sent a note with a subset of these same concerns! > > That's quite the laundry list ... > > Mark Hindess wrote: > > > > 6) Mikhail (IIRC?) modified a few of the module build files to use > > macros. I like this idea (in fact one of my earlier abandoned JIRAs > > took it quite a bit further) because it helps to hide the less > > important details of what is going on away from the important ones - > > in the case of the modules leaving only differences between modules. > > As long as I can understand what is happening with a quick glance -- > let's not get 'clever' ;-)
Nothing much 'cleverer' than the macros Mikhail has already started using. It'll take a while to get there but I was thinking of bringing the macros out to the shared/imported ant file(s). See modules/crypto/make/common/build.xml for example. > > 8) Running "ant -f make/build.xml" from a module sub-directory doesn't > > actually clean the main compiled classes. (I think this is pretty > > important to getting consistent expected behaviour so I'm looking at > > this right now and will fix it shortly unless anyone shouts.) > > > > Well, these are some of the things that are bothering me. I suspect > > others have other issues? > > Related to the build or in general :-p ? "In general" would be a much, much longer list. ;-) > I'd like to be able to download dependencies from the top-level script > too, so > > svn co ... > cd ... > ant get-depends (or whatever) > ant (builds everything) > ant test > > and you are done. Yes, definitely. This was intended to be covered by the ant API in issue 1. Regards, Mark. --------------------------------------------------------------------- Terms of use : http://incubator.apache.org/harmony/mailing.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
