Fix maven BuildIT failures #31494
Merged
Fix maven BuildIT failures #31494
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The dependency `stax-api` is not compatible with the dependency `quarkus-jaxb` because both add the same type `javax.xml.namespace.QName`. This was done on purpose to validate the `parent-first-artifacts` property when building projects with conflicts with Maven, so we need to skip the JaxbContext validation at build time. This pull request should fix all the CI failures in the latest pull requests.
geoand
approved these changes
Mar 1, 2023
|
Failures do not seem to be related. |
gsmet
approved these changes
Mar 1, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Context
The dependency
stax-apiis not compatible with the dependencyquarkus-jaxbbecause both add the same typejavax.xml.namespace.QName(fromglassfish jaxb). This dependency was added on purpose to validate theparent-first-artifactsproperty when building projects with these conflicts with Maven.After this change was merged, the
javax.types were replaced by thequarkus-jaxbextension as part of the jakarta migration, but never with the intention of using the default JAXBContext.Therefore, we need to skip the JaxbContext validation at build time.
Note that in real scenarios, users would need to either exclude glassfish or the stax-api dependency.
This pull request should fix all the CI failures in the latest pull requests.