<div dir="ltr"><div><div>If you would add maven-enforcer-plugin it would fail if you try to add something like this.<br><br></div>We rely on it for this kind checking in WildFly build.<br><br>--<br></div>tomaz<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Oct 21, 2015 at 2:52 PM, James Netherton <span dir="ltr"><<a href="mailto:jnethert@redhat.com" target="_blank">jnethert@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello everyone,<br>
<br>
Consider the following.<br>
<br>
Feature pack 'A' has a dependency on the WildFly 9 feature pack. E.g:<br>
<br>
<dependencies><br>
<artifact name="org.wildfly:wildfly-feature-pack:9.0.1.Final" /><br>
</dependencies><br>
<br>
Feature pack 'B' has a dependency on the WildFly 10 feature pack and also on feature pack 'A'. E.g:<br>
<br>
<dependencies><br>
<artifact name="org.wildfly:wildfly-feature-pack:10.0.0.CR3" /><br>
<artifact name="org.foo:feature-pack-A" /><br>
</dependencies><br>
<br>
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?<br>
<br>
At the moment the plugins allow this scenario.<br>
<br>
Cheers,<br>
<br>
James<br>
<br>
_______________________________________________<br>
wildfly-dev mailing list<br>
<a href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a></blockquote></div><br></div>