[MRELEASE-784] SNAPSHOT version in Dependency in DependencyManagement with scope import and type pom is not replaced
- Dominant language
- Java
- Stars
- 128
- Forks
- 145
- Avg merge
- 7h 7m
- Merged PRs (30d)
- 3
Description
**[Michael Niedermaier](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=mniedermaier)** opened **[MRELEASE-784](https://issues.apache.org/jira/browse/MRELEASE-784?redirect=false)** and commented
In the test case he asks for the external:artifactId version on console, but it should only ask and change for the import dependencyManagement dependency external:parent-artifactid-withimport-dm which's version is not changed by the release plugin
I attached my sample repository, the project in tryed to release (including the created pom for tag, which still contains the SNAPSHOT version) and the console output
---
**Affects:** 2.3.2
**Attachments:**
- [console.out](https://issues.apache.org/jira/secure/attachment/12717943/console.out) (_235.23 kB_)
- [internal-managed-snapshot-dependency.zip](https://issues.apache.org/jira/secure/attachment/12718191/internal-managed-snapshot-dependency.zip) (_18.71 kB_)
- [remote-repository.zip](https://issues.apache.org/jira/secure/attachment/12718070/remote-repository.zip) (_27.98 kB_)
2 votes, 5 watchers
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by examining the attached internal-managed-snapshot-dependency.zip and console.out, then reproduce the release with the Maven Release Plugin against the supplied remote repository. The fix is complete when an import-scoped, type-pom dependency-management dependency has its SNAPSHOT version replaced and the release prompt changes only the intended dependency.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system, release
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100