[MGNLGROOVY-163] Remove uses of the Content API Created: 14/Jul/17  Updated: 21/Nov/17  Resolved: 29/Aug/17

Status: Closed
Project: Magnolia Groovy Module
Component/s: None
Affects Version/s: None
Fix Version/s: 2.6

Type: Task Priority: Neutral
Reporter: Michael Mühlebach Assignee: Federico Grilli
Resolution: Fixed Votes: 0
Labels: tech-debt
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to DOCU-1235 Update "Groovy module" page Closed
is related to MGNLGROOVY-164 Remove code deprecated since 2.4.x (n... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Release notes required:
Yes
Documentation update required:
Yes
Date of First Response:
Epic Link: Remove Content API
Sprint: Basel 106, Basel 107, Basel 108, Basel 109, Basel 110, Basel 111
Story Points: 8

 Description   

see https://wiki.magnolia-cms.com/pages/viewpage.action?pageId=136852051 for further detail.



 Comments   
Comment by Federico Grilli [ 18/Oct/17 ]

@docuteam:

  • Maven group id changed from info.magnolia to info.magnolia.groovy
  • artifact ids changed as follows
    • magnolia-module-groovy -> magnolia-groovy-compatibility (for the backward compatible one)
    • magnolia-module-groovy -> magnolia-groovy (name of the new shiny imaging module)

Maven relocations are provided to point users referring to old group and artifact ids in their pom.xml to the new artifacts
E.g. assume a user has

 <dependency>
        <groupId>info.magnolia</groupId>
        <artifactId>magnolia-module-groovy</artifactId>
        <version>2.6</version>
      </dependency>

that will cause a redirection to the artifact info.magnolia.groovy:magnolia-groovy-compatibility which is Content API compatible. A message in the console/logs will encourage such user to update to the latest artifact info.magnolia.groovy:magnolia-groovy which is Content API free.

Generated at Mon Feb 12 05:56:12 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.