Detect and update the server if a newer version is available about jws HOT 4 CLOSED

I think we cannot get away without providing a way for user to have their own zipfile instead of our sane defaults. One use case I can see is an organization building its own, customized version of JWS, zipping in under my-org-java-server-1.1.zip. We need to have path for this use case.
However, yes, we should not have tomcat_zipfile has a mandatory parameters to provides, but more as an option.

from jws.

In case anyone hits this issue, I wanted to drop a note so that it's searchable :) I experienced it by accident after running the playbook twice and upgrading from 9.0.50 to 9.0.62 in between (without deleting tomcat.zip first). I think adding this feature would make the playbook much more robust. Output:

TASK [middleware_automation.jws.jws : Ensure service script is deployed] ***************************************************************************************************************************************************************************************************************************************************** fatal: [localhost]: FAILED! => {"changed": false, "checksum": "6c5a8239a5be03ff60caa24cca027067b8eddc84", "msg": "Destination directory /opt/apache-tomcat-9.0.62/bin does not exist"}

from jws.

The cause of this issue is that we allow to override the installation zipfile to a file name that does not contain the version.
tomcat_zipfile: "tomcat.zip"
There is no clean way to check if an arbitrarily named zipfile really contains what is declared in tomcat_version.

I think we should remove the option tomcat_zipfile completely; and instead rely on what filenames are provided by the download enpoints

from jws.

Parameter tomcat_force_install introduced in #80 allows to perform the update (no uninstall happens); setting a tomcat_version (and thus tomcat_home) which does not match with the contents of zipfile continues to throw an error. We might want to use a better wording than 'Destination directory /opt/apache-tomcat-X.X.X does not exist`?

from jws.