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.
Stuart
On Mon, Jan 15, 2018 at 10:00 PM, Sanne Grinovero <sanne(a)hibernate.org>
wrote:
On 15 January 2018 at 02:23, Stuart Douglas
<stuart.w.douglas(a)gmail.com>
wrote:
> I have released 1.2.5.Final that does not allow overrides by default,
there
> is now a 'allow-maven-version-overrides' property that allows you to
revert
> to the 1.2.4.Final behaviour.
>
> If swarm is relying on this behaviour then this option will need to be
set
> when you upgrade.
>
> Stuart
>
> On Mon, Jan 15, 2018 at 12:29 PM, Stuart Douglas
> <stuart.w.douglas(a)gmail.com> wrote:
>>
>> So I had a quick look into this and I can't replicate the same problem
but
>> something does appear to be screwy with the plugin.
>>
>> This commit
>>
https://github.com/wildfly/wildfly-build-tools/commit/
91a076d5e58cebfbd4f734afd6d17b150123c3b1#diff-
151a2d1d08d798fdc36537eb125fdbe7R121
>> seems to have introduced an issue that I did not notice where the maven
>> plugin will take versions out of the maven project, instead of using the
>> correct versions from the feature pack. This means that if your project
has
>> any dependencies that are shared with Wildfly but a different version
you
>> will end up using these versions instead and provisioning a broken
server
>> config.
>>
>> I am not sure if this is the same issue though, can you try with version
>> 1.2.0 of the plugin and see what you get?
You're right, 1.2.0 deals with it just fine, while both 1.2.4 and 1.2.5
fail.
I have this minimal project able to reproduce the issue, just checkout
my branch `FeaturePacksv2` - as listed in the PR:
https://github.com/hibernate/lucene-jbossmodules/pull/6
It's a very light project, you should be able to see the failure in
seconds [after downloading dependencies].
I'll see if I can use 1.2.0 for the time being..
Thanks,
Sanne
>>
>> Stuart
>>
>> On Mon, Jan 15, 2018 at 11:10 AM, Sanne Grinovero <sanne(a)hibernate.org>
>> wrote:
>>>
>>> Hi all,
>>>
>>> I'm attempting to provision an instance of WildFly 11.0.0.Final (full)
>>> to run integration tests using the
>>> `wildfly-server-provisioning-maven-plugin`, but I'm getting the
>>> following error:
>>>
>>> [ERROR] Failed to execute goal
>>>
>>> org.wildfly.build:wildfly-server-provisioning-maven-
plugin:1.2.4.Final:build
>>> (server-provisioning-node1) on project
>>> hibernate-search-integrationtest-wildfly: Execution
>>> server-provisioning-node1 of goal
>>>
>>> org.wildfly.build:wildfly-server-provisioning-maven-
plugin:1.2.4.Final:build
>>> failed: java.lang.RuntimeException: java.lang.RuntimeException: Failed
>>> to process feature pack
>>>
>>> /home/sanne/.m2/repository/org/wildfly/wildfly-feature-
pack/11.0.0.Final/wildfly-feature-pack-11.0.0.Final.zip
>>> modules: Could not extract resources from
>>> org.apache.cxf:cxf-rt-ws-security?jandex: Failed to resolve
>>> expression: ${org.apache.cxf:cxf-rt-ws-security?jandex}
>>>
>>> Checking the content, one can see:
>>>
>>> # module org.apache.cxf.ws-security contains:
>>>
>>> <resources>
>>> <artifact
name="${org.apache.cxf:cxf-rt-ws-security?jandex}"/>
>>> </resources>
>>>
>>> # module org.apache.cxf.impl:
>>>
>>> <resources>
>>> <artifact
name="${org.apache.cxf:cxf-rt-security?jandex}"/>
>>> ...
>>>
>>> I assume this "?jandex" string is not intentional?
>>>
>>> Thanks,
>>> Sanne
>>> _______________________________________________
>>> wildfly-dev mailing list
>>> wildfly-dev(a)lists.jboss.org
>>>
https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>
>>
>