Ah, I see now that I have to use a slightly different command line than what I have been using for composite projects. That might explain it.
My project is a composite project, which is how I have it saved on my local machine. I noticed that on the other machine that it isn't opened as a composite project. Is this setting not saved with the project? The new project showed the new environment I added once I changed it to being a composite project on the remote machine.
While I can't comment on the specifics of the missing Environment, I did want to point out (Note: I'm using version 1.7) that when you save a project as a composite project it creates the new composite project directory and all it's contents, but leaves the original project xml file in place. Thus you have to delete the old project file yourself, including from your source control.
If you converted your project to composite, edited and saved it, and then reopened the original non-composite version, this would not contain the edits. This is just a scenario that may of happened but would cause the symptoms you describe.
Really, I'm just trying to be able to run the test runner in an automated fashion. If I have to somehow make modifications to the project before I can run the tests, it makes much less automated.
Apologies I wasn't clear enough on my previous post, I was really responding to your comment:
"I noticed that on the other machine that it isn't opened as a composite project. Is this setting not saved with the project?"
A project that has been set as a composite project can only be opened as a composite project.
I was trying to point out that when you initially convert a project to a composite project, SoapUI does not delete the original, non-composite XML project file. Unless you delete this file, there is nothing to stop you accidentally opening the old non-composite project file which wouldn't have any changes that were saved into the new-composite project.
Hope that makes sense?
I only see one project file.
