Hi folks, I am not sure, but I think there are numerous projects that depend on Notifications framework from Mylyn. For example LSP4E does:
https://git.eclipse.org/r/plugins/gitiles/lsp4e/lsp4e/+/refs/heads/master/org.eclipse.lsp4e/src/org/eclipse/lsp4e/ServerMessageHandler.java Not sure what the best path forward for that is, for example how easy would it be to pull out of Mylyn. Over the last few years BIRT went temporarily into this same situation (It is coming back now! https://twitter.com/BirtEclipse/status/1367319082987622400) - so in SimRel this was handled by the projects that needed parts of BIRT having to contribute those parts themself (e.g. the MAT project does that https://git.eclipse.org/r/plugins/gitiles/simrel/org.eclipse.simrel.build/+/refs/heads/master/mat.aggrcon#4). I hope that BIRT comes back soon to SimRel as the reboot progresses. Likewise I hope that Mylyn can also have such a resurgence. Thanks Jonah ~~~ Jonah Graham Kichwa Coders www.kichwacoders.com On Fri, 21 May 2021 at 16:14, Sam Davis <sam.da...@tasktop.com> wrote: > From: Mik Kersten <m...@tasktop.com> > Date: Fri, May 21, 2021 at 10:34 AM > Subject: Mylyn > To: <cross-project-issues-dev@eclipse.org> > Cc: Sam Davis <sam.da...@tasktop.com> > > > I wanted to give the group a heads up that there are issues with Mylyn > that could affect the simultaneous release. > > For context, Mylyn (originally Mylar) was a passion and PhD project of > mine that has been a part of the Eclipse ecosystem for 15 years now. It > has lived a good and full product lifecycle, and for the past few years, > neither I nor the other staff at Tasktop who have been contributing once my > role transitioned have been able to put enough time into to provide > adequate support for inclusion in the simultaneous release. Back in > December, Sam Davis pushed a review to pull Mylyn out of the Simultaneous > release, but that did not happen due to dependencies, and there wasn’t > follow up on the corresponding communication so it has not yet happened. > > Where we stand today is that due to the JIPP migration, Mylyn cannot > release. This puts the SimRel at risk of being blocked. Given that the > Mylyn project lacks the resources to address this, so we would like to > remove Mylyn from the SimRel. This will require other projects, EPP > packages, and Oomph to remove their dependencies on Mylyn unless there are > other parties who could contribute the resources to make this happen. > > If anyone is interested in taking this on, Sam and I would be more than > happy to pass on the reins! > > Assuming that does not happen, we think that it would be in everyone's > interest to deal with this now, before it becomes urgent. Please reply to > this thread if your project depends on Mylyn. This includes Mylyn > Tasks/Context/Commons/Builds/Reviews/Versions, but not Mylyn Docs/Wikitext. > > And on a more personal note, I have very fond memories of being a close > part of the Eclipse ecosystem. It is great to see it continuing, I miss > interacting the many people who were collaborators over the years, and hope > everyone is doing well and that we cross paths at some conference or other > in 2022! > > Best, > > Mik > > -- > Dr. Mik Kersten > CEO https://tasktop.com > Author https://projecttoproduct.org > > > > > _______________________________________________ > cross-project-issues-dev mailing list > cross-project-issues-dev@eclipse.org > To unsubscribe from this list, visit > https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev >
_______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
