We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Lets say that you have two themes in a Liferay Workspace and wondering how to do it specifically in a CI build.
@jbalsas suggested the use of manually adding relative paths in the package.json. You can see I've added an example of that here:
https://github.com/gamerson/two-themes-test/blob/main/themes/extended-theme/package.json#L19 https://github.com/gamerson/two-themes-test/blob/main/themes/extended-theme/package.json#L45
Ideally, it would be good to add some more "tooling" up front to help developers in a Liferay workspace configure these relative paths.
The text was updated successfully, but these errors were encountered:
cc @david-truong
Sorry, something went wrong.
@gamerson Is this still needed? I guess it is...
Closing this due to inactivity
No branches or pull requests
Lets say that you have two themes in a Liferay Workspace and wondering how to do it specifically in a CI build.
@jbalsas suggested the use of manually adding relative paths in the package.json. You can see I've added an example of that here:
https://github.com/gamerson/two-themes-test/blob/main/themes/extended-theme/package.json#L19
https://github.com/gamerson/two-themes-test/blob/main/themes/extended-theme/package.json#L45
Ideally, it would be good to add some more "tooling" up front to help developers in a Liferay workspace configure these relative paths.
The text was updated successfully, but these errors were encountered: