skills.rest
kinhluan
kinhluanCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

rules-quarkus

Integrate Quarkus applications with Bazel using custom Starlark rules.

3|Updated Mar 13, 2026
Search Tags:#java#quarkus#bazel#build integration#starlark#rules-quarkus
One-click install
npx skills add https://github.com/kinhluan/rules-quarkus-skills --skill rules-quarkus
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: rules-quarkus
Source: https://github.com/kinhluan/rules-quarkus-skills/tree/main/.agent-skills/rules-quarkus
Command: npx skills add https://github.com/kinhluan/rules-quarkus-skills --skill rules-quarkus

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the fundamental conflict between Quarkus's dynamic build-time "Augmentation" and Bazel's strictly hermetic model, enabling seamless integration for modern enterprise Java development.

Core Features & Use Cases

  • Bazel Integration: Provides native Bazel rules (rules_quarkus) for building Quarkus applications.
  • Augmentation Handling: Reconciles Quarkus's augmentation phase with Bazel's deterministic build system.
  • Troubleshooting: Offers workflows for common issues like "Unable to locate CDIProvider" or "Argument list too long".
  • Use Case: You are building a Quarkus application using Bazel and encountering build errors related to Quarkus's augmentation process. This skill will help you understand and resolve these issues.

Quick Start

Use the rules-quarkus skill to troubleshoot a Quarkus CDIProvider error during Bazel augmentation.

Frequently Asked Questions about rules-quarkus

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I integrate a Quarkus application with Bazel without breaking hermetic builds?▼

Custom Starlark rules resolve the Quarkus augmentation conflict in Bazel by mapping dynamic build-time classloading and dependency resolution into Bazel's hermetic model, ensuring deterministic Quarkus application builds.

Why does my Quarkus build fail with an 'Unable to locate CDIProvider' error in Bazel?▼

The 'Unable to locate CDIProvider' error in Bazel happens when standard build rules fail to handle Quarkus's dynamic classloading during augmentation, requiring custom Starlark rules to properly resolve dependencies.

What Bazel and Java versions are required to build Quarkus applications?▼

Building Quarkus applications with Bazel requires Bazel 7.x+, Java 21, and Quarkus 3.20.1 to properly support the custom Starlark rules and augmentation phase integration.

How do I fix the 'Argument list too long' error during Quarkus Bazel augmentation?▼

The 'Argument list too long' error during Quarkus Bazel augmentation is a known limitation resolved by using custom Starlark rules that restructure dependency resolution to avoid exceeding system argument limits.

Can I use standard Bazel rules for Quarkus build-time augmentation?▼

Standard Bazel rules cannot handle Quarkus build-time augmentation because Quarkus dynamically modifies classes and resolves dependencies at build time, fundamentally conflicting with Bazel's strictly hermetic and deterministic model.

Related Skills

Explore More Software Engineering Skills→
kinhluankinhluan
3

bazel-expert

Guide idiomatic Bazel rule writing and Starlark best practices for build performance.

Community
Advanced
jabrenajabrena
423

400-frameworks-quarkus-create-project

Generate a new Quarkus Maven project using SDKMAN-managed Java and the Quarkus CLI.

Community
Intermediate
kinhluankinhluan
3

maven-expert

Provide expert guidance on Apache Maven dependency management and Maven-to-Bazel migration.

Community
Intermediate
GabeujinGabeujin

java-add-graalvm-native-image-support

Automate GraalVM Native Image configuration for Java Maven and Gradle projects.

Community
Advanced