Gradle/Grails: Task 'start' not found in project ':client' - vue.js

I followed the following guide to create a Grails Project with Vue Profile. https://grails-profiles.github.io/vue/latest/guide/
First:
When i run ./gradlew server:bootRun the process is stuck at 85%, but correctly displays Grails application running at http://localhost:8080 in environment: development and the localhost page is accessible.
Then:
When running ./gradlew client:start, the build Fails stating:
Starting a Gradle Daemon, 1 busy and 2 stopped Daemons could not be reused, use --status for details
FAILURE: Build failed with an exception.
* What went wrong:
Task 'start' not found in project ':client'.
* Try:
Run gradlew tasks to get a list of available tasks. Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
* Get more help at https://help.gradle.org
The funny thing is it worked before, but as i decided to start over i deleted the project folder and created a new one according to the guide, it wasn't working anymore.
Has anyone experienced a similar error?

When i run ./gradlew server:bootRun the process is stuck at 85%, but
correctly displays Grails application running at http://localhost:8080
in environment: development and the localhost page is accessible.
If you are asking if that indicates something is wrong, it doesn't. That is expected behavior. It never gets to 100% because the task is running as long as the app is running.
Then: When running ./gradlew client:start, the build Fails stating:
That is likely a mistake in the docs. ./gradlew client:serve should work.
Has anyone experienced a similar error?
Likely yes. We will get the docs updated.

Related

React Native FAILURE: Build failed with an exception. I need someone to look at this?

What went wrong:
Could not open settings generic class cache for settings file 'C:\Users\Nelson Ndimba\Documents\MTN-YelloHive\android\settings.gradle' (C:\Users\Nelson Ndimba.gradle\caches\7.1.1\scripts\4gzdkdviqbv5h262ml6gwf2d7).
BUG! exception in phase 'semantic analysis' in source unit 'BuildScript' Unsupported class file major version 63
Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
Get more help at https://help.gradle.org
i think the problems come from your Java version.
did you install JDK11 as mentioned in the CLI project set up ?
if yes and the problem is always there then make sure to add a variable envirenement to your system named JAVA_HOME with value :
"C:\Program Files\Eclipse Adoptium\jdk-11.0.16.101-hotspot"
Note 1: make sure to restart you PC after this.
Note 2: the path may change based on the jdk 11 subversion and where your system stores installed software

"Could not open init generic class cache for initialization script"

Hi everyone am new to Kotlin language , i have encountered some errors in the process of running the Hello World code.
Could not open init generic class cache for initialization script 'C:\Users\HP\AppData\Local\Temp\wrapper_init.gradle' (C:\Users\HP.gradle\caches\6.8\scripts\5mjee5vr2mabvvexqryui51pg).
BUG! exception in phase 'semantic analysis' in source unit 'BuildScript' Unsupported class file major version 60
Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
Any help will be appreciated. Thanks in advance
I caught this problem by downloading a different version of Java. I had version 16 installed, however the IDE (IntelliJ) warned me that Gradle was not compatible with this latest version, so I installed version 11. If the configuration of the project points to version 11, and that error that you show in console was corrected.
Here is the link to the OpenJDK: https://jdk.java.net/archive/

react-native run-android randomly not able to delete or create folder

I am running on Windows 10:
Permission to the folder is Everyone & Full Access.
Cmd line is set to Administrator.
--version react-native-cli: 2.0.1
--version react-native: 0.47.2
* What went wrong:
Execution failed for task ':#myApp/react-native-spinkit:mergeReleaseResources'.
> java.io.IOException: Could not delete path 'C:\Users\My\Desktop\App\node_modules\#myApp
\react-native-spinkit\android\build\intermediates\res\merged\release\drawable-xhdpi-v4'.
For example, I will get the error above. Sometimes it says could not delete some intermediate path, sometimes, it says it could not create them.
It is not a fixed error output, intermediate folders that got into trouble is different every time. When I repeat React-native run-android on the good days 2-3 times, it will compile successfully. On the bad days I will repeat the cmd 10-15 times, then it suddenly works.
By the way, I use android/gradlew clean command to make sure it does the cleaning, too.
One thing I noticed is that every time it fails the compile percentage % gets a bit further. Until the end if I see 100% then it will work.
The same code compiles in one go with Mac, android physical or virtual machine, same thing on Mac is very stable. This problem only happens with my Windows setup. Anyone experiencing the same thing as me? Is there anything I can do to fix this issue?
You can try this: Error:Execution failed for task ':app:processDebugResources'. > java.io.IOException: Could not delete folder "" in android studio
Deleting the /build folder did it for me.
I guess some of the files in the target build directory is open in another tool you use. Just a file handle open in the folder which has to be cleaned. The build task 'clean' wants to delete all the files in the build directory(normally 'target') and when it fails, the build fails.
This worked for me:
cd ./android && ./gradlew app:assembleDebug && ./gradlew installDebug

intelliJidea plus Gradle, where can i find Compiler Ouput?

Don't know if this is because android-studio does something wrong, or just common to all gradle projects in intelliJ, but sometimes when i run the build/debug, all I get is:
Gradle:
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':ProjectA:compileDebug'.
> Compilation failed; see the compiler error output for details.
* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.
I can't seem to find any way to get more information, as this text already appear on what i consider to be the compiler output.
Where should I be looking at?
One thing I've done to get some better information is go to the project root via the command line and run
gradlew compileDebug
this does give more information, but I'm not 100% sure its running the same command as the IDE.

StatLight hangs when run from TeamCity as single command

I'm running TeamCity 6.5 on a Windows Server, with a couple of build agents on the same server (all running as the system user as services). I had been building SilverLight projects and running the StatLight (v 1.4.4147) tests previously under Jenkins with no problems. On Jenkins, I called the StatLight test in a custom script as follows:
StatLight.exe -x="Tests.xap"
StatLight.exe -x="MoreTests.xap"
StatLight.exe -x="EvenMoreTests.xap"
... etc., but when I migrated my build jobs to TeamCity, I also changed these into a single command line step as follows:
StatLight.exe --teamcity -x="Tests.xap" -x="MoreTests.xap" -x="EvenMoreTests.xap"
This works about 50% of the time, but when it fails, there's no output in the build log to tell me why - I just get:
[11:41:18]: [MyProject\bin\Release\MoreTests.xap] Tests.ExtensionsTests.WatchObservableCollection
[11:41:18]: [MyProject\bin\Release\MoreTests.xap] Tests.SubscribingModelBaseTests.DisposeIsCalled
[11:41:18]: [MyProject\bin\Release\MoreTests.xap] --- Completed Test Run at: 28/09/2011 11:41:18. Total Run Time: 00:00:11.8125000
[11:41:19]: [MyProject\bin\Release\MoreTests.xap] Test run results: Total 6, Successful 6, Failed 0,
[11:41:19]: [Step 5/6] MyProject\bin\Release\EvenMoreTests.xap (9m:42s)
... and then nothing more. The time reported in that last line just goes up and up until I kill the the build job. Adding the --debug switch to StatLight doesn't improve the above output either.
Right now, I've switched the TeamCity build step to call each test individually as I was in Jenkins, but this is more of a workaround than a proper solution. And of course, I may still run into the above problem - I've yet to find out.
What I'd like to know is what steps I can take to debug this issue properly, or whether there are known issues that can cause the above behaviour?
There was one issue fixed in the 1.5 version relating to teamcity. http://statlight.codeplex.com/workitem/13654
I'm not sure it will fix your issue, but would you mind upgrading, trying and reporting back?