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]
For additional commands, e-mail: [email protected]
