[MRELEASE-1057] Allow to use project.scm properties in a maven release
- Dominant language
- Java
- Stars
- 128
- Forks
- 145
- Avg merge
- 7h 7m
- Merged PRs (30d)
- 3
Description
**[Armand BERGES](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=lvffy)** opened **[MRELEASE-1057](https://issues.apache.org/jira/browse/MRELEASE-1057?redirect=false)** and commented
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
---
**Affects:** 2.5.3, 3.0.0-M1
Contributor guide
No contributing guide indexed for this repository
Research direction
Reproduce the release step with a custom parent POM that defines project.scm properties instead of an scm section, using the examples in the issue. Start by tracing the maven-release-plugin lookup that produces “Unable to find scm section.” Done means inherited project.scm properties are accepted and release modifications can be pushed without incorrect SCM interpolation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100