Re: Getting "OverConstrainedVersionException" in jaxb-maven-plugin

Howdy,

best would be to create some reproducer? Or point at your repo, if it is public?

T

On Thu, Jan 8, 2026 at 5:34 PM KARR, DAVID via users
<[email protected]> wrote:
>
> This is the repo for it: https://github.com/highsource/jaxb-tools .
>
> I’m on Maven v3.9.8.
>
> I think I found something that might be causing this, but I’m not sure yet.
>
> Our services use a versioned parent pom that imports a BOM that specifies a version range for all of our internal libraries. I remembered that one problem we’ve seen sometimes is that some people have developed their own libraries with somewhat “ad hoc” development strategies, which often results in conflicting dependency specifications.  I just saw that one dependency in my problem service’s pom.xml has a parent pom with a different version than the main pom.xml, so both of them will include the BOM, with different versions, resulting in different ranges for the internal libraries. This seems like an important fact. I will see if that is the cause.
>
> From: Tamás Cservenák <[email protected]>
> Sent: Thursday, January 8, 2026 6:46 AM
> To: Maven Users List <[email protected]>
> Subject: Re: Getting "OverConstrainedVersionException" in jaxb-maven-plugin
>
> Howdy, Can you point me in the github repo of the plugin you use? Also, what Maven do you use? On Wed, Jan 7, 2026 at 10: 51 PM KARR, DAVID via users <users@ maven. apache. org> wrote: > > I'm having an issue that might be a problem
>
>
> Howdy,
>
>
>
> Can you point me in the github repo of the plugin you use?
>
> Also, what Maven do you use?
>
>
>
> On Wed, Jan 7, 2026 at 10:51 PM KARR, DAVID via users
>
> <[email protected]<mailto:[email protected]>> wrote:
>
> >
>
> > I'm having an issue that might be a problem with our use of the jaxb-maven-plugin, or it may be something else.  We only see a particular error with respect to that plugin, but the exception we get is not specific to the plugin, so perhaps this is a wider issue.
>
> >
>
> > We had been using jaxb-maven-plugin version 4.0.8. We support many services using this.  Very rarely we have seen an error stating 'Cannot invoke "java.io.File.toURI()" because "file" is null'. It provides no other diagnostics, so we can't tell what this means.  I created an issue in the plugin's github repo, but that didn't really get anywhere.
>
> >
>
> > However, I thought I would try upgrading the plugin to the latest available version, which is 4.0.12.  When I did that, I got different, perhaps more specific errors, but I'm still at a loss to understand it.  It's possible these errors are not specific to the plugin, which is why I'm asking here.
>
> >
>
> > It gives a bunch of errors like this:
>
> > ---------------
>
> > 09:06:06 [ERROR] artifactResolutionResult has exceptions : [org.apache.maven.artifact.versioning.OverConstrainedVersionException: The artifact has no valid ranges
>
> >   <groupid>:<artifactid>:jar:3.0.1
>
> >
>
> > Path to dependency:
>
> >         1) <groupid>:BillingServicesOrchestrationMs:jar:0.0.1-SNAPSHOT
>
> > ---------------
>
> >
>
> > I am seeing a number of these messages, some of which for the same GAV, and some for different versions of the same artifact.  Looking at the OverConstrainedVersionException, it says "Occurs when ranges exclude each other and no valid value remains." Ok, I can see how that would be a problem. The "problem" is, although we do use version ranges for these artifacts, we only have a single version range, and they are perfectly ordinary.  I even tried looking at the effective pom (verbose mode), and I find no surprises there.
>
> >
>
> > I don't understand how to debug this.
>
> >
>
> > ---------------------------------------------------------------------
>
> > To unsubscribe, e-mail: [email protected]<mailto:[email protected]>
>
> > For additional commands, e-mail: [email protected]<mailto:[email protected]>
>
> >
>
>
>
> ---------------------------------------------------------------------
>
> To unsubscribe, e-mail: [email protected]<mailto:[email protected]>
>
> For additional commands, e-mail: [email protected]<mailto:[email protected]>
>
>