Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

Is there an AEM version matrix?

jkpanera
Level 5
Level 5

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

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

1 Accepted Solution
Jörg_Hoh
Correct answer by
Employee
Employee

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.

 

View solution in original post

0 Replies
Theo_Pendle
Community Advisor
Community Advisor

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 🙂

jkpanera
Level 5
Level 5
Not exactly what I was after, but somewhat helpful
Theo_Pendle
Community Advisor
Community Advisor
Yeah I know, sorry man 😕 But if the Adobe employee @sunjot16 is saying there's no such matrix, your chances are unfortunately slim :S
sunjot16
Employee
Employee

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.

Nirmal_Jose
Community Advisor
Community Advisor
This will be great addon to our release notes of AEM. Is there a way we can raise it as a formal request.
sunjot16
Employee
Employee
I agree with @Jörg_Hoh . It will be huge. But, we can definitely raise a DocBug request to have such information included with every Service Pack or something, whichever is feasible. Can anyone please raise a Daycare ticket and mention my name in it? It will get assigned to me. I will raise a DocBug request to have such information included in the Release Notes. Thank you !! 🙂
Jörg_Hoh
Correct answer by
Employee
Employee

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.

 

jkpanera
Level 5
Level 5
@Jörg_Hoh I am used to developing with OSS. When I run into issues, I download the source code and even debug into it. Not all of AEM is open, but I'd like to be able to see the code that is open.
Jörg_Hoh
Employee
Employee
Well, you can check the OSGI Webconsole for the exact bundle name and version, and in case it's opensource, you should be able to get the source for it from the usual locations.