Over the past few months I have slowly and, on the whole successfully, migrated a project that was based on Eclipse to one that is based on maven (and m2eclipse), in the process, learning much about Maven and I'm generally quite happy with it. It's a nice improvement.
The one step I haven't taken yet is generating a fully automated build starting with pristine sources, checking everything it needs out from Source Control and then building it. That has always seemed to me to be the "holy grail" of automated building, going back to the make days. You "nuke" all the source, get a fresh copy from the source control (tied to a given tag) and build from scratch. We don't want anything from a developer's working copy involved in any way. I haven't done this with Maven yet and to be fair, I also hadn't done it with the earlier Eclipse-based system in use here but I still want to do it. And yes, I understand that there is a bit of a chicken-egg problem here - where is this definition of "everything" to be version controlled and how do you avoid nuking that? So there has to be something of a two-tier setup. I know this and accept it. I hadn't spent much time looking at the Maven SCM plugin, but now that I have, I don't really see what I'm looking for there. The examples tend to be very sparse, and "Maven - The Definitive Guide" doesn't even touch the SCM plugin. Can someone point me at documentation directed toward achieving this "holy grail" with Maven? Thanks. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
