jabrena/plinth / skills/111-java-maven-dependencies
111-java-maven-dependencies
VerifiedUse when you need to add or evaluate Maven dependencies that improve code quality or domain modeling — including nullness annotations (JSpecify), static analysis (Error Prone + NullAway), functional programming (VAVR), architecture testing (ArchUnit), or money and currency support (JavaMoney) — and want a consultative, question-driven approach that adds only what you actually need. This should trigger for requests such as Add Maven dependencies; Add JSpecify nullness dependencies; Add Error Prone NullAway dependencies; Add VAVR functional dependencies; Add ArchUnit architecture testing dependencies; Add JavaMoney dependencies. Part of Plinth Toolkit
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 5.9 KB |
| references/111-java-maven-dependencies-archunit.md | markdown | 1.3 KB |
| references/111-java-maven-dependencies-javamoney.md | markdown | 2.8 KB |
| references/111-java-maven-dependencies-jspecify.md | markdown | 4.0 KB |
| references/111-java-maven-dependencies-vavr.md | markdown | 1.2 KB |
references/111-java-maven-dependencies-jspecify.md
View on GitHub---
name: 111-java-maven-dependencies-jspecify
description: JSpecify, Error Prone, and NullAway Maven dependency guidance for the interactive Maven dependencies skill.
license: Apache-2.0
metadata:
author: Juan Antonio Breña Moral
version: 0.19.0
---
# Add Maven dependencies for improved code quality
## Role
You are a Senior software engineer with extensive experience in Java software development.
## Goal
Configure nullness analysis only when selected by the user. This reference owns both the JSpecify dependency and the conditional Error Prone + NullAway compiler analysis path because enhanced NullAway analysis depends on the JSpecify decision in the question flow.
## Constraints
Apply only the selected nullness-analysis pieces after the questions embedded in SKILL.md have been answered.
- Use `provided` scope for JSpecify.
- Add Error Prone + NullAway only when the user selected enhanced compiler analysis after selecting JSpecify.
- Ask for and use the real project package name in `NullAway:AnnotatedPackages`.
- Create `.mvn/jvm.config` only when enhanced compiler analysis is selected.
## Steps
### Step 1: Add selected version properties
Add only the properties needed by the user's selections:
```xml
<jspecify.version>1.0.0</jspecify.version>
<error-prone.version>2.35.1</error-prone.version>
<nullaway.version>0.12.0</nullaway.version>
```
### Step 2: Add JSpecify dependency when selected
```xml
<dependency>
<groupId>org.jspecify</groupId>
<artifactId>jspecify</artifactId>
<version>${jspecify.version}</version>
<scope>provided</scope>
</dependency>
```
### Step 3: Add enhanced compiler analysis when selected
Update or add `maven-compiler-plugin` configuration only when the user selected enhanced analysis. Replace `com.example.myproject` with the package name confirmed by the user.
```xml
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<version>${maven-plugin-compiler.version}</version>
<configuration>
<release>${java.version}</release>
<compilerArgs>
<arg>-Xlint:all</arg>
<arg>-Werror</arg>
<arg>-XDcompilePolicy=simple</arg>
<arg>--should-stop=ifError=FLOW</arg>
<arg>-Xplugin:ErrorProne
-Xep:NullAway:ERROR
-XepOpt:NullAway:JSpecifyMode=true
-XepOpt:NullAway:TreatGeneratedAsUnannotated=true
-XepOpt:NullAway:CheckOptionalEmptiness=true
-XepOpt:NullAway:HandleTestAssertionLibraries=true
-XepOpt:NullAway:AssertsEnabled=true
-XepOpt:NullAway:AnnotatedPackages=com.example.myproject
</arg>
</compilerArgs>
<annotationProcessorPaths>
<path>
<groupId>com.google.errorprone</groupId>
<artifactId>error_prone_core</artifactId>
<version>${error-prone.version}</version>
</path>
<path>
<groupId>com.uber.nullaway</groupId>
<artifactId>nullaway</artifactId>
<version>${nullaway.version}</version>
</path>
</annotationProcessorPaths>
</configuration>
</plugin>
```
### Step 4: Create JVM configuration for enhanced analysis
Create `.mvn/jvm.config` only when enhanced compiler analysis is selected:
```text
--add-exports=jdk.compiler/com.sun.tools.javac.api=ALL-UNNAMED
--add-exports=jdk.compiler/com.sun.tools.javac.file=ALL-UNNAMED
--add-exports=jdk.compiler/com.sun.tools.javac.main=ALL-UNNAMED
--add-exports=jdk.compiler/com.sun.tools.javac.model=ALL-UNNAMED
--add-exports=jdk.compiler/com.sun.tools.javac.parser=ALL-UNNAMED
--add-exports=jdk.compiler/com.sun.tools.javac.processing=ALL-UNNAMED
--add-exports=jdk.compiler/com.sun.tools.javac.tree=ALL-UNNAMED
--add-exports=jdk.compiler/com.sun.tools.javac.util=ALL-UNNAMED
--add-opens=jdk.compiler/com.sun.tools.javac.code=ALL-UNNAMED
--add-opens=jdk.compiler/com.sun.tools.javac.comp=ALL-UNNAMED
```Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 197k | Updated | Claude CodeCodex | Verified | Install |