I'm developing a tool that among other things, allows for the user to pick a CVS version and build it with maven (this is part of the process anyways). While I have not got as far as you seem to be yet, I do not know of any automated way to do this.
Could you elaborate on how you use the maven release plugin? Does it generate a pom file by itself? I have successfully mavenized the file system, so that dependencies reside inside of the resources folder and the code is in its right place, however I haven't yet figured out how to go about generating a pom file to feed maven with all the correct dependencies in it, keeping in mind inter-dependence and whatnot (such that things aren't listed multiple times..) On Wed, Jun 18, 2008 at 10:38, Jeudy, Guillaume <[EMAIL PROTECTED]> wrote: > Hi maven savvy developers, > > Is there an automated way to trigger a maven build from a cvs tagged > version ? > > Basically I want to check out the source code for a given tag and trigger > the maven build. > > So far I need to do these steps separately (checkout with cvs then build > with maven). > > I use the maven release plugin to create a new CVS tag and handle the build > and everything. > > The trick is I have to rebuild with a different profile for every > environment we have. This rebuild operation is done locally on the box where > its going to be deployed using an environment properties file injected on > the command-line. This rebuild needs to sync for a given tag in CVS > automatically. > > It would be great to know how others have tackled this. > > Thanks, > -Guillaume > > > > ____________________________________________________________________________________________________ > This electronic mail (including any attachments) may contain information > that is privileged, confidential, and/or otherwise protected from disclosure > to anyone other than its intended recipient(s). Any dissemination or use of > this electronic email or its contents (including any attachments) by persons > other than the intended recipient(s) is strictly prohibited. If you have > received this message in error, please notify us immediately by reply email > so that we may correct our internal records. Please then delete the original > message (including any attachments) in its entirety. Thank you. >
