maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas Schaller (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MRELEASE-986) release:branch doesn't check if current project is located at it's scm location
Date Fri, 11 Aug 2017 09:33:00 GMT

     [ https://issues.apache.org/jira/browse/MRELEASE-986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Andreas Schaller updated MRELEASE-986:
--------------------------------------
    Description: 
I accidentally had a wrong scm location in one of my projects, when then using the release:branch
command to create a new branch, maven branched the scm location instead of the projects svn
location.
Indeed this behavior is not wrong, but can be very confusing.

Example for my situation:
svn repository layout:

{noformat}
project
 |- trunk
 |- branches
     |- v1
     |- v2
{noformat}

In trunk there is always the newest version, the branches ar old releases.
For some accidentally merges I had the cm location for branches/v2 in the trunk.
Now I tried to branch v3 from trunk but I got the version of v2 in the v3 branch.

It would be helpful, if the release plugin could check the current working copy remote version
(svn info provides the full path) and ensures, that this path is also set as the current scm
location.

  was:
I accidentally had a wrong scm location in one of my projects, when then using the release:branch
command to create a new branch, maven branched the scm location instead of the projects svn
location.
Indeed this behavior is not wrong, but can be very confusing.

Example for my situation:
svn repository layout:
project
 |- trunk
 |- branches
     |- v1
     |- v2

In trunk there is always the newest version, the branches ar old releases.
For some accidentally merges I had the cm location for branches/v2 in the trunk.
Now I tried to branch v3 from trunk but I got the version of v2 in the v3 branch.

It would be helpful, if the release plugin could check the current working copy remote version
(svn info provides the full path) and ensures, that this path is also set as the current scm
location.


> release:branch doesn't check if current project is located at it's scm location
> -------------------------------------------------------------------------------
>
>                 Key: MRELEASE-986
>                 URL: https://issues.apache.org/jira/browse/MRELEASE-986
>             Project: Maven Release Plugin
>          Issue Type: Bug
>          Components: branch
>    Affects Versions: 2.5.3
>            Reporter: Andreas Schaller
>            Priority: Minor
>
> I accidentally had a wrong scm location in one of my projects, when then using the release:branch
command to create a new branch, maven branched the scm location instead of the projects svn
location.
> Indeed this behavior is not wrong, but can be very confusing.
> Example for my situation:
> svn repository layout:
> {noformat}
> project
>  |- trunk
>  |- branches
>      |- v1
>      |- v2
> {noformat}
> In trunk there is always the newest version, the branches ar old releases.
> For some accidentally merges I had the cm location for branches/v2 in the trunk.
> Now I tried to branch v3 from trunk but I got the version of v2 in the v3 branch.
> It would be helpful, if the release plugin could check the current working copy remote
version (svn info provides the full path) and ensures, that this path is also set as the current
scm location.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message