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

Bug 340530

Summary:	[R4E] Unable to write anomalies to files not present in the work space
Product:	z_Archived	Reporter:	Alvaro Sanchez-Leon <alvaro.sanchez-leon>
Component:	Mylyn	Assignee:	Sebastien Dubois <sebastien.dubois>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	sebastien.dubois
Version:	unspecified
Target Milestone:	0.9
Hardware:	PC
OS:	Windows Vista
Whiteboard:

Description Alvaro Sanchez-Leon

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

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

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

2011-05-20 16:07:09 EDT

This problem is now fixed