[
https://issues.apache.org/jira/browse/MRELEASE-1057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17248144#comment-17248144
]
Robert Scholte commented on MRELEASE-1057:
------------------------------------------
I've moved this issue to the maven-release-plugin, because it is actually the
plugin that suffers this issue.
To me, just like artifact repositories, source repositories are fixed
repositories, they shouln't contain any variable.
And if a child project forgets to set the property, scm will be configured
incorrectly.
It is something you set only once. So if you need to choose between setting a
property of scm.developerConnection, just pick the latter.
Also, there's no need to specify them all.
In general you only define the developerConnection.
One might provide a connection for anonymous usage, but that only makes sense
if it is different compared to the developConnection.
The URL should point to the http/https page of the repository when available
(and when you want to expose this).
> Allow to use project.scm properties in a maven release
> ------------------------------------------------------
>
> Key: MRELEASE-1057
> URL: https://issues.apache.org/jira/browse/MRELEASE-1057
> Project: Maven Release Plugin
> Issue Type: Bug
> Affects Versions: 2.5.3, 3.0.0-M1
> Reporter: Armand BERGES
> Priority: Major
>
> 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)
