<div dir="ltr">I have fixed this upstream (it was only an issue with thin servers, which is why my attempt to reproduce worked). I will release 1.2.6.Final shortly, however I am looking at adding some additional features to help with the Java EE work so this may be in a couple of days.<div><br></div><div>Stuart</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jan 15, 2018 at 10:00 PM, Sanne Grinovero <span dir="ltr"><<a href="mailto:sanne@hibernate.org" target="_blank">sanne@hibernate.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 15 January 2018 at 02:23, Stuart Douglas <<a href="mailto:stuart.w.douglas@gmail.com">stuart.w.douglas@gmail.com</a>> wrote:<br>
> I have released 1.2.5.Final that does not allow overrides by default, there<br>
> is now a 'allow-maven-version-<wbr>overrides' property that allows you to revert<br>
> to the 1.2.4.Final behaviour.<br>
><br>
> If swarm is relying on this behaviour then this option will need to be set<br>
> when you upgrade.<br>
><br>
> Stuart<br>
><br>
> On Mon, Jan 15, 2018 at 12:29 PM, Stuart Douglas<br>
> <<a href="mailto:stuart.w.douglas@gmail.com">stuart.w.douglas@gmail.com</a>> wrote:<br>
>><br>
>> So I had a quick look into this and I can't replicate the same problem but<br>
>> something does appear to be screwy with the plugin.<br>
>><br>
>> This commit<br>
>> <a href="https://github.com/wildfly/wildfly-build-tools/commit/91a076d5e58cebfbd4f734afd6d17b150123c3b1#diff-151a2d1d08d798fdc36537eb125fdbe7R121" rel="noreferrer" target="_blank">https://github.com/wildfly/<wbr>wildfly-build-tools/commit/<wbr>91a076d5e58cebfbd4f734afd6d17b<wbr>150123c3b1#diff-<wbr>151a2d1d08d798fdc36537eb125fdb<wbr>e7R121</a><br>
>> seems to have introduced an issue that I did not notice where the maven<br>
>> plugin will take versions out of the maven project, instead of using the<br>
>> correct versions from the feature pack. This means that if your project has<br>
>> any dependencies that are shared with Wildfly but a different version you<br>
>> will end up using these versions instead and provisioning a broken server<br>
>> config.<br>
>><br>
>> I am not sure if this is the same issue though, can you try with version<br>
>> 1.2.0 of the plugin and see what you get?<br>
<br>
</span>You're right, 1.2.0 deals with it just fine, while both 1.2.4 and 1.2.5 fail.<br>
<br>
I have this minimal project able to reproduce the issue, just checkout<br>
my branch `FeaturePacksv2` - as listed in the PR:<br>
<br>
<a href="https://github.com/hibernate/lucene-jbossmodules/pull/6" rel="noreferrer" target="_blank">https://github.com/hibernate/<wbr>lucene-jbossmodules/pull/6</a><br>
<br>
It's a very light project, you should be able to see the failure in<br>
seconds [after downloading dependencies].<br>
<br>
I'll see if I can use 1.2.0 for the time being..<br>
<br>
Thanks,<br>
Sanne<br>
<div class="HOEnZb"><div class="h5"><br>
>><br>
>> Stuart<br>
>><br>
>> On Mon, Jan 15, 2018 at 11:10 AM, Sanne Grinovero <<a href="mailto:sanne@hibernate.org">sanne@hibernate.org</a>><br>
>> wrote:<br>
>>><br>
>>> Hi all,<br>
>>><br>
>>> I'm attempting to provision an instance of WildFly 11.0.0.Final (full)<br>
>>> to run integration tests using the<br>
>>> `wildfly-server-provisioning-<wbr>maven-plugin`, but I'm getting the<br>
>>> following error:<br>
>>><br>
>>> [ERROR] Failed to execute goal<br>
>>><br>
>>> org.wildfly.build:wildfly-<wbr>server-provisioning-maven-<wbr>plugin:1.2.4.Final:build<br>
>>> (server-provisioning-node1) on project<br>
>>> hibernate-search-<wbr>integrationtest-wildfly: Execution<br>
>>> server-provisioning-node1 of goal<br>
>>><br>
>>> org.wildfly.build:wildfly-<wbr>server-provisioning-maven-<wbr>plugin:1.2.4.Final:build<br>
>>> failed: java.lang.RuntimeException: java.lang.RuntimeException: Failed<br>
>>> to process feature pack<br>
>>><br>
>>> /home/sanne/.m2/repository/<wbr>org/wildfly/wildfly-feature-<wbr>pack/11.0.0.Final/wildfly-<wbr>feature-pack-11.0.0.Final.zip<br>
>>> modules: Could not extract resources from<br>
>>> org.apache.cxf:cxf-rt-ws-<wbr>security?jandex: Failed to resolve<br>
>>> expression: ${org.apache.cxf:cxf-rt-ws-<wbr>security?jandex}<br>
>>><br>
>>> Checking the content, one can see:<br>
>>><br>
>>> # module org.apache.cxf.ws-security contains:<br>
>>><br>
>>> <resources><br>
>>> <artifact name="${org.apache.cxf:cxf-rt-<wbr>ws-security?jandex}"/><br>
>>> </resources><br>
>>><br>
>>> # module org.apache.cxf.impl:<br>
>>><br>
>>> <resources><br>
>>> <artifact name="${org.apache.cxf:cxf-rt-<wbr>security?jandex}"/><br>
>>> ...<br>
>>><br>
>>> I assume this "?jandex" string is not intentional?<br>
>>><br>
>>> Thanks,<br>
>>> Sanne<br>
>>> ______________________________<wbr>_________________<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/<wbr>mailman/listinfo/wildfly-dev</a><br>
>><br>
>><br>
><br>
</div></div></blockquote></div><br></div>