Details
-
Task
-
Resolution: Unresolved
-
Neutral
-
None
-
None
-
None
Description
- this is a corner case that the bot doesn't support, even goes against Maven principles, requiring manual involvement
- dx-core bundles content-editor v1 and then the demo showcases content-editor v2. hence, we could rollback the content-editor v2 back to v1 when 6.3 comes out
- that way releasing both branches is easy, 6.2 keeps its relevant maintenance v1 version and 6.3 can showcase content-editor v2
Background
Why have we shipped two different versions of content-editor so far?
6.2 still ships with content-editor v1 by default (in dx-core-webapp), because upgrading to v2 is not directly compatible (change of data structure, hence required changes in project templates), only the demo-webapp bumps it to v2
Problems
- 6.2.40's release included a SNAPSHOT version of content-editor v2 because content-editor v1 had been released by hand and since v2 version is not managed in root pom, it is out of the bot's reach. This problem could easily have been avoided by releasing v2 manually instead, but given we don't do such releases frequently, this is hard to remember. Also, the release process shouldn't require manual steps.
- In 6.2.27, Maxime & Federico tried to allow the bot to manage both versions, in the end this resulted in broken customer setups. The reason isn't 100% clear but customers got their content-editor v1 version upgraded to v2. See:
- because of the pecularities with the setup, and adding to the complexity of the situation, we have to have a dedicated VersionMatcher for content-editor (info.magnolia.mgmt.service.preflight.ThreeWayVersionMatcher.ContentEditorThreeWayMatcher)
Checklists
Acceptance criteria
Attachments
Issue Links
- is related to
-
BUILD-1179 Introduce a safety net step that makes sure there is no leftover SNAPSHOT after automatic dependency resolution
-
- Closed
-