Possible solutions
Separate branch
- special branch on of enterprise-bundle https://git.magnolia-cms.com/projects/PLATFORM/repos/ee/browse?at=refs%2Fheads%2Fmagnolia-enterprise-bundle-5.4.x-cp13n which contains only
- magnolia-ee-integration-tests-fixture-module-cp13n
- magnolia-ee-test-public-webapp-cp13n
- magnolia-ee-test-webapp-cp13n
- tests-cp13n
- special branch on of ee-packs
- special artefacts IDs (-cp13n)
- hudson job https://jenkins.magnolia-cms.com/job/ee_bundle-5.4.x-cp13n-with-selenium_profile/
- nexus, same folder, different artefacts names https://nexus.magnolia-cms.com/content/groups/enterprise/info/magnolia/eebundle/magnolia-enterprise-pro-webapp-cp13n/
- special branch for ee-packs which contains only, hudson job for it
cp13n is completely separated
cp13n ee and ee-packs has to be release per every 5.4.x release
Include cp13n as separate artefact into the current branch
- enterprise bundle would include:
- enterprise-pro-webapp-cp13n
- enterprise-test-webapp-cp13n
- enterprise-test-public-webapp-cp13n
- additional mvn profile which would include tests for cp13n
- no need of a separate release
- not independent, need to back port component personalisation tests
Include cp13n into the default bundle
- no extra work
- includes major version of personalization into the minor version of 5.4
- we would force customers to update web apps, magnolia.properties...
Overview
Content Tools
Apps
Activity