On 11/29/05, Dominique Devienne <[EMAIL PROTECTED]> wrote: > > > > The two issues I faced when creating large multi-build files builds were: > 1) Easily refer to the files to import arbitrarily deep in the file > hierarchy. > 2) Easily use "resources" relative to the imported builds, > for further <import> or <property file> or such. > > I used an env. var. for (1), and the <dirname> on the property set by > import for (2). --DD
I've encountered the same issues, as well as: 3) Sharing Build Files Between Projects - My solution was to have shared cvs module between the multiple projects just for build files, which works fine for internal purposes, but not for public purposes. The url import with caching allows project files to be easily shared and distributed between projects. Build files can easily published to websites. No more need to copy around examples. Without too much effort, maven could be rewritten as a simple build file that conforms to the maven standard. In theory, you could just import " http://maven.apache.org/buildfiles/maven-build.xml"; into your build file to get a build that works just like maven. I'm not advocating this, but just providing it as an example. I don't care for maven, and believe that if ant just supported url imports then I could finally stop wasting my time trying to work with it. Ivy provides the sophisticated dependency management that I need, and URL imports provide an elegant solution for build standardization and sharing across projects.. Mike
