Bug 73740 - Diagnosis for serialization should not render j2me development impossible
Summary: Diagnosis for serialization should not render j2me development impossible
Status: VERIFIED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: 3.1 M2   Edit
Assignee: Philipe Mulet CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-09-13 04:12 EDT by Philipe Mulet CLA
Modified: 2004-09-24 07:40 EDT (History)
0 users

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 Philipe Mulet CLA 2004-09-13 04:12:37 EDT 
3.1m1

From newsgroup:

I am using Eclispe 3.1 build 200409070800.

When I use that to build a j2me project (i manually add all j2me class 
files to the project), i get this error:

* The project was not build since its build path is incomplete. Cannot 
find the class file for the java.io.Serializable.

But when I add the J2*S*E system library, it works.

Can you please tell me how to resolve this error? I only see this error 
in Eclispe 3.1 build. And my j2me project build just using ANT, so i am 
sure I don't use java.io.Serializable in my j2me project.

Thank you.
Comment 1 Philipe Mulet CLA 2004-09-14 04:30:44 EDT 
Problem is that compiler is triggering load of Serializable so as to perform 
diagnosis of missing serialVersionUID. It should not cause such a load.
Comment 2 Philipe Mulet CLA 2004-09-20 07:36:21 EDT 
Changed diagnosis to avoid triggering load of Serializable (comparing well-
known ID instead).

Fixed
Comment 3 David Audel CLA 2004-09-24 07:40:02 EDT 
Verified in I200409231635.