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

Bug 343057

Summary: Feature project's OS filter not registering list of OSs with white spaces after commas
Product: [Eclipse Project] PDE Reporter: Petri Tuononen <petri.tuononen>
Component: UIAssignee: PDE-UI-Inbox <pde-ui-inbox>
Status: CLOSED WONTFIX QA Contact:
Severity: normal    
Priority: P3    
Version: 4.0   
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard: stalebug

Description Petri Tuononen CLA 2011-04-16 23:36:09 EDT 
Build Identifier: 20100617-1415

If one tries to form an OS filter list in feature project I personally find it intuitive to add a white space after a comma. Although what really happens is that if user types white spaces after commas only the first OS on the list is actually registered by the feature project. This can be seen by pressing the browse button next to the text field and it is clear that the only OS checkbox that is selected is the first one on the list. This leads to the fact that user is not able to install the plug-in on another operating systems than the first one on the list.

Typing a list without white spaces works but I would suggest that a list with white spaces after commas would be registered similarly.

Reproducible: Always

Steps to Reproduce:
1. Create a feature project (PDE tools)
2. Open feature.xml
3. Open Overview tab
4. Under Supported Environment -> Operating Systems type the following "linux, macosx, win32"
5. Click Browse... button on the right side of the text field
6. Notice that only one operating system checkbox is selected
(7. Add plug-in on the plug-ins tab; create update-site project and create a category with feature inside it; build all; transfer update-site via ftp to a web server; try to install plug-in on Windows via update site; notice error that filter is not applicable preventing installation of the plug-in)
Comment 1 Eclipse Genie CLA 2019-09-23 09:44:49 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.