My pom.xml has been configured to checkout the project
${basedir}/target/checkout/source (I have configured the
<checkoutDirectoryfor <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: users-unsubscribe (AT) maven (DOT) apache.org
For additional commands, e-mail: users-help (AT) maven (DOT) apache.org

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

-D

6/12/06, Dhananjay Nene <dhananjay.nene (AT) cash-tech (DOT) comwrote:

My pom.xml has been configured to checkout the project
${basedir}/target/checkout/source (I have configured the
<checkoutDirectoryfor <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: users-unsubscribe (AT) maven (DOT) apache.org
For additional commands, e-mail: users-help (AT) maven (DOT) apache.org
--

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

6/12/06, Dhananjay Nene <dhananjay.nene (AT) cash-tech (DOT) comwrote:

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 ?

[INF] [release:prepare]
[INF] Resuming release from phase 'scm-check-modifications'
[INF] 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.
[INF] Executing: cvs -z3 -f -d [ correct cvs root ] -n -q update -d
[INF] Working directory: [ correct base directory ie. the one which
contains pom.xml ]
[INF]

[ERRR] BUILD FAILURE
[INF]

[INF] 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

[INF]

[DEBUG] Trace
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

-D

6/12/06, Dhananjay Nene <dhananjay.nene (AT) cash-tech (DOT) comwrote:
>>
>My pom.xml has been configured to checkout the project
>${basedir}/target/checkout/source (I have configured the
><checkoutDirectoryfor <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: users-unsubscribe (AT) maven (DOT) apache.org
>For additional commands, e-mail: users-help (AT) maven (DOT) apache.org
>>
>>
>
>
>

To unsubscribe, e-mail: users-unsubscribe (AT) maven (DOT) apache.org
For additional commands, e-mail: users-help (AT) maven (DOT) apache.org
--

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 ?

[INF] [release:prepare]
[INF] Resuming release from phase 'scm-check-modifications'
[INF] 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.
[INF] Executing: cvs -z3 -f -d [ correct cvs root ] -n -q update -d
[INF] Working directory: [ correct base directory ie. the one which
contains pom.xml ]
[INF]

[ERRR] BUILD FAILURE
[INF]

[INF] 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

[INF]

[DEBUG] Trace
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

-D

6/12/06, Dhananjay Nene <dhananjay.nene (AT) cash-tech (DOT) comwrote:
>>
>My pom.xml has been configured to checkout the project
>${basedir}/target/checkout/source (I have configured the
><checkoutDirectoryfor <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: users-unsubscribe (AT) maven (DOT) apache.org
>For additional commands, e-mail: users-help (AT) maven (DOT) apache.org
>>
>>
>

To unsubscribe, e-mail: users-unsubscribe (AT) maven (DOT) apache.org
For additional commands, e-mail: users-help (AT) maven (DOT) apache.org

I am using release plugin 2.0-beta-4. The output of the command (after
deleting release.properties) follows :

[DEBUG] Using defaults for missing PM

[DEBUG] (selected for compile)
[DEBUG]

(selected for runtime)
[DEBUG] Retrieving parent-PM:
for project:
from the repository.
[DEBUG] Retrieving parent-PM:
for project:
from the repository.
[DEBUG] Retrieving parent-PM:
for project:
from the repository.
[DEBUG] Retrieving parent-PM: for
project: from the repository.
[DEBUG] Retrieving parent-PM: org.apache:apache::1 for project:
from the repository.
[DEBUG]

(selected for runtime)
[DEBUG] Retrieving parent-PM: for
project: null:plexus-utils:jar:1.1 from the repository.
[DEBUG] (selected
for runtime)
[DEBUG] Retrieving parent-PM:
for project:
from the repository.
[DEBUG] Retrieving parent-PM: for
project: from the repository.
[DEBUG] Retrieving parent-PM: org.apache:apache::1 for project:
from the repository.
[DEBUG]
(selected for runtime)
[DEBUG] junit:junit:jar:3.8.1:runtime (selected for runtime)
[DEBUG] Retrieving parent-PM:
for project:
from the repository.
[DEBUG] Retrieving parent-PM:
for project:
from the repository.
[DEBUG] Retrieving parent-PM:
for project:
from the repository.
[DEBUG] Retrieving parent-PM: for
project: from the repository.
[DEBUG] Retrieving parent-PM: org.apache:apache::1 for project:
from the repository.
[DEBUG]

(selected for runtime)
[DEBUG] Retrieving parent-PM:
for project:
from the repository.
[DEBUG] Retrieving parent-PM:
for project:
from the repository.
[DEBUG] Retrieving parent-PM: for
project: from the repository.
[DEBUG] Retrieving parent-PM: org.apache:apache::1 for project:
from the repository.
[DEBUG]

(selected for runtime)
[DEBUG] regexp:regexp:jar:1.3:runtime (selected for runtime)
[DEBUG] Retrieving parent-PM:
for project:
from the repository.
[DEBUG] Retrieving parent-PM:
for project:
from the repository.
[DEBUG] Retrieving parent-PM: for
project: from the repository.
[DEBUG] Retrieving parent-PM: org.apache:apache::1 for project:
from the repository.
[DEBUG]

(selected for runtime)
[DEBUG]

(selected for runtime)
[DEBUG] (selected
for runtime)
[DEBUG] (selected for runtime)
[DEBUG] (removed - causes a cycle in
the graph)
[DEBUG] jdom:jdom:jar:1.0:runtime (selected for runtime)
[DEBUG] jdom:jdom:jar:1.0:runtime (selected for runtime)
[DEBUG] Retrieving parent-PM: org.apache.maven:maven::2.0 for project:
from the repository.
[DEBUG]
(selected for runtime)
[DEBUG] (removed
- nearer found: 1.1)
[DEBUG] Retrieving parent-PM: org.apache.maven:maven::2.0 for project:
from the repository.
[DEBUG] (selected
for runtime)
[DEBUG]
(removed - nearer found: 1.1)
[DEBUG] Retrieving parent-PM: org.apache.maven:maven::2.0 for project:
from the repository.
[DEBUG]
(selected for runtime)
[DEBUG]
(removed - nearer found: 1.1)
[DEBUG]

(selected for runtime)
[DEBUG]
(removed - nearer found: 1.1)
[DEBUG] Retrieving parent-PM:
for project:
from the repository.
[DEBUG] Retrieving parent-PM:
for project:
from the repository.
[DEBUG] Retrieving parent-PM: for
project: from the repository.
[DEBUG] Retrieving parent-PM: org.apache:apache::1 for project:
from the repository.
[DEBUG]

(selected for runtime)
[DEBUG]
(selected for runtime)
[DEBUG] junit:junit:jar:3.8.1:runtime (selected for runtime)
[DEBUG] Retrieving parent-PM: org.apache.maven:maven::2.0 for project:
null:maven-project:jar:2.0 from the repository.
[DEBUG] (selected for
runtime)
[DEBUG] (removed
- nearer found: 1.1)
[DEBUG]

(selected for runtime)
[DEBUG]
(removed - nearer found: 1.1)
[DEBUG] Retrieving parent-PM: org.apache.maven:maven::2.0 for project:
from the repository.
[DEBUG] (selected for
runtime)
[DEBUG]
(removed - nearer found: 1.1)
[DEBUG] Retrieving parent-PM: org.apache.maven:maven::2.0 for project:
null:maven-profile:jar:2.0 from the repository.
[DEBUG] (selected for
runtime)
[DEBUG]
(removed - nearer found: 1.1)
[DEBUG] Retrieving parent-PM:
for project:
from the repository.
[DEBUG] Retrieving parent-PM:
for project:
from the repository.
[DEBUG] Retrieving parent-PM: for
project: from the repository.
[DEBUG] Retrieving parent-PM: org.apache:apache::1 for project:
from the repository.
[DEBUG]

(selected for runtime)
[DEBUG] Retrieving parent-PM: for
project:
from the repository.
[DEBUG] Retrieving parent-PM: plexus:plexus-root::1.0.3 for project:
from the repository.
[DEBUG]

(removed - nearer found: 1.0-alpha-8)
[DEBUG] (selected for
runtime)
[DEBUG] (removed
- nearer found: 1.1)
[DEBUG] Retrieving parent-PM: org.apache.maven:maven::2.0 for project:
from the repository.
[DEBUG] (selected
for runtime)
[DEBUG] Retrieving parent-PM: org.apache.maven:maven::2.0 for project:
from the repository.
[DEBUG] (selected for runtime)
[DEBUG] (removed
- nearer found: 1.1)
[DEBUG] Retrieving parent-PM: org.apache.maven:maven::2.0 for project:
from the repository.
[DEBUG]

(selected for runtime)
[DEBUG]
(removed - nearer found: 1.1)
[DEBUG] Retrieving parent-PM: org.apache.maven:maven::2.0 for project:
from the repository.
[DEBUG]
(selected for runtime)
[DEBUG] Retrieving parent-PM: org.apache.maven:maven::2.0 for project:
from the repository.
[DEBUG] (selected for
runtime)
[DEBUG] Retrieving parent-PM: org.apache.maven:maven::2.0 for project:
null:maven-settings:jar:2.0 from the repository.
[DEBUG] (selected
for runtime)
[DEBUG]
(removed - nearer found: 1.1)
[DEBUG]

(selected for runtime)
[DEBUG]
(removed - nearer found: 1.1)
[DEBUG]
(selected for runtime)
[DEBUG]
(removed - nearer found: 1.1)
[DEBUG] Retrieving parent-PM: org.apache.maven:maven::2.0 for project:
from the repository.
[DEBUG]
(selected for runtime)
[DEBUG] (selected for runtime)
[DEBUG]
(selected for runtime)
[DEBUG] (selected for runtime)
[DEBUG]
(removed - nearer found: 1.1)
[DEBUG] Retrieving parent-PM:
for project:
from the repository.
[DEBUG] Retrieving parent-PM: org.apache.maven:maven::2.0 for project:
from the repository.
[DEBUG]
(selected
for runtime)
[DEBUG] (selected for
runtime)
[DEBUG] Retrieving parent-PM: org.apache.maven:maven::2.0 for project:
from the repository.
[DEBUG]
(selected for runtime)
[DEBUG]
(removed - nearer found: 1.1)
[DEBUG] Retrieving parent-PM:
for project:
from the repository.
[DEBUG] Retrieving parent-PM:
for project:
from the repository.
[DEBUG] Retrieving parent-PM:
for project:
from the repository.
[DEBUG] Retrieving parent-PM: for
project: from the repository.
[DEBUG] Retrieving parent-PM: org.apache:apache::1 for project:
from the repository.
[DEBUG]

(selected for runtime)
[DEBUG] Retrieving parent-PM:
for project:
from the repository.
[DEBUG] Retrieving parent-PM:
for project:
from the repository.
[DEBUG] Retrieving parent-PM:
for project:
from the repository.
[DEBUG] Retrieving parent-PM: for
project: from the repository.
[DEBUG] Retrieving parent-PM: org.apache:apache::1 for project:
from the repository.
[DEBUG]

(selected for runtime)
[DEBUG] Retrieving parent-PM:
for project:
from the repository.
[DEBUG] Retrieving parent-PM:
for project:
from the repository.
[DEBUG] Retrieving parent-PM: for
project: from the repository.
[DEBUG] Retrieving parent-PM: org.apache:apache::1 for project:
from the repository.
[DEBUG]

(selected for runtime)
[DEBUG] Configuring mojo
''
[DEBUG] (f) addSchema = true
[DEBUG] (f) basedir = /
[DEBUG] (f) dryRun = true
[DEBUG] (f) generateReleasePoms = false
[DEBUG] (f) preparationGoals = clean integration-test
[DEBUG] (f) project = @33705635
[DEBUG] (f) reactorProjects =
[@33705635]
[DEBUG] (f) resume = true
[DEBUG] (f) settings = @8c436b
[DEBUG] (f) useEditMode = false
[DEBUG] -- end configuration --
[INF] [release:prepare]
[DEBUG] release.properties not found - using empty properties
[INF] Verifying that there are no local modifications
[DEBUG] cvsRoot:
:pserver:danny@
[DEBUG] passFile: /home/dhananjay/.cvspass
[DEBUG] cvsroot
:pserver:danny@
already exist in /home/dhananjay/.cvspass. SKIPPED.
[INF] Executing: cvs -z3 -f -d
:pserver:danny@ -n -q
update -d
[INF] Working directory: /
[INF]

[ERRR] BUILD FAILURE
[INF]

[INF] 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

[INF]

[DEBUG] Trace
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

at
()
at
()
at
()
at
()
at
()
at
()
at (DefaultMaven.java:322)
at (DefaultMaven.java:115)
at (MavenCli.java:256)
at (Native Method)
at
()
at
()
at (Method.java:585)
at
(Launcher.java:315)
at (Launcher.java:255)
at
(Launcher.java:430)
at (Launcher.java:375)
Caused by: 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

at
(PrepareReleaseMojo.java:114)
at
(DefaultPluginManager.java:412)
at
()
16 more
[INF]

[INF] Total time: 9 seconds
[INF] Finished at: Tue Jun 13 01:05:38 IST 2006
[INF] Final Memory: 4M/9M
[INF]

dan tran wrote:
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
--
6/12/06, Dhananjay Nene <dhananjay.nene (AT) cash-tech (DOT) comwrote:
>>
>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 ?
>>
>[INF] [release:prepare]
>[INF] Resuming release from phase 'scm-check-modifications'
>[INF] 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.
>[INF] Executing: cvs -z3 -f -d [ correct cvs root ] -n -q update -d
>[INF] Working directory: [ correct base directory ie. the one which
>contains pom.xml ]
>[INF]
>
>[ERRR] BUILD FAILURE
>[INF]
>
>[INF] 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
>>
>[INF]
>
>[DEBUG] Trace
>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
>>
>
>>
>-D
>>
>6/12/06, Dhananjay Nene <dhananjay.nene (AT) cash-tech (DOT) comwrote:
>>>
>>My pom.xml has been configured to checkout the project
>>${basedir}/target/checkout/source (I have configured the
>><checkoutDirectoryfor <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: users-unsubscribe (AT) maven (DOT) apache.org
>>For additional commands, e-mail: users-help (AT) maven (DOT) apache.org
>>>
>>>
>>
>>
>>
>
>To unsubscribe, e-mail: users-unsubscribe (AT) maven (DOT) apache.org
>For additional commands, e-mail: users-help (AT) maven (DOT) apache.org
>>
>>
>

To unsubscribe, e-mail: users-unsubscribe (AT) maven (DOT) apache.org
For additional commands, e-mail: users-help (AT) maven (DOT) apache.org

cvs provider uses cvs update to check for your local modification(s),
however it fails.

You will need to trouble shoot they that command fails thou
-D

6/12/06, Dhananjay Nene <dhananjay.nene (AT) cash-tech (DOT) comwrote:

I am using release plugin 2.0-beta-4. The output of the command (after
deleting release.properties) follows :

[DEBUG] Using defaults for missing PM

[DEBUG] (selected for compile)
[DEBUG]

(selected for runtime)
[DEBUG] Retrieving parent-PM:
for project:
from the repository.
[DEBUG] Retrieving parent-PM:
for project:
from the repository.
[DEBUG] Retrieving parent-PM:
for project:
from the repository.
[DEBUG] Retrieving parent-PM: for
project: from the
repository.
[DEBUG] Retrieving parent-PM: org.apache:apache::1 for project:
from the repository.
[DEBUG]

(selected for runtime)
[DEBUG] Retrieving parent-PM: for
project: null:plexus-utils:jar:1.1 from the repository.
[DEBUG] (selected
for runtime)
[DEBUG] Retrieving parent-PM:
for project:
from the repository.
[DEBUG] Retrieving parent-PM: for
project: from the
repository.
[DEBUG] Retrieving parent-PM: org.apache:apache::1 for project:
from the repository.
[DEBUG]
(selected for runtime)
[DEBUG] junit:junit:jar:3.8.1:runtime (selected for runtime)
[DEBUG] Retrieving parent-PM:
for project:
from the repository.
[DEBUG] Retrieving parent-PM:
for project:
from the repository.
[DEBUG] Retrieving parent-PM:
for project:
from the repository.
[DEBUG] Retrieving parent-PM: for
project: from the
repository.
[DEBUG] Retrieving parent-PM: org.apache:apache::1 for project:
from the repository.
[DEBUG]

(selected for runtime)
[DEBUG] Retrieving parent-PM:
for project:
from the repository.
[DEBUG] Retrieving parent-PM:
for project:
from the repository.
[DEBUG] Retrieving parent-PM: for
project: from the
repository.
[DEBUG] Retrieving parent-PM: org.apache:apache::1 for project:
from the repository.
[DEBUG]

(selected for runtime)
[DEBUG] regexp:regexp:jar:1.3:runtime (selected for runtime)
[DEBUG] Retrieving parent-PM:
for project:
from the repository.
[DEBUG] Retrieving parent-PM:
for project:
from the repository.
[DEBUG] Retrieving parent-PM: for
project: from the
repository.
[DEBUG] Retrieving parent-PM: org.apache:apache::1 for project:
from the repository.
[DEBUG]

(selected for runtime)
[DEBUG]

(selected for runtime)
[DEBUG] (selected
for runtime)
[DEBUG] (selected for runtime)
[DEBUG] (removed - causes a cycle in
the graph)
[DEBUG] jdom:jdom:jar:1.0:runtime (selected for runtime)
[DEBUG] jdom:jdom:jar:1.0:runtime (selected for runtime)
[DEBUG] Retrieving parent-PM: org.apache.maven:maven::2.0 for project:
from the repository.
[DEBUG]
(selected for runtime)
[DEBUG] (removed
- nearer found: 1.1)
[DEBUG] Retrieving parent-PM: org.apache.maven:maven::2.0 for project:
from the repository.
[DEBUG] (selected
for runtime)
[DEBUG]
(removed - nearer found: 1.1)
[DEBUG] Retrieving parent-PM: org.apache.maven:maven::2.0 for project:
from the repository.
[DEBUG]
(selected for runtime)
[DEBUG]
(removed - nearer found: 1.1)
[DEBUG]

(selected for runtime)
[DEBUG]
(removed - nearer found: 1.1)
[DEBUG] Retrieving parent-PM:
for project:
from the repository.
[DEBUG] Retrieving parent-PM:
for project:
from the repository.
[DEBUG] Retrieving parent-PM: for
project: from the
repository.
[DEBUG] Retrieving parent-PM: org.apache:apache::1 for project:
from the repository.
[DEBUG]

(selected for runtime)
[DEBUG]
(selected for runtime)
[DEBUG] junit:junit:jar:3.8.1:runtime (selected for runtime)
[DEBUG] Retrieving parent-PM: org.apache.maven:maven::2.0 for project:
null:maven-project:jar:2.0 from the repository.
[DEBUG] (selected for
runtime)
[DEBUG] (removed
- nearer found: 1.1)
[DEBUG]

(selected for runtime)
[DEBUG]
(removed - nearer found: 1.1)
[DEBUG] Retrieving parent-PM: org.apache.maven:maven::2.0 for project:
from the repository.
[DEBUG] (selected for
runtime)
[DEBUG]
(removed - nearer found: 1.1)
[DEBUG] Retrieving parent-PM: org.apache.maven:maven::2.0 for project:
null:maven-profile:jar:2.0 from the repository.
[DEBUG] (selected for
runtime)
[DEBUG]
(removed - nearer found: 1.1)
[DEBUG] Retrieving parent-PM:
for project:
from the repository.
[DEBUG] Retrieving parent-PM:
for project:
from the repository.
[DEBUG] Retrieving parent-PM: for
project: from the
repository.
[DEBUG] Retrieving parent-PM: org.apache:apache::1 for project:
from the repository.
[DEBUG]

(selected for runtime)
[DEBUG] Retrieving parent-PM: for
project:
from the repository.
[DEBUG] Retrieving parent-PM: plexus:plexus-root::1.0.3 for project:
from the repository.
[DEBUG]

(removed - nearer found: 1.0-alpha-8)
[DEBUG] (selected for
runtime)
[DEBUG] (removed
- nearer found: 1.1)
[DEBUG] Retrieving parent-PM: org.apache.maven:maven::2.0 for project:
from the repository.
[DEBUG] (selected
for runtime)
[DEBUG] Retrieving parent-PM: org.apache.maven:maven::2.0 for project:
from the repository.
[DEBUG] (selected for
runtime)
[DEBUG] (removed
- nearer found: 1.1)
[DEBUG] Retrieving parent-PM: org.apache.maven:maven::2.0 for project:
from the repository.
[DEBUG]

(selected for runtime)
[DEBUG]
(removed - nearer found: 1.1)
[DEBUG] Retrieving parent-PM: org.apache.maven:maven::2.0 for project:
from the repository.
[DEBUG]
(selected for runtime)
[DEBUG] Retrieving parent-PM: org.apache.maven:maven::2.0 for project:
from the repository.
[DEBUG] (selected for
runtime)
[DEBUG] Retrieving parent-PM: org.apache.maven:maven::2.0 for project:
null:maven-settings:jar:2.0 from the repository.
[DEBUG] (selected
for runtime)
[DEBUG]
(removed - nearer found: 1.1)
[DEBUG]

(selected for runtime)
[DEBUG]
(removed - nearer found: 1.1)
[DEBUG]
(selected for runtime)
[DEBUG]
(removed - nearer found: 1.1)
[DEBUG] Retrieving parent-PM: org.apache.maven:maven::2.0 for project:
from the repository.
[DEBUG]
(selected for runtime)
[DEBUG] (selected for runtime)
[DEBUG]
(selected for runtime)
[DEBUG] (selected for runtime)
[DEBUG]
(removed - nearer found: 1.1)
[DEBUG] Retrieving parent-PM:
for project:
from the repository.
[DEBUG] Retrieving parent-PM: org.apache.maven:maven::2.0 for project:
from the repository.
[DEBUG]
(selected
for runtime)
[DEBUG] (selected for
runtime)
[DEBUG] Retrieving parent-PM: org.apache.maven:maven::2.0 for project:
from the repository.
[DEBUG]
(selected for runtime)
[DEBUG]
(removed - nearer found: 1.1)
[DEBUG] Retrieving parent-PM:
for project:
from the repository.
[DEBUG] Retrieving parent-PM:
for project:
from the repository.
[DEBUG] Retrieving parent-PM:
for project:
from the repository.
[DEBUG] Retrieving parent-PM: for
project: from the
repository.
[DEBUG] Retrieving parent-PM: org.apache:apache::1 for project:
from the repository.
[DEBUG]

(selected for runtime)
[DEBUG] Retrieving parent-PM:
for project:
from the repository.
[DEBUG] Retrieving parent-PM:
for project:
from the repository.
[DEBUG] Retrieving parent-PM:
for project:
from the repository.
[DEBUG] Retrieving parent-PM: for
project: from the
repository.
[DEBUG] Retrieving parent-PM: org.apache:apache::1 for project:
from the repository.
[DEBUG]

(selected for runtime)
[DEBUG] Retrieving parent-PM:
for project:
from the repository.
[DEBUG] Retrieving parent-PM:
for project:
from the repository.
[DEBUG] Retrieving parent-PM: for
project: from the
repository.
[DEBUG] Retrieving parent-PM: org.apache:apache::1 for project:
from the repository.
[DEBUG]

(selected for runtime)
[DEBUG] Configuring mojo
''
[DEBUG] (f) addSchema = true
[DEBUG] (f) basedir = /
[DEBUG] (f) dryRun = true
[DEBUG] (f) generateReleasePoms = false
[DEBUG] (f) preparationGoals = clean integration-test
[DEBUG] (f) project = @33705635
[DEBUG] (f) reactorProjects =
[@33705635]
[DEBUG] (f) resume = true
[DEBUG] (f) settings = @8c436b
[DEBUG] (f) useEditMode = false
[DEBUG] -- end configuration --
[INF] [release:prepare]
[DEBUG] release.properties not found - using empty properties
[INF] Verifying that there are no local modifications
[DEBUG] cvsRoot:
:pserver:danny@
[DEBUG] passFile: /home/dhananjay/.cvspass
[DEBUG] cvsroot
:pserver:danny@
already exist in /home/dhananjay/.cvspass. SKIPPED.
[INF] Executing: cvs -z3 -f -d
:pserver:danny@ -n -q
update -d
[INF] Working directory:
/
[INF]

[ERRR] BUILD FAILURE
[INF]

[INF] 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

[INF]

[DEBUG] Trace
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

at
(
)
at
(
)
at
(
)
at

()
at
(
)
at
(
)
at (DefaultMaven.java:322)
at (DefaultMaven.java:115)
at (MavenCli.java:256)
at (Native Method)
at
(NativeMethodAccessorImpl.java
:39)
at
(
)
at (Method.java:585)
at
(Launcher.java:315)
at (Launcher.java:255)
at
(Launcher.java:430)
at (Launcher.java:375)
Caused by: 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

at
(
PrepareReleaseMojo.java:114)
at
(
DefaultPluginManager.java:412)
at
(
)
16 more
[INF]

[INF] Total time: 9 seconds
[INF] Finished at: Tue Jun 13 01:05:38 IST 2006
[INF] Final Memory: 4M/9M
[INF]

dan tran wrote:
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
--
6/12/06, Dhananjay Nene <dhananjay.nene (AT) cash-tech (DOT) comwrote:
>>
>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 ?
>>
>[INF] [release:prepare]
>[INF] Resuming release from phase 'scm-check-modifications'
>[INF] 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.
>[INF] Executing: cvs -z3 -f -d [ correct cvs root ] -n -q update
-d
>[INF] Working directory: [ correct base directory ie. the one which
>contains pom.xml ]
>[INF]
>>

>[ERRR] BUILD FAILURE
>[INF]
>>

>[INF] 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
>>
>[INF]
>>

>[DEBUG] Trace
>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
>>
>>

>>
>-D
>>
>6/12/06, Dhananjay Nene <dhananjay.nene (AT) cash-tech (DOT) comwrote:
>>>
>>My pom.xml has been configured to checkout the project
>>${basedir}/target/checkout/source (I have configured the
>><checkoutDirectoryfor <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: users-unsubscribe (AT) maven (DOT) apache.org
>>For additional commands, e-mail: users-help (AT) maven (DOT) apache.org
>>>
>>>
>>
>>
>>
>
>To unsubscribe, e-mail: users-unsubscribe (AT) maven (DOT) apache.org
>For additional commands, e-mail: users-help (AT) maven (DOT) apache.org
>>
>>
>
>
>

To unsubscribe, e-mail: users-unsubscribe (AT) maven (DOT) apache.org
For additional commands, e-mail: users-help (AT) maven (DOT) apache.org
--