I am getting some error regarding unnamed module not being able to access io.objectsbox.convertor package on my javafx applicaion

[MaardinK522]

I am using IntelliJ IDEA and JavaFX project template with maven (not gradle).
I am also having this modul-info.java file which is detecting objectbox.java and objectbox.java.api;
and when I try to build my project it prints error:

Executing pre-compile tasks…
Running 'before' tasks
Checking sources
Copying resources... [ExpenseCalculator]
Parsing java… [ExpenseCalculator]
java: the unnamed module reads package io.objectbox.converter from both objectbox.java and objectbox.java.api
java: module objectbox.java.api reads package io.objectbox.converter from both objectbox.java and objectbox.java.api
java: module objectbox.java reads package io.objectbox.converter from both objectbox.java.api and objectbox.java
Checking dependencies… [ExpenseCalculator]
Dependency analysis found 0 affected files
Errors occurred while compiling module 'ExpenseCalculator'
javac 21.0.2 was used to compile java sources
Finished, saving caches…
Compilation failed: errors: 4; warnings: 0
Executing post-compile tasks…
Synchronizing output directories…
15-04-2025 18:13 - Build completed with 4 errors and 0 warnings in 1 sec, 420 ms

I had used Objectbox in my one of my Flutter project it worked great. I was almost like using a butter with toast. But I really want to use this database on my custom java applications too.
I hope you/your team can help me fix my issues.
BTW, I love to use objectbox.

[greenrobot-team]

Thanks for reporting! As the error message is about modules, I suspect that your project is targeting Java 9 or higher and is using the new Java module system?

The ObjectBox Java library does not support the module system, yet. See #840 for details.

If you confirm this, I will close this issue as a duplicate.

Note: I labeled this issue with "more info required" so it will auto-close in a few days if there are no follow-up comments.

[github-actions]

Without additional information, we are unfortunately not sure how to resolve this issue. Therefore this issue has been automatically closed. Feel free to comment with additional details and we can re-open this issue.