But those for for demo only to show off the holygrail maven commands :-) Use a CI server to do you checkout and cut your release.
On Sat, Apr 3, 2010 at 12:10 AM, Dan Tran <[email protected]> wrote: > mvn scm:bootstrap -DconnectionUrl="maven-scm-url-to-your-soruce" > -Dgoals="-B release:prepare release:perform" > > will checkout your project, tag it, build from the tag, and finally > deploy your artifact to your maven repo. > > (please look up for the precise syntax) > > mvn scm:bootstrap -DconnectionUrl="maven-scm-url-to-your-soruce" > -Dgoals="install" > > will check out your project and built it > > > > On Fri, Apr 2, 2010 at 11:28 PM, Markku Saarela <[email protected]> wrote: >> Hi, >> >> You could use Maven SCM plugin for bootstrapping the project with minimal >> pom. >> >> http://maven.apache.org/scm/maven-scm-plugin/examples/bootstrapping-with-pom.html >> >> rgds, >> >> Markku >> >> On 3.4.2010 0:09, Steve Cohen wrote: >>> >>> Ok, your needs are probably more extreme than mine. I HAPPEN at present >>> to be the only developer actively engaged on this project so I can get >>> away with non-holy-grail stuff - which explains why I stayed so long >>> with the Eclipse setup, but I would still like to get to the >>> single-command-line total rebuild from scratch. >>> >>> I have less need for CI and as the only developer I can even get away >>> with a local repository (for now) but I would still like to move this >>> ball down the field so it would be easier to extend should things get >>> more complicated. >>> >>> Are you saying then, that managing of builds at this level must depend >>> on something outside of Maven? I'm not likely to find funding for >>> anything more sophisticated than that (I work for a budget-strapped >>> small team inside a large corporation that is off to the side), so I am >>> interested in a solution that depends on nothing beyond Maven itself. >>> We have and use Subversion, and that's about it. >>> >>> >>> >>> David Hoffer wrote: >>> >>>> >>>> That "holy grail" is the only way to use maven, imho. I don't know >>>> about a single documentation source but there is lots of info >>>> available on the web to achieve this. >>>> >>>> In short we use TeamCity for CI, Artifactory for corporate maven repo, >>>> SVN& Maven. >>>> >>>> -Dave >>>> >>>> >>>> On Fri, Apr 2, 2010 at 2:48 PM, Steve Cohen<[email protected]> >>>> wrote: >>>> >>>>> >>>>> 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] >>>>> >>>>> >>>>> >>>> >>>> --------------------------------------------------------------------- >>>> 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] >>> >>> >> >> --------------------------------------------------------------------- >> 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]
