Forum Discussion
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">
- BenSav7 years agoNew Contributor
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!
- ArthurM6 years agoOccasional Contributor
Hi all,
is there any update on this ?
We are facing some of the issues described in this thread on version 2.6.0.
Is anyone able to use ReadyAPI 2.6.0 with team collaboration successfully ?
- TanyaYatskovska6 years agoSmartBear Alumni (Retired)
Hi ArthurM,
This is 2-year topic. I suggest that you submit a new question and describe the issue you faced in detail.
Related Content
Recent Discussions
- 19 hours agogroovyguy