We want to use that existing code and deploy it to Openshift – there are some openshift specific files and we prefer to keep them on a branch instead of having them in our main line.This text takes advantage of rails instructions listed here.
You will need to make sure you are pushing your branch to the correct remote repository.
You can do this with the following command If you want to set this as the default target, add the -u option to the command.
The downside to doing your git statuscommand will compare your local openshift branch against the remote openshift:master branch.
i'm using spring-ws 2.0.2 , spring-ws-test run integration tests of soap server.
i'm using approach code i'm running expected response xml omitted brevity , because it's not relevant question.
The main reason this may happen is if you modify a line, like in one of your configuration files, that you’ve also modified in your openshift branch (simply adding code to other parts of the file should not cause a problem).