CE and EE packs

Motivation

Sometimes we need release webapps, bundles without releasing magnolia-core, but this is not possible now, because Magnolia main and ce-bundles shares one JIRA project MAGNOLIA. Also version number is retrieved from magnolia-core (/info/magnolia/cms/license/license.xml) or from enterprise module (/info/magnolia/enterprise/license/license.xml).

Introducing ce/ee packs, it's because actual ce-bundle and ee-bundle git repos are too heavy. For example during release when integration tests pass, but then genereating dmg files fails then it's needed to re-release whole bundle project. Plan would be to keep in ce-bundle and ee-bundle only necessary stuff and move all other webapps, bundles and installers into ce/ee-packs.

New structure

3 JIRA projects MAGNOLIA, MGNLCE, MGNLEE and 5 git repos main, ce, ce-packs, ee and ee-packs.

New Product descriptor artifacts

New artifacts

Maven relocations (deprecated artifacts)

Project	Repo	Sub-modules	JIRA issue
MAGNOLIA	main	No changes
MGNLCE	ce former ce-bundle	`magnolia-community-product-descriptor`	MAGNOLIA-6398 - Getting issue details... STATUS
		`magnolia-empty-webapp`
		`magnolia-community-webapp` same as bundled-webapp, without demo	MGNLCE-1 - Getting issue details... STATUS
		`magnolia-integration-tests` still depends on STK, we should consider rewriting tests for mte and demo
		`magnolia-bundled-webapp-maven-relocate` relocation to magnolia-community-demo-webapp	MGNLCE-5 - Getting issue details... STATUS
		`magnolia-tomcat-bundle-maven-relocate` relocation to magnolia-community-demo-bundle	MGNLCE-5 - Getting issue details... STATUS
	ce-packs	`magnolia-community-demo-webapp` same as former bundled-webapp
		`magnolia-community-demo-bundle` same as former tomcat-bundle
		+ other additional webapps and bundles if needed
MGNLEE	ee former ee-bundle	`magnolia-module-enterprise`
		`magnolia-enterprise-standard-product-descriptor`	MGNLEE-402 - Getting issue details... STATUS
		`magnolia-enterprise-pro-product-descriptor`	MGNLEE-402 - Getting issue details... STATUS
		`magnolia-enterprise-standard-webapp` new EE standard webapp, without EE pro modules, and without demo	MGNLEE-403 - Getting issue details... STATUS
		`magnolia-enterprise-pro-webapp` same as former enterprise-webapp, without demo
		`magnolia-ee-integration-tests` still depends on STK, we should consider rewriting tests for mte and demo
		`magnolia-enterprise-webapp-maven-relocate` relocation to magnolia-enterprise-pro-demo-webapp	MGNLEE-412 - Getting issue details... STATUS
		`magnolia-enterprise-bundle-maven-relocate` relocation to magnolia-enterprise-pro-demo-bundle	MGNLEE-412 - Getting issue details... STATUS
	ee-packs	`magnolia-enterprise-standard-demo-webapp` new EE standard webapp, with demo	MGNLEE-403 - Getting issue details... STATUS
		`magnolia-enterprise-pro-demo-webapp` same as former enterprise-webapp
		`magnolia-enterprise-pro-demo-bundle` same as former enterprise-bundle
		`magnolia-enterprise-pro-stk-webapp` new EE pro webapp, with STK and demo-project	MGNLEE-411 - Getting issue details... STATUS
		`magnolia-enterprise-pro-stk-bundle` new bundle for EE pro STK webapp	MGNLEE-411 - Getting issue details... STATUS
		`magnolia-enterprise-weblogic-webapp`
		`magnolia-enterprise-websphere-webapp`
		`magnolia-enterprise-installer` installer for magnolia-enterprise-pro-demo-bundle
		+ other additional webapps and bundles if needed

Page tree

Motivation

New structure

1 Comment

Christoph Meier