> From: Stefan Bodewig [mailto:[EMAIL PROTECTED] > In the end the major difference is a philosophical one. What is the > central piece of the task, the repository or downloading of files. > > I guess I'm more on the side of the declarative approach dependencies > takes, but I do want those additional bells and whistles like MD5 > checksum validations and timestamp checks if needed.
I feel similarly. I prefer the declarative approach of <dependencies>, but would like timestamp checking for latest-like dependencies that get overwritten (which does need a pseudo-atomic copy-to-tmp+move scheme). Additionally, if the notion of what is a dependency could be abstracted a bit, it would be great. I'm not sure it's reasonable to ask for this now, but I'm throwing that it now so whatever design decision is made does not preclude it in the future. What I have in mind are zip dependencies containing jar+native-libs+descriptors+etc... We're in a mixed Java-C/C++ environment, and some dependencies are in fact C++ libraries which export their public headers, import libs, and runtime .dll/.so as a zip. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
