Ready! API and GIT SCM struggles
Hi All, Just wondering if some of you could offer some advice on using Ready! API with teams where multiple team members are working on shared projects. We are using GIT as our source control man...
Forum Discussion
have you tried to see if these are fixed in the latest version?
I have had some of these issues especially in regards to merge conflicts with earlier versions.
We are using 1.9.0 but we can upgrade to 2.0 and see if the issues persist. When you mention previous versions.........do you know if you hit the issues in 1.8.0+?
Thats what I had before
Since my post in this thread seems to have suspiciously vanished off the face of the planet, I'll ask again -- has anyone had any problems with the <con:resource> node in the service XML files? It's at line 2, and the order of the xmlns:xsi and xmlns:con properties seems to inexplicably get reversed, so our service XMLs always show as having changes when we sync.
My local copy:
<con:resource name="app" path="/sentinel/app" id="de861a43-df9b-4cc1-a4ad-0c95614c2ded" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:con="http://eviware.com/soapui/config">
My SVN repo copy:
<con:resource name="app" path="/sentinel/app" id="de861a43-df9b-4cc1-a4ad-0c95614c2ded" xmlns:con="http://eviware.com/soapui/config" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
Is there a solution for this yet?
Looks like I was able to prevent most of the unwanted git changes (added spaces or enters, formatedd xml instead of one line files...)Still stuck with this one. Really annoying, had 62 file changes after running 2 test cases!
