Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 122984 - JDT core plugin version does not match the version referenced in the feature
Summary: JDT core plugin version does not match the version referenced in the feature
Status: RESOLVED DUPLICATE of bug 89428
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Update (deprecated - use Eclipse>Equinox>p2) (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-Update-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-01-06 18:09 EST by Qingfeng He CLA
Modified: 2006-02-17 09:00 EST (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Qingfeng He CLA 2006-01-06 18:09:02 EST 
I installed Eclipse SDK 3.2M4. 
I clicked help -> software updates -> manage configuration
I expanded c:\eclipse until I saw "Eclipse Java Development Tools 3.2.0.v20051212-0800-05frhQbfqg".
There was an acclaimation symbol with this feature. I checked its property and found its status was as follows:

"Plug-in: "org.eclipse.jdt.core" version: "3.2.0.v-631" referenced by this feature is not included at runtime. Runtime includes plug-in version "3.2.0.v_631" supplied by feature "Eclipse Java Development Tools" version "3.2.0.v20051212-0800-05frhQbfqg"."

Apparently, there was a typo somewhere in Eclipse that the developer confused v-631 and v_631.

I'm not sure this is a severe problem. 

Regards,
Qingfeng
Comment 1 Gunnar Wagenknecht CLA 2006-01-07 03:24:04 EST 
Qingfeng, Community/Bugzilla is for reporting issus with bugs.eclipse.org.

Moving to JDT.
Comment 2 Philipe Mulet CLA 2006-01-09 05:06:46 EST 
The offending qualifier is computed by Releng scripts.
Comment 3 Kim Moir CLA 2006-01-09 10:28:26 EST 
The version in the feature.xml and the name of the jar is correct on the filesystem.  Just the status references 3.2.0.v-631 instead of the correct 3.2.0.v_631. This is not an releng issue, moving to update.
Comment 4 Pascal Rapicault CLA 2006-02-17 09:00:01 EST 

*** This bug has been marked as a duplicate of 89428 ***