Hi folks, TL;DR: LSP4J is contributing 0.8.1 <https://projects.eclipse.org/projects/technology.lsp4j/releases/0.8.1> after all to 2019-12.
Unfortunately we are not in a position to release 0.9.0 in a timely manner today. However I have figured out how to fully release 0.8.1 to download.eclipse.org. Therefore for 2019-12 we are contributing <https://git.eclipse.org/r/#/c/153441/> v0.8.1 as planned. Thank you Christian for your reviews today on automating the LSP4J releases on Eclipse's CI infrastructure. I am still not clear as to why 0.8.1 was not fully released in September, hopefully we can get some clarity on that in the future. Jonah ~~~ Jonah Graham Kichwa Coders www.kichwacoders.com On Tue, 26 Nov 2019 at 09:51, Jonah Graham <jo...@kichwacoders.com> wrote: > Hello folks, > > TL;DR: I want to contribute LSP4J 0.9.0 > <https://projects.eclipse.org/projects/technology.lsp4j/releases/0.9.0> > to instead of 0.8.1 > <https://projects.eclipse.org/projects/technology.lsp4j/releases/0.8.1>. > > The Eclipse LSP4J project wants to change the version it is contributing > to the simrel. At the moment we are signed up for releasing 0.8.1, however > there is no one available to do the release engineering to complete the > P2/simrel part of this release (the release is partially completed on > maven, but no one has done the simrel contributions & upload of artifacts > to download.eclipse.org). Instead I am updating LSP4J so that we can > release 0.9.0 along with the 2019-12 simrel. Note that consumers of LSP4J > (namely LSP4E) have contributed fixes to LSP4J that they want to use in > 2019-12. > > I am aware this is last minute, as a result I have checked all consumers > in simrel of LSP4J (based on declaring dependency to an LSP4J package or > bundle in their MANIFEST.MF) and these are all the bundles that consume > LSP4J. > > org.eclipse.lsp4e > org.eclipse.lsp4e.debug > org.eclipse.corrosion > org.eclipse.cdt.debug.dap > org.eclipse.cdt.debug.dap.gdbjtag > org.eclipse.wildwebdeveloper > org.eclipse.xtext.ide > org.eclipse.xtext.testing > > Today is LSP4J's contibution day for M3 (+2), so please let me know as > soon as possible if this is a problem as I plan on doing the release later > today. See LSP4J's Bug 369 <https://github.com/eclipse/lsp4j/issues/369> for > some details of how we got to this point. > > Jonah > > > ~~~ > Jonah Graham > Kichwa Coders > www.kichwacoders.com >
_______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
