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

Konrad Windszus edited comment on MRELEASE-1053 at 1/19/21, 11:16 AM:
----------------------------------------------------------------------

It happened again in 
https://github.com/apache/jackrabbit-filevault/commit/00ec91784b52f3b87ff890535228d45e37a4630f.
 
[~hboutemy] Do you have any pointers what may go wrong here, as you implemented 
https://issues.apache.org/jira/browse/MNG-6059?

Probably something in 
https://github.com/apache/maven-release/blob/44ff401499713c981732f3379de2cf6693e0fdef/maven-release-manager/src/main/java/org/apache/maven/shared/release/phase/RewritePomsForDevelopmentPhase.java#L48
 goes wrong.


was (Author: kwin):
It happened again in 
https://github.com/apache/jackrabbit-filevault/commit/00ec91784b52f3b87ff890535228d45e37a4630f.
 
[~hboutemy] Do you have any pointers what may go wrong here, as you implemented 
https://issues.apache.org/jira/browse/MNG-6059?

> scm element removed during release:prepare when leveraging custom inheritance 
> rules
> -----------------------------------------------------------------------------------
>
>                 Key: MRELEASE-1053
>                 URL: https://issues.apache.org/jira/browse/MRELEASE-1053
>             Project: Maven Release Plugin
>          Issue Type: Bug
>          Components: prepare
>    Affects Versions: 3.0.0-M1
>            Reporter: Konrad Windszus
>            Priority: Major
>
> When leveraging the custom inheritance rules being introduced with MNG-6059 
> the m-release-p removes the {{scm}} element from the pom.xml during 
> {{release:prepare}}.
> You find an example for that behaviour at 
> https://github.com/apache/jackrabbit-filevault/commit/3a175724d8d3608bc96e92ed7fd9154fd56d1e30#diff-04dc5d029560773ac79faaf3da0fbb22L68



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to