Skip to content
This repository has been archived by the owner on Oct 12, 2021. It is now read-only.

Use of the old Lyo Client drags the JSR311 dep #28

Closed
berezovskyi opened this issue Feb 17, 2019 · 5 comments · Fixed by #32
Closed

Use of the old Lyo Client drags the JSR311 dep #28

berezovskyi opened this issue Feb 17, 2019 · 5 comments · Fixed by #32
Assignees
@berezovskyi
Labels
Priority: Critical Status: Blocked Type: Bug

Comments

@berezovskyi
Copy link
Contributor

See eclipse-lyo/lyo.core#79 for the bug report.
@berezovskyi berezovskyi self-assigned this Feb 17, 2019
@berezovskyi berezovskyi mentioned this issue Feb 17, 2019
Closed
@berezovskyi
Copy link
Contributor Author

Blocked by eclipse-lyo/lyo.client#40

@berezovskyi
Copy link
Contributor Author

Prompted by EricssonResearch/scott-eu#150

@berezovskyi
Copy link
Contributor Author

berezovskyi commented Feb 17, 2019 •
edited
Loading

An actual disaster is not a client API change but extensive use of old OAuth classes & APIs.

@berezovskyi berezovskyi mentioned this issue Feb 17, 2019
Merged
@jamsden
Copy link

jamsden commented Feb 18, 2019

I was aware of this. Is there a problem leaving this dependency in the old code?

@berezovskyi
Copy link
Contributor Author

I am OK leaving it in the old adaptors but this one is about the TRS Client which I depend on in every new OSLC Server I build... So, no, this is not an option. But I managed to eliminate any OAuth-related code: it turned out to be a lot of exception signatures that dragged imports from oauth libs.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@berezovskyi berezovskyi

Labels
Priority: Critical Status: Blocked Type: Bug
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Migrate to the new oslc4j-client eclipse-lyo/lyo.trs-client
2 participants
@berezovskyi @jamsden