On Fri, October 26, 2007 2:20 pm, Guillaume Lederrey wrote: > I'm working in a large organization, thinking of moving to maven. We > have lots of projects, having lots of dependencies between them. For > the moment, those projects are deployed in a central, proprietary > repository. We have ant scripts taking care of downloading the jars > needed by a project. > > We need to be able to transition to maven one project after another > (we cant just stop working for one month ;-). So we need to be able to > still refer to our "old" proprietary repository if we move a project > to maven but not all its dependencies are managed by maven.
It is a pretty standard problem to have to support a "bridged" solution while you move from one system to another. We had to move off of a hacked together local repository hosted on a windows share, to a proper maven repo hosted on a webserver. Initially we started with an empty maven repo, and then manually imported all the jars that were needed for each project from the existing proprietry repo as we needed them. What we did find is that the vast majority of jars being hosted in the old repo were jars that were already available in the maven repos at http://repo1.maven.org. In these cases, no import was done at all - we just configured the pom files to use the correct versions of these external jars, and let maven handle the downloads automatically. There were a few jars left over that were no publically availalbe, and so those jars were uploaded to our project-private in house repository. At all times both the old ant based way, and the new maven way, worked for those projects that had been converted. This way we eased off the old, and eventually switched it off. Regards, Graham -- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
