Destination deployment still works as normal.
Ok. May be the mistake is in my configuration. I think I will ask the people in deployment forum.
Thank you for your confirmation.
Have a search in this forum too.
I vaguely recall people having similar problems moving from 1.2.0 to 1.3.0 and they resolved it. Some problem in their config - maybe something to do with scoping (in 1.3.0 you shouldn't scope anything)
You are absolutely correct. The problem is that I created the *-service.xml in scoped manner.
Now after the configuration has been unscoped, the hot-deployment works like before.
Thank you very much