You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Bob Allison (JIRA)" <ji...@codehaus.org> on 2006/05/09 22:07:41 UTC

[jira] Created: (MRELEASE-104) Probable Invalid Default SVN Tag Information

Probable Invalid Default SVN Tag Information
--------------------------------------------

         Key: MRELEASE-104
         URL: http://jira.codehaus.org/browse/MRELEASE-104
     Project: Maven 2.x Release Plugin
        Type: Improvement

    Versions: 2.0-beta-4    
 Environment: Release plugin snapshot 20060509.101136-3, Subversion
    Reporter: Bob Allison
    Priority: Minor
     Fix For: 2.0


When experimenting with a small POM, I neglected to place any configuration for the release plugin in the POM.  When trying to tag the release, the plugin tried to commit the release into the SVN repository as ${basedir}/tags

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Closed: (MRELEASE-104) Probable Invalid Default SVN Tag Information

Posted by "Emmanuel Venisse (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MRELEASE-104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Emmanuel Venisse closed MRELEASE-104.
-------------------------------------

      Assignee: Emmanuel Venisse
    Resolution: Won't Fix

You don't use the standard svn directory structure (trunk/branches/tags) so the release plugin can't find de path of your tags directory in svn.
You must configure the release plugin with the tagBase parameter

> Probable Invalid Default SVN Tag Information
> --------------------------------------------
>
>                 Key: MRELEASE-104
>                 URL: http://jira.codehaus.org/browse/MRELEASE-104
>             Project: Maven 2.x Release Plugin
>          Issue Type: Improvement
>          Components: scm
>    Affects Versions: 2.0-beta-4
>         Environment: Release plugin snapshot 20060509.101136-3, Subversion
>            Reporter: Bob Allison
>            Assignee: Emmanuel Venisse
>            Priority: Minor
>         Attachments: MRELEASE-104.pom
>
>
> When experimenting with a small POM, I neglected to place any configuration for the release plugin in the POM.  When trying to tag the release, the plugin tried to commit the release into the SVN repository as ${basedir}/tags

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Updated: (MRELEASE-104) Probable Invalid Default SVN Tag Information

Posted by "Emmanuel Venisse (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MRELEASE-104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Emmanuel Venisse updated MRELEASE-104:
--------------------------------------

    Component/s: scm

> Probable Invalid Default SVN Tag Information
> --------------------------------------------
>
>                 Key: MRELEASE-104
>                 URL: http://jira.codehaus.org/browse/MRELEASE-104
>             Project: Maven 2.x Release Plugin
>          Issue Type: Improvement
>          Components: scm
>    Affects Versions: 2.0-beta-4
>         Environment: Release plugin snapshot 20060509.101136-3, Subversion
>            Reporter: Bob Allison
>            Priority: Minor
>         Attachments: MRELEASE-104.pom
>
>
> When experimenting with a small POM, I neglected to place any configuration for the release plugin in the POM.  When trying to tag the release, the plugin tried to commit the release into the SVN repository as ${basedir}/tags

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Updated: (MRELEASE-104) Probable Invalid Default SVN Tag Information

Posted by "Bob Allison (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MRELEASE-104?page=all ]

Bob Allison updated MRELEASE-104:
---------------------------------

    Attachment: MRELEASE-104.pom

> Probable Invalid Default SVN Tag Information
> --------------------------------------------
>
>          Key: MRELEASE-104
>          URL: http://jira.codehaus.org/browse/MRELEASE-104
>      Project: Maven 2.x Release Plugin
>         Type: Improvement

>     Versions: 2.0-beta-4
>  Environment: Release plugin snapshot 20060509.101136-3, Subversion
>     Reporter: Bob Allison
>     Priority: Minor
>      Fix For: 2.0
>  Attachments: MRELEASE-104.pom
>
>
> When experimenting with a small POM, I neglected to place any configuration for the release plugin in the POM.  When trying to tag the release, the plugin tried to commit the release into the SVN repository as ${basedir}/tags

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira