(This time with text.)

OK. That’s how we got away with CDT’s build cycle. Does point out a bit of a 
flaw with our offsets here. At the end of the day, we’ll build against your 
builds on Jenkins, not on what you post to the downloads area, to make sure we 
find out about changes early enough to recover.


From: cross-project-issues-dev-boun...@eclipse.org 
[mailto:cross-project-issues-dev-boun...@eclipse.org] On Behalf Of Mickael 
Sent: Thursday, August 10, 2017 12:48 PM
To: Cross project issues <cross-project-issues-dev@eclipse.org>
Subject: Re: [cross-project-issues-dev] LSP4E participation in Photon

> Just curious, why +3?

Because the main dependency (LSP4J) is +2.

> We are thinking of adding a component that uses it to CDT to access the 
> clangd language server.
You can still use it. At the moment, LSP4E tries to keep focus on good forward 
and backward compatibility, so CDT shouldn't face so much issues on release if 
it's using LSP4E snapshots or milestones.
cross-project-issues-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit

Reply via email to