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

Bug 349884

Summary: ChangeLog entry should add a blank line if adding a new entry above existing one
Product: [Tools] Linux Tools Reporter: Jeff Johnston <jjohnstn>
Component: ChangeLogAssignee: Jeff Johnston <jjohnstn>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: af_0_af, linux.changelog-inbox
Version: 0.8.0   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Whiteboard: stalebug
Attachments:
Description Flags
This patch recognizes new lines by reading the entire line instead of 1 char, so it can tell the differences between sequences like "\n\n" and "\n\t" and decide to keep "\n\n" none

Description Jeff Johnston CLA 2011-06-20 18:02:20 EDT
Adding a new ChangeLog entry above the last entry does not provide a space between the last line of the new entry and the date/comitter line of the existing entry.  A space should be added.  This space was added in the past and perhaps a regression has occurred.
Comment 1 Ken Leung CLA 2011-06-28 10:13:31 EDT
Created attachment 198731 [details]
This patch recognizes new lines by reading the entire line instead of 1 char, so it can tell the differences between sequences like "\n\n" and "\n\t" and decide to keep "\n\n"
Comment 2 Eclipse Genie CLA 2014-06-18 03:14:00 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.
Comment 3 Andrew Ferrazzutti CLA 2015-05-06 15:47:27 EDT
This must have been fixed at some point, since the Insert ChangeLog Entry command indeed adds a new line to the log in the correct section, even when the line is to placed above the last entry in the log. Also, a prefix is added to the line when appropriate; for instance, executing the command while editing a Java method (in a project managed by SVN) prefixes the added Changelog line with the name of the method.

Since everything is again working as intended, I'm marking this as resolved.