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

Bug 433193

Summary: Failed to create a project whose name contains question mark
Product: [ECD] Orion Reporter: Akihiko Takajo <takajo>
Component: ClientAssignee: Mark Macdonald <mamacdon>
Status: RESOLVED WONTFIX QA Contact:
Severity: minor    
Priority: P3 CC: ahunter.eclipse, camle, elijahe, ken_walker, mamacdon
Version: 5.0   
Target Milestone: ---   
Hardware: PC   
OS: Windows 7   
Whiteboard:

Description Akihiko Takajo CLA 2014-04-22 08:07:38 EDT 
Failed to create a project whose name contains question mark '?' (e.g. question?project), And can't delete the content.

Steps:
1. Create a basic project which name has a question mark e.g. question?project
=> Failed to create a project
2. Refresh the screen and remove the project
 (right-click on the tree view and select delete)
3. Click OK
=> the content remains

workaround to delete the content: rename the content which should not contain question mark, then delete.

testcase: GVT0110 – CREATE A NEW BASIC PROJECT USING THE FILE MENU

environment:
IE11, Firefox28, Chrome34
Comment 1 Anthony Hunter CLA 2014-04-30 13:09:53 EDT 
(In reply to Akihiko Takajo from comment #0)
> Failed to create a project whose name contains question mark '?' (e.g.
> question?project), And can't delete the content.

You cannot create a folder with a name containing a question mark '?' on Windows.

So we need to add special handling if we really want these projects.

A filename cannot contain / \ : * ? " < > | on Windows. We already added special support for | since we had a customer using it. I would suggest we prevent folder creation with these characters.
Comment 2 Mark Macdonald CLA 2014-04-30 13:33:17 EDT 
The client seems to be double-encoding ? into %253F, but even if you change that to just %3F the server interprets it as query separator and truncates the name.

We could disable ? completely I guess, but it is a legal character on *nix systems, and IMO would should at least get the encoding correct regardless of whether we allow it in the end.
Comment 3 John Arthorne CLA 2015-05-05 16:17:55 EDT 
Closing as part of a mass clean up of inactive bugs. Please reopen if this problem still occurs or is relevant to you. For more details see:


https://dev.eclipse.org/mhonarc/lists/orion-dev/msg03444.html