I have the feeling that Ivy [1] can help us regarding our dependencies. The advantages include:
- central repository (eventually, see below) - dependencies need not be in SVN (eventually, see below) - transitive dependency management (i.e. we say we need X, if X depends on Y it will come automatically) - conflict management between dependencies (easier upgrading of dependencies) - much easier integration testing. We can have different build configurations for release, development and test, release using fully tested jars, development using latest releases and/or milestones - easier continuous integration testing - full dependency reports (i.e. better developer docs) - modules could be resolve via dependencies and could have dependencies on its own. The disadvantage is that, as far as I am aware, no developers here other than myself know ivy (and I'm still learning). However, Ivy docs are great [2] Here is a possible plan: 1 - Create a lenya only repo in SVN (Forrest has started something that we can reuse). although wherever possible we will use the IVY repo and the Maven2 repo 2 - We modify our build files to use IVY (Forrest has some set of generic build files that are intended to be extended by project specific build files.) 3 - We make sure it works 4 - We move the entries in our repo to the IVY repo (We need to enter into a dialogue with IVY devs to see what is happening with regards an official Apache repo) The end result will be a build system that uses three repos: The lenya/forrest one for any jars we have customised but are not yet available in the main project releases (i.e. we have something in the patch queue) The official IVY repo (whatever that turns out to be) The official ASF Maven repo wdyt? salu2 [1] http://incubator.apache.org/ivy/ [2] http://incubator.apache.org/ivy/doc.html -- Thorsten Scherler thorsten.at.apache.org Open Source Java consulting, training and solutions --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
