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

Bug 387021

Summary: revert unmotivated changes to readableNames.props in bug 381567
Product: [Eclipse Project] JDT Reporter: Stephan Herrmann <stephan.herrmann>
Component: CoreAssignee: Stephan Herrmann <stephan.herrmann>
Status: CLOSED WORKSFORME QA Contact:
Severity: normal    
Priority: P3 CC: srikanth_sankaran
Version: 3.8   
Target Milestone: 4.16 M3   
Hardware: All   
OS: All   
Whiteboard: stalebug

Description Stephan Herrmann CLA 2012-08-10 10:22:55 EDT 
Bug 381567 changed the generated file readableNames.props, why?

This change removed the copyright notice in that file which looks wrong to me.
Comment 1 Srikanth Sankaran CLA 2012-08-10 11:02:51 EDT 
(In reply to comment #0)
> Bug 381567 changed the generated file readableNames.props, why?

Mea culpa. The underlying problem is that the (non-public) parser 
generator tools discard the copyright. This is a pain in the wrong 
place.

I'll fix this once M1 sails out. Thanks for spotting this.
Comment 2 Stephan Herrmann CLA 2014-11-02 08:16:18 EST 
Didn't Jesper come up with a Java main for invoking the parser generator and invoking post processing?

Otherwise I might contribute (and improve) the corresponding shell scripts from the Object Teams project.

I think it would be good to have a simple tool that's publicly available for all contributors.
Comment 3 Srikanth Sankaran CLA 2014-11-03 21:38:45 EST 
(In reply to Stephan Herrmann from comment #2)
> Didn't Jesper come up with a Java main for invoking the parser generator and
> invoking post processing?

Don't know the status of this.

> Otherwise I might contribute (and improve) the corresponding shell scripts
> from the Object Teams project.

Thanks!
Comment 4 Eclipse Genie CLA 2020-04-19 16:30:13 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. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. 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.
Comment 5 Stephan Herrmann CLA 2020-04-19 17:48:03 EDT 
The file has been restored many times since.