kevinveenbirkenbachandClaude Opus 5
aceb5295ef
Cosmos, Quick Setup and Credits follow from meta/services.yml, categories.yml and galaxy_info.author, yet 279 role READMEs carried a copy that went stale whenever the metadata moved and nobody re-ran make docs. The documentation build now runs the generators itself, against its own scratch checkout, and the committed READMEs keep only the prose a person writes. utils.cache.PROJECT_ROOT derives from the module's location, so putting the checkout first on PYTHONPATH makes the generator operate on the scratch tree. i18n.py and builder.py add it; the one remaining coupling, a relative_to over PROJECT_ROOT in a log line, is gone. CI extracted the "### Production" block from the committed README with awk. Stripping the section made guide_deployable() return "" for every role, which selects no deploy row and turns nothing red: a fail-open regression. It now asks _is_role_invokable, which matches the old condition exactly (178 roles either way, both difference sets empty), and cli/build/docs/readme/production.py renders the block for the two guide scripts. All 178 renders are byte-identical to what HEAD served, and both scripts' extraction pipelines produce identical output for a web app, a service and a desktop role. test_readme.py inverts: the three sections are now a hard failure in a committed README. readme_md.md documents what each is derived from. Removed: the docs, cosmos, readme-generate, readme-index and readme-check targets, the five aliases pointing at them, and docs from make quality. Verified by running generate_commands() in series against a copy of the checkout: every command exits 0, no README is left without Cosmos or Credits, and exactly the 178 invokable roles get a Quick Setup. The ansible_roles step needs pandoc, which only the docs image carries, so that one link of the chain is unexercised here; it is unchanged by this commit. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Java
Description
Installs OpenJDK 11 (jdk11-openjdk) on Pacman-based systems to provide a Java runtime and development environment.
Overview
This README file is for the Java role, which is part of the infinito. The role is specifically designed to automate the installation of Java on a system, focusing on the OpenJDK 11 version.
Features
- Automated provisioning: Configured by Ansible without manual steps.
Contents of the role
The main.yml file within the java role consists of a single, but crucial task:
- Install Java: This task uses the
community.general.pacmanmodule to install thejdk11-openjdkpackage. It ensures that Java Development Kit 11 (OpenJDK 11) is present on the system.
Purpose
The primary objective of this role is to provide a straightforward and efficient method for setting up Java, specifically JDK 11, on personal computers or development environments. This setup is essential for developers who work with Java or run applications that require the Java runtime environment.
Prerequisites
- Ansible: You need to have Ansible installed on your system to use this role.
- Arch Linux-based System: The role uses the
pacmanpackage manager, indicating that it is intended for use on systems based on Arch Linux or its derivatives.
Running the role
To run this role:
- Clone the
computer-rolerepository to your system. - Navigate to the
roles/javadirectory within the repository. - Execute the role using Ansible. Make sure you have the necessary permissions to install packages on your system.
Customization
This role is focused on installing JDK 11, but it can be easily modified to install different versions of the JDK or additional Java-related tools as per your requirements.
Support and Contribution
For support, feedback, or contributions to the role, please open an issue or submit a pull request in the infinito repository. Contributions that enhance the role or broaden its applicability are greatly appreciated.