Hi Libor,
thanks a lot for your quick reply!
I specified the desired MOXy version in the pom.xml using the
dependencyManagement, and it worked fine.
For the upgrade to a newer MOXy version, I am still waiting for a bugfix
to be officially released. I'll create an issue after that.
Thanks again and kind regards
Duc
On 28.01.2015 10:31, Libor Kramolis wrote:
> Hi Duc.
>
> You can force Maven to use your preferred version in pom.xml, see http://stackoverflow.com/a/3937255/957021 <http://stackoverflow.com/a/3937255/957021>. Regarding to upgrading to newer MOXy version, please create an issue for that https://java.net/jira/browse/JERSEY <https://java.net/jira/browse/JERSEY>. Thanks.
>
> Best regards,
> Libor
>
>
>> On 27 Jan 2015, at 18:00, Duc Luu <laudak_at_gmx.net> wrote:
>>
>> Hi all,
>>
>> I discovered that the newest version 2.15 of jersey-media-moxy is still dependent to an old version 2.5.0 of EclipseLink MOXy (when using Maven to resolve dependencies).
>>
>> Is there any convenient way to switch to a newer version of MOXy, besides building an own version from source?
>>
>> And when would jersey-media-moxy officially switch to a newer MOXy version?
>>
>> Thanks and regards
>> Duc
>
>