Remove hard dependency on your OpenJDK role?

[ches]

Hiya, thanks for sharing your role!

We're using smola.java because of its great support for either OpenJDK or Oracle and choice of Java versions. We have production Java services that have been tested and shown to perform better on Oracle Java, so even though Rundeck is a utility, ideally I'd like to be able to standardize across our infrastructure and not have us pulling in a half dozen different Java roles as Ansible deps.

Would you consider removing the hard dependency, since it's so simple and there are a gillion ways to install Java? AFAIK Rundeck simply respects JAVA_HOME in its user's shell profile (or /etc/default).

Since it would be a less batteries-included experience for users of your role to have to manually add a Java role, I can understand if you'd prefer not to change it. I'm just trying to think about how Galaxy users might deal with this situation in general, it comes up regularly, with Java being a leading culprit—so I'm open to ideas. I'd much rather use your role and contribute back config file templates and such as we need them than to have a fork or vendored copy that we're lazy about because it's divergent.

Thanks for your consideration.

Also, could you bump a version on the Galaxy site please? It looks like you added the Postgres support (which needs docs 😉) and other changes since the last one. I use git SHAs like neel.rundeck,4b121be158e88 for most 3rd-party roles, but the ansible-galaxy CLI tool seems to not support that if the author has actual point versions set up on Galaxy. That system is kind of a mess in its present state, but that's another rant...

[ches]

Ah, so actually neel.openjdk7 isn't even published to Galaxy now it seems, and ansible-galaxy install neel.rundeck doesn't seem to complain about that, so... nevermind I guess 😄

[mat-green]

Fixed in v0.0.4. Thanks for the feed back.

[mat-green]

This has been done in v0.0.5.