I'm migrating to a new Windows Server 2016 build server and running into gradlew build errors when it tries to compile the first portlet module in the Liferay CE 7.0.4 GA5 workspace. On the gradle "task" buildCSS, I see:
Using native Sass compiler
# BridJ: LoadLibrary error when loading C:\Users\WES-DA~3\AppData\Local\Temp\BridJExtractedLibraries3401615323110354692\liferaysass.dll : A dynamic link library (DLL) initialization routine failed
I think I am just missing an installation, version incompatibility, or path issues on the new server. Here are some of the new build server installation details:
node v8.9.4, npm 5.6.0
Python 3.7.6, pip 20.0.1
openjdk version "1.8.0_212", OpenJDK Runtime Environment (AdoptOpenJDK)(build 1.8.0_212-b03), OpenJDK 64-Bit Server VM (AdoptOpenJDK)(build 25.212-b03, mixed mode)
npm global packages (output from npm list -g --depth 0)+-- bower@1.8.8
+-- grunt@1.0.4
+-- grunt-cli@1.3.2
+-- gulp-cli@2.2.0
+-- karma-cli@2.0.0
+-- npm@5.6.0
+-- protractor@5.4.2
`--
windows-build-tools@5.2.2I saw a similar error reported that was due to JDK 11, but since OpenJDK 1.8 is being used on the new build server. I have also confirmed the path C:\Users\WES-DA~3\AppData\Local\Temp\BridJExtractedLibraries3401615323110354692\liferaysass.dll does not exist before or after the build. During the build the folder appears with the dll present, and when I make a copy of the dll (during the build) I can see the liferaysass.dll has a file version 1.0.0.0 and product version 0.9.0.0. I've been comparing the new build server to the old working MS server 2012 and the only differences seem to be the old server has python 2.7 on the system path, and it doesn't have the windows-build-tools global npm package installed either. Thanks for any advice.
-Luke
