<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <title>Got exception on theme build liferay 7.3.5</title>
  <link rel="self" href="https://liferay.dev/c/message_boards/find_thread?p_l_id=119785294&amp;threadId=120535702" />
  <subtitle>Got exception on theme build liferay 7.3.5</subtitle>
  <id>https://liferay.dev/c/message_boards/find_thread?p_l_id=119785294&amp;threadId=120535702</id>
  <updated>2026-04-04T21:58:40Z</updated>
  <dc:date>2026-04-04T21:58:40Z</dc:date>
  <entry>
    <title>RE: Got exception on theme build liferay 7.3.5</title>
    <link rel="alternate" href="https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&amp;messageId=120536214" />
    <author>
      <name>Olaf Kock</name>
    </author>
    <id>https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&amp;messageId=120536214</id>
    <updated>2021-01-05T08:56:25Z</updated>
    <published>2021-01-05T08:56:25Z</published>
    <summary type="html">&lt;p&gt;I haven't tried this, but IMHO themes are so dependent on little
  details that I'd not assume that skipping two versions results in a
  usable theme on the newer version. There are so many updates of
  underlying libraries, the HTML DOM, etc that at the very least you're
  starting in a weirder place than when you create a new theme in the
  target environment and carry over individual theme elements piece by
  piece - validating if they need tweaking or not. This way, the change
  that you'll need to introduce is manageable, and it doesn't mean a
  completely new theme development.&lt;/p&gt;
&lt;p&gt;Upgrading a theme as a monolith, fixing all appearing issues in buld
  doesn't sound appealing to me.&lt;/p&gt;
&lt;p&gt;Note: That's my personal approach. It might well be that there's a
  claim that themes are upgradable, but with all designs that have been
  applied to an older version, I don't assume that they can be applied
  unchanged to a newer version and deliver the same (or even a usable) result.&lt;/p&gt;</summary>
    <dc:creator>Olaf Kock</dc:creator>
    <dc:date>2021-01-05T08:56:25Z</dc:date>
  </entry>
  <entry>
    <title>Got exception on theme build liferay 7.3.5</title>
    <link rel="alternate" href="https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&amp;messageId=120535701" />
    <author>
      <name>Deepak Panda</name>
    </author>
    <id>https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&amp;messageId=120535701</id>
    <updated>2021-01-04T14:36:29Z</updated>
    <published>2021-01-04T14:36:29Z</published>
    <summary type="html">&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;I have one theme previously deployed on liferay 7.1.1, now I want to
  deploy it on liferay 7.3.5.&lt;/p&gt;
&lt;p&gt;But at the time of build creation with 7.3.5 it shows below error,
  kindly help to resolve it.&lt;/p&gt;
&lt;p&gt;
  &lt;u&gt;
    &lt;strong&gt;Error Log&lt;/strong&gt;&lt;/u&gt;&lt;/p&gt;
&lt;p&gt; BridJ: LoadLibrary error when loading
  C:\Users\XXXXX\AppData\Local\Temp\BridJExtractedLibraries6231663513559297866\liferaysass.dll
  : A dynamic link libException in thread &amp;quot;main&amp;quot;
  java.lang.UnsatisfiedLinkError:
  com.liferay.sass.compiler.jni.internal.libsass.LiferaysassLibrary.sassMakeFileContext(J)J&lt;br /&gt;    at
  com.liferay.sass.compiler.jni.internal.libsass.LiferaysassLibrary.sassMakeFileContext(Native
  Method)&lt;br /&gt;    at
  com.liferay.sass.compiler.jni.internal.libsass.LiferaysassLibrary.sassMakeFileContext(LiferaysassLibrary.java:1275)&lt;br /&gt;    at
  com.liferay.sass.compiler.jni.internal.JniSassCompiler.createSassFileContext(JniSassCompiler.java:292)&lt;br /&gt;    at
  com.liferay.sass.compiler.jni.internal.JniSassCompiler.compileFile(JniSassCompiler.java:147)&lt;br /&gt;    at
  com.liferay.css.builder.CSSBuilder._parseSass(CSSBuilder.java:380)&lt;br /&gt;    at
  com.liferay.css.builder.CSSBuilder._parseSassFile(CSSBuilder.java:394)&lt;br /&gt;    at
  com.liferay.css.builder.CSSBuilder.execute(CSSBuilder.java:160)&lt;br /&gt;    at com.liferay.css.builder.CSSBuilder.main(CSSBuilder.java:79)&lt;/p&gt;
&lt;p&gt;build.gradle&lt;/p&gt;
&lt;p&gt;-------------------------&lt;/p&gt;
&lt;p&gt;buildscript {&lt;br /&gt;    dependencies {&lt;br /&gt;        classpath group:
  &amp;quot;com.liferay&amp;quot;, name:
  &amp;quot;com.liferay.gradle.plugins.theme.builder&amp;quot;, version: &amp;quot;2.0.5&amp;quot;&lt;br /&gt;    }&lt;/p&gt;
&lt;p&gt;    repositories {&lt;br /&gt;        maven {&lt;br /&gt;            url &amp;quot;https://repository-cdn.liferay.com/nexus/content/groups/public&amp;quot;&lt;br /&gt;        }&lt;br /&gt;    }&lt;br /&gt;}&lt;/p&gt;
&lt;p&gt;apply plugin: &amp;quot;com.liferay.portal.tools.theme.builder&amp;quot;&lt;/p&gt;
&lt;p&gt;dependencies {&lt;br /&gt;    parentThemes group: &amp;quot;com.liferay&amp;quot;,
  name: &amp;quot;com.liferay.frontend.theme.styled&amp;quot;, version:
  &amp;quot;3.0.4&amp;quot;&lt;br /&gt;    parentThemes group:
  &amp;quot;com.liferay&amp;quot;, name:
  &amp;quot;com.liferay.frontend.theme.unstyled&amp;quot;, version:
  &amp;quot;3.0.4&amp;quot;&lt;br /&gt;    portalCommonCSS group:
  &amp;quot;com.liferay&amp;quot;, name:
  &amp;quot;com.liferay.frontend.css.common&amp;quot;, version:
  &amp;quot;3.0.1&amp;quot;&lt;br /&gt;    themeBuilder group:
  &amp;quot;com.liferay&amp;quot;, name:
  &amp;quot;com.liferay.portal.tools.theme.builder&amp;quot;, version:
  &amp;quot;1.1.6&amp;quot;&lt;br /&gt;    cssBuilder group: &amp;quot;com.liferay&amp;quot;,
  name: &amp;quot;com.liferay.css.builder&amp;quot;, version: &amp;quot;2.1.3&amp;quot; &lt;br /&gt;}&lt;br /&gt; &lt;/p&gt;</summary>
    <dc:creator>Deepak Panda</dc:creator>
    <dc:date>2021-01-04T14:36:29Z</dc:date>
  </entry>
</feed>
