You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
⚠ This is a good to about build systems. This issue cannot be solved with an AI (alone). You really have to think though the build systems for yourself! Take this issue only if you are willing to invest significant time. ⚠
Execute the gradle task: jabgui > application > run to check if the system builds. If not, you need to adapt the .kts and/or module-info.java files.
This is more a code-and-fix task
The build will take some seconds until you get feedback. Reserve some time and be prepared to "idle".
A first test is that JabGui runs; tests if it fits for Status Log of JabRef 5.15 APIdia-net/apidia.net#2 (comment) can be done by jar --file flexmark-0.64.8.jar -d. You will find the jars by everything. Is much effort. If this is too much effort for you, you can submit a PR and then ask Stewori to check.
In #13401, we switched the build tooling. Thereby, we "renamed" Java modules. This causes issues: APIdia-net/apidia.net#2 (comment)
Task: Semantically (revert) the update
jabref/build-logic/src/main/kotlin/org.jabref.gradle.base.dependency-rules.gradle.kts
Line 80 in 28b7350
module-info.javaaccordingly.The diff for one module java is determined as follows
This has to be reverted (and new updates be kept)
(and much more)
Hints
⚠ This is a good to about build systems. This issue cannot be solved with an AI (alone). You really have to think though the build systems for yourself! Take this issue only if you are willing to invest significant time. ⚠
.ktsand/ormodule-info.javafiles.jar --file flexmark-0.64.8.jar -d. You will find the jars by everything. Is much effort. If this is too much effort for you, you can submit a PR and then askSteworito check.