Hi,
No matter what I try, CodeRunner.bat does not deploy my current service version but keeps an old one.
In an old version I had a method “sayHello”. This has been removed since, and I verified that it does not end up in the service-tmp.jar created by coderunner. Yet, the method still appears in the deployed service.
Am I doing something wrong, or is this a bug?
Same problem with Deploy.bat
Michel,
Is this for Debug or Production deployment?
Could you try deleting the service from console and redeploy again?
Regards,
Mark
Thanks for this super fast answer.
With CodeRunner.bat this is for debug, with Deploy.bat it’s for production.
I deleted the services multiple times, no success. I also made sure that the class and JAR files are deleted and rebuilt before deploying, no success either.
Since it leads to an error when the class files or the local repo don’t exist (as expected), I’m confident that the deployed files are not picked up from somewhere else.
Could you please email the jar you’re deploying to support@backendless.com ?
Ok I found the problem;
I did not update one of the dependencies in coderunner/lib so the result in repo/debug-tmp was inconsistent. As soon as I updated it, it worked.
Would be good if backendless threw an error 
Your code has a reference to the facebook4j.auth.AccessToken class which is not included into the jar. As a result, the deployment of that service will fail. I am not sure where the other version is coming from though.
I understand that I put dependencies into coderunner/lib. The JAR file is built by coderunner.
(But notice my answer above)
Do you have the dependencies in coderunner/lib or coderunner/libs ?
Sorry I meant libs. It is working for me now, but it would be good if Backendless threw an error