Protecting project files (xpr) among team

[mstockman]

Hi, we're currently using SVN to share our content and project files among a team of 20+ people. It's been working well for defining templates and transforms, but we're having problems with people overwriting changes.

It seems that Oxygen updates the project file too freely... for example, when you use a transform (without modifying it), the project file gets updated with some information about that, and the xpr file shows up in the SVN client as modified when writers go to commit changed files. If they're not careful, they end up committing a project file that may not be up to date, so someone else's deliberate (not accidental) changes are overwritten.

Is there a team-oriented best-practice for managing project files? Or should we just lock it down in SVN so fewer people can modify it, which seems a little draconian? (I've seen the instructions at https://www.oxygenxml.com/doc/versions/ ... jects.html which hasn't helped here.)

Thanks,
Mike

[Radu]

Hi Mike,

Indeed right now we save associations between XML documents and the default scenarios used to publish them at project level. We are considering to change this in a future version.
Until then indeed as you are using SVN you can decide to lock the XPR.

Regards,
Radu

[Cosmin Duna]

Hello Mike,

Oxygen 22 is out now and it contains a new preferences page named "Project Level Settings" that allows you to control where to save the scenario association:
https://www.oxygenxml.com/doc/versions/ ... tings.html

Best regards,
Cosmin DUNA