• 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.