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.
Regards
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.
Doug.
*From:*[email protected]
[mailto:[email protected]] *On Behalf Of
*Mickael Istria
*Sent:* Thursday, August 10, 2017 12:48 PM
*To:* Cross project issues <[email protected]>
*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
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
_______________________________________________
cross-project-issues-dev mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev