AEM 6.3 | Upgrade from AEM 6.0 to AEM 6.3 | Community
Skip to main content
ak481808
ak481808
Level 2
April 13, 2017
Solved

AEM 6.3 | Upgrade from AEM 6.0 to AEM 6.3

  • April 13, 2017
  • 3 replies
  • 1968 views

Hello, I was trying to use the beta version of AEM 6.3. I thought of spinning up the 6.3 beta instance and deploy the existing package and bundles. But after doing so, everything started failing. There are lots of missing dependencies in the bundle and the UI package got imported with error.

Here is an excerpt of the error log:

12.04.2017 15:42:45.017 *ERROR* [0:0:0:0:0:0:0:1 [1491991949225] GET /libs/granite/core/content/login.html HTTP/1.1] org.apache.sling.servlets.resolver.internal.SlingServletResolver Original error class java.io.IOException
java.io.IOException: Unable to get component of class 'interface org.apache.sling.rewriter.Transformer' with type 'versioned-clientlibs'.
    at org.apache.sling.rewriter.impl.PipelineImpl.getPipelineComponent(PipelineImpl.java:160)
    at org.apache.sling.rewriter.impl.PipelineImpl.init(PipelineImpl.java:102)

Any one else got this error? When can we expect the 6.0 to 6.3 upgrade planning docs?

Thank you

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Best answer by DominikSu

    The prerelease documentation for upgrades can be found at https://docs.adobe.com/content/docs/en/aem/prerelease/upgrade.html. Nevertheless we anyways recommend to test and adjust the application with some small test content package on a blank instance before focusing on the upgrade itself.

    What you would need to do is to recompile the existing application against the latest uber jar. I'm not entirely sure how this is shipped in the beta program  but for GA it will be made publicly available through our maven repo. In case you are hitting breaking APIs you might need to consult the javadocs and on removal check the last javadoc versions to find replacement instructions in the deprecation notice of the javadocs.

    The versioned-clientlibs message might also relate to usage of the ACS Commons features which are provided by Adobe Consulting Services as open source project but are not part of the product - for backwards compatibility you would need to deploy the latest release of ACS commons which should already be made compatible with AEM 6.3.

    HTH

    Dominik

    3 replies

    D
    Adobe Employee
    DominikSuAdobe EmployeeAccepted solution
    Adobe Employee
    April 13, 2017

    The prerelease documentation for upgrades can be found at https://docs.adobe.com/content/docs/en/aem/prerelease/upgrade.html. Nevertheless we anyways recommend to test and adjust the application with some small test content package on a blank instance before focusing on the upgrade itself.

    What you would need to do is to recompile the existing application against the latest uber jar. I'm not entirely sure how this is shipped in the beta program  but for GA it will be made publicly available through our maven repo. In case you are hitting breaking APIs you might need to consult the javadocs and on removal check the last javadoc versions to find replacement instructions in the deprecation notice of the javadocs.

    The versioned-clientlibs message might also relate to usage of the ACS Commons features which are provided by Adobe Consulting Services as open source project but are not part of the product - for backwards compatibility you would need to deploy the latest release of ACS commons which should already be made compatible with AEM 6.3.

    HTH

    Dominik

      ak481808
      ak481808Author
      Level 2
      April 14, 2017

      Hi @Dominik

      Dominik Suess wrote...

      The prerelease documentation for upgrades can be found at https://docs.adobe.com/content/docs/en/aem/prerelease/upgrade.html. Nevertheless we anyways recommend to test and adjust the application with some small test content package on a blank instance before focusing on the upgrade itself.

      What you would need to do is to recompile the existing application against the latest uber jar. I'm not entirely sure how this is shipped in the beta program  but for GA it will be made publicly available through our maven repo. In case you are hitting breaking APIs you might need to consult the javadocs and on removal check the last javadoc versions to find replacement instructions in the deprecation notice of the javadocs.

      The versioned-clientlibs message might also relate to usage of the ACS Commons features which are provided by Adobe Consulting Services as open source project but are not part of the product - for backwards compatibility you would need to deploy the latest release of ACS commons which should already be made compatible with AEM 6.3.

      HTH

      Dominik

       

      Hi Dominik, Thank you for the information. It is quite helpful.

      ak481808
      ak481808Author
      Level 2
      May 5, 2017

      Hi Domink,

      The link you gave (https://docs.adobe.com/content/docs/en/aem/prerelease/upgrade.html) is not working now. Could you please provide the new link?

      Terms & ConditionsAccessibility statement

      Loading footer...