search

wildfly-extras / wildfly-jar-maven-plugin

WildFly Bootable JAR
https://docs.wildfly.org/bootablejar/
Apache License 2.0
57 stars 40 forks source link

Arquillian containers depends on deps outside of central #200

Open codylerum opened 3 years ago

codylerum commented 3 years ago

Working on getting bootable jar testing working Arquillian and I'm hitting a snag.

After adding 

<dependency>
    <groupId>org.wildfly.arquillian</groupId>
    <artifactId>wildfly-arquillian-container-bootable</artifactId>
    <version>3.0.1.Final</version>
    <scope>test</scope>
</dependency>

I'm getting a build error as it appears to be depending on a picketbox version that is not published to central.

Could not find artifact org.picketbox:picketbox:jar:5.0.3.Final-redhat-00006

jamezp commented 3 years ago

I had to do the same fix for wildfly-arquillian. We should probably do the same here https://issues.redhat.com/browse/WFARQ-91.

codylerum commented 3 years ago

Adding a 

<repository>
    <id>redhat-releases</id>
    <name>Redhat Maven Repository</name>
    <url>https://maven.repository.redhat.com/ga/</url>
    <layout>default</layout>
</repository>

To the pom is a workaround, but this is probably something that will trip up users.

jamezp commented 3 years ago

Yes that is definitely the workaround. It is something that we should solve as it's not ideal to have users enter that in their POM.

codylerum commented 3 years ago

Definitely not ideal as now dependabot starts trying to pull in updates like

Guava from 30.1-jre to 30.1.0.jre-redhat-00001.