This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 166358 - Unusable paths from Move Project not handled gracefully
Summary: Unusable paths from Move Project not handled gracefully
Status: RESOLVED WONTFIX
Alias: None
Product: projects
Classification: Unclassified
Component: Generic Projects UI (show other bugs)
Version: 6.x
Hardware: All All
: P4 blocker (vote)
Assignee: Jesse Glick
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-01 17:33 UTC by martinhavle
Modified: 2010-10-15 20:45 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description martinhavle 2009-06-01 17:33:16 UTC
Occurs on build build 200906010201 with JDK7b57.

At http://wiki.netbeans.org/TS_61_WebProject Test suite: Testing basic actions on project 3.Complex actions II #  2.
Invoke Move and 3. Invoke Copy when invalid path is selected, no warning is shown and it is possible to confirm the
dialog. Only message that it was not possible to create the folder is shown afterwards.
Comment 1 Petr Jiricka 2009-06-10 14:06:15 UTC
I am not sure I completely understand the steps (please provide easy to understand steps), but I believe this is a
general projects issue. Here are my steps to reproduce:

1. Create a new project (Java SE project or C++ project, for example)
2. Select Move in the project's popup menu
3. Enter an invalid value into the project location, e.g.: "/Users/petrjiricka/NetBeansProjects*****"

=> No warning is shown.
Comment 2 Milan Kubec 2009-09-09 14:28:40 UTC
There is nothing bad with "/Users/petrjiricka/NetBeansProjects*****", I can move project there without problems on Mac.

There is no simple way how to validate a path for any platform that Java runs on. The only sure way is try to create a
folder and catch the exception. Lowering priority, there is error message afterwards.
Comment 3 Jesse Glick 2010-10-15 20:45:38 UTC
Not sure what to do about it. Users should simply avoid specifying unusable file paths to begin with.