If you would add maven-enforcer-plugin it would fail if you try to add something like this.

We rely on it for this kind checking in WildFly build.


On Wed, Oct 21, 2015 at 2:52 PM, James Netherton <jnethert@redhat.com> wrote:
Hello everyone,

Consider the following.

Feature pack 'A' has a dependency on the WildFly 9 feature pack. E.g:

  <artifact name="org.wildfly:wildfly-feature-pack:9.0.1.Final" />

Feature pack 'B' has a dependency on the WildFly 10 feature pack and also on feature pack 'A'. E.g:

  <artifact name="org.wildfly:wildfly-feature-pack:10.0.0.CR3" />
  <artifact name="org.foo:feature-pack-A" />

Leaving the sanity and validity of doing this aside, should the feature-pack-build or server-provisioning-plugin be detecting this as an error condition, given that you'll have overlapping and possibly problematic non-overlapping file paths coming from the conflicting WildFly versions?

At the moment the plugins allow this scenario.



wildfly-dev mailing list