Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Depending on rest-assured (in some particular way, maven-dependency-plugin with <useRepositoryLayout>true?) fails Maven build under Java 11 #1991

Closed
vorburger opened this issue Apr 10, 2019 · 3 comments
Milestone

Comments

@vorburger
Copy link
Contributor

vorburger commented Apr 10, 2019

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?

@vorburger
Copy link
Contributor Author

Just FTR, the part of #1929 which causes above is this change .

@vorburger 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
Copy link
Contributor Author

OK, so this does the trick and solves this problem:

        <dependency>
            <groupId>io.rest-assured</groupId>
            <artifactId>rest-assured</artifactId>
            <scope>test</scope>
            <exclusions>
                <exclusion>
                    <groupId>com.sun.xml.bind</groupId>
                    <artifactId>jaxb-osgi</artifactId>
                </exclusion>
            </exclusions>
        </dependency>

FTR: I first tried an exclusion of com.sun:tools, but that didn't help.

@vorburger 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
@Sanne Sanne added this to the 0.14.0 milestone Apr 10, 2019
@Sanne Sanne closed this as completed in f86407b Apr 10, 2019
Sanne added a commit that referenced this issue Apr 10, 2019
add jaxb-osgi exclusion for rest-assured to BOM (fixes #1991)
@Prashant0731
Copy link

sadasddasdadasd dadsadads

asdsadasdasd

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants