[MAGNOLIA-1421] Samples should not be bootstrapped when updating to a newer version Created: 05/Mar/07  Updated: 23/Jan/13  Resolved: 05/Mar/07

Status: Closed
Project: Magnolia
Component/s: samples
Affects Version/s: 3.0.1
Fix Version/s: 3.0.2

Type: Bug Priority: Major
Reporter: Magnolia International Assignee: Magnolia International
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
depends upon MAGNOLIA-1285 modules: dependency check should get ... Closed
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

 Description   

Until we fix MAGNOLIA-1285, we could simply mark the sample module definition as being of version 3.0 instead of using maven's version number



 Comments   
Comment by Magnolia International [ 05/Mar/07 ]

Made it 3.0.1 since this problem already existing for 3.0.1

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