Community
Participate
Working Groups
The README at org.eclipse.egit.github.core/ says there are built versions of the GitHub Java library from the Sonatype OSS repository, but they are quite old. Any chance of updating them?
FWIW, you can use Eclipse's Maven repository instead, which has newer releases: https://wiki.eclipse.org/Services/Nexus#Pulling_artifacts_from_Nexus Maven Central might get a recent release after EclipseCon: http://dev.eclipse.org/mhonarc/lists/egit-dev/msg03810.html
(In reply to Chris Rebert from comment #1) > FWIW, you can use Eclipse's Maven repository instead, which has newer > releases: > https://wiki.eclipse.org/Services/Nexus#Pulling_artifacts_from_Nexus > > Maven Central might get a recent release after EclipseCon: > http://dev.eclipse.org/mhonarc/lists/egit-dev/msg03810.html Thanks for the info, I didn't know those repos existed.
Well, bump :-) This seems to not have too much priority so I'd like to add my use case. EGit/GitHub is a solid, low-dependencies, OSGi-enabled library which is precisely what I am looking for. The downside is that it is not available on Maven Central. Building an open-source application (http://sling.apache.org/) we are unable to ask our users to add custom Maven repositories. So I come back to this bug and ask you to reconsider publishing GitHub to Maven Central as it would make consuming EGit/GitHub much easier. You can see the effect of the library not being deployed on Maven at https://github.com/github/maven-plugins/issues/74 . Thanks for considering this.
+1 from my side. Reasons: 1. The library is recommended *as first item* by GitHub: https://developer.github.com/v3/libraries/ 2. Old versions are published on Maven Central: https://search.maven.org/search?q=g:org.eclipse.mylyn.github%20AND%20a:org.eclipse.egit.github.core&core=gav 3. The library seems to be the most complete one to work on commits.
This bug is being problematic for me as well.
@Matthias, can we set up the egit-github-stable job to do that automatically if it builds an "-r" version? Besides having a GPG key on JIRO and GPG-signing the code & source bundles as explained at [1] what else would be needed? [1] https://wiki.eclipse.org/Jenkins#How_can_artifacts_be_deployed_to_OSSRH_.2F_Maven_Central.3F
Any chance this will be fixed soon? The mylyn team would take responsibility for the mylyn GitHub Connector but not for org.eclipse.egit.github.core. So we need a way that we can consume the jar/plugin/feature.
