Book a Demo

Author Topic: Problems initializing version cntrol in EA  (Read 3921 times)

alexkko

  • EA Novice
  • *
  • Posts: 1
  • Karma: +0/-0
    • View Profile
Problems initializing version cntrol in EA
« on: October 30, 2008, 01:13:44 am »
Hi folks,

I've searched the forum for a similar problem and solution, but did not find anything.

I am trying to enable version controlling via SVN, but it does not work properly. I did everything like on the incturcting video http://www.sparxsystems.com.au/resources/demos/controllingeapackages/Using%20VC%20in%20EA-final.htm
but I still get a red horizontal bar on the left to the package icon (the first icon showed on the page http://www.sparxsystems.com/uml_tool_guide/uml_modeling_tool_features/projectbrowseroverlays.html), instead of the suspected little "eight" icon. The latter page explains the red bar: "This package is controlled and is represented by an XMI file on disk. Version control either is not being used or is not available."

How could I fix this thing? Strange is, that the XMI file is created and even commited (!) to the SVN repository. But any further changes in the package do not affect the created XMI (nor they are commited to the repository). I am not able to check-out or check-in as well (the menu items are greyed out).

Thanks for your advices and time.

Cheers
Alex




jsbueno

  • EA User
  • **
  • Posts: 26
  • Karma: +0/-0
    • View Profile
Re: Problems initializing version cntrol in EA
« Reply #1 on: November 08, 2008, 04:51:18 am »
If the package gets to be comitted to the repository, tehn SVN is doing it, abnd is porbably issuing an error on a subseqeunt operation - (like "lsit", "info" r "status" ) which EA is failing to display correctly to you.

I suggest you use the command line svn to check the status of the .xmi file in the disk -  
exactly svn info, svn status , etc...and check if the fie is in any inconsistent SVN state. Resolve it with the svn command line, and get back to work with EA.

I ahd this happen to me once, when the .xmi file as marked as  conflicted by the SVN. Issuing an "svn resolved" fixed things up.