-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Intelij run configuration not working #9303
Comments
What is your output of Mine is: $ java -version
openjdk version "19" 2022-09-20
OpenJDK Runtime Environment Temurin-19+36 (build 19+36)
OpenJDK 64-Bit Server VM Temurin-19+36 (build 19+36, mixed mode, sharing) |
What is the output of $ gradlew --version
------------------------------------------------------------
Gradle 7.5.1
------------------------------------------------------------
Build time: 2022-08-05 21:17:56 UTC
Revision: d1daa0cbf1a0103000b71484e1dbfe096e095918
Kotlin: 1.6.21
Groovy: 3.0.10
Ant: Apache Ant(TM) version 1.10.11 compiled on July 10 2021
JVM: 18.0.2 (Oracle Corporation 18.0.2+9-61)
OS: Windows 10 10.0 amd64 |
And yes, I can run the project with gradle task "run" (and from the command line with
I'm also up-to-date with the main branch, with commit 349c879. And indeed, there's only a |
The problem with not having IntelliJ run config is that, as far as I know, it would not be possible to run the application in debugger mode within the IDE. So, wouldn´t it be a better option to just update the Intelij run configuration file? |
Debug works here with Gradle without issues. |
I worked on refining the guideline. It is currently under review at #9355. You have to configure IntelliJ to use Gradle for Build and running - and "IntelliJ IDEA" for test: IntelliJ creates the launch configurations. Check out following steps: |
JabRef version
Other (please describe below)
Operating system
GNU / Linux
Details on version and operating system
Manjaro with GNOME 42.4, Jabref main branch (commit 349c879)
Checked with the latest development build
Steps to reproduce the behaviour
JabRef Main
run config;This behavior seems to manifest in two ways:
org.jabref.gui.JabRefMain
toorg.jabref.cli.Launcher
in PR Process CLI arguments before starting gui #9217. I've been able to run normally by just changing the entry point on the config file (and was not sure if this was going to be reverted, as PR Revert "Process CLI arguments before starting gui" #9257 was still open at the time)org.jabref.gui.desktop.os.Windows
. See appendix for error message.Appendix
...
Log File
The text was updated successfully, but these errors were encountered: