-
Notifications
You must be signed in to change notification settings - Fork 8
Lyo 4.0 JAX-RS 2.0 migration breaks twins #150
Comments
Problems caused by TRS Server were fixed by eclipse-lyo/lyo.trs-server#26 Problems caused by TRS Client are tracked in eclipse-lyo/lyo.trs-client#28 |
@jadelkhoury I am actually still at loss: I have tried everything I can to clean up the POM and to clean the IDE cache but I still get that nasty error. Here is my deps tree:
|
@jadelkhoury sorry for the false alarm. Seems like I had broken deps under my M2 folder. Switching to Jersey 2.26 or 2.28 removed warnings. |
But I have a question regarding the base URI, @jadelkhoury: How are we supposed to produce this URI even before the context initialisation event? I load the URI from the You just hardcoded it in the Application class: OSLC/lyo-adaptor-sample-modelling@60ea9ca#diff-f0ffe2c6bda92d771257d76c3525c75bR129 |
Another question @jadelkhoury: The fix for the client (OSLC/lyo-adaptor-sample-modelling@60ea9ca#diff-24dbf31a056f8a216e75f5090c86a92fR45) does not work. Your patch never got merged; @jamsden's client is in master but not deployed on Maven. |
From Portainer logs:
@jadelkhoury made the migration in OSLC/lyo-adaptor-sample-modelling@60ea9ca, we should do the same.
The text was updated successfully, but these errors were encountered: