Hi, Just been hit by some strange gradle behavior. My android (though I believe my question is generic to gradle tool) gradle build file contains dependency to a jar file as pasted below:
compile files(‘lib/some-library.jar’) }
After a few hours of fight everything works fine but initially I had a typo in path to that jar file. I’d expected that such typos should cause build process to fail so one can easily detect/find the problem. Instead gradle ignores the fact that given path is wrong. Even running gradle with ‘-debug’ option didn’t help finding the problem - I could find a line in gradle that passed mistyped path of file to some command and this command succeeded.
Is there a way to force gradle to be pedantic and check correctness of all paths? Shouldn’t such pedantic behavior be default? It is so obvious that I simply expected it to work this way.
thanks in advance Marcin