Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 340530 - [R4E] Unable to write anomalies to files not present in the work space
Summary: [R4E] Unable to write anomalies to files not present in the work space
Status: RESOLVED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Mylyn (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows Vista
: P3 normal (vote)
Target Milestone: 0.9   Edit
Assignee: Sebastien Dubois CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-20 19:29 EDT by Alvaro Sanchez-Leon CLA
Modified: 2012-01-24 17:28 EST (History)
1 user (show)

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 Alvaro Sanchez-Leon CLA 2011-03-20 19:29:58 EDT 
It shall be possible to create anomalies to any file version registered / serialised within a review item.

This is, the serialised file version is copied to the local reviews repository and the original relative path is serialised with the review item file version. 
Therefore a user selected location shall be resolved and the anomaly shall contain a reference to this same file version.
The above is true for any version control system.
Comment 1 Sebastien Dubois CLA 2011-03-21 23:18:32 EDT 
Another problem related to that is that when writing an anomaly from the compare editor,  we get a ReviewVersionsException so the file is not seen as being within source control (it is in Git) and a warning dialog pops up erroneously
Comment 2 Alvaro Sanchez-Leon CLA 2011-03-22 09:38:56 EDT 
Even if the file is in a git repository, the project in the workspace needs to be attached to the repository.
Are you sure the project is attached to the git team provider ?
Comment 3 Sebastien Dubois CLA 2011-05-20 16:07:09 EDT 
This problem is now fixed