Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] LSP4E participation in Photon

Hi Doug

It's unavoidable without partitioning some projects into +1/+2/+3 subprojects. Whenever a non +1 project offers something consumable at +1 there is a problem. Xtext at +2 gives similar troubles for OCL and probably EMF at +1.


        Ed Willink

On 10/08/2017 19:02, Doug Schaefer wrote:

(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-bounces@xxxxxxxxxxx [mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] On Behalf Of Mickael Istria
Sent: Thursday, August 10, 2017 12:48 PM
To: Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
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


Back to the top