Closed mdre closed 4 years ago
Version 1.1.2 work well.
OS: Ubuntu JDK version: 11.0.4 Gradle version: 5.6.2 Vaadin Plugin version: 1.2 Vaadin: 14.0.3
I am encountering the same error. With --info and --debug see it is failing on the following command -
11:52:25.130 [INFO] [org.gradle.process.internal.DefaultExecHandle] Starting process 'command '/home/bob/work/vaadintest/.gradle/yarn/yarn-v1.12.3/bin/yarn''. Working directory: /home/bob/work/vaadintest/build/frontend Command: /home/bob/work/vaadintest/.gradle/yarn/yarn-v1.12.3/bin/yarn --prefer-offline --cwd /home/bob/work/vaadintest/build/frontend init -y 11:52:25.219 [DEBUG] [org.gradle.process.internal.DefaultExecHandle] Changing state to: FAILED 11:52:25.219 [DEBUG] [org.gradle.process.internal.DefaultExecHandle] Process 'command '/home/bob/work/vaadintest/.gradle/yarn/yarn-v1.12.3/bin/yarn'' finished with exit value 139 (state: FAILED)
The following comands executed are successful when executed outside of gradle - cd /home/bob/work/vaadintest/build/frontend /home/bob/work/vaadintest/.gradle/yarn/yarn-v1.12.3/bin/yarn --prefer-offline --cwd /home/bob/work/vaadintest/build/frontend init -y
Not sure how to further debug why yarn is returning exit code 139.
Hi, I tested the Zip file and updated the plugin version to 1.3.beta5
and got the following;
> Task :build
***************************************************************
SISTEMA: build
VERSION: 0.2.0.3
***************************************************************
BUILD SUCCESSFUL in 11s
12 actionable tasks: 7 executed, 5 up-to-date
So looks like it works with the latest plugin. Please update to the latest version and re-open if you still are having issues.
Desktop (please complete the following information):
Describe the bug The build process fail with this error:
The plugin work well combined with the 'war' plugin, but fail for 'java' plugin. It was working well but now it fail.
test.zip
To Reproduce Steps to reproduce the behavior:
Expected behavior It must build a .jar file in the lib diretory