Skip to main content

Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » EGit / JGit » Future expectations for
Future expectations for [message #1852522] Fri, 20 May 2022 05:47 Go to next message
Ed Merks is currently offline Ed MerksFriend
Messages: 32493
Registered: July 2009
Senior Member
With the slow demise of Mylyn, I wonder what is the expectation for the contents of in the future?

This project in particular looks to be quite useful and is independent of Mylyn

But it's a bit hard to develop anything against it because the repository doesn't contain sources.

I could imagine using this to automatically create additional remotes to forks when one exists for the user. Many other useful operations would be possible to implement.

But it doesn't make sense to build anything if this bundle might go extinct.

Ed Merks
Professional Support:
Re: Future expectations for [message #1852707 is a reply to message #1852522] Wed, 01 June 2022 16:52 Go to previous messageGo to next message
Thomas Wolf is currently offline Thomas WolfFriend
Messages: 494
Registered: August 2016
Senior Member
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.
Re: Future expectations for [message #1852831 is a reply to message #1852707] Tue, 07 June 2022 07:25 Go to previous message
Thomas Wolf is currently offline Thomas WolfFriend
Messages: 494
Registered: August 2016
Senior Member
BTW: from :
End of Life:

The EGit Mylyn connector is discontinued since Mylyn is no longer maintained. was its last release.

I guess it's high time to move the org.eclipse.egit.github.core library into the main EGit repo. Minor problem might be that the artifact is in the org.eclipse.mylyn.github group.
Previous Topic:Feature Wish: more descriptive Information instead of "Ours"/"Theirs"
Next Topic:File Property Set & Read API in Jgit equivalent to SVN's SvnSetProperty
Goto Forum:

Current Time: Mon Sep 26 10:58:29 GMT 2022

Powered by FUDForum. Page generated in 0.01940 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top