On Fri, October 26, 2007 4:47 pm, Guillaume Lederrey wrote: > That's our main problem ! > > For organizational / political reasons, the "bottom" of our > dependency tree will not migrate anytime soon ... that's why we need > some way to depend on projects NOT in the maven repository ...
In that case, you will need to deploy these "bottom" packages into your maven repository, and set up the poms for them by hand. Basically, for maven to work, it needs dependencies in a maven repo. Maven doesn't care how those dependencies got created (old build system, new build system, doesn't matter), only that the dependencies are where maven expects to find them in the correct directory structure on the maven repo. > I know, we're going to have a lot of fun ! Keep things small and simple, and do things one step at a time. We finished the migration of a project that combined EJB elements with Eclipse RCP, and beginning to end the full migration process took a full year. The rewards are worth it though: We need to release code at short notice, and this process is now a non event for us, typically completed within 30 minutes. Regards, Graham -- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
