Wildfly 26.1.2 - Bootable jar fails due private dependency to picketbox?

187 views
Skip to first unread message

ralfbat...@gmail.com

unread,
Oct 15, 2022, 4:28:22 AM10/15/22
to WildFly
Dear Wildfly

I tried to switch from Wildfly 24.0.1 to WIldfly 26.1.2. The bootable jar application cannot be built because of a not resolvable dependency:

[ERROR] Failed to execute goal org.wildfly.plugins:wildfly-jar-maven-plugin:8.0.1.Final:package (default) on project tru-module-ear-prod-business: Provisioning failed: Failed to process JBoss module XML template for feature-pack wildfly-ee@maven(org.jboss.universe:community-universe):current#26.1.2.Final package org.picketbox: Failed to resolve artifact org.picketbox:picketbox:jar:5.0.3.Final-redhat-00008: Failed to resolve org.picketbox:picketbox:jar:5.0.3.Final-redhat-00008: Could not transfer artifact org.picketbox:picketbox:jar:5.0.3.Final-redhat-00008 from/to jboss-public-repository (https://repository.jboss.org/nexus/content/groups/public/): Transfer failed for https://repository.jboss.org/nexus/content/groups/public/org/picketbox/picketbox/5.0.3.Final-redhat-00008/picketbox-5.0.3.Final-redhat-00008.jar: Connect to repository.jboss.org:443 [repository.jboss.org/23.213.161.197, repository.jboss.org/23.213.161.219] failed: Connection refused: connect -> [Help 1]

How can I solve this issue?

Thank in advance
Ralf

Jean Francois Denise

unread,
Oct 17, 2022, 3:56:12 AM10/17/22
to wil...@googlegroups.com
Hi,
I suspect a maven issue when trying to connect to "https://maven.repository.redhat.com/ga/" in which this artifact has been deployed.
You could try deleting .m2/repository/org/picketbox/picketbox/5.0.3.Final-redhat-00008/ ?

JF
--
You received this message because you are subscribed to the Google Groups "WildFly" group.
To unsubscribe from this group and stop receiving emails from it, send an email to wildfly+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/wildfly/f5a82281-9231-490f-bbc8-73890d646ef9n%40googlegroups.com.


ralfbat...@gmail.com

unread,
Oct 26, 2022, 3:48:44 AM10/26/22
to WildFly
Hi JF

Thank you for your help. We found the issue for the picketbox dependency. We had to configure the RedHat GA repository in our company nexus. The picketbox was originally located in a RedHat Tech Preview repo. So, that is solved but we got another issue for which we have no idea to solve it.

The dependency to com.sun.faces:jsf-impl:jar:2.3.17.SP01 is not resolvable:

[ERROR] Failed to execute goal org.wildfly.plugins:wildfly-jar-maven-plugin:8.0.1.Final:package (default) on project rno-bootable-jar-hollow-backend: Provisioning failed: Failed to process JBoss module XML template for feature-pack wildfly-ee@maven(org.jboss.universe:community-universe):current#26.1.2.Final package com.sun.jsf-impl: Failed to resolve artifact com.sun.faces:jsf-impl:jar:2.3.17.SP01: Failed to resolve com.sun.faces:jsf-impl:jar:2.3.17.SP01: Could not transfer artifact com.sun.faces:jsf-impl:jar:2.3.17.SP01 from/to jboss-public-repository (https://repository.jboss.org/nexus/content/groups/public/): Transfer failed for https://repository.jboss.org/nexus/content/groups/public/com/sun/faces/jsf-impl/2.3.17.SP01/jsf-impl-2.3.17.SP01.jar: Connect to repository.jboss.org:443 [repository.jboss.org/23.3.88.66, repository.jboss.org/23.3.88.40] failed: Connection refused: connect -> [Help 1]

Looking at maven central, then this one should be in the JBoss EA repository, but there is no jar for this version in this repo: https://repository.jboss.org/nexus/content/repositories/ea/

Any idea how we can create a bootable jar with Wildfly-26.1.2.Final ? 

Ralf

Jean Francois Denise

unread,
Oct 26, 2022, 4:08:12 AM10/26/22
to wil...@googlegroups.com
Hi,
The bootable JAR maven plugin adds this maven repository to the set of maven repositories during build. I suspect that you would need to add it to your company nexus.

JF

ralfbat...@gmail.com

unread,
Oct 26, 2022, 5:51:05 AM10/26/22
to WildFly
Thanks a lot JF. We will adjust it accordingly. That means, Maven Central points this version to a wrong repository.

Ralf

Reply all
Reply to author
Forward
0 new messages