On 11/30/06, Chris Hilton <[EMAIL PROTECTED]> wrote:
Believe me, I'm in no danger of wanting to ditch Maven, but I've got a team of 30 or so developers to keep happy and they need to believe it's worth it. We have a large number of projects and Maven's big selling point has been that by using Maven's dependency resolution, we've been able to reduce the number of projects that a developer has to keep checked out in order to build a product, resulting in faster build times. Part of having that project not checked out means that Eclipse needs to have a way to resolve dependencies on those missing projects, which m2eclipse gloriously provides. But because of MNGECLIPSE-59, inter-project dependencies when a developer DOES have the projects checked out are broken; you end up referring to the artifact in your local repository and not to the locally checked-out project.
I use eclipse and the snapshot build of mvn eclipse:eclipse. So I need to touch a command line, very occasionally. Most builds are done inside Eclipse, and a mvn clean install should be run prior to developer checkin. And if they don't then the Continuum build will check for most things. Continuum 1.1 will fix my frustration about dependent projects not getting re-built but what is working is working to my satisfaction. Admittedly I only have 6 developers, but this will grow. --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
