Sling Resource Merger and granite tab including | Community
Skip to main content
antond26624417
antond26624417
Level 2
August 17, 2018
Solved

Sling Resource Merger and granite tab including

  • August 17, 2018
  • 2 replies
  • 2128 views

In our project there is usage 2.0.0 version of Core Components.

The problem is that with applying SP2 for AEM 6.3 and upgrading Core Components library to version 2.0.6. (It is system requirements GitHub - Adobe-Marketing-Cloud/aem-core-wcm-components: Adobe Experience Manager (AEM) Sites Core Components - flexible,…​ ) customization(hide/add properties within tabs) for dialog of  "core/wcm/components/page/v2/page" is become broken for our pages. As i understand it's due to changing dialog structure and its tabs is included using "granite/ui/components/foundation/include" and this include breaks Sling Resource Merger mechanism.

Using 2.0.0 within AEM 6.3 SP2 brings also some challenges into OSGI dependencies resolution.
Do we have some any way to resolve this issue?
Thanks in advance.

    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 cwalter-1

    I had some trouble while using Sling Resource Merger & includes too (in 6.1 though). From my experience I can say: don't use both together! Either use the Resource Merging mechanism or includes separately.

    2 replies

    cwalter-1
    cwalter-1Accepted solution
    Level 2
    August 17, 2018

    I had some trouble while using Sling Resource Merger & includes too (in 6.1 though). From my experience I can say: don't use both together! Either use the Resource Merging mechanism or includes separately.

      smacdonald2008
      smacdonald2008
      Level 10
      August 17, 2018

      In AEM 6.3 - when you build the Core Components from Github - is the project building for you and deploying successfully?

      Terms & ConditionsAccessibility statement

      Loading footer...