Issue with SCM checkout, prepare-release and perform-release

[Juan Alvarado <ja...@uaig.net>]

Hello:

 

We are trying to use the scm plugin to check out and build our project
right out of CVS. 

 

The following are the steps in our sequence of events

maven scm:checkout-project -Dmaven.scm.cvs.tag=HEAD

 

The above checks out the project from CVS into the ${basedir}/checkout
directory as indicated below in our properties settings.

 

Next steps in the sequence are these:

maven scm:prepare-release  -Dmaven.scm.cvs.tag=$buildVersion

maven scm:perform-release  -Dmaven.scm.cvs.tag=$buildVersion

 

We run the above command from a shell script so just assume that
$buildVersion is a valid tag.

 

The problem we are having is that maven is not using the files in the
${basedir}/checkout directory in the above two commands. Maven is using
a completely different set of files to run scm:prepare-release and
scm:perform-release. Obviously this is not going to work. Is this a bug
or are we missing something here. I have included our scm properties
below.

 

Any help is greatly appreciated in this matter since it is holding us
back for the time being.

 

Thanks in advance!!!

 

maven.scm.cvs.module=FPI

maven.scm.cvs.root=${pom.repository.cvsRoot}

maven.scm.bootstrap.goals=multiproject:deploy,multiproject:site

maven.scm.project.dir=${basedir}/checkout/FPI/JavaSource/fpi-website

maven.scm.checkout.dir=${basedir}/checkout

This email is confidential and it is intended solely for the use of the individual or entity to which it is addressed.  If you are not the named addressee, you should not disseminate, distribute or copy this email.  If you have received this email in error, please notify the sender by a Reply.

If this email is addressed to or sent by an attorney, this email is either an attorney-client privileged communication or a work-product privileged communication, or both.  The United Automobile Insurance Company as well as the sender and intended recipient of this email expressly reserve any and all rights to assert the aforesaid privileges, and do not waive any such rights thereto by virtue of an erroneous email transmission.  This statement shall not hereafter be construed as limiting the assertion of any additional and further legal rights that the parties may have to limit or prohibit any further dissemination, distribution, copying or use of this email.