|Re: Future expectations for https://git.eclipse.org/c/egit/egit-github.git/ [message #1852707 is a reply to message #1852522]
||Wed, 01 June 2022 16:52
| Thomas Wolf
Registered: August 2016
Perhaps this question might get more discussion if posted to the egit-dev mailing list.|
egit-github contains one general-purpose Github HTTPS REST API library org.eclipse.egit.github.core. That one does not depend on Mylyn, nor on EGit nor on JGit, and occasionally there were new contributions and fixes. AFAIK it is in pretty good shape and uses Java 8 as BREE for Android backwards compatibility. It would be good if we could set up some automatic deployment of releases to maven central; there is a long-standing bug about this. It appears that this lapsed way back. Some newer Github API needs HTTP PATCH requests and those are not supported. Support for that could be added in a new bundle org.eclipse.egit.github.extensions with BREE Java 11, using the Java 11 HttpClient.
The other org.eclipse.mylyn.* bundles use EGit, JGit, and the above REST API bundle to implement a number of nice features in the Mylyn framework to work with Github PRs, issues, and gists. The implementation appears not to be fully complete (IIRC some odds and ends are missing). There has been basically no development after 2012; we mostly only made sure these bundles still compile and build. When Github started to require a PAT for API calls, I changed the repository setup wizard in this Mylyn Github Connector to support that better.
If Mylyn dies, so will these bundles, and functionality then missing and still wanted would need to be re-implemented either using a different framework or from scratch.
Long-term I think the org.eclipse.egit.github.core bundle could perhaps move to the main egit repository.
Powered by FUDForum
. Page generated in 0.01940 seconds