[ARCH-19] Theme archetype should create a dependency to the newest STK or let the user set it during the setup process Created: 01/Feb/13  Updated: 14/Mar/14  Resolved: 28/Aug/13

Status: Closed
Project: Archetypes
Component/s: stk-theme
Affects Version/s: 1.0
Fix Version/s: 1.1

Type: Improvement Priority: Neutral
Reporter: Natascha Desmarais Assignee: Magnolia International
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)
Date of First Response:

 Description   

Right now when creating a theme module with the stk-theme archetype, it automatically sets the dependencies in the pom and the module descriptor to STK 1.4.2 by default.

Especially for projects using Magnolia v4.5 and newer this is quite ugly.

The archetype should set be up with a dependency to a newer STK version by default (2.0.6 for example) or even better: it should give you the chance to set it yourself during the setup process, right after specifying the version of Magnolia.



 Comments   
Comment by Magnolia International [ 28/Aug/13 ]

Removed <defaultValue> uses until ARCHETYPE-308 is fixed.

Generated at Sun Feb 11 23:22:44 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.