EA version control and subversion auto-props?

[Wolfem]

With EA, an model can be put under version control. However, I have a problem with the usage of auto-props from subversion.

There is a menu item "Add Branch to Version Control...". The action triggered by this action fails in my case because EA does not set subversion properties as defined in the subversion configuration file "config". The settings there are correct, I have verified this by executing the svn client from the command line.

By the way, I am not very fond of the idea of EA committing files without my interaction. As subversion user I am used to modify files locally knowing that modifications are only committed to a subversion database if I deliberately want to.

Why do I need the auto-props feature? Our development policy requires us to add mandatory subversion properties to files, which in turn is automatically done by the subversion client as imposed by the configuration file.

So, when EA tries to commit its files via the subversion client, the subversion server refuses the request due to the missing subversion properties. EA stops with the first XML-file, which cannot be committed.

I appreciate any help here! Why does EA not set subversion properties? How can I put an EA model under subversion control?

[Geert Bellekens]

Wolfem,

If you don't like the way EA integrates with SVN then you can simply do it manually.
If you control a package, but leave the Version Control to (None) then you can specify an xml file to store the contents of the package. You can then checkin/out the individual xml files manually.

Geert

[Wolfem]

Geert,

thanks for your hint. I'll give it a try and figure out how it suits to working in a team. Particularly, I'll have to experiment with the creation, moving, deletion of packages. The EA approach would solve that quite nicely, but unfortunately it conflicts with our subversion policy.

[Wolfem]

Meanwhile I have found why subversion auto-props does not work with EA. EA uses its own configuration directory with subversion, and therefore its own set of rules for auto-props.

During the creation of the subversion settings, EA calls e.g.

Code: [Select]

<your path>\svn add --auto-props --config-dir "C:\Program Files\Sparx Systems\EA\Config\SVN" "ea9\9FF6F137BE13.xml"
<your path>\svn commit -m "EA Package addition: 19.01.2012 14:55:45 "  "ea9\9FF6F137BE13.xml"
There, you'll notice the option --config-dir, where EA uses its own configuration file config, which contains

Code: [Select]

### Enterprise Architect SVN configuration file.
### ============================================================================
### This file instructs SVN to set the svn:needs-lock property on all xml files
### when they are added or imported.

[auto-props]
*.xml = svn:needs-lock=NL
*.XML = svn:needs-lock=NL
*.eab = svn:needs-lock=NL
*.EAB = svn:needs-lock=NL
The point is: The user may have its own configuration file (as I have), but that configuration is overridden by EA. Consequently, you have to transfer your settings to the configuration file used by EA. E.g., you have to append lines describing your own auto-props.

I'd suggest to EA people to re-consider this behaviour, or at least give a notice to users (in dialog box, or in online help, or FAQ, ...).

[Guillaume]

Anyone is aware of anything clever that can be done by updating this SVN config file? I haven't found anything about autoprops or this file in EA Help

thanks