0

I created a JS client-extension for Liferay 7.4 (U60). Everything works fine on my local environment, but after deploying to our Dev environment through a Jenkins pipeline, I’m getting 404 Not Found errors in the browser console.

The generated script URLs look incorrect—they are being concatenated repeatedly, for example:
https://mibldev.infoaxon.com/o/mibl-global-js/global.29c4a4a957b9f8a361af59c64e6e38ffee53ecb7.js/o/mibl-global-js/global.4cd080595d96f0775f3020105be232dbcd0639f4.js/o/mibl-global-js/global.53955147c32c9075ae33db7d46ab44d341ffe2dd.js ...

This obviously leads to a 404, but I’m not sure why it only happens after Jenkins deployment, while it works perfectly on my local machine.

Has anyone faced this issue with JS client-extensions in Liferay 7.4? What could cause the URL to be generated incorrectly in Dev, and how can I fix it?

for reference my .yaml file is -

assemble:
    -   from: src
        hashify: global.js
        into: static
mibl-global-js:
    name: Mibl Global JS
    type: globalJS
    url: global.*.js

Any help would be appreciated!

Improve this question
Related questions
12225
How can I remove a specific item from an array in JavaScript?
7610
How do JavaScript closures work?
8540
What does "use strict" do in JavaScript, and what is the reasoning behind it?
Load 7 more related questions Show fewer related questions

0

Reset to default

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.