Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 359193 - Assigning value to a variable causes Runtime exception
Summary: Assigning value to a variable causes Runtime exception
Status: CLOSED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: EDT (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P1 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-28 05:12 EDT by pf yu CLA
Modified: 2017-02-23 14:19 EST (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description pf yu CLA 2011-09-28 05:12:32 EDT
Build Identifier: 0.7.0.v201109270901-1CM-Fh1z-WFEbA2fb8WD

Assigning value to a variable causes Runtime exception:
Multiple markers at this line
	- IWN.JavaGen.9998.e 25/647 Exception occurred: 
	 java.lang.NullPointerException
	- IWN.JavaGen.9999.e 25/647 Stack Trace: java.lang.NullPointerException

Reproducible: Always

Steps to Reproduce:
1. Check out project "org.eclipse.edt.eunit.test" from kan-cvs.
2. Add java generator to the project.
3. Clean the whole workspace.
4. The errors exist in the following egl files:
fvt.datatypes.TestNullableStringLib
fvt.datatypes.TestStringsLib
fvt.primitives.TestDateTimeLib
fvt.systemWords.TestGeneralSystemFunctionsLib
fvt.systemWords.TestSysLibTestLib
Comment 1 Paul Harmon CLA 2011-11-01 11:11:04 EDT
By runtime exception, i assume you meant generation exception.

These EGL files all appear to generate cleanly now. I did not attempt to run them, though.
Comment 2 pf yu CLA 2011-11-08 02:55:13 EST
Verified in build 20111107