Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 368096 - Component Editor does not respect maximum line length in manifest
Summary: Component Editor does not respect maximum line length in manifest
Status: CLOSED WONTFIX
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.2   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: PDE-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: investigate
Depends on:
Blocks:
 
Reported: 2012-01-08 04:28 EST by Christoph Laeubrich CLA
Modified: 2019-09-05 23:25 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Christoph Laeubrich CLA 2012-01-08 04:28:10 EST 
Build Identifier: 20110916-0149

The Component Editor currently adds each component XML file name in one line.
If you add a lot (or some with long path name) component XMLs the ManifestEditor complains "Line to long" of type error.

It would be preferable that the Component Editor wraps the line for each component.xml like it is done for the import/export package, this would also improve readability.

Reproducible: Always

Steps to Reproduce:
1. Create some component.xml's with long names or several with short names
Comment 1 Curtis Windatt CLA 2012-01-13 12:37:01 EST 
This sounds like bug 345045, but that fix should be in the build you specified.  Can you try a newer build and look at bug 345045 to confirm if the problem still exists?
Comment 2 Eclipse Genie CLA 2019-09-05 14:54:05 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.