[MAGNOLIA-2848] Support other variables than ${pom.version} for development version in module xml Created: 18/Aug/09  Updated: 23/Jan/13  Resolved: 18/Aug/09

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: 4.1
Fix Version/s: 4.1.1

Type: Improvement Priority: Trivial
Reporter: Fabrizio Giustina Assignee: Fabrizio Giustina
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)

 Description   

In a module xml <version>${pom.version}</version> has a special handling and it's defined as a "undefined development version".

There are also other way of making incrementing the module version, for example using the maven build number plugin we could need to define it as:
<version>${buildNumber}</version>

Instead of checking for ${pom.version} so it would be better to check for any variable string (starting with "${").



 Comments   
Comment by Fabrizio Giustina [ 18/Aug/09 ]

patch committed

Generated at Mon Feb 12 03:40:42 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.