[
https://issues.apache.org/jira/browse/MRELEASE-1057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte moved MNG-7030 to MRELEASE-1057:
-----------------------------------------------
Component/s: (was: POM)
Key: MRELEASE-1057 (was: MNG-7030)
Affects Version/s: (was: 3.6.3)
(was: 3.6.2)
2.5.3
3.0.0-M1
Project: Maven Release Plugin (was: Maven)
> 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: 3.0.0-M1, 2.5.3
> 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)
