-
Bug
-
Resolution: Incomplete
-
Major
-
None
-
Mac OS X 10.6.7
I have a multi-module maven project. It successfully builds, and the release:prepare successfully competes. However, after all of the steps (looking at console output) have completed, the whole thing fails when it tries to do something with an extra workspace directory that doesn't exist.
Here's the last part of the exception.
Caused by: org.codehaus.plexus.util.cli.CommandLineException: Working directory "/Users/dallwardt/.jenkins/jobs/Vault-test6/workspace/target/checkout/workspace" does not exist!
at org.codehaus.plexus.util.cli.Commandline.execute(Commandline.java:644)
at org.codehaus.plexus.util.cli.CommandLineUtils.executeCommandLine(CommandLineUtils.java:118)
at org.codehaus.plexus.util.cli.CommandLineUtils.executeCommandLine(CommandLineUtils.java:93)
at org.apache.maven.shared.invoker.DefaultInvoker.executeCommandLine(DefaultInvoker.java:149)
at org.apache.maven.shared.invoker.DefaultInvoker.execute(DefaultInvoker.java:102)
at org.apache.maven.shared.release.exec.InvokerMavenExecutor.executeGoals(InvokerMavenExecutor.java:387)
... 36 more
channel stopped
Finished: FAILURE
Here's what the file system looks like:
dallwardt$ pwd
/Users/dallwardt/.jenkins/jobs/Vault-test6/workspace
dallwardt$ ls
Common WzlDocs pom.xml pom.xml.releaseBackup release.properties target
dallwardt$ pwd
/Users/dallwardt/.jenkins/jobs/Vault-test6/workspace/target/checkout
dallwardt$ ls
dev tags trunk
Notice there is no workspace directory under target/checkout. Who is supposed to create an extra workspace folder under target/checkout ?
[JENKINS-9869] Jenkins Maven Release Plug-in fails because workspace directory does not exist
Derek Allwardt
created issue -
Derek Allwardt
made changes -
| Description |
Original:
I have a multi-module maven project. It successfully builds, and the release:prepare successfully competes. However, after all of the steps (looking at console output) have completed, the whole thing fails when it tries to do something with an extra workspace directory that doesn't exist. Here's the last part of the exception. Caused by: org.codehaus.plexus.util.cli.CommandLineException: Working directory "/Users/dallwardt/.jenkins/jobs/Vault-test6/workspace/target/checkout/workspace" does not exist! at org.codehaus.plexus.util.cli.Commandline.execute(Commandline.java:644) at org.codehaus.plexus.util.cli.CommandLineUtils.executeCommandLine(CommandLineUtils.java:118) at org.codehaus.plexus.util.cli.CommandLineUtils.executeCommandLine(CommandLineUtils.java:93) at org.apache.maven.shared.invoker.DefaultInvoker.executeCommandLine(DefaultInvoker.java:149) at org.apache.maven.shared.invoker.DefaultInvoker.execute(DefaultInvoker.java:102) at org.apache.maven.shared.release.exec.InvokerMavenExecutor.executeGoals(InvokerMavenExecutor.java:387) ... 36 more channel stopped Finished: FAILURE Here's what the file system looks like: dallwardt$ pwd /Users/dallwardt/.jenkins/jobs/Vault-test6/workspace dallwardt$ ls Common WzlDocs pom.xml pom.xml.releaseBackup release.properties target dallwardt$ pwd /Users/dallwardt/.jenkins/jobs/Vault-test6/workspace/target/checkout dallwardt$ ls dev tags trunk ---- Notice there is no workspace directory under target/checkout. Here's a more complete look at the console output: ---------------------------------------- [INFO] [INFO] [INFO] [INFO] --- maven-war-plugin:2.0.2:war (default-war) @ docs --- [INFO] [INFO] Exploding webapp... [INFO] [INFO] Assembling webapp docs in /Users/dallwardt/.jenkins/jobs/Vault-test6/workspace/WzlDocs/target/docs-1.5.0.3 [INFO] [INFO] Copy webapp webResources to /Users/dallwardt/.jenkins/jobs/Vault-test6/workspace/WzlDocs/target/docs-1.5.0.3 [INFO] [INFO] Generating war /Users/dallwardt/.jenkins/jobs/Vault-test6/workspace/WzlDocs/target/docs-1.5.0.3.war [INFO] [INFO] Building war: /Users/dallwardt/.jenkins/jobs/Vault-test6/workspace/WzlDocs/target/docs-1.5.0.3.war [INFO] [INFO] [INFO] [INFO] ------------------------------------------------------------------------ [INFO] [INFO] Building woozle 1.5.0.3 [INFO] [INFO] ------------------------------------------------------------------------ [INFO] [INFO] [INFO] [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ woozle --- [INFO] [INFO] Deleting /Users/dallwardt/.jenkins/jobs/Vault-test6/workspace/target [INFO] [INFO] ------------------------------------------------------------------------ [INFO] [INFO] Reactor Summary: [INFO] [INFO] [INFO] [INFO] Common ............................................ SUCCESS [8.257s] [INFO] [INFO] docs .............................................. SUCCESS [1:54.136s] [INFO] [INFO] woozle ............................................ SUCCESS [0.929s] [INFO] [INFO] ------------------------------------------------------------------------ [INFO] [INFO] BUILD SUCCESS [INFO] [INFO] ------------------------------------------------------------------------ [INFO] [INFO] Total time: 2:03.526s [INFO] [INFO] Finished at: Fri Jun 03 09:32:32 PDT 2011 [INFO] [INFO] Final Memory: 18M/540M [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Checking in modified POMs... [INFO] Executing: /bin/sh -c cd /Users/dallwardt/.jenkins/jobs/Vault-test6/workspace && svn --non-interactive commit --file /var/folders/hk/hkB7h7JzF3aAutP5dS+OyE+++TI/-Tmp-/maven-scm-1819360901.commit --targets /var/folders/hk/hkB7h7JzF3aAutP5dS+OyE+++TI/-Tmp-/maven-scm-574114402534079045-targets [INFO] Working directory: /Users/dallwardt/.jenkins/jobs/Vault-test6/workspace [INFO] Tagging release with the label woozle-1.5.0.3... [INFO] Executing: /bin/sh -c cd /Users/dallwardt/.jenkins/jobs/Vault-test6 && svn --non-interactive copy --file /var/folders/hk/hkB7h7JzF3aAutP5dS+OyE+++TI/-Tmp-/maven-scm-219891468.commit --revision 3486 https://svnhost/woozle/test6/dev https://svnhost/woozle/test6/dev/tags/woozle-1.5.0.3 [INFO] Working directory: /Users/dallwardt/.jenkins/jobs/Vault-test6 [INFO] Transforming 'Common'... [INFO] Transforming 'docs'... [INFO] Updating Common to 1.5.0.4-SNAPSHOT [INFO] Transforming 'woozle'... [INFO] Not removing release POMs [INFO] Checking in modified POMs... [INFO] Executing: /bin/sh -c cd /Users/dallwardt/.jenkins/jobs/Vault-test6/workspace && svn --non-interactive commit --file /var/folders/hk/hkB7h7JzF3aAutP5dS+OyE+++TI/-Tmp-/maven-scm-1649947372.commit --targets /var/folders/hk/hkB7h7JzF3aAutP5dS+OyE+++TI/-Tmp-/maven-scm-8830657010116301312-targets [INFO] Working directory: /Users/dallwardt/.jenkins/jobs/Vault-test6/workspace [INFO] Release preparation complete. [INFO] [INFO] --- maven-release-plugin:2.0:perform (default-cli) @ woozle --- [INFO] Checking out the project to perform the release ... [INFO] Executing: /bin/sh -c cd /Users/dallwardt/.jenkins/jobs/Vault-test6/workspace/target && svn --non-interactive checkout https://svnhost/woozle/test6/dev/tags/woozle-1.5.0.3 /Users/dallwardt/.jenkins/jobs/Vault-test6/workspace/target/checkout [INFO] Working directory: /Users/dallwardt/.jenkins/jobs/Vault-test6/workspace/target [INFO] Executing goals 'deploy'... [WARNING] Base directory is a file. Using base directory as POM location. mojoFailed org.apache.maven.plugins:maven-release-plugin:2.0(default-cli) projectFailed veeva.ecm:woozle:1.5.0.4-SNAPSHOT [JENKINS] Archiving /Users/dallwardt/.jenkins/jobs/Vault-test6/workspace/pom.xml to /Users/dallwardt/.jenkins/jobs/Vault-test6/modules/veeva.ecm$woozle/builds/2011-06-03_09-30-23/archive/veeva.ecm/woozle/1.5.0.4-SNAPSHOT/woozle-1.5.0.4-SNAPSHOT.pom sessionEnded [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary: [INFO] [INFO] Common ............................................ SKIPPED [INFO] docs .............................................. SKIPPED [INFO] woozle ............................................ FAILURE [2:54.062s] [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 2:54.891s [INFO] Finished at: Fri Jun 03 09:33:20 PDT 2011 [INFO] Final Memory: 7M/540M [INFO] ------------------------------------------------------------------------ mavenExecutionResult exceptions not empty message : Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.0:perform (default-cli) on project woozle: Error executing Maven. cause : Error executing Maven. Stack trace : org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.0:perform (default-cli) on project woozle: Error executing Maven. at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.jvnet.hudson.maven3.launcher.Maven3Launcher.main(Maven3Launcher.java:79) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:329) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:239) at org.jvnet.hudson.maven3.agent.Maven3Main.launch(Maven3Main.java:158) at hudson.maven.Maven3Builder.call(Maven3Builder.java:128) at hudson.maven.Maven3Builder.call(Maven3Builder.java:75) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:270) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:680) Caused by: org.apache.maven.plugin.MojoExecutionException: Error executing Maven. at org.apache.maven.plugins.release.PerformReleaseMojo.execute(PerformReleaseMojo.java:135) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:107) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) ... 27 more Caused by: org.apache.maven.shared.release.ReleaseExecutionException: Error executing Maven. at org.apache.maven.shared.release.phase.AbstractRunGoalsPhase.execute(AbstractRunGoalsPhase.java:90) at org.apache.maven.shared.release.phase.RunPerformGoalsPhase.execute(RunPerformGoalsPhase.java:67) at org.apache.maven.shared.release.DefaultReleaseManager.perform(DefaultReleaseManager.java:343) at org.apache.maven.shared.release.DefaultReleaseManager.perform(DefaultReleaseManager.java:289) at org.apache.maven.shared.release.DefaultReleaseManager.perform(DefaultReleaseManager.java:269) at org.apache.maven.plugins.release.PerformReleaseMojo.execute(PerformReleaseMojo.java:131) ... 29 more Caused by: org.apache.maven.shared.release.exec.MavenExecutorException: Error executing Maven. at org.apache.maven.shared.release.exec.InvokerMavenExecutor.executeGoals(InvokerMavenExecutor.java:391) at org.apache.maven.shared.release.exec.InvokerMavenExecutor.executeGoals(InvokerMavenExecutor.java:413) at org.apache.maven.shared.release.phase.AbstractRunGoalsPhase.execute(AbstractRunGoalsPhase.java:82) ... 34 more Caused by: org.codehaus.plexus.util.cli.CommandLineException: Working directory "/Users/dallwardt/.jenkins/jobs/Vault-test6/workspace/target/checkout/workspace" does not exist! at org.codehaus.plexus.util.cli.Commandline.execute(Commandline.java:644) at org.codehaus.plexus.util.cli.CommandLineUtils.executeCommandLine(CommandLineUtils.java:118) at org.codehaus.plexus.util.cli.CommandLineUtils.executeCommandLine(CommandLineUtils.java:93) at org.apache.maven.shared.invoker.DefaultInvoker.executeCommandLine(DefaultInvoker.java:149) at org.apache.maven.shared.invoker.DefaultInvoker.execute(DefaultInvoker.java:102) at org.apache.maven.shared.release.exec.InvokerMavenExecutor.executeGoals(InvokerMavenExecutor.java:387) ... 36 more channel stopped Finished: FAILURE |
New:
I have a multi-module maven project. It successfully builds, and the release:prepare successfully competes. However, after all of the steps (looking at console output) have completed, the whole thing fails when it tries to do something with an extra workspace directory that doesn't exist. Here's the last part of the exception. Caused by: org.codehaus.plexus.util.cli.CommandLineException: Working directory "/Users/dallwardt/.jenkins/jobs/Vault-test6/workspace/target/checkout/workspace" does not exist! at org.codehaus.plexus.util.cli.Commandline.execute(Commandline.java:644) at org.codehaus.plexus.util.cli.CommandLineUtils.executeCommandLine(CommandLineUtils.java:118) at org.codehaus.plexus.util.cli.CommandLineUtils.executeCommandLine(CommandLineUtils.java:93) at org.apache.maven.shared.invoker.DefaultInvoker.executeCommandLine(DefaultInvoker.java:149) at org.apache.maven.shared.invoker.DefaultInvoker.execute(DefaultInvoker.java:102) at org.apache.maven.shared.release.exec.InvokerMavenExecutor.executeGoals(InvokerMavenExecutor.java:387) ... 36 more channel stopped Finished: FAILURE Here's what the file system looks like: dallwardt$ pwd /Users/dallwardt/.jenkins/jobs/Vault-test6/workspace dallwardt$ ls Common WzlDocs pom.xml pom.xml.releaseBackup release.properties target dallwardt$ pwd /Users/dallwardt/.jenkins/jobs/Vault-test6/workspace/target/checkout dallwardt$ ls dev tags trunk ---- Notice there is no workspace directory under target/checkout. Who is supposed to create an extra workspace folder under target/checkout ? |
Derek Allwardt
added a comment - Wow, thanks for the quick response!
I'm not sure exactly what the base directory refers to. But I thought I would share the scm settings for the parent pom and the two modules to see if anything glaring pops out for you.
Parent POM scm settings:
<scm>
<connection>
scm:svn:https://svnhost/woozle/test6/dev/trunk
</connection>
<developerConnection>
scm:svn:https://svnhost/woozle/test6/dev/trunk
</developerConnection>
<url>
scm:svn:https://svnhost/woozle/test6/dev/trunk
</url>
</scm>
Module Common scm settings:
<scm>
<connection>
scm:svn:https://svnhost/woozle/test6/dev/trunk/Common
</connection>
<developerConnection>
scm:svn:https://svnhost/woozle/test6/dev/trunk/Common
</developerConnection>
<url>
scm:svn:https://svnhost/woozle/test6/dev/trunk/Common
</url>
</scm>
Module WzlDocs scm settings:
<scm>
<connection>
scm:svn:https://svnhost/woozle/test6/dev/trunk/WzlDocs
</connection>
<developerConnection>
scm:svn:https://svnhost/woozle/test6/dev/trunk/WzlDocs
</developerConnection>
<url>
scm:svn:https://svnhost/woozle/test6/dev/trunk/WzlDocs
</url>
</scm>
Derek Allwardt
added a comment - Wow, thanks for the quick response!
I'm not sure exactly what the base directory refers to. But I thought I would share the scm settings for the parent pom and the two modules to see if anything glaring pops out for you.
Parent POM scm settings:
<scm>
<connection>
scm:svn: https://svnhost/woozle/test6/dev/trunk
</connection>
<developerConnection>
scm:svn: https://svnhost/woozle/test6/dev/trunk
</developerConnection>
<url>
scm:svn: https://svnhost/woozle/test6/dev/trunk
</url>
</scm>
Module Common scm settings:
<scm>
<connection>
scm:svn: https://svnhost/woozle/test6/dev/trunk/Common
</connection>
<developerConnection>
scm:svn: https://svnhost/woozle/test6/dev/trunk/Common
</developerConnection>
<url>
scm:svn: https://svnhost/woozle/test6/dev/trunk/Common
</url>
</scm>
Module WzlDocs scm settings:
<scm>
<connection>
scm:svn: https://svnhost/woozle/test6/dev/trunk/WzlDocs
</connection>
<developerConnection>
scm:svn: https://svnhost/woozle/test6/dev/trunk/WzlDocs
</developerConnection>
<url>
scm:svn: https://svnhost/woozle/test6/dev/trunk/WzlDocs
</url>
</scm> Derek Allwardt
added a comment - I believe the way the tagging is working is causing the problem. Below, I've copied the output from the console that I believe is relevant, and added comments [dallwardt].
[INFO] Executing: /bin/sh c cd /Users/dallwardt/.jenkins/jobs/Vault-test6 && svn --non-interactive copy --file /var/folders/hk/hkB7h7JzF3aAutP5dS+OyE+++TI/-Tmp/maven-scm-2140088471.commit --revision 3521 https://svnhost/woozle/test6/dev https://svnhost/woozle/test6/dev/tags/woozle-1.5.0.5
[dallwardt] copy is made from /woozle/test6/dev instead of /woozle/test6/dev/trunk. My scm settings are scm:svn:https://svnhost/woozle/test6/dev/trunk. Why is it dropping the "trunk" part of it?
[INFO] Release preparation complete.
[INFO] Checking out the project to perform the release ...
[INFO] Executing: /bin/sh -c cd /Users/dallwardt/.jenkins/jobs/Vault-test6/workspace/target && svn --non-interactive checkout https://svnhost/woozle/test6/dev/tags/woozle-1.5.0.5 /Users/dallwardt/.jenkins/jobs/Vault-test6/workspace/target/checkout
[INFO] Working directory: /Users/dallwardt/.jenkins/jobs/Vault-test6/workspace/target
[dallwardt] /Users/dallwardt/.jenkins/jobs/Vault-test6/workspace/target/checkout contains the following:
drwxr-xr-x 3 dallwardt staff 102 Jun 3 18:31 tags
drwxr-xr-x 6 dallwardt staff 204 Jun 3 18:43 trunk
[INFO] Executing goals 'deploy'...
[WARNING] Base directory is a file. Using base directory as POM location.
mojoFailed org.apache.maven.plugins:maven-release-plugin:2.0(default-cli)
Derek Allwardt
added a comment - I believe the way the tagging is working is causing the problem. Below, I've copied the output from the console that I believe is relevant, and added comments [dallwardt] .
[INFO] Executing: /bin/sh c cd /Users/dallwardt/.jenkins/jobs/Vault-test6 && svn --non-interactive copy --file /var/folders/hk/hkB7h7JzF3aAutP5dS+OyE+++TI/-Tmp /maven-scm-2140088471.commit --revision 3521 https://svnhost/woozle/test6/dev https://svnhost/woozle/test6/dev/tags/woozle-1.5.0.5
[dallwardt] copy is made from /woozle/test6/dev instead of /woozle/test6/dev/trunk. My scm settings are scm:svn: https://svnhost/woozle/test6/dev/trunk . Why is it dropping the "trunk" part of it?
[INFO] Release preparation complete.
[INFO] Checking out the project to perform the release ...
[INFO] Executing: /bin/sh -c cd /Users/dallwardt/.jenkins/jobs/Vault-test6/workspace/target && svn --non-interactive checkout https://svnhost/woozle/test6/dev/tags/woozle-1.5.0.5 /Users/dallwardt/.jenkins/jobs/Vault-test6/workspace/target/checkout
[INFO] Working directory: /Users/dallwardt/.jenkins/jobs/Vault-test6/workspace/target
[dallwardt] /Users/dallwardt/.jenkins/jobs/Vault-test6/workspace/target/checkout contains the following:
drwxr-xr-x 3 dallwardt staff 102 Jun 3 18:31 tags
drwxr-xr-x 6 dallwardt staff 204 Jun 3 18:43 trunk
[INFO] Executing goals 'deploy'...
[WARNING] Base directory is a file. Using base directory as POM location.
mojoFailed org.apache.maven.plugins:maven-release-plugin:2.0(default-cli) Derek Allwardt
added a comment - I tried adding the trailing slash, and here's the results:
- running mvn release:prepare release:perform from the command line works.
- using the Jenkins release plugin still does not work.
The release:prepare phase (in Jenkins) is removing the trailing slash, thus causing the original problem "[WARNING] Base directory is a file. Using base directory as POM location". I verified this by comparing the original pom version to the one that maven checks in on the tag.
Why would we get different results from Maven and Jenkins (which is calling maven)?
Derek Allwardt
added a comment - I tried adding the trailing slash, and here's the results:
running mvn release:prepare release:perform from the command line works.
using the Jenkins release plugin still does not work.
The release:prepare phase (in Jenkins) is removing the trailing slash, thus causing the original problem " [WARNING] Base directory is a file. Using base directory as POM location". I verified this by comparing the original pom version to the one that maven checks in on the tag.
Why would we get different results from Maven and Jenkins (which is calling maven)? The reason that springs to mind would be that it is using different plug in versions.
having said that an old version of maven-relrase-plugin will fail for a different reason.
Was the workspace cleaned before the re test?
Derek Allwardt
added a comment - When I run it from the command line, I see this:
[INFO] — maven-release-plugin:2.0:perform (default-cli) @ vault —
When I look at the console output from Jenkins, I see this:
[INFO] — maven-release-plugin:2.0:prepare (default-cli) @ vault —
and here's the info about the Jenkins Maven Release plugin
About Jenkins Maven Release Plug-in Plug-in 0.7.1
Here's the command line output from mvn --version
Apache Maven 3.0.2 (r1056850; 2011-01-08 16:58:10-0800)
Java version: 1.6.0_24, vendor: Apple Inc.
Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
Default locale: en_US, platform encoding: MacRoman
OS name: "mac os x", version: "10.6.7", arch: "x86_64", family: "mac"
Derek Allwardt
added a comment - When I run it from the command line, I see this:
[INFO] — maven-release-plugin:2.0:perform (default-cli) @ vault —
When I look at the console output from Jenkins, I see this:
[INFO] — maven-release-plugin:2.0:prepare (default-cli) @ vault —
and here's the info about the Jenkins Maven Release plugin
About Jenkins Maven Release Plug-in Plug-in 0.7.1
Here's the command line output from mvn --version
Apache Maven 3.0.2 (r1056850; 2011-01-08 16:58:10-0800)
Java version: 1.6.0_24, vendor: Apple Inc.
Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
Default locale: en_US, platform encoding: MacRoman
OS name: "mac os x", version: "10.6.7", arch: "x86_64", family: "mac" Can you attach a sample maven project, with the release.properties and poms when you try to do a release.
which version of svn are you using?
From the entry
[WARNING] Base directory is a file. Using base directory as POM location.
It looks like your SCM section in your pom is not correct, which would tie up.with the checkout having trunk,dev&tags
If you don't think this is the case please provide a sample maven project and the full build.log.