On Tue, Jun 29, 2010 at 3:02 AM, sk07 <[email protected]> wrote:
> say i build a war file from a trunk for a project n name it as Project > 1-snapshot version 1. n the project go live. when there is enhancement, > developer make necessary changes n update the svn repo. now, for next > release i can trigger to build the file again. how to keep existing war file > build via continuum and new war file which will get build by triggering the > build button in continuum? is the a way where i can make a new project name, > example Project 1 - snapshot 2 in continuum? getting same project with > different version (diff war file)? or the only way is i manually moved the > existing war file to a folder, only then trigger build via continuum? It sounds like you are not yet deploying your artifacts to a remote repository. That's where you normally store releases when using Maven. Take a look at Apache Archiva for a repository manager (but you can start with a simple filesystem.) At a minimum, set <distributionManagement> in your project pom and change the build definition to "clean deploy". There is also a release process built into Maven and Continuum that will tag your svn repository and change the version numbers for you. Is the requirement really to put the old releases under version control (in svn) or just to keep them around? -- Wendy
