Re: wildfly-gradle plugin

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Re: wildfly-gradle plugin

Sanne Grinovero
hi Ahmed!

Good point, I didn't make an example for that.

Such defails are controlled in the provisioning.xml file; add
copy-module-artifacts="true" in the server-provisioning, that's in the
main element.

For example see the main example at [1]

<server-provisioning xmlns="urn:wildfly:server-provisioning:1.1"
extract-schemas="true" copy-module-artifacts="true"
                     extract-schemas-groups="org.jboss.as org.wildfly
org.wildfly.core org.jboss.metadata">
  <feature-packs>
    <feature-pack groupId="org.wildfly"
artifactId="wildfly-feature-pack" version="${project.version}">
      <contents>
        <filter pattern="copyright.txt" include="false"/>
        <filter pattern="README.txt" include="false"/>
        <filter pattern="docs/contrib/*" include="false"/>
      </contents>
    </feature-pack>
  </feature-packs>
</server-provisioning>

I'll add an example to the README.

1 - https://github.com/wildfly/wildfly-build-tools/

Thanks,
Sanne

On Tue, 15 Jan 2019 at 14:59, ahmed galal <[hidden email]> wrote:
>
> good day sanne
>
> i was trying to use wildfly-gradle plugin to run some tests on the materialized server using arquillian.
> but the plugin creates a thin version of the server , ho can i configure the plugin to generate a fat version of the server with all the jars ? so i can run it directly from the build directory?
_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev