When deploying with --libraries, the deployment process does not check if the specified files actually
exist on disk.
For users (like me) not reading the documentation which states that "relative paths are relative to
instance-root/lib/applibs", the deployment is said to have completed successfully but the libraries cannot
be located at runtime (which could lead people to think this is some sort of class-loader issue).
I would suggest that the deployment should :
- echo the absolute name of the library
- fail when the library file(s) don't exist on disk at deploy-time