5:44 a.m.
I'm trying to provision a server with the
wildfly-server-provisioning-maven-plugin. The server needs some modules
defined in the core-feature-pack excluded, so I put up excludes in the
dependency management of the pom. However all modules seem to be
included regardless of the projects dependency management.
Is server provisioning ignoring dependency management? If so, I think it
is a bug.
If not, then how should it be done?
Carlo
8:51 a.m.
To answer my own question:
server-provisioning.xml:
<server-provisioning xmlns="urn:wildfly:server-provisioning:1.1"
extract-schemas="true" copy-module-artifacts="true"
extract-schemas-groups="org.wildfly.core">
<feature-packs>
<feature-pack groupId="org.wildfly.core"
artifactId="wildfly-core-feature-pack"
version="${org.wildfly.core}">
<modules>
<filter pattern="*something*"
include="false"/>
</modules>
</feature-pack>
</feature-packs>
</server-provisioning>
Note that it matches against the module.xml path relative to the modules
directory. E.g. system/layers/base/something/main/module.xml
This strikes me as odd, because neither module name comes into play nor
is the pattern a true Java pattern, but a weird mix-up.
Carlo
On 05/18/2017 12:44 PM, Carlo de Wolf wrote:
I'm trying to provision a server with the
wildfly-server-provisioning-maven-plugin. The server needs some modules
defined in the core-feature-pack excluded, so I put up excludes in the
dependency management of the pom. However all modules seem to be
included regardless of the projects dependency management.
Is server provisioning ignoring dependency management? If so, I think it
is a bug.
If not, then how should it be done?
Carlo
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev
2783
days inactive
2783
days old
1 comments
1 participants
participants (1)
-
Carlo de Wolf