Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 231613 - Upload rule destination does not update when working directory is changed from non-default to default.
Summary: Upload rule destination does not update when working directory is changed fro...
Status: CLOSED FIXED
Alias: None
Product: PTP
Classification: Tools
Component: Remote Tools (show other bugs)
Version: 2.0.1   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Daniel Felix Ferber CLA
QA Contact: Greg Watson CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-05-12 13:35 EDT by Everton Rufino Constantino CLA
Modified: 2011-05-14 06:34 EDT (History)
0 users

See Also:


Attachments
This patch solves the problem making sure that every time the rule is displayed the right value is taken for the "To:" field. (2.42 KB, patch)
2008-05-12 13:37 EDT, Everton Rufino Constantino CLA
g.watson: iplog+
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Everton Rufino Constantino CLA 2008-05-12 13:35:16 EDT
When I am creating a new "Run Target" I have the option of setting, in the "Target" tab, the working directory. The working directory can either, be a location I define or a default location. 

At the "Synchronize" tab I can add, upload rules. While adding rules I can choose to use a specified directory or use the one from the launch configuration. 

If I use, as my working directory, a non-default value, the "To:" field of the upload rule is automatically changed, however if I change it back to the default value the "To:" field is not updated.
Comment 1 Everton Rufino Constantino CLA 2008-05-12 13:37:26 EDT
Created attachment 99761 [details]
This patch solves the problem making sure that every time the rule is displayed the right value is taken for the "To:" field.
Comment 2 Greg Watson CLA 2008-05-13 09:48:11 EDT
This patch generates errors on HEAD and warnings on 2.0. Can you update the patch?
Comment 3 Daniel Felix Ferber CLA 2008-05-13 14:02:25 EDT
Hi Greg,
I noticed that the changes from the patch are already on HEAD. I got no errors nor warnings. Current version from HEAD is working for us.
Would it be possible to send us the error messages so we can investigate?
Comment 4 Greg Watson CLA 2008-05-14 15:31:48 EDT
The 2.0 and HEAD versions of EnhancedSynchronizeTab.java are identical, so can I assume that this patch is no longer needed?
Comment 5 Daniel Felix Ferber CLA 2008-05-21 13:30:44 EDT
I checked trunk and ptp_2_0 branch. Both are ok.
Comment 6 Everton Rufino Constantino CLA 2008-05-21 16:45:07 EDT
Works for me.