These days, the IDE tends to do the ongoing work. For my current project (about 25 developers in our location, about 75 total with other locations), individual developers do not run Maven. A couple will, but for working on docs published with Maven, such as FAQ and other pages, before checking them in.
-----Original Message----- From: tlecavel.ml [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 23, 2005 10:14 AM To: users Subject: Maven for enterprise projects Hello, I'm collecting some informations about Maven 1.1 and its usage for large project, involving a teen workers team. I see the advantages of Maven for building and releasing versions of the project, but I don't see anywhere if each developer must have a local copy of Maven running on his workstation to work, and when (and how) they must commit their work to the "main" repository. Could you give me some hints? Do you know a good document about usage of Maven in a team work? Thanks by advance. -- Tom Accédez au courrier électronique de La Poste : www.laposte.net ; 3615 LAPOSTENET (0,34€/mn) ; tél : 08 92 68 13 50 (0,34€/mn) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
