[DOCU-1502] Fix / adapt usage of the maven archetype in existing doc pages Created: 08/May/18  Updated: 14/May/18  Resolved: 11/May/18

Status: Closed
Project: Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Neutral
Reporter: Christoph Meier Assignee: Christoph Meier
Resolution: Done Votes: 0
Labels: underestimated
Remaining Estimate: 1m
Time Spent: Not Specified
Original Estimate: 1m

Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Sprint: Docu Sprint 49
Story Points: 3

 Description   

We have recently changed the Magnolia Maven archetypes due to several reasons.

These archetypes are used within some tutorials. Fix the usages accordingly.


Details to change

Replace parameter Magnolia version with magnolia-bundle-version
 

Where have we used the prototypes?

DOCS54
    Page: Creating a custom bundle 
    Page: Module structure 
    Page: How to create a custom webapp with STK modules 

DOCS53
    Page: Creating a custom bundle -  (no more maintained)

INCL
    Page: _getting started with Blossom 

DOCS55
    Page: How to create a custom webapp with STK modules 
    Page: Module structure 
    Page: How to create a custom Java-based REST endpoint
    Page: Creating a custom bundle 

DOCS56
    Page: Module structure 
    Page: How to create a custom Java-based REST endpoint 
    Page: Creating a custom bundle 
    Page: How to create a custom webapp with STK modules   /

 This list is based on the page info of https://documentation.magnolia-cms.com/display/INCL/_mvn+archetype+command

Test

Some of the tutorials must be checked to make sure the produced artifacts are properly working

 



 Comments   
Comment by Christoph Meier [ 08/May/18 ]

Creating a custom bundle, fixed and tested on 56, 55 and 54. 53 - I do not maintain anymore.

Comment by Christoph Meier [ 09/May/18 ]

Module structure - fixed and tested on 56, 55 and 54.

Comment by Christoph Meier [ 09/May/18 ]

How to create a custom Java-based REST endpoint - fixed on 56, 55

There is an starting with: The archetype creates a pom file which imports ...
Would be nice if we could link to "somewhere" where we explain in more details about the reason to import the BOM (which is the CE bundle parent pom file)

Comment by Christoph Meier [ 10/May/18 ]

How to create a custom webapp with STK modules

  • 54: fixed and tested
  • 55: fixed and tested
  • 56: currently works with 5.6.1 only - The maven archetype related things are changed / fixed now.
    But there is a note  to use 5.6.1 magnolia-bundle-version, although it is not the latest one.
Comment by Christoph Meier [ 11/May/18 ]

What's the problem with the 5.6.6 version of custom-stk-project-webapp?

5.6.1 bundle-version:
works fine.
See dependency tree

5.6.6 bundle-version: 
not starting properly due to wrong module versions.
See dependency tree
See log with error messages

 

Comment by Christoph Meier [ 11/May/18 ]

https://documentation.magnolia-cms.com/display/DOCS56/How+to+create+a+custom+webapp+with+STK+modules has a note to use magnolia-bundle-version 5.6.1 
Hence I stop here and close this ticket.

Generated at Mon Feb 12 01:18:41 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.