The package javax.xml.namespace is accessible from more than one module <unnamed>,java.xml

[mohana krishna thangella]

I am trying to upgrade from java 8 to java 11.I am using maven build.

I am using classpath instead of module path, I don't have module-info.java files in my project but still I am getting the error 

"The package javax.xml.namespace is accessible from more than one module <unnamed>,java.xml"

I am getting this error when maven build system is trying to generate java classes using XML, XSD and xml parsing.

Once the classes are generated maven is trying to build.

In the generated classes I am getting this error.

Please help to let me know how to resolve the issue

[Rob Spoor]

One of your dependencies is not doing things the right way. Instead of depending on the code provided by the JDK/JRE, they added their own version of the javax.xml.namespace package. What you need to do is figure out which one (your IDE usually lets you browse inside the dependencies), and see if you can upgrade or replace that dependency.

[Tim Holloway]

Rob Spoor wrote:One of your dependencies is not doing things the right way. Instead of depending on the code provided by the JDK/JRE, they added their own version of the javax.xml.namespace package. What you need to do is figure out which one (your IDE usually lets you browse inside the dependencies), and see if you can upgrade or replace that dependency.

Yes, this was a problem that someone else had - and solved - not long ago, so search the Ranch for that thread.

Basically, the jaxb package that was part of JDK 8 was removed and now has to be supplied externally (as a Maven dependency) to build properly with later JDKs.

The sticky part is that the newer jaxb packages are now in their own module and older code not written to use modules has a problem with that. The solutions are to either pull an older non-module version of JAXB from Maven or change your code to understand the new  module usage.

[Rob Spoor]

javax.xml.namespace isn't part of JAXB, it's part of the JSE java.xml module. Still, that doesn't prevent libraries from including the API. For instance, xmlsec 1.5.8 included javax.xml.crypto which is part of the java.xml.crypto module. I remember this one well because it's given me quite a lot of class loading errors in the past.