Is there an AEM version matrix?

Avatar

Avatar

jkpanera

Avatar

jkpanera

jkpanera

08-05-2020

Is there a matrix somewhere which maps AEM versions to the versions of sling, jcr, oak, and jackrabbit?

AEM JCR oak sling

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar

Jörg_Hoh

Employee

Total Posts

3.0K

Likes

942

Correct Reply

1.0K

Avatar

Jörg_Hoh

Employee

Total Posts

3.0K

Likes

942

Correct Reply

1.0K
Jörg_Hoh
Employee

09-05-2020

There is no exact matching, because if you add the service packs and the lots of Sling bundles to it, it would be getting huge. And the benefit would be questionable.

 

My rules of thumb:

 

* AEM 6.0: Oak 1.0.x

* AEM 6.1: Oak 1.2.x

* AEM 6.2: Oak 1.4.x

* AEM 6.3: Oak 1.6.x

* AEM 6.4: Oak 1.8.x

* AEM 6.5: Oak 1.10.x 

 

Sling does not have a consistent version, as the bundles are typically versioned independently of each other, and also the inclusion of these bundles seems sometimes quite random.

For what do you need that? Maybe there's a way to fullfill your requirement without the exact knowledge of all of these versions.

 

Answers (3)

Answers (3)

Avatar

Avatar

Andrew_Khoury

Employee

Avatar

Andrew_Khoury

Employee

Andrew_Khoury
Employee

11-05-2020

@jkpanera for now, until we have such documentation, you could search the json in this tool for the versions:

https://helpx.adobe.com/experience-manager/kb/tools/bundle-version-checker.html

Avatar

Avatar

sunjot16

Employee

Avatar

sunjot16

Employee

sunjot16
Employee

08-05-2020

I don't think there's any matrix or document that specifies the versions of sling, jcr, oak, and jackrabbit specific to each AEM version.

Avatar

Avatar

Theo_Pendle

MVP

Avatar

Theo_Pendle

MVP

Theo_Pendle
MVP

08-05-2020

Perhaps someone will correct me but as far as I know, no there isn't 😕

However, if you're doing an upgrade and you're worried about versions, just make sure that:

  • Your Java Maven project includes the right uber-jar dependenciy
  • Your oak-run.jar version corresponds to the version visible in CRX DE: 
    theop76211228_0-1588959112728.png
  • Your AEM forms version corresponds to the AEM version (if you have AEM Forms)
  • Your ACS Commons version is compatible with your AEM version (in this case there is a compatibilitiy matrix: https://adobe-consulting-services.github.io/acs-aem-commons/pages/compatibility.html
  • Your AEM Core Components is the latest version and is referenced/embeded in you Java Maven project as opposed to manual upload.

Sorry that this answer is a bit of a deflection, hopefully it's useful to you or someone else 🙂