This is a "documentation" commit to show that *.jinfo files are now well
handled in Webupd8 packages. These files are therefore no more needed to
be deployed by Chef recipes and they will be removed in next commit.
- Remove obsolete .jinfo files for Oracle JDK7 and JDK8, since Webupd8
packages configure 'alternatives' well
- Clean OpenJDK7 recipe, since Ubuntu package configure 'alternative'
well on 12.04 (compatible with jdk_switcher alias)
- At the end, ensure that OpenJDK7 (hardcoded for now) is set as default java version
For the records, see in particular:
This way we ensure that:
- all java runtime will behave the same, independently of selected JDK
- most common SSL CA will be supported (including popular authorities like
clojars.org now uses certificate issued by RapidSSL CA, and I
verified that default keystore provided by Webupd8 packages also work
fine to run Leiningen2. But as argumented above, for any other similar
possible use case, it is safer to use the certificates provided by
The current implementation will auto-install an openjdk6 JRE as
dependency of the package ca-certificates-java. This is not *ideal*, but
it should have no impact. As a variant, we could provision a static copy
of the ubuntu keystore file, via cookbook_file or remote_file.
Remove outdated README.md and obsolete/unused pieces of code. This
will make cookbook more readable and easier to maintain. We'll have time
to refactor back the day we want to support more linux flavors :)
Note that tzdata workaround (65b0eca) is kept
untouched (just the package installation statements that are written a
Attention: the 'multi' recipe must not be directly called, since it is
now conditionally included by 'default' recipe (depending on
'alternate_versions' value). travis-images run_list for JVM and Ruby
must be hence updated.