Newbie to newbie here >From my understanding bootstrap does an initial checkout from SCM otherwise and update is issued.
The release perform actual creates a release of your application and version change in your SCM. although I am not positive about the version change piece but it does mark for release somehow Phill -----Original Message----- From: Steven Rowe [mailto:[EMAIL PROTECTED] Sent: April 9, 2007 1:18 PM To: Maven Users List Subject: release:perform vs. scm:bootstrap Hi, I'm in the process of converting my (small) organization's Maven 1.X infrastructure to Maven 2. As a Maven 2 newbie, I'm curious about the differences between release:perform and scm:bootstrap, and the reasons why both of these apparently very similar goals co-exist in Maven2. The latter seems to be more Maven-1.X-like, in that you specify a list of actions to perform (the bootstrap goals), as opposed to the former, which appears to be more Maven2-like (actions are declared via lifecycle bindings). Are these differences cosmetic only? Does anyone use either one or the other exclusively (and why)? Or sometimes one, sometimes the other (again, rationale?)? Steve --------------------------------------------------------------------- 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]
