[MGNLCDEP-19] Unprocessed ${project.version} shown on update/install screen Created: 03/Feb/12  Updated: 25/Jul/13  Resolved: 01/Mar/12

Status: Closed
Project: Content Dependencies
Component/s: None
Affects Version/s: 1.0.3
Fix Version/s: 1.0.3

Type: Bug Priority: Neutral
Reporter: Matt Dertinger Assignee: Federico Grilli
Resolution: Fixed Votes: 0
Labels: installation
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File content-dependencies-update.png    
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)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

Hi,

When updating a webapp to magnolia 4.5-beta5, I noticed that the content-dependencies module shows an unprocessed ${project.version} on the update/install page. See screenshot.

Cheers,
Matt



 Comments   
Comment by Federico Grilli [ 06/Feb/12 ]

Hi Matt, thanks for reporting this.

Cheers,

Federico

Comment by Federico Grilli [ 06/Feb/12 ]

need to have look at mvn process-resources (google maven phases) (Greg's suggestion)

Generated at Mon Feb 12 00:11:45 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.