jira.codehaus.org

  • Log In Access more options
    • Online Help
    • Keyboard Shortcuts
    • About JIRA
    • JIRA Credits
    • What?s New
  • Dashboards Access more options (Alt+d)
  • Projects Access more options (Alt+p)
  • Issues Access more options (Alt+i)
  • Maven 2.x Release Plugin
  • MRELEASE-461

Add a mojo parameter for using the new remote tagging for svn scm provider (to prevent issue with svn > 1.5.0) in branch mojo

  • Log In
  • Views
    • XML
    • Word
    • Printable

Details

  • Type: Improvement Improvement
  • Status: Closed Closed
  • Priority: Critical Critical
  • Resolution: Fixed
  • Affects Version/s: 2.0-beta-9
  • Fix Version/s: 2.0
  • Component/s: scm
  • Labels:
    None

Description

Due to an issue with svn > 1.5.0, release plugin doesn't work. The scm (1.2) implements a new remote tagging mechanism as a workaround.

This is fixed for release:prepare in MRELEASE-427

I have the same problem when executing mvn release:branch.

It would be useful to add the -DremoteTagging argument also when making branches.

Thank you.

Issue Links

depends upon

Improvement - An improvement or enhancement to an existing feature or task. SCM-515 branch command must support remote branching (svnexe)

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.
is duplicated by

Bug - A problem which impairs or prevents the functions of the product. MRELEASE-433 Add parameter remoteTagging to release:branch (to prevent issue with svn > 1.5.0)

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Bug - A problem which impairs or prevents the functions of the product. MRELEASE-446 "Already exists" SVN error during release:branch

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Bug - A problem which impairs or prevents the functions of the product. MRELEASE-514 release:branch hit remoteTagging problem

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
  • All
  • Comments
  • Work Log
  • History
  • Activity
Hide
Permalink
Olivier Lamy added a comment - 26/Jul/09 1:28 PM

fix in rev 797971

Show
Olivier Lamy added a comment - 26/Jul/09 1:28 PM fix in rev 797971
Hide
Permalink
Benson Margulies added a comment - 16/Sep/09 1:33 PM

The current snapshot does not work.

If the snapshot is stale, please publish a new one. If it is not, please reopen.

Provider message:
The svn branch command failed.
Command output:
svn: Commit failed (details follow):
svn: File '/engineering/rex2009/branches/rlp-7.0/ama/pom.xml' already exists

Show
Benson Margulies added a comment - 16/Sep/09 1:33 PM The current snapshot does not work. If the snapshot is stale, please publish a new one. If it is not, please reopen. Provider message: The svn branch command failed. Command output: svn: Commit failed (details follow): svn: File '/engineering/rex2009/branches/rlp-7.0/ama/pom.xml' already exists
Hide
Permalink
Olivier Lamy added a comment - 16/Sep/09 2:14 PM

reopen due to user comment.

Show
Olivier Lamy added a comment - 16/Sep/09 2:14 PM reopen due to user comment.
Hide
Permalink
Olivier Lamy added a comment - 19/Dec/09 1:16 PM

fix in rev 892499
SNAPSHOTS deployed.
Reopen the issue if you have any trouble.

Show
Olivier Lamy added a comment - 19/Dec/09 1:16 PM fix in rev 892499 SNAPSHOTS deployed. Reopen the issue if you have any trouble.

People

  • Assignee:
    Olivier Lamy
    Reporter:
    Orestes Garcia
Vote (1)
Watch (2)

Dates

  • Created:
    22/Jul/09 2:45 PM
    Updated:
    01/Feb/10 11:39 AM
    Resolved:
    19/Dec/09 1:16 PM
  • Atlassian JIRA (v5.0.4#731-sha1:3aa7374)
  • Report a problem
  • Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.