Summary: | Strange javac behaviour when using javac from 1.3.1_09 | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Antoan Nikolaev <anikolaev> | ||||||
Component: | Core | Assignee: | JDT-Core-Inbox <jdt-core-inbox> | ||||||
Status: | RESOLVED DUPLICATE | QA Contact: | |||||||
Severity: | normal | ||||||||
Priority: | P3 | CC: | anikolaev | ||||||
Version: | 3.0 | ||||||||
Target Milestone: | --- | ||||||||
Hardware: | PC | ||||||||
OS: | Windows 2000 | ||||||||
Whiteboard: | |||||||||
Attachments: |
|
Description
Antoan Nikolaev
2003-09-18 14:36:25 EDT
Created attachment 6156 [details]
The file generated with the standard javac
This is the file generated with the standard javac (1.3.1_09)
Created attachment 6157 [details]
File generated through eclipse
this file is generated with eclipse, using 1.3.1_09
Eclipse defines its own compiler implementation, which explains these inconsistencies. This is a known issue coming from the fact that these compiler internals are not specified, and neither compiler is right or wrong. They are just different. Various evolutions of the same compiler also are affecting serialization as well. The only solution is to stick with one compiler version either Eclipse or javac. Also see bug 10104 and related ones. *** This bug has been marked as a duplicate of 10104 *** Note that you can run the Eclipse compiler outside Eclipse through its Ant adapter, or as a command line tool: http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/jdt-core- home/howto/batch%20compile/batchCompile.html |