Expand my Community achievements bar.

SOLVED

updating jar file versions

Avatar

Level 4

Hi,

As part of our recent upgrade from 5.5 to 5.6.1 we need to update the versions of some of our jars eg cq-commons-5.5. My question is inside the adobe repo what version of the jars should we be using for 5.6.1 and do we need to update the author/publish instance with the jars from the repo?

Thanks

Chris 

1 Accepted Solution

Avatar

Correct answer by
Level 10

I recommend reading this AEM topic that talks about upgrading AEM:

https://dev.day.com/docs/en/cq/current/deploying/upgrading.html

https://dev.day.com/docs/en/cq/current/deploying/upgrading/planning.html

If you want to take advantage of some of the latest features in AEM 5.6  - you may have to update some of  your OSGi bundles with AEM 5.6 JAR files. For example - assume that in 5.5 -- you wrote a custom workflow step using Java APIs located in this Java package:

com.day.cq.workflow.exec.*

In AEM 5.6 -- you can build a custom workflow step using Java APIs located in this package:

com.adobe.granite.workflow.exec.*

In this situation - you have to update your OSGi bundle (that represents the custom workflow step) and reference the newer AEM JARS in your bundle.

Also - take a look at this forum thread - its related:

http://help-forums.adobe.com/content/adobeforums/en/experience-manager-forum/adobe-experience-manage...

Hope this helps

View solution in original post

1 Reply

Avatar

Correct answer by
Level 10

I recommend reading this AEM topic that talks about upgrading AEM:

https://dev.day.com/docs/en/cq/current/deploying/upgrading.html

https://dev.day.com/docs/en/cq/current/deploying/upgrading/planning.html

If you want to take advantage of some of the latest features in AEM 5.6  - you may have to update some of  your OSGi bundles with AEM 5.6 JAR files. For example - assume that in 5.5 -- you wrote a custom workflow step using Java APIs located in this Java package:

com.day.cq.workflow.exec.*

In AEM 5.6 -- you can build a custom workflow step using Java APIs located in this package:

com.adobe.granite.workflow.exec.*

In this situation - you have to update your OSGi bundle (that represents the custom workflow step) and reference the newer AEM JARS in your bundle.

Also - take a look at this forum thread - its related:

http://help-forums.adobe.com/content/adobeforums/en/experience-manager-forum/adobe-experience-manage...

Hope this helps