Hello, The Oxygen project file contains only the structure of the project tree and the display filters set in the Project view. The files that remained open the last time when Oxygen was closed are stored in the user preferences, not the project file so if different users keep different files open that will not create a conflict in the shared project file. A conflict between two copies of the project file can be caused only by the two users setting different file filters in the Project view which should be very easy to resolve (just one difference reported for example by the diff operation of a Subversion application) by following the sharing policy set for the team or by changing the structure of the project tree in the Project view for which again I think the decision belongs to the user of the Oxygen project (the sharing policy), not to Oxygen. A quick diff in the SVN application should reveal the second type of conflict immediately. Am I missing something? Regards, Sorin Christian Wittern wrote:
Hi there,
For a project here, I would like to share a project file between the users, so that I can set it up for a group of users and update it when necessary. My first thought was using SVN, but that leads to conflicts pretty soon, since information about state and open files is also contained in the project file, and this is user specific. So I wonder what others are doing to avoid this problem?
Is there a way to efficiently share project files? If it is not currently possible, I would encourage the Syncro team to think about this, since I would believe it to be a common requirement, no? But maybe I am missing something obvious?
All the best,
Christian