I'm using JArgs.jar for the command line parsing. It's working fine without Gradle but when I'm using Gradle to run my tests it's now working. It seems somehow the jar is not copied by Gradle!
Any help will be highly appreciated.
Related
I am trying to run a spring-boot Kotlin project.
When running mvn clean install I am getting this error:
A required class was missing while executing org.jetbrains.kotlin:kotlin-maven-plugin:1.4.10:compile: org/jetbrains/kotlin/cli/common/messages/MessageCollector
Good to mention that I do not have a folder named cli under .m2/repository/org/jetbrains/kotlin/
I tried to delete the repository folder and build again but that didn’t help.
I am using maven 3.6.3, JDK 11 and Kotlin compiler 1.4 which match with the config of the project.
If someone could help, it would be much appreciated.
The Kotlin compiler jar was broken for some reason. Downloading it from here and replacing it fixed the problem, in case somebody faces the same problem in the future! :)
I am using Eclipse/STS with Maven and also pointing eclipse/sts maven path to local direcotry for my artifacts repository. However, when I run or debug the maven project, it gets terminate without any output on console, also other team member are using same setup of maven in eclipse/sts but they do not face any such problem. When I run the project from command prompt it run fine without any problem.
Is there any solution for this, I have tried in eclipse and STS and facing same problem. I would appreciate your inputs.
I was using maven which is not compatible with STS/Eclipse due to which it was terminating the program immidiatly after running!!!
I am working on some investigation on Gradle Build Plugins, written in Groovy.
I could find the jar files, and locate the plugin code that I have to check. As I am new to the Groovy, I am not able to follow its syntax.
Can some one help me to figure it out. I need to know what does the line do.
arrayOfCallSite[0].call(arrayOfCallSite[1].call(target), "java");
I just converted my Maven project to a gradle project. It was a multi project structure:
master-project
pom.xml
---->project1
-------->pom.xml
---->project2
-------->pom.xml
---->project3
-------->pom.xml
I ran a gradle init on it and have this structure now:
master-project
build.gradle
---->project1
-------->build.gradle
---->project2
-------->build.gradle
---->project3
-------->build.gradle
Everything builds fine, and I have been able to get some things done with that I couldn't figure out how to do with Maven, so that's great. Next step was to integrate that into the IDE since the Maven Dependencies are gone since I have removed the pom.xml files.
However the project isn't recognized as a gradle project - and I am not sure how to change that?
In Eclipse Mars it's still recognized as a Maven build, not gradle....
Thanks in advance.
EDIT: I reimported the projects which enabled the plugin for Eclipse. Now I am having weird behavior.
The build works from the command line, however when attempting the same execution from within Eclipse, it fails trying to copy the file dependencies.
For example:
Couldn't copy dependency jakarta-regexp-1.4.jar
java.nio.file.NoSuchFileException: C:\Users\user.m2\repository\jakarta-regexp\jakarta-regexp\1.4\jakarta-regexp-1.4.jar -> build\jfx\app\lib\jakarta-regexp-1.4.jar
I haven't changed the repo from maven yet - just changed the build scripts. This is running from the master project. So I am confused as to why the script would work from the commandline but not from within eclipse.
EDIT 2: Turns out this behavior is also present when running from the command line when the --daemon flag is set. Is there anyway to run the tasks without the daemon in Buildship? Or perhaps a way to fix this issue when the --daemon flag is enabled?
Thanks.
The issue with the build was that there is a leak in the JDK when bundling the JRE with the native app. This only happens when running with the --daemon flag (which all IDEs user). Therefore until this is fixed you will need to run gradle --stop and then run the clean.
The plug in I am using is no longer running the native task when running with --daemon.
I’m using AspectJ in my project. My project is based on Maven.
I’m able to successfully compile the .aj file and when I try to run the testcase using maven my aspects are working fine.
But when I start executing the program from command prompt (eg.. java <*.jar>) my aspects are not working. Is it necessary to set any Java JVM option for my aspect to execute.
Thanks In Advance