0002015: Missing check in MOVE_MODULES of already existing module in other project

ID	Project	Category	View Status	Date Submitted	Last Update

0002015	JEDI VCS	Server	public	2004-07-30 14:43	2005-06-13 17:03

Reporter	THuber	Assigned To	THuber
Priority	normal	Severity	major	Reproducibility	always
Status	closed	Resolution	fixed
Product Version	2.40 RC1
Target Version		Fixed in Version	2.40 RC2

Summary	0002015: Missing check in MOVE_MODULES of already existing module in other project
Description	It is possible to move a module to the same path of another module which is already checked in in another project with with several revisions. On synchronising of this module it can happen you'll get an older revision!
Steps To Reproduce	assume you have (a) c:\project\readme.txt (rev.0.3) in project_a and (b) c:\project\1.1\readme.txt (rev 0.11) in project_b, (b) has to exist already physically: 1) call move modules for (a) 2) move this module to c:\project\1.1\readme.tx 3) now you have to times the same module and depending on which module you checkout/checkin/snych you might get a wrong local file.
Additional Information	This is regarded as a problem which has to be handled manually. Server should only detect this problem and report the problem for manual resolving.
Tags	No tags attached.

Fix in JVCS version	2.40 RC2
Releasedocumentation

Date Modified	Username	Field	Change
2004-07-30 14:43	THuber	New Issue
2004-07-30 14:43	THuber	Fix in JVCS version	=> 2.40
2004-08-07 11:36	THuber	Fix in JVCS version	2.40 => 2.40 RC2
2004-08-07 11:36	THuber	Assigned To	=> THuber
2004-08-07 11:36	THuber	Status	new => assigned
2004-08-07 11:36	THuber	Product Version	2.40 (First JVCS release) => 2.40 RC1
2004-08-09 04:04	THuber	Status	assigned => resolved
2004-08-09 04:04	THuber	Resolution	open => fixed
2004-12-10 16:03	THuber	Fixed in Version	=> 2.40 RC2
2005-01-15 05:55	THuber	Relationship added	child of 0002361
2005-06-13 17:03	THuber	Status	resolved => closed