WildFly 30 Galleon provisioning

198 views
Skip to first unread message

M K

unread,
Oct 31, 2023, 3:10:52 AM10/31/23
to WildFly
Hi,

we are using Galleon to provision our WildFly server with the following layers:
  • base-server
  • bean-validation
  • cdi
  • core-server
  • core-tools
  • datasources
  • datasources-web-server
  • deployment-scanner
  • ee
  • ejb
  • jaxrs
  • jpa
  • jsf
  • logging
  • mail
  • messaging-activemq
  • naming
  • remote-activemq
  • resource-adapters
  • undertow
  • undertow-https
  • web-server
The following questions came up:
  1. What Galleon layer(s) do I need to include to get the docs\contrib and docs\schema directories? If there is none, how else do I achieve this using Galleon? Or do I need to copy them manually?
  2. The modules javax.api and sun.jdk are no longer provisioned. Was it a conscious decision to get rid of these deprecated modules? Can I get them back using any layer or other Galleon option? Or do I need to copy them manually?
If this sounds familiar: I asked the same questions on Zulip two weeks ago but got no answer, so I'm trying my luck here! I hope this doesn't break any written or unwritten rules.

Thank you very much in advance!
Greetings
Manuel

Jean Francois Denise

unread,
Oct 31, 2023, 5:59:14 AM10/31/23
to wil...@googlegroups.com

Hi,

you can include packages. Look at :https://github.com/wildfly/wildfly/blob/main/ee-dist/pom.xml#L118

In your case include docs.contrib and docs.schema packages.

For javax.api and sun.jdk modules, you can look at the JIRA that removed them: https://issues.redhat.com/browse/WFLY-17931 and https://issues.redhat.com/browse/WFLY-17932 There are no layers to bring them.

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/29ab5f6b-d7db-45b7-b127-a4c9a99aa725n%40googlegroups.com.

M K

unread,
Oct 31, 2023, 6:19:28 AM10/31/23
to WildFly
Hi,

thanks for your reply! I should have mentioned that we are actually using the Galleon CLI tool to provision the server (https://docs.wildfly.org/galleon/#_galleon_cli_tool). I'm not sure if I'm doing this right, but it doesn't work:

[server]$ state edit
Entering provisioning edit mode.Use 'add-dependency' command to add feature packs. Call 'leave-state' to leave this sta
te.

[!edit!server!/]$ include-package docs.contrib
Error: Retrieve producer failed.
 * Unknown docs.contrib

Can this be done using the CLI tool, and if so, how?

Greetings
Manuel

Jean Francois Denise

unread,
Oct 31, 2023, 6:55:46 AM10/31/23
to wil...@googlegroups.com

Interesting to see that you use the 'state' feature of Galleon CLI.

You could use tab completion with the include-package command to have the list of feature-packs present in your current installation.

I did (inside a directory containing an installation):

include-package wildfly@maven(org.jboss.universe:community-universe)/docs.schema

include-package wildfly-ee@maven(org.jboss.universe:community-universe)/docs.schema

include-package wildfly-ee@maven(org.jboss.universe:community-universe)/docs.contrib

export changed-provisioning.xml

The exported changed-provisioning.xml content:

<installation xmlns="urn:jboss:galleon:provisioning:3.0">
    <transitive>
        <feature-pack location="wildfly-ee@maven(org.jboss.universe:community-universe)">
            <packages>
                <include name="docs.contrib"/>
                <include name="docs.schema"/>
            </packages>
        </feature-pack>
    </transitive>
    <feature-pack location="wildfly@maven(org.jboss.universe:community-universe):current#30.0.0.Final">
        <default-configs inherit="false"/>
        <packages inherit="false">
            <include name="docs.schema"/>
        </packages>
    </feature-pack>
    <config model="standalone" name="standalone.xml">
        <layers>
            <include name="cloud-server"/>
        </layers>
    </config>
    <options>
        <option name="optional-packages" value="passive+"/>
    </options>
</installation>

M K

unread,
Oct 31, 2023, 9:49:02 AM10/31/23
to WildFly
I was using the 'state' feature just now as it was the only way I could find to include these packages. I was now able to provision a server with the docs.contrib and docs.schema packages included.

Thank you very much!

Greetings
Manuel
Reply all
Reply to author
Forward
0 new messages