You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The PR #1929 (mine) failed to build with this interesting message:
[WARNING] Failed to build parent project for com.sun.xml.bind.mvn:jaxb-bundles:pom:2.2.10
[WARNING] Failed to build parent project for com.sun.xml.bind.mvn:jaxb-osgi:pom:2.2.10
[WARNING] Failed to build parent project for com.sun.xml.bind:jaxb-osgi:jar:2.2.10
(...)
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:3.1.1:copy-dependencies (copy-dependencies) on project quarkus-gradle-plugin-integration-test: Some problems were encountered while processing the POMs:
[ERROR] [WARNING] Reporting configuration should be done in <reporting> section, not in maven-site-plugin <configuration> as reportPlugins parameter. @
[ERROR] [ERROR] 'dependencyManagement.dependencies.dependency.systemPath' for com.sun:tools:jar must specify an absolute path but is ${tools.jar} @ com.sun.xml.bind.mvn:jaxb-parent:[unknown-version], /home/vsts/.m2/repository/com/sun/xml/bind/mvn/jaxb-parent/2.2.10/jaxb-parent-2.2.10.pom, line 188, column 29: 2 problems were encountered while building the effective model for com.sun.xml.bind:jaxb-osgi:2.2.10
[ERROR] [WARNING] Reporting configuration should be done in <reporting> section, not in maven-site-plugin <configuration> as reportPlugins parameter. @
[ERROR] [ERROR] 'dependencyManagement.dependencies.dependency.systemPath' for com.sun:tools:jar must specify an absolute path but is ${tools.jar} @ com.sun.xml.bind.mvn:jaxb-parent:[unknown-version], /home/vsts/.m2/repository/com/sun/xml/bind/mvn/jaxb-parent/2.2.10/jaxb-parent-2.2.10.pom, line 188, column 29
It had passed when I locally built using Java 8 - this is a Java 11 specific build problem (reproducibly locally when building that PR with Java 11).
I'll work around it in that PR, but wanted to raise this issue for discussion whether we may would like to add some suitable <exclusion> (?) in some Quarkus POM?
The text was updated successfully, but these errors were encountered:
vorburger
changed the title
Adding e.g. quarkus-resteasy-deployment as a dependency fails Maven build under Java 11
Using rest-assured with maven-dependency-plugin with <useRepositoryLayout>true fails Maven build under Java 11
Apr 10, 2019
vorburger
changed the title
Using rest-assured with maven-dependency-plugin with <useRepositoryLayout>true fails Maven build under Java 11
Depending on rest-assured (in some particular way, maven-dependency-plugin with <useRepositoryLayout>true?) fails Maven build under Java 11
Apr 10, 2019
vorburger
added a commit
to vorburger/quarkus
that referenced
this issue
Apr 10, 2019
The PR #1929 (mine) failed to build with this interesting message:
It had passed when I locally built using Java 8 - this is a Java 11 specific build problem (reproducibly locally when building that PR with Java 11).
I'll work around it in that PR, but wanted to raise this issue for discussion whether we may would like to add some suitable
<exclusion>
(?) in some Quarkus POM?The text was updated successfully, but these errors were encountered: