AEM 5.6.1 embedded client libraries compilation issue. | Community
Skip to main content
D
DPM
Level 2
October 16, 2015
Solved

AEM 5.6.1 embedded client libraries compilation issue.

  • October 16, 2015
  • 5 replies
  • 1087 views

Hi Guys,

We currently have an issue with embedded client libraries often breaking when changes to CSS or JS have been made, and also when deploying packages to publish.

We have a workaround, which is to rename the client library and rename it back. This gets it to recompile and work.

Is there a known cause for this?

Something which we can do differently to prevent the need for this fix.

We have had this issue since 5.4, and even the adobe help desk did not come up with an answer.

Thanks

Damian.

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 Sham_HC

Seems like custom issue or related to less. File an support ticket by attaching "com.day.cq.widget" to Loglevel DEBUG & repeating test case.

5 replies

joerghoh
Adobe Employee
joerghohAdobe Employee
Adobe Employee
October 16, 2015

Hi Damian,

so you change a single CSS or Javascript file, and this change isn't reflected in the respective clientlib? Do you see any suspicius messages when you set "com.day.cq.widget" to Loglevel DEBUG?

kind regards,
Jörg

D
DPMAuthor
Level 2
October 16, 2015

Hi Guys.

 

We are running "5.6.1", but have had this issue since "5.4".

I am assuming it is caused by changes to JS and CSS that are embedded. It happens from time to time in auth, and almost always in publish when we deploy.

It's not that the client library is not reflecting the changes, it's that it stops working altogether. We have to get it to recompile by renaming and renaming it back.

Thanks.

-Damian

D
DPMAuthor
Level 2
October 16, 2015

I have tried

 http://server:port//libs/granite/ui/content/dumplibs.rebuild.html.

This did not clear the issue.

Sham_HC
Sham_HCAccepted solution
Level 10
October 16, 2015

Seems like custom issue or related to less. File an support ticket by attaching "com.day.cq.widget" to Loglevel DEBUG & repeating test case.

Terms & ConditionsAccessibility statement

Loading footer...