I'm trying the release plugin and I get the following error:
 
$ mvn -e release:prepare
+ Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'release'.
[INFO] -------------------------------------------------------------------------
---
[INFO] Building Dependency Maven Plugin
[INFO]    task-segment: [release:prepare] (aggregator-style)
[INFO] -------------------------------------------------------------------------
---
[WARNING]
        Artifact junit:junit:jar:3.8.1 retains local scope 'test' overriding bro
ader scope 'compile'
        given by a dependency. If this is not intended, modify or remove the loc
al scope.
 
[INFO] [release:prepare]
[INFO] Checking in modified POMs
[INFO] What tag name should be used?
dependency-maven-plugin-1.0
[INFO] Tagging release with the label dependency-maven-plugin-1.0.
Provider message:
The svn tag command failed.
Command output:
svn: Commit failed (details follow):
svn: MKACTIVITY of '/mojo/!svn/act/a9c42856-b1b7-014c-82a2-c813398c4427': author
ization failed (https://svn.codehaus.org)
 
[INFO] -------------------------------------------------------------------------
---
[ERROR] BUILD ERROR
[INFO] -------------------------------------------------------------------------
---
[INFO] An error is occurred in the tag process.
 
Embedded error: Error!
[INFO] -------------------------------------------------------------------------
---
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: An error is occurred in
the tag process.
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
ultLifecycleExecutor.java:544)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandalone
Goal(DefaultLifecycleExecutor.java:482)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
ltLifecycleExecutor.java:452)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
dleFailures(DefaultLifecycleExecutor.java:301)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
ts(DefaultLifecycleExecutor.java:214)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
fecycleExecutor.java:137)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:316)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:113)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:249)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:324)
        at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
        at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
        at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
 
        at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.MojoExecutionException: An error is occurred
in the tag process.
        at org.apache.maven.plugins.release.PrepareReleaseMojo.tagRelease(Prepar
eReleaseMojo.java:1414)
        at org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareRe
leaseMojo.java:246)
        at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
nManager.java:399)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
ultLifecycleExecutor.java:519)
        ... 16 more
Caused by: org.apache.maven.scm.ScmException: Error!
        at org.apache.maven.plugins.release.helpers.ScmHelper.checkResult(ScmHel
per.java:124)
        at org.apache.maven.plugins.release.helpers.ScmHelper.tag(ScmHelper.java
:226)
        at org.apache.maven.plugins.release.PrepareReleaseMojo.tagRelease(Prepar
eReleaseMojo.java:1410)
        ... 19 more
[INFO] -------------------------------------------------------------------------
---
[INFO] Total time: 25 seconds
[INFO] Finished at: Mon Jan 02 14:16:17 EST 2006
[INFO] Final Memory: 3M/6M
[INFO] -------------------------------------------------------------------------
---


From: dan tran [mailto:[EMAIL PROTECTED]
Sent: Monday, January 02, 2006 12:11 AM
To: dev@mojo.codehaus.org
Subject: Re: [mojo-dev] Mojo synch to ibiblio missing hashes

Hi Brian,
 
Did you change the permission after invoke maven deploy?  I could be that the sync between iliblio and codehaus staging area fails due
to permission problem.
 
I also notice you did not use maven-release-plugin to do the release because the version in the pom now should be 1.x-SNAPSHOT
not staying at 1.0.  Also there no SVN tag for your release.
 
One way to fix is to change the version to 1.0-SNAPSHOT, check it in and run maven-release-plugin:prepare and maven-release-plugin:release
 
-Dan


 
On 1/1/06, Brian E. Fox <[EMAIL PROTECTED]> wrote:
Also appears that http://www.ibiblio.org/pub/packages/maven2/org/codehaus/mojo/dependency-maven-plugin/1.0/maven-metadata.xml isn't readable by apache because it returns permission denied.


From: Brian E. Fox [mailto:[EMAIL PROTECTED]]
Sent: Sunday, January 01, 2006 11:45 PM
To: dev@mojo.codehaus.org
Subject: [mojo-dev] Mojo synch to ibiblio missing hashes

 
I released the dependency plugin today and now that it's synched with ibiblio, the hashes are missing. They are on the repo1 repository where I deployed, but not at http://www.ibiblio.org/pub/packages/maven2/org/codehaus/mojo/dependency-maven-plugin/1.0/. I'm pretty sure that's not normal but maybe I missed something.

Reply via email to