Xavier Hanin wrote:
On 3/15/07, Scott Goldstein <[EMAIL PROTECTED]> wrote:
...
Then if we see that users would be interested to share their Ivy files in a
central repository, we will talk with the repository team to see if they
are
ok to host Ivy files. But this require an important amount of work of
maintenance, and the Ivy community is not strong enough for the moment
IMHO.
Over at Apache Forrest we are moving to Ivy (very slowly at present). We
are discussing whether to use the Maven2 repos or whether to create a
local repo to Forrest with the intention of passing it over to the Ivy
project once we are satisfied all dependencies are correctly described
in ivy.xml files.
Since Forrest is based on Apache Cocoon there is a fairly large number
of modules we will be working with. However, it will be much easier for
us to just use the Maven ones.
So, I read this thread with interest and look forward to understanding
the best way forward for the Forrest project (right now I change my mind
every time I think about it, the community is also undecided at this point).
Another point is that with Ivy you can quite easily have distributed
repositories, and I'm not sure that a central repository is the best. If
Ivy
gain momentum, I would prefer seeing each project using Ivy provide their
own Ivy repository with their modules, and an ivyconf.xml for this
repository with proper per module configuration of resolvers.
Can you point to the relevant doc for me to do background reading on this?
Ross
