Bug 262720 - feature patch wizard guesses feature name incorrectly
Summary: feature patch wizard guesses feature name incorrectly
Status: CLOSED WONTFIX
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.5   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: PDE-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: bugday
Depends on:
Blocks:
 
Reported: 2009-01-28 05:25 EST by Jacek Pospychala CLA
Modified: 2019-09-09 02:39 EDT (History)
1 user (show)

See Also:

Attachments
screenshot (30.09 KB, image/png)
2009-01-28 05:31 EST, Jacek Pospychala CLA 		no flags Details
View All 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 Jacek Pospychala CLA 2009-01-28 05:25:48 EST 
Build: 3.5M4

In New Feature Patch wizard, when selecting feature to be patched, PDE automatically fills the Feature Name and Feature version fields.
Unfortunately Feature name is always filled with "%featureName".

Note, I'm not sure if this "Feature Name" field is ever used, because later in feature.xml nor in feature editor, there's no mention about patched feature name.
Only feature ID and version are used.

Maybe simply remove that field?
Comment 1 Jacek Pospychala CLA 2009-01-28 05:31:03 EST 
Created attachment 124003 [details]
screenshot

screenshot
Comment 2 Eclipse Webmaster CLA 2019-09-06 15:30:23 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.
Comment 3 Julian Honnen CLA 2019-09-09 02:39:17 EDT 
Please remove the stalebug flag, if this issue is still relevant and can be reproduced on the latest release.