[MNG-624] automatic parent versioning

• Type: Improvement
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Fix Version/s: 4.0.0-alpha-2, 4.0.0
• Component/s: FDPFC, Inheritance and Interpolation
• Assignee: Robert Scholte
• Reporter: Brett Porter
• Created: 20/Jul/05 20:56
• Updated: 20/Oct/22 08:11
• Resolved: 24/Jun/20 06:39

Description

(this may be bumped to 2.1 or even made WON't FIX as it is contentious - see MNG-521)

currently, you have to specify the parent version when extending which makes a project stand alone very easily, but has the drawback of being a maintainance problem when you start development on a new version. Tools can help, but it would be nice not to have to rely on them.

One alternative is to allow the parent version to be omitted, and when it is it is assumed you want the latest. The parent is used from the reactor or the universal source directory. IT may also be read from a LATEST in the repository though this is contentious - it may be better to simply fail in that environment and require builds be in a known checkout structure for building individual projects.

This also introduces the need for tool support to populate the version on release and deployment for reproducibility.

Issue Links

• is duplicated by: MNG-4369 Maven does not expand expressions while installing artifacts locally
• is duplicated by: MNG-2569 Expressions not evaluated inside <parent>
• is fixed by: MNG-6656 Introduce base for build/consumer process
• is related to: MNG-3057 properties not expanded in generated POMs when building A/B/C nested projects
• is related to: MNG-3782 Variable substition not performed in transitive dependency using value from active profile
• is related to: MNG-2446 parent Pom properties not resolved for module dependencies
• is related to: MNG-4161 possibility to omit version in dependency of same project (and fill in on install/deploy)
• is related to: MNG-3267 replacing variables in version, groupId or artifactId when POM is installed/deployed
• is related to: MNG-2199 Support version ranges in parent elements
• relates to: MNG-5840 <relativePath> is used if the groupId and artifactId match irrespective of the version
• relates to: MNG-2971 Variables are not replaced into installed pom file
• relates to: MNG-3070 ${x} properties no longer expanded in </version> tag after 2.0.3
• relates to: MNG-1468 best practices: version management in multi project builds
• relates to: MINSTALL-50 provide property filtering on .pom files placed in local repo
• relates to: MNG-521 Version inheritance from the parent pom
• mentioned in: Page Loading...
• mentioned in: Page Loading...