Book a Demo

Author Topic: GIT Support in Version Control Settings  (Read 5149 times)

Dmitriy Stolyarov

  • EA Novice
  • *
  • Posts: 2
  • Karma: +0/-0
  • Thinkler
    • View Profile
GIT Support in Version Control Settings
« on: December 23, 2014, 06:33:07 pm »
Please, add GIT version control system support in Version Control Settings (GIT integration). In our IT-projects developers use GIT as source code version control system. For our team it'll be very useful. As I know, GIT using a lot of IT teams all over world. It will be very useful and for SPARX EA product selling (+1 ponderable argument for buying SPARX EA  :))
« Last Edit: December 23, 2014, 06:33:46 pm by thinkler »
Tempus edax - homo edacior

qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +397/-301
  • I'm no guru at all
    • View Profile
Re: GIT Support in Version Control Settings
« Reply #1 on: December 23, 2014, 08:41:46 pm »
No. This is simply not possible. Use the Search button top left to find the reason.

q.

Dmitriy Stolyarov

  • EA Novice
  • *
  • Posts: 2
  • Karma: +0/-0
  • Thinkler
    • View Profile
Re: GIT Support in Version Control Settings
« Reply #2 on: December 24, 2014, 05:57:58 pm »
Ok, qwerty, thanks for answer. I found old discussion in Google about GIT support in SPARX EA
As I understood, for implementation of this feature need some code refactoring of SPARX EA. So, I hope, this feature will be implemented sometime  :)
« Last Edit: December 24, 2014, 05:59:54 pm by thinkler »
Tempus edax - homo edacior

qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +397/-301
  • I'm no guru at all
    • View Profile
Re: GIT Support in Version Control Settings
« Reply #3 on: December 24, 2014, 07:16:32 pm »
Well, for sure not. I've been watching what has been changed in this product fr about a dozen years now. And the missing locking mechanism is so substantial that we will not see it in the say next 100 years. Alternatively adding a merge for XMI will make no sense. You can try yourself. Just put the XMI in git and see what melange it will produce from two independent changes. Once again (a different story though): a model is not code.

q.