Ask Questions and Find Answers
Important:
Ask is now read-only. You can review any existing questions and answers, but not add anything new.
But - don't panic! While ask is no more, we've replaced it with discuss - the new Liferay Discussion Forum! Read more here here or just visit the site here:
discuss.liferay.com
RE: Won't build
Ran build but get the following error:
Unzipping
/home/rognod/.gradle/wrapper/dists/gradle-3.3-bin/64bhckfm0iuu9gap9hg3r7ev2/gradle-3.3-bin.zip
to
/home/rognod/.gradle/wrapper/dists/gradle-3.3-bin/64bhckfm0iuu9gap9hg3r7ev2
Exception in thread "main" java.util.zip.ZipException: error
in opening zip file
at java.util.zip.ZipFile.open(Native
Method)
at
java.util.zip.ZipFile.<init>(ZipFile.java:225)
at
java.util.zip.ZipFile.<init>(ZipFile.java:155)
at
java.util.zip.ZipFile.<init>(ZipFile.java:169)
at
org.gradle.wrapper.Install.unzip(Install.java:215)
at
org.gradle.wrapper.Install.access$600(Install.java:27)
at org.gradle.wrapper.Install$1.call(Install.java:75)
at
org.gradle.wrapper.Install$1.call(Install.java:48)
at
org.gradle.wrapper.ExclusiveFileAccessManager.access(ExclusiveFileAccessManager.java:69)
at
org.gradle.wrapper.Install.createDist(Install.java:48)
at
org.gradle.wrapper.WrapperExecutor.execute(WrapperExecutor.java:107)
at
org.gradle.wrapper.GradleWrapperMain.main(GradleWrapperMain.java:61)
any ideas on how to fix? Thanks
Has anyone else been successful at getting emporio to build?
unfortunately, I also failed to build.
I don't know if there are detailed build guides, including build tools, dependent versions, Environment configuration, etc.,I always had different errors during the building process, which may be the problems with tools and environment settings.
any good news, please share.
thanks for the reply. I just followed Liferays' Github instructions for building. Did not work. Hopefully, someday Liferay staff will reply with fix.
thanks
Ok - a little bit further along. I deleted gradle-3.3.bin folder and then ran the command again. This time it unzipped and started the build. However, the build failed and I got this error:
Caused by: org.gradle.process.internal.ExecException: Process
'command
'/home/rognod/books/com-liferay-commerce/build/node/bin/node''
finished with non-zero exit value 1
at org.gradle.process.internal.DefaultExecHandle$ExecResultImpl.assertNormalExitValue(DefaultExecHandle.java:369)
Not sure how to fix this. Any thoughts?
I could build it, but I cheated a bit. For me it failed with "Unable to find com.liferay.dynamic.data.mapping.taglib.jar in /home/crabel/shoptest/bundles/osgi"
So, I took a beta of Liferay 7.1, since those modules are there unpacked in that version and copied it in the bundles folder. After building it, I copied all commerce modules to the real Liferay instance (note: for some reason it has to be up and running, commerce doesn't work when you add it to osgi/modules and start Liferay)
Christoph: Thanks for this post. What beta version did you use? Can't wait to try!
thanks again
Beta 3. You probably could also unpack the lpkg files and place them into the osgi/modules folder.
Christoph: Thanks really appreciate it. Have you been able to play with commerce?
My error is as follows:
npminstall
node install
What I don't understand is that I have installed npm and node. Why do some module build require npminstall and node install again to add packages, and some module build don't need.
Attachments:
Modules usually download their own node instance and place it in build/ and use that one instead of the globally installed node. Of course, that commerce module might be configured otherwise (there are options available to configure the node build task https://dev.liferay.com/develop/reference/-/knowledge_base/7-0/node-gradle-plugin ).
That said, the problem seems to be Windows specific:
https://github.com/gradle/gradle/issues/882
Maybe you could try to replace gradle 3.3 with gradle 3.4?
hi,
while building ,some modules are successful and someone failed.
so i delete the modules which are successful and build the failed modules again and again.
i build all modules finally, so if failed just to try it again. i do not know the reason but it work.
Christoph Rabel:That said, the problem seems to be Windows specific:
https://github.com/gradle/gradle/issues/882
Maybe you could try to replace gradle 3.3 with gradle 3.4?
I had the same problem and solved, as suggested in the issue comments, issuing the command:
gradlew.bat deploy -Dbuild.profile=portal --console plain
HTH,
Denis
Powered by Liferay™