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

Bug 431085

Summary:	[1.8] Compiler/Classfile Generation: Store method parameter names requires clean when re-enabled
Product:	[Eclipse Project] JDT	Reporter:	Maarten Bodewes <maarten.bodewes>
Component:	Core	Assignee:	Sasikanth Bharadwaj <sasikanth.bharadwaj>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	minor
Priority:	P3	CC:	jarthana, srikanth_sankaran
Version:	4.3.2
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
Whiteboard:	stalebug

Description Maarten Bodewes

2014-03-25 05:18:48 EDT

When re-enabling Java 8 parameter names in Kepler (see title) using the initial support in Java Development Tools Core version 3.9.50.v20140317-1741, it is required to do a clean to regenerate the parameter names.

How to reproduce this bug:

 - make sure auto-build is on
 - enable "Store method parameter names" for a project
 - run application printing out parameter name using reflection, this will e.g. display "args" for the main method (and not "arg0" as in Java 7)
 - disable "Store method parameter names" for a project
 - run application printing out parameter name using reflection, this will output "arg0" for the first parameter
 - re-enable "Store method parameter names" for a project
 - run application printing out parameter name using reflection, this will output "arg0" for the first parameter <- that's incorrect
 - clean project
 - run application printing out parameter name using reflection, this will output "args" for the first parameter, which is different from before the clean

Note that I don't see this minor issue in 4.4 with Java 8 enabled, so I presume something is incorrect in the class file detection in 4.3.

(that's a lot of text for such a small bug :) )

Comment 1 Srikanth Sankaran

2014-03-25 23:30:53 EDT

Sasi, please take a look. You need to write a program using reflection to
test behavior. See org.eclipse.jdt.core.tests.compiler.regression.LambdaExpressionsTest.test430015()
for example.

Comment 2 Jay Arthanareeswaran

2014-05-22 22:52:32 EDT

With not much time left in Luna, we will handle this in 4.5 or 4.4.1.

Comment 3 Sasikanth Bharadwaj

2015-04-20 01:19:13 EDT

Moving out, @Jay, is this still relevant?

Comment 4 Eclipse Genie

2019-10-24 15:52:29 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.