Details
-
Bug
-
Resolution: Done
-
Blocker
-
None
-
None
-
False
-
None
-
False
-
Rejected
-
+
Description
Apart from the Arquillian, as Martin has described in JBEAP-24125, there seems to be also another issue in the wildfly-jaxws-client-bom with the javax.xml.bind:jaxb-api:pom:2.3.0-b161121.1438 artifact. One can see following error when trying to build the dependency tree on a project that utilizes just the wildfly-jaxws-client-bom:
Could not resolve dependencies for project org.jboss.test:repo-test:jar:1.0.0.redhat-1: Failed to collect dependencies at org.jboss.eap:wildfly-jaxws-client-bom:pom:8.0.0.Beta-redhat-20221021 -> org.apache.cxf:cxf-rt-ws-rm:jar:3.5.2.redhat-00003 -> org.apache.cxf:cxf-rt-ws-security:jar:3.5.2.redhat-00003 -> org.ehcache:ehcache:jar:jakarta:3.10.0 -> org.glassfish.jaxb:jaxb-runtime:jar:2.3.0-b170127.1453 -> org.glassfish.jaxb:jaxb-core:jar:2.3.0-b170127.1453 -> javax.xml.bind:jaxb-api:jar:2.3.0-b161121.1438
Later on you can see also:
Caused by: org.eclipse.aether.resolution.ArtifactResolutionException: Could not transfer artifact javax.xml.bind:jaxb-api:pom:2.3.0-b161121.1438 from/to maven-default-http-blocker (http://0.0.0.0/): Blocked mirror for repositories: [releases.java.net (http://maven.java.net/content/repositories/releases/, default, releases+snapshots), shapshots.java.net (http://maven.java.net/content/repositories/snapshots/, default, releases+snapshots), jvnet-nexus-staging (http://maven.java.net/content/repositories/staging/, default, releases+snapshots), netbeans (http://bits.netbeans.org/nexus/content/groups/netbeans, default, releases)]
Well, plain-text HTTP again? Yeah, but it's also fair to point out that even if we use HTTPS, there is no such artifact in https://maven.java.net/content/repositories/releases/javax/xml/bind/jaxb-api/ . So we must look elsewhere. If this artifact should be part of the BOM, we should have it in the maven repository too.
BUT: actually it looks that we need to exclude it on appripriate place, as discussed e.g. here and also here. You can see that jbossws-cxf seems to be excluding this already too. Also, we are probably more interested in Jakarta then in javax now... But not sure at the moment whether this missing artifact may prevent something else from proper working.
Note: we support wildfly-jaxws-client-bom (JBoss EAP Client BOMs section) for customer use in EAP7. I suppose this isn't gonna change in EAP8.
Attachments
Issue Links
- is related to
-
-
- Verified
-
-
-
- Verified
-
