I'm happy to have lyo Designer tied to OSLC4J releases, and don't think its necessary to have a lyo Designer option to specify the target OSLC4J version to use.
Jim Amsden, Senior Technical Staff Member
OSLC and Linked Lifecycle Data
919-525-6575
From: Andrii Berezovskyi <andriib@xxxxxx>
To: Lyo project developer discussions <lyo-dev@xxxxxxxxxxx>
Date: 03/05/2019 02:49 PM
Subject: Re: [lyo-dev] [LYO] LyoDesigner for Jersey2.0
Sent by: lyo-dev-bounces@xxxxxxxxxxx
Jim,
I am not sure how to interpret your reply. Do you want to tie Lyo Designed to the version of the Lyo libraries or not? They have been tied this way from the early LyoD releases (I think circa Lyo 2.2).
For everyone else: JAX-RS 2.0 requires breaking changes to both the libraries and the generator. Both of those changes have been merged to master on for the upcoming 4.0 release. If you use Lyo 2.x, stay on the same version of LyoD.
/A
2019-03-05 kl. 19:53 skrev Jim Amsden <jamsden@xxxxxxxxxx>:
I think Lyo Designer users are mostly interested in the Lyo Designer features that can be modeled and translated into an implementing server. Where that requires some alignment with a lyo.core, lyo.server
or lyo.client version in order to support the particular feature, this would seem relevant and desirable to distinguish.
Where the changes reflect underlying implementation details that have no surface manifestation (e.g. Jena version, JAX-RS version, etc.) then version alignment seems less important.
Jim Amsden, Senior Technical Staff Member
OSLC and Linked Lifecycle Data
919-525-6575
From: Andrii Berezovskyi <andriib@xxxxxx>
To: Eclipse Lyo Dev List <lyo-dev@xxxxxxxxxxx>
Date: 03/05/2019 01:26 PM
Subject: Re: [lyo-dev] [LYO] LyoDesigner for Jersey2.0
Sent by: lyo-dev-bounces@xxxxxxxxxxx
Hello everyone,
CCing you on the Lyo Designer discussion. The question is how much should LyoD support old Lyo releases.
Jim, Jad, I believe Alt1 and "Alt3" are the same thing. The users of Lyo 4.0 will use LyoD 4.0 and those who wish to stay on Lyo 2.4 use LyoD 2.4. Just as the users of Lyo 2.3 use LyoD 2.3.
/A
2019-03-01 kl. 22:39 skrev Jad El-Khoury <jad@xxxxxx>:
Hi Jim
I am not sure what you mean by this third option.
The generated code will certainly look different for Wink or Jax-rs2.0.
I am inclined for Alt1, which means LyoDesigner 2.4.0 is suitable for OSLC4J 2.4.0, while LyoDesigner 4.0.0 is suitable for OSLC4J 4.0.0.
@Andrii! I am not sure why I only emailed committers. I think I just copied the email list from your latest email.
regards
______________________________
Jad El-khoury, PhD
KTH Royal Institute of Technology
School of Industrial Engineering and Management, Mechatronics Division
Brinellvägen 83, SE-100 44 Stockholm, Sweden
Phone: +46(0)8 790 6877 Mobile: +46(0)70 773 93 45
jad@xxxxxx,
www.kth.se
From: Jim Amsden [mailto:jamsden@xxxxxxxxxx]
Sent: 01 March 2019 18:45
To: Andrii Berezovskyi <andriib@xxxxxx>
Cc: Jad El-Khoury <jad@xxxxxx>; Ricardo Javier Herrera Ledesma <neormx@xxxxxxxxx>;
Yash Khatri <yash.s.khatri@xxxxxxxxx>
Subject: Re: [LYO] LyoDesigner for Jersey2.0
There's a third option - sync Lyo designer 2.4.0 with OSLC4J 2.4.0 and leave it at that.
Its not clear why any user of Lyo Designer would care about JAX-RS 1/2, as that's simply an internal REST services API. Nor do I see why they'd care what version of OSLC4J is used in the implementation. There code that depends on these versions is implementation
detail. What they would care about is the features and functions of the server.
Jim Amsden, Senior Technical Staff Member
OSLC and Linked Lifecycle Data
919-525-6575
From: Andrii Berezovskyi <andriib@xxxxxx>
To: Jad El-Khoury <jad@xxxxxx>
Cc: Jim Amsden <jamsden@xxxxxxxxxx>, Yash Khatri <yash.s.khatri@xxxxxxxxx>,
Ricardo Javier Herrera Ledesma <neormx@xxxxxxxxx>
Date: 02/27/2019 07:22 AM
Subject: Re: [LYO] LyoDesigner for Jersey2.0
+1 for Alt1!
Most importantly, I don't think anybody is using LyoD in production just yet and you still can get away with a breaking change or two. I don't have time to maintain Alt2 or anything related to that. Plus, there are security vulnerabilities in old releases that
nobody should be using anyway.
P.S. Why not on lyo-dev?
2019-02-27 kl. 11:48 skrev Jad El-Khoury <jad@xxxxxx>:
Hi,
Now that Lyo 4.0 has moved to Jax-rs2.0, we need to update LyoDesigner generation to match. I see 2 alternatives that I would like your input on.
Alt1. Generate code that suits jax-rs2.0, making LyoDesigner 4.0 not suitable for people still using Lyo 2.4.0 (ie. Wink)
Alt2. Give the user an alternative to choose generation for Wink or Jax-rs2.0.
Of course, Alt1 is much easier for me to handle. But there is a risk that we loose those that still want to use Lyo 2.4.0.
Or, could it be that Jax-rs2.0 code is still compatible with Wink?
Regards
Jad
Ps. I’m now back online, and in the process of going through Lyo mails
_______________________________________________
lyo-dev mailing list
lyo-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/lyo-dev
_______________________________________________
lyo-dev mailing list
lyo-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/lyo-dev
_______________________________________________
lyo-dev mailing list
lyo-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/lyo-dev
_______________________________________________
lyo-dev mailing list
lyo-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/lyo-dev
