Wildfly integration


#1

I wanted to delete this post because I managed to sort it out myself, but I can’t find any way to do that.

Hi, I am trying to follow the instructions for how to add the hibernate-search-jbossmodules-elasticsearch feature pack functionality, but the plugin build goal fails with the message below. Is this a problem with any known solution?

[ERROR] Failed to execute goal org.wildfly.build:wildfly-server-provisioning-maven-plugin:1.2.8.Final:build (default-cli) on project hiberlab: Execution default-cli of goal org.wildfly.build:wildfly-server-provisioning-maven-plugin:1.2.8.Final:build failed: java.lang.RuntimeException: java.lang.RuntimeException: failed to resolve artifact org.glassfish.jaxb:txw2:jar:2.2.11.jbossorg-1: Failure to find org.glassfish.jaxb:txw2:jar:2.2.11.jbossorg-1 in https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced -> [Help 1]


#2

So I’m not the go to person for that but I think the issue is that this plugin depends on artifacts not deployed on Central (which is unfortunate and should probably be fixed…).

I think you can fix your issue by getting this settings.xml: https://github.com/hibernate/hibernate-validator/blob/master/settings-example.xml and launching your Maven command with mvn -s settings-example.xml …

HTH


#3

As mentioned in a warning in the documentation:

Depending on the WildFly feature pack you chose, some transitive dependencies may not be available in Maven Central. In that case, you should set up the JBoss Nexus repository.

The problem is some WildFly feature packs (not ours, but probably one you provisionned in your server) rely on dependencies that are not available on central. And no, I don’t know why they do that :confused: