[jira] [Comment Edited] (MRELEASE-1072) scm.tag removed for next snapshot during prepare when using svn

2022-05-31 Thread Herve Boutemy (Jira)


[ 
https://issues.apache.org/jira/browse/MRELEASE-1072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17544638#comment-17544638
 ] 

Herve Boutemy edited comment on MRELEASE-1072 at 5/31/22 11:21 PM:
---

it's not a bug, it's a new feature: you're trying to do something that was 
never done/intended (and for svn that we used for years with no problem, and 
don't really use any more)
abstract description is too abstract
please show concrete scm configuration you're wanting to support, ideally also 
with link to some live svn repositories


was (Author: hboutemy):
it's not a bug, it's a new feature: you're trying to do something that was 
never done/intended (and for svn that we used for years with ho problem, and 
don't really use any more)
abstract description is too abstract
please show concrete scm configuration you're wanting to support

> scm.tag removed for next snapshot during prepare when using svn
> ---
>
> Key: MRELEASE-1072
> URL: https://issues.apache.org/jira/browse/MRELEASE-1072
> Project: Maven Release Plugin
>  Issue Type: Bug
>  Components: prepare
>Reporter: Konrad Windszus
>Priority: Major
> Fix For: 3.0.0-M6
>
>
> In case that the original {{project.scm}} section contains a tag element 
> (e.g. with value "trunk") this is removed during prepare for the next 
> snapshot version. The tagged/release version contains the properly adjusted 
> tag element.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)


[jira] [Comment Edited] (MRELEASE-1072) scm.tag removed for next snapshot during prepare when using svn

2022-05-31 Thread Herve Boutemy (Jira)


[ 
https://issues.apache.org/jira/browse/MRELEASE-1072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17544638#comment-17544638
 ] 

Herve Boutemy edited comment on MRELEASE-1072 at 5/31/22 11:12 PM:
---

it's not a bug, it's a new feature: you're trying to do something that was 
never done/intended (and for svn that we used for years with ho problem, and 
don't really use any more)
abstract description is too abstract
please show concrete scm configuration you're wanting to support


was (Author: hboutemy):
it's not a bug, it's a new feature: you're trying to do something that was 
never done/intended (and for svn that we used for years, and don't really use 
any more)
abstract description is too abstract
please show concrete scm configuration you're wanting to support

> scm.tag removed for next snapshot during prepare when using svn
> ---
>
> Key: MRELEASE-1072
> URL: https://issues.apache.org/jira/browse/MRELEASE-1072
> Project: Maven Release Plugin
>  Issue Type: Bug
>  Components: prepare
>Reporter: Konrad Windszus
>Priority: Major
> Fix For: 3.0.0-M6
>
>
> In case that the original {{project.scm}} section contains a tag element 
> (e.g. with value "trunk") this is removed during prepare for the next 
> snapshot version. The tagged/release version contains the properly adjusted 
> tag element.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)


[jira] [Comment Edited] (MRELEASE-1072) scm.tag removed for next snapshot during prepare when using svn

2022-05-31 Thread Herve Boutemy (Jira)


[ 
https://issues.apache.org/jira/browse/MRELEASE-1072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17544638#comment-17544638
 ] 

Herve Boutemy edited comment on MRELEASE-1072 at 5/31/22 11:12 PM:
---

it's not a bug, it's a new feature: you're trying to do something that was 
never done/intended (and for svn that we used for years, and don't really use 
any more)
abstract description is too abstract
please show concrete scm configuration you're wanting to support


was (Author: hboutemy):
it's not a bug, it's a new feature: you're trying to do something that was 
never done/intended
abstract description is too abstract
please show concrete scm configuration you're wanting to support

> scm.tag removed for next snapshot during prepare when using svn
> ---
>
> Key: MRELEASE-1072
> URL: https://issues.apache.org/jira/browse/MRELEASE-1072
> Project: Maven Release Plugin
>  Issue Type: Bug
>  Components: prepare
>Reporter: Konrad Windszus
>Priority: Major
> Fix For: 3.0.0-M6
>
>
> In case that the original {{project.scm}} section contains a tag element 
> (e.g. with value "trunk") this is removed during prepare for the next 
> snapshot version. The tagged/release version contains the properly adjusted 
> tag element.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)


[jira] [Comment Edited] (MRELEASE-1072) scm.tag removed for next snapshot during prepare

2022-05-29 Thread Michael Osipov (Jira)


[ 
https://issues.apache.org/jira/browse/MRELEASE-1072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17543703#comment-17543703
 ] 

Michael Osipov edited comment on MRELEASE-1072 at 5/29/22 7:21 PM:
---

I'm trying to figure out if it is a regression or a missing edge case, to know 
if I should study the MRELEASE-988 big refactoring or if it's really about 
adding new code.

 

Do you have a real work example visible, so I can look at dry run tests, before 
digging into code, please?


was (Author: hboutemy):
I'm trying to figure out if it is a regression or a missing edge case, to know 
if I should study teh MRELEASE-988 big refactoring or if it's really about 
adding new code

 

do you have a real work example visible, so I can look at dry run tests, before 
digging into code, please?

> scm.tag removed for next snapshot during prepare
> 
>
> Key: MRELEASE-1072
> URL: https://issues.apache.org/jira/browse/MRELEASE-1072
> Project: Maven Release Plugin
>  Issue Type: Bug
>  Components: prepare
>Reporter: Konrad Windszus
>Priority: Major
> Fix For: 3.0.0-M6
>
>
> In case that the original {{project.scm}} section contains a tag element 
> (e.g. with value "trunk") this is removed during prepare for the next 
> snapshot version. The tagged/release version contains the properly adjusted 
> tag element.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)


[jira] [Comment Edited] (MRELEASE-1072) scm.tag removed for next snapshot during prepare

2022-01-02 Thread Konrad Windszus (Jira)


[ 
https://issues.apache.org/jira/browse/MRELEASE-1072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17467661#comment-17467661
 ] 

Konrad Windszus edited comment on MRELEASE-1072 at 1/2/22, 3:22 PM:


Test failure in my PR is fixed now. Please check again.

Regarding:
bq. The issue is that the tag is modified for all providers but Subversion. 

Modification of the tag value is not a problem (usually it is HEAD before and 
afterwards), as long as the value is correct. But removal is a problem in case 
you refer to that element anywhere else in your pom.xml.


was (Author: kwin):
Test failure in my PR is fixed now. Please check again.

> scm.tag removed for next snapshot during prepare
> 
>
> Key: MRELEASE-1072
> URL: https://issues.apache.org/jira/browse/MRELEASE-1072
> Project: Maven Release Plugin
>  Issue Type: Bug
>  Components: prepare
>Reporter: Konrad Windszus
>Priority: Major
>
> In case that the original {{project.scm}} section contains a tag element 
> (e.g. with value "trunk") this is removed during prepare for the next 
> snapshot version. The tagged/release version contains the properly adjusted 
> tag element.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)


[jira] [Comment Edited] (MRELEASE-1072) scm.tag removed for next snapshot during prepare

2022-01-01 Thread Michael Osipov (Jira)


[ 
https://issues.apache.org/jira/browse/MRELEASE-1072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17439640#comment-17439640
 ] 

Michael Osipov edited comment on MRELEASE-1072 at 1/1/22, 7:14 PM:
---

Where is the bug? You mean it is not re-added afterwards? 


was (Author: michael-o):
Where is the bug? You mean it is not readded afterwards? 

> scm.tag removed for next snapshot during prepare
> 
>
> Key: MRELEASE-1072
> URL: https://issues.apache.org/jira/browse/MRELEASE-1072
> Project: Maven Release Plugin
>  Issue Type: Bug
>  Components: prepare
>Reporter: Konrad Windszus
>Priority: Major
>
> In case the original {{project.scm}} section contains a tag element (e.g. 
> with value "trunk") this is removed during prepare for the next snapshot 
> version. The tagged/release version contains the properly adjusted tag 
> element.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)


[jira] [Comment Edited] (MRELEASE-1072) scm.tag removed for next snapshot during prepare

2022-01-01 Thread Michael Osipov (Jira)


[ 
https://issues.apache.org/jira/browse/MRELEASE-1072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17439640#comment-17439640
 ] 

Michael Osipov edited comment on MRELEASE-1072 at 1/1/22, 11:28 AM:


Where is the bug? You mean it is not readded afterwards? 


was (Author: michael-o):
Where is the bug? You mean it is not readied afterwards? 

> scm.tag removed for next snapshot during prepare
> 
>
> Key: MRELEASE-1072
> URL: https://issues.apache.org/jira/browse/MRELEASE-1072
> Project: Maven Release Plugin
>  Issue Type: Bug
>  Components: prepare
>Reporter: Konrad Windszus
>Priority: Major
>
> In case the original {{project.scm}} section contains a tag element (e.g. 
> with value "trunk") this is removed during prepare for the next snapshot 
> version. The tagged/release version contains the properly adjusted tag 
> element.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)