Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 347937

Summary: "org.eclipse.cdt.ui_5.1.0.200906161748.jar" plugin can not be rebuilt by eclipse successfully
Product: [Tools] CDT Reporter: Weiquan Cao <caoweiquan322>
Component: cdt-editorAssignee: Project Inbox <cdt-editor-inbox>
Status: RESOLVED INVALID QA Contact: Anton Leherbauer <aleherb+eclipse>
Severity: normal    
Priority: P3 CC: cdtdoug
Version: 8.0   
Target Milestone: ---   
Hardware: PC   
OS: Windows 7   
Whiteboard:

Description Weiquan Cao CLA 2011-06-01 09:36:44 EDT
Build Identifier: 20090621-0832

I tried to make some change to the plugin above("org.eclipse.cdt.ui_5.1.0.200906161748.jar") in order to have a better experience of CDT. I import the source of that plugin, built a new "*.jar" by eclipse without making any change to it. However, the CDT won't open "*.cpp" files any more if I replace the "org.eclipse.cdt.ui_5.1.0.200906161748.jar" with the recently generated one.

Reproducible: Always

Steps to Reproduce:
1.Import "org.eclipse.cdt.ui_5.1.0.200906161748.jar" as source project.
2.Export the project as "Deployable plug-ins and fragments", so get a new "*.jar".
3.replace the "org.eclipse.cdt.ui_5.1.0.200906161748.jar" under "eclipse/plugins" with the new "*.jar" file.
4.restart eclipse.
5.open a "*.cpp" file
6.file open error with some NullPointerException
Comment 1 Anton Leherbauer CLA 2011-06-01 09:42:31 EDT
Replacing the jar file in the installation is not a proper way of installing a new version.  You can try to export into the running installation (look at the export wizard options).
Comment 2 Weiquan Cao CLA 2011-06-01 10:11:41 EDT
(In reply to comment #1)
> Replacing the jar file in the installation is not a proper way of installing a
> new version.  You can try to export into the running installation (look at the
> export wizard options).

It's so kind of you~ Many thanks!
but isn't the new ".jar" all the same with the original one? because I didn't make any change to the source.
Comment 3 Anton Leherbauer CLA 2011-06-01 10:14:10 EDT
If you keep the version exactly the same, i.e. including the qualifier "200906161748", you can also replace the jar in the installation, but that's a hack.