Thanks for the follow up. I pushed a test app and I'm seeing the same "503
Service Unavailable" from Maven. Is that what you're seeing?
On Sun, Oct 25, 2015 at 4:32 PM, Krzysztof Wilk <chris.m.wilk(a)gmail.com>
It seems to me that there is more than one cause of this problem.
I have done the following:
1. upgraded cf CLI from 6.12 to 6.13
2.cf set-health-check MY_APP_NAME none
3. set <healthCheckTimeout>180</healthCheckTimeout> (pom.xml)
4. removed env variables in order to allow Maven to set them again
Still no luck.
However, I have read that there is intensive development of Maven client
plugin 2.x happening now. I will give it a try as soon as first release is