[ARCH-68] Update "magnolia-project-archetype" to reflect the new product strategy Created: 01/Apr/19  Updated: 06/Jun/19  Resolved: 05/Jun/19

Status: Closed
Project: Archetypes
Component/s: None
Affects Version/s: None
Fix Version/s: 1.2.5

Type: Task Priority: Neutral
Reporter: Christoph Meier Assignee: Dai Ha
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 1h
Original Estimate: Not Specified

Issue Links:
dependency
depends upon MGNLEE-569 Re-work dx-core artifact names: group... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:
Epic Link: DX Core
Sprint: Features 12
Story Points: 5

 Description   
  • Validate that the maven relocations work.
  • Generate new coordinates.

Context

With the new product strategy - see Product naming - we will have no more EE-Std-, EE-Pro- artifacts for webapps and bundles, but there will be only one PRO artifact (or maybe one webapp and one Tomcat bundle).

Maven archetype to create custom Magnolia webapps

We provide a Maven archetype to create custom Magnolia webapps. (See Creating a custom webapp with Maven docu).

The archetype info.magnolia.maven.archetypes:magnolia-project-archetype - the archetype to build a custom webapp, creates options to inherit the custom webapp from magnolia-enterprise-standard-webapp,  magnolia-enterprise-pro-webapp (and others).

We should adapt this archetype, removing the EE-Std and EE-Pro option and adding there instead the option to inherit from the new one and only dx-core artifact.

No more stk-theme archetype

When releasing the new versions of the archetypes - I propose to stop providing a new version for the STK-theme.

No more Forge archetype

Same for the Forge, which now provides GitHub templates, cf. https://github.com/magnolia-community/

GIT

maven-archetypes repository.

 

Required

Maven groupId and artifactId of the new artifac(s) need(s) to be known.



 Comments   
Comment by Christoph Meier [ 22/May/19 ]

rkovarik, cc mgeljic

I have just realized that we prbly. also should update the archetypes to create modules.

  • magnolia-module-archetype
  • magnolia-forge-module-archetype

We could adapt the archetype(s) in a way, that it creates the config.yaml (and the Module class could contain a dummy bean property).
Just an idea ... but if somebody takes care for the archetypes, we could do this in just one sweep.
(Just an idea)

Comment by Richard Gange [ 06/Jun/19 ]

Also what do you think about actually "releasing" this?

[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Build Order:
[INFO] 
[INFO] dx-core (parent pom)
[INFO] dx-core: webapp
[INFO]                                                                         
[INFO] ------------------------------------------------------------------------
[INFO] Building dx-core (parent pom) 1.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] 
[INFO] >>> maven-archetype-plugin:2.4:generate (default-cli) > generate-sources @ dx-core >>>
[INFO] 
[INFO] <<< maven-archetype-plugin:2.4:generate (default-cli) < generate-sources @ dx-core <<<
[INFO] 
[INFO] --- maven-archetype-plugin:2.4:generate (default-cli) @ dx-core ---
[INFO] Generating project in Interactive mode
[INFO] No archetype defined. Using maven-archetype-quickstart (org.apache.maven.archetypes:maven-archetype-quickstart:1.0)
Choose archetype:
1: https://nexus.magnolia-cms.com/content/groups/public/ -> info.magnolia.maven.archetypes:magnolia-theme-archetype (An archetype to create STK Theme modules)
2: https://nexus.magnolia-cms.com/content/groups/public/ -> info.magnolia.maven.archetypes:magnolia-project-archetype (An archetype to create a Magnolia project (a parent pom and a webapp))
3: https://nexus.magnolia-cms.com/content/groups/public/ -> info.magnolia.maven.archetypes:magnolia-module-archetype (An archetype to create basic Magnolia modules)
4: https://nexus.magnolia-cms.com/content/groups/public/ -> info.magnolia.maven.archetypes:magnolia-forge-module-archetype (An archetype to create a Magnolia module to be hosted on the Magnolia Forge)
5: https://nexus.magnolia-cms.com/content/groups/public/ -> info.magnolia.maven.archetypes:magnolia-blossom-module-archetype (An archetype to create Magnolia modules using Blossom)
Choose a number or apply filter (format: [groupId:]artifactId, case sensitive contains): : 2
Choose info.magnolia.maven.archetypes:magnolia-project-archetype version: 
1: 1.1.0
2: 1.2.0
3: 1.2.1
4: 1.2.2
5: 1.2.3
6: 1.2.4
7: 1.2.5-SNAPSHOT
Choose a number: 7: 7
Generated at Sun Feb 11 23:23:13 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.