What version of release-plugin do yo use? try to remove release.properties in your root dir and run mvn release:prepare -DdryDrun -X
-D On 6/12/06, Dhananjay Nene <[EMAIL PROTECTED]> wrote:
release:prepare is attempting an update. My assumption is that the same is for ensuring that the source has not changed and thus it will need need to know exactly where the source has been checked out earlier. Not sure if I have made a mistake in understanding the process. The log output is as follows. My assumption is that there would require to be a parameter I could pass to release:prepare which would be appended to the update command in the log below. Have I misunderstood the process ? [INFO] [release:prepare] [INFO] Resuming release from phase 'scm-check-modifications' [INFO] Verifying that there are no local modifications... [DEBUG] cvsRoot: [.. correct cvs root ..] [DEBUG] passFile: [.. correct cvs password file ..] [DEBUG] cvsroot [.. correct cvs root..] already exist in [.. correct cvs password file ..] SKIPPED. [INFO] Executing: cvs -z3 -f -d [.. correct cvs root ..] -n -q update -d [INFO] Working directory: [.. correct base directory ie. the one which contains pom.xml ..] [INFO] ------------------------------------------------------------------------ [ERROR] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Unable to check for local modifications Provider message: The cvs command failed. Command output: cvs update: in directory .: cvs [update aborted]: there is no version here; run 'cvs checkout' first [INFO] ------------------------------------------------------------------------ [DEBUG] Trace org.apache.maven.BuildFailureException: Unable to check for local modifications Provider message: The cvs command failed. Command output: cvs update: in directory .: cvs [update aborted]: there is no version here; run 'cvs checkout' first dan tran wrote: > release-plugin does not use maven-scm-plugin, it, however, talks > directory > to maven-scm-api layer. > So your maven-scm-plugin settings are ignored. Also, the release:prepare > does not do any checkout. > release:perform does. You can change the checkout directory thru > release:perform's workingDirectory > > http://maven.apache.org/plugins/maven-release-plugin/perform-mojo.html > > -D > > On 6/12/06, Dhananjay Nene <[EMAIL PROTECTED]> wrote: >> >> My pom.xml has been configured to checkout the project >> ${basedir}/target/checkout/source (I have configured the >> <checkoutDirectory> for <maven-scm-plugin>). However release:prepare >> continuously fails since the cvs update command does not contain the >> directory where the project is checked out. The log shows the following >> command being executed : >> >> cvs -z3 -f -d <cvs_root> -n -q update -d >> >> The command fails since there is no parameter after the "-d" above to >> indicate the directory (it needs to be the same as the source directory >> which is used by scm:checkout). I tried passing command line parameters >> (-D) and by using prepareVerifyArgs. However I am unable to pass the >> directory name. >> >> How do I pass the parameter to indicate the directory where the code is >> checked out to maven-release-plugin ? >> >> Dhananjay >> >> >> >> --------------------------------------------------------------------- >> 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]
