Hello,

Has anyone found a solution to this problem yet? I'm getting the same error message using subversion 1.2.3 on cygwin with maven 2.0.1 and release plugin version 2.0 beta 3.

Jurgen
I tried running the command 'svn cp . ../tags/0.4' and that gave the same error message. I'm starting to think it may be a problem with svn. I ran 'svn cp /full/path/to/trunk ../tags/0.4' and that worked without a problem.
Rich

Richard Wallace wrote:
  
I tried setting the tagBase via the -DtagBase option, but that didn't seem to make a difference.
Arik Kfir wrote:
    
Hi,

Make sure you define the following in your pom.xml:
  <build>
    <plugins>
      <plugin>
        <artifactId>maven-release-plugin</artifactId>
        <configuration>
          <tagBase>http://www.mysvnserver.com/myproject/tags</tagBase>
        </configuration>
      </plugin>
    </plugins>
  </build>

This tells the release plugin where to place tagged sources (see svn
docs for info how tagging in svn).

cheers,
  Arik.

On 11/15/05, Richard Wallace <[EMAIL PROTECTED]> wrote:
      
I'm trying to use the release plugin to do a release of my project. I'm
using subversion 1.2.3 and everything proceeds to the point where m2
        
tries to do the svn copy but svn kicks back the following error message:
svn: Cannot copy path '.' into its own child '../tags/0.3'

        
I was able to do releases with the m1 plugin, but this is the first time
I've tried with m2.  Any ideas?

Thanks,
Rich

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

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

Reply via email to