package not in module graph

[DavidEgeaJimenez]

I'm trying to do make an app to let me count the pages of each chapter of a book. The only problem my code is in the import part.

It gives me the following error in the three imports:
"package <package_name> is not visible (package <package_name> is declared in module odfdom.java, which is not in the module graph."

My module graph is this one:

I have the same module path in Compile, Processor, Run, Compile Tests and Run Tests. I'm using Apache Netbeans IDE 27. My main java platform is JDK 24, but I installed JDK 11 for this single project. I'm also using a project of Java with Ant.

I've been breaking my head with this all evening, I'm new installing external libraries and changing the properties of my projects, I would happily accept some help, thank you.

[svanteschubert]

Thanks for reminding me of the moduling (Project Jigsaw). I started to work on this and aim to fix it in our next release #54

I have the following suggestions for you:

1. Add module-info.java (The Most Likely Fix)

If your project has a module-info.java file (NetBeans often creates one by default in newer JDKs), you must explicitly declare that your project depends on the ODFDOM module.

Locate module-info.java in your Source Packages.

Add the following line inside the module block:

module YourProjectName {
    requires odfdom.java; // Add this line
}

Note: The module name for the ODF Toolkit is usually odfdom.java.

---

2. Move JARs from Modulepath to Classpath

If you do not want to use the Java Module System and just want the library to work like older Java versions:

1. Right-click your project in NetBeans and select Properties.
2. Go to Libraries.
3. Look at the Compile tab.
4. If the ODF Toolkit JAR files are under Modulepath, remove them.
5. Click on Classpath and add the JAR files there instead.
6. Delete module-info.java from your source packages if it exists.

This will force the project to run in the unnamed module, which can see all libraries on the classpath.

---

3. Check for Missing Dependencies

The ODF Toolkit (ODFDOM) depends on several other libraries (such as Apache Jena and various XML libraries). If you are adding the JARs manually:

• Ensure you have also added all required dependency JARs to your project's library path.

If you are using Maven instead of Ant:

• Ensure you have the odfdom-java dependency in your pom.xml, as Maven handles these module and dependency graph issues automatically.

---

4. NetBeans-Specific Refresh

Sometimes NetBeans' indexer gets stuck:

1. Go to Project Properties → Libraries.
2. Ensure the Java Platform is set to JDK 11.
3. Click Clean and Build on the project.

---

Summary

This error occurs because Java 11+ strictly enforces module boundaries.

You have two main options:

• Use the module system: Declare the dependency in module-info.java.
• Bypass the module system: Delete module-info.java and move the JARs to the classpath.

Either approach should be able to resolve the visibility issue with ODFDOM.

PS: And I started to fix it on our side today and created a branch to add modularity to the ODF Toolkit project! :-)