https://bugzilla.redhat.com/show_bug.cgi?id=1455279
--- Comment #7 from Jerry Amundson <jamundso(a)gmail.com> ---
(In reply to Roland Grunberg from comment #6)
I should have noticed this earlier but it looks like
org.eclipse.jgit_4.7.0.201704051617-r is requiring com.googlecode.javaewah;
version="[0.8.0,1.0.0)" but javaewah-1.1.6-1.fc26.noarch would be exporting
outside that range, hence the inability to resolve.
However looking inside org.eclipse.jgit_4.7.0.201704051617-r,
(/usr/share/java/jgit/org.eclipse.jgit.jar symlinked from
/usr/share/eclipse/droplets/jgit/eclipse/plugins/org.eclipse.jgit_4.7.0.
201704051617-r.jar) I can clearly see 'Import-Package =
com.googlecode.javaewah;version="[1.1.6,2.0.0)"' . What is the
Import-Package statement you see in the jgit jar on your system ?
Import-Package: com.googlecode.javaewah;version="[1.1.6,2.0.0)",com.jc
raft.jsch;version="[0.1.37,0.2.0)",javax.crypto,javax.net.ssl,org.slf
4j;version="[1.7.0,2.0.0)",org.xml.sax,org.xml.sax.helpers
If it's identical to what I've listed above (eg.
[1.1.6,2.0.0) ), then I
would try re-running Eclipse from the commandline with the '-clean' option.
This could be a case of stale data that's still cached by Eclipse.
This is a shot in the dark, but this likely happened due to
http://pkgs.fedoraproject.org/cgit/rpms/eclipse-jgit.git/commit/
?id=be531b427c93118a7e5b8703fcc73f69a15de064 . This modified the dependency
metadata but since the timestamp likely remained the same (it's a symlink),
a 'clean' never occurred.
That did it! Whoot!
I see the Git perspective, the Git menu under the Team preferences, etc. Yay!
Thank you!
--
You are receiving this mail because:
You are on the CC list for the bug.