Generating jboss-deployment.structure.xml using Maven

One way you could automate the generation of the jboss-deployment-structure.xml is by using the Maven resource filtering feature, which allows you to replace placeholders in your resource files with their respective values from the Maven properties during the build process.

You would first need to include placeholders for the versions of your libraries in the jboss-deployment-structure.xml, like so:

<?xml version="1.0" encoding="UTF-8"?>
<jboss-deployment-structure>
    <!-- Make sub deployments isolated by default, so they cannot see each others 
        classes without a Class-Path entry -->
    <ear-subdeployments-isolated>true</ear-subdeployments-isolated>
    <deployment>
        <resources>
            <resource-root path="lib/apache/commons-lang3-${commons.lang.version}.jar" />
            <resource-root path="lib/joda/joda-time-${joda.time.version}.jar" />
        </resources>
    </deployment>
</jboss-deployment-structure>

Next, you would define these placeholders in your pom.xml:

<properties>
    <commons.lang.version>3.3.2</commons.lang.version>
    <joda.time.version>2.0</joda.time.version>
</properties>

Finally, you would need to configure your project to use Maven resource filtering. You can do this by adding a resources element to your build configuration in your pom.xml:

<build>
    <resources>
        <resource>
            <directory>src/main/application/META-INF</directory>
            <filtering>true</filtering>
        </resource>
    </resources>
    ...
</build>

This setup will replace the placeholders in your jboss-deployment-structure.xml with the respective values from the Maven properties when you build your project.

Remember to update the version numbers in the properties section of your pom.xml file whenever you change the version of a library, and the jboss-deployment-structure.xml will be updated automatically during the build process.