Bug 296661

Summary: subclipse doesn't work anymore with 1.2.4 update
Product: [Fedora] Fedora Reporter: Hugues Thiébaux <ht>
Component: eclipse-subclipseAssignee: Robert Marcano <robert>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: low    
Version: 7CC: fedora
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-09-19 17:57:01 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
java.lang.ClassNotFoundException: org.tigris.subversion.subclipse.ui.repository.RepositoriesView none

Description Hugues Thiébaux 2007-09-19 17:40:25 UTC 
Description of problem:
Subclipse doesn't work anymore after an update from 1.2.0 to 1.2.4

Version-Release number of selected component (if applicable):
1.2.4

How reproducible:
yum update ...

Steps to Reproduce:
1. update package
2. launch eclipse
3. go to SVN repository view
  
Actual results:
Unable to create view: Plug-in org.tigris.subversion.subclipse.ui was unable to
load class org.tigris.subversion.subclipse.ui.repository.RepositoriesView.

Expected results:
Working

Additional info:
See log in attachment
Comment 1 Hugues Thiébaux 2007-09-19 17:40:25 UTC 
Created attachment 199841 [details]
java.lang.ClassNotFoundException: org.tigris.subversion.subclipse.ui.repository.RepositoriesView
Comment 2 Robert Marcano 2007-09-19 17:57:01 UTC 
Received a direct email about the problem and the update is already on the way.
Temporary workaround:

edit
/usr/share/eclipse/plugins/org.tigris.subversion.subclipse.core_1.2.4/META-INF/MANIFEST.MF

and add 

 lib/subclipse-core.jar,

after

Bundle-ClassPath: .,

and remove your $HOME/.eclipse directory

For some reason something is cached there that when I tested the
previous version of the Classpath was used and not this new wrong one,
so i think that was the reason i did not saw the error (If you do not
remove your .eclipse directory the error will continue to appear even
after the MANIFEST.MF file is fixed weird)
Comment 3 Robert Marcano 2007-09-20 12:30:43 UTC 
*** Bug 297651 has been marked as a duplicate of this bug. ***