[
https://issues.apache.org/jira/browse/MNG-7030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17248088#comment-17248088
]
Michael Osipov commented on MNG-7030:
-------------------------------------
OK, I do now understand your request. The current is not designed to support
this kind of approach. Please also note MNG-6384 and similiar issues on other
Maven components. Whether this should be supported is a whole different
discussion. SCM should be a semi-static thing. But as you know, SCM coordinates
shouldn't change every day, should they? More over how shall MRELEASE update
your POM for a release version if it cannot modify for a tag? It isn't that
easy.
Can you please create an IT which shows your desired structure along with the
failure one sees?
[~rfscholte], what is your opinion? I tend to say that Can lead to brittle
setups just like with repo URLs with expressions not present in the POM. Just
like an incomplete parent with a chicken-and-egg problem.
> Allow to use project.scm properties in a maven release
> ------------------------------------------------------
>
> Key: MNG-7030
> URL: https://issues.apache.org/jira/browse/MNG-7030
> Project: Maven
> Issue Type: Bug
> Components: POM
> Affects Versions: 3.6.2, 3.6.3
> Reporter: Armand BERGES
> Priority: Major
> Fix For: waiting-for-feedback
>
>
> I try to create a custom parent pom for my company.
> Everything works great except for the release step. Actually, I would allow
> my team mate to only declare a property (say *util.scm.url*) to enable all
> the scm release block in maven-release-plugin.
> For this, I have two problems :
>
> * When I declare *scm* section only in parent pom I fall into a SCM issue
> that blocks my child projects during my release steps (since the scm is badly
> interpolated my build can't push release modifications)
> * When I try to use *project.scm.** properties in my parent pom instead of
> *scm* section, the release plugin blocks me with "Unable to find scm
> section". I think he tries to find out the *scm* section only and not the
> properties created by it
> Please tell me if I'm missing something or if you need other informations
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
