> On Jan 10, 2008 10:34 AM, Xavier Hanin <[EMAIL PROTECTED]> wrote: > > On Jan 10, 2008 5:13 PM, Dominique Devienne <[EMAIL PROTECTED]> wrote: > > it so that my involvement with Ant took a back step, and I'm mostly > > watching from afar what's going on in Ant. I've never used Ivy for > > example. I'd probably have replaced my dependency stuff with Ivy by > > now, although my stuff was C++ aware and was pulling not just jars > > with also C++ headers and libraries, packaged sources of dependent > > modules for debugging, etc... > > BTW Ivy is language agnostic, so you can use it for non java dependency > management. But this is out of topic.
Can I abuse of your time to explore this a little more Xavier? Being language agnostic doesn't necessarily translate in being usable to deal with natively compiled and linked dependencies. The ad-hoc system I built wasn't agnostic. When a dependency had native code associated to it (the JNI glue code and supporting native libs it depended upon) as described in the published artifact descriptor, the system knew to look for foo-module-win32.zip in addition to foo-module.zip, if you were building on win32, and each platform was getting its own specific binaries. Then once the dependency was expanded, in addition to automatically adding the dependent JARs on the classpath, it also appended to the compilation include path, link library path, and runtime PATH and java.library.path, and all transitive dependencies of the current project. The common build could then reference all these paths by well know ids, with no further configuration. The system depended on a fixed and well know hierarchy for the artifact zips. Given the agnostic nature of Ivy, how would one go about replicating the kind of system I describing above on top of existing Ivy? Note that I'm pretty ignore of Ivy, and haven't taken the time to explore the doc before asking this question, so feel free to brush me off to find the answers myself ;-) But since I have your attention, I thought I'd try to get advice from the Ivy man directly ;-) Thanks, --DD --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
