An automated diagnostic tool for identifying and fixing dependency conflicts and version inconsistencies in Spring Boot applications.
Install & Download
1. ClawHub CLI
The fastest way to install a skill directly from the registry.
npx clawhub@latest install jar-conflict-detector
2. Manual Installation
Copy the skill folder to one of these locations
~/.openclaw/skills/ <project>/skills/ Priority: Workspace > Local > Bundled
3. Prompt Installation
Copy this prompt to OpenClaw to install it automatically.
Help me install jar-conflict-detector using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).
Prefer to download?
Get the raw skill files in a ZIP archive.
What is JAR Conflict Detector?
The JAR Conflict Detector is a specialized technical skill designed for Java developers managing Spring Boot microservices using Maven or Gradle. It solves the common 'dependency hell' by scanning project structures to find version mismatches, duplicate JARs, and known incompatible library pairs. By integrating this into your Openclaw Skills library, you can significantly reduce the time spent debugging classpath issues and runtime exceptions like LinkageError.
This skill provides a deep analysis of the dependency tree, offering more than just a list of versions. It understands the nuances of the Spring ecosystem, including the complex relationships between Spring Cloud and Spring Boot, as well as the transition requirements for Jakarta EE. It acts as a bridge between automated scanning and actionable developer tasks, providing specific configuration snippets to resolve issues.
JAR Conflict Detector Use Cases
- Debugging runtime exceptions such as NoSuchMethodError, ClassNotFoundException, or LinkageError caused by classpath pollution.
- Validating dependency compatibility during major framework upgrades, such as migrating from Spring Boot 2.x to 3.x.
- Auditing complex multi-module Maven or Gradle projects to ensure version convergence across all services.
- Performing automated dependency health checks within CI/CD pipelines before deployment to production.
- Resolving common logging conflicts like dual SLF4J bindings or logback-classic overlaps.
How JAR Conflict Detector Works
- Project Scanning: The skill identifies the project root and automatically detects whether the project uses Maven or Gradle.
- Dependency Resolution: It executes standard build tool commands like dependency:tree to generate a full map of resolved transitive dependencies.
- Conflict Analysis: A bundled Python engine analyzes the tree against a database of known conflict patterns and version compatibility matrices.
- Report Generation: The skill produces visual HTML reports for humans or JSON data for automated systems.
- Mitigation Guidance: Finally, it suggests specific XML or Gradle resolution strategy blocks to fix the identified conflicts.
JAR Conflict Detector Setup
To utilize this feature within Openclaw Skills, ensure Python is available in your environment. Run the detection script against your project directory:
python scripts/detect_conflicts.py \
--project-dir /path/to/your/project \
--output conflict-report.html \
--mode auto \
--level all
If Maven or Gradle are installed on your system path, the tool will provide high-accuracy transitive dependency analysis. Otherwise, it will fall back to static file parsing.
JAR Conflict Detector Data Schema & Taxonomy
The skill organizes its output into multiple formats to support different developer workflows:
| File Type | Output Path | Description |
|---|---|---|
| HTML | conflict-report.html | A visual dashboard showing ERROR and WARN levels with specific resolution advice. |
| JSON | conflict-report.json | A structured data format suitable for CI/CD gates and automated filtering. |
| Text | conflict-report.txt | A simplified summary for quick terminal review during local development. |
| Matrix | references/conflict_patterns.md | A reference guide containing compatibility matrices for Spring Boot and Hibernate. |
JAR Conflict Detector Advanced Features
- Multi-module support: Automatically aggregates and scans all sub-modules from a single parent root.
- Jakarta Migration Check: Specific logic to detect conflicts between javax.* and jakarta.* namespaces during modern Java upgrades.
- Static Fallback Mode: Ability to parse pom.xml and build.gradle files even when the underlying build tools are not installed.
- Exit Code Logic: Returns non-zero exit codes when critical conflicts are found, making it ideal for build pipeline integration.
- Custom Resolution Strategies: Provides ready-to-copy dependencyManagement snippets based on the specific version of Spring Boot in use.
SKILL.md
Loading
Related Openclaw Skills
EasyAccounts
A comprehensive natural language interface for the EasyAccounts self-hosted personal finance system, allowing AI agents to record, query, and analyze household finances.
Smart Home Assistant
A specialized tool for monitoring real-time energy usage and generating automated power-saving logic within Home Assistant.
Elastolink Meeting Assistant
A specialized MCP server skill for managing Elastolink meetings, offering automated tools for list retrieval, status checks, and document exports.
Guofeng Lyric Writer
A specialized AI assistant for composing authentic traditional Chinese-style (Guofeng) lyrics with classical imagery and rhyme schemes.
ggzy_collect
An automated scraper designed to collect bidding and tender data from the Zibo Public Resource Trading website and export it into structured Excel reports.
Claws Daily
Claws Daily provides personalized, scheduled news briefings twice a day by aggregating global trends and specific user interests into structured summaries.
Featured*
