Bug 315049 - [import/export] exception printed to stdout when synchronizing to non-writable folder
Summary: [import/export] exception printed to stdout when synchronizing to non-writabl...
Status: NEW
Alias: None
Product: Target Management
Classification: Tools
Component: RSE (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: dsdp.tm.rse-inbox CLA
QA Contact: Martin Oberhuber CLA
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2010-05-31 06:23 EDT by Martin Oberhuber CLA
Modified: 2010-05-31 06:24 EDT (History)
0 users

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 Martin Oberhuber CLA 2010-05-31 06:23:39 EDT 
Build ID: RSE 3.2rc3

1. Create local project foo with some content
2. Right-click > Export > Remote Systems > Remote File System
3. Select a remote folder that is not writable
4. Switch on "Review / Synchronize"

--> The export fails, and an exception is printed to stdout.

It looks like the problematic place is in FileSystemOperations.java line 553.
It looks like the RSE's SecurityException needs to be translated into a proper TeamException here.

Note: When "Review/Synchronize" is switched off, a "Security Violation" is reported as expected; BUT the error message does not tell on what folder the exception happened.
Comment 1 Martin Oberhuber CLA 2010-05-31 06:24:07 EDT 
It should be easy to create a Unittest for this scenario in RSESynchronizeTest.