Composite project save problem
Hi,
We've noticed that if you have a non-composite project, and we update the project file from subversion and then attempt to save the file in SoapUI without reloading it first, we get a warning message asking us if we want to overwrite a newer file. This is fine.
However when we switch to a composite project and a testcase file gets updated from subversion, saving the project without reloading/refreshing in SoapUI overwrites the newly checked out file with the version in SoapUI with no warning.
It would be good if the same kind of check (and warning message) could be done for composite saves as for non-composite saves.
Regards
Peter
We've noticed that if you have a non-composite project, and we update the project file from subversion and then attempt to save the file in SoapUI without reloading it first, we get a warning message asking us if we want to overwrite a newer file. This is fine.
However when we switch to a composite project and a testcase file gets updated from subversion, saving the project without reloading/refreshing in SoapUI overwrites the newly checked out file with the version in SoapUI with no warning.
It would be good if the same kind of check (and warning message) could be done for composite saves as for non-composite saves.
Regards
Peter
