Using the Wildfly Channel manifest file to override the module version in provisioned WildFly server.

I have added a jberet-manifest module into the JBeret project this week:

The above PR shows the usage how to wrap a manifest file into a module, and how to use it in the wildfly-maven-plugin to override the module version used in the provisioned WildFly server. The format of the manifest file is defined in this project:

The manifest file can be generated by tool or can be handwritten. In the above PR, the file is handwritten:

And you don’t have to include all the component versions used in WildFly server, and you can only specify the component version you want to override.

Otherwise, the file can also be generated by the Galleon Provisioning tool:

Which I won’t extend the usage of this tool in this blog post. But if you are interested in how to use the tool to generate the manifest file, this branch can be used for reference:

Which contains the usage of the plugin:


As the code shown above, the generate-channel-manifest option of the plugin can be used to generate the manifest file.

So after we have the manifest file, we can use it in the wildfly-maven-plugin:

As you can see the built manifest will be used in provision:


And in the provisioned WildFly server directory we can see the module is override according to the configuration:

➤ find . | grep jberet

You can see the jberet-core-2.2.0-SNAPSHOT.jar is the module overridden by the manifest.

I’d like to thank these people provides me help on this:

My Github Page:

Powered by Jekyll and Theme by solid

If you have any question want to ask or find bugs regarding with my blog posts, please report it here: