111-java-maven-dependencies

To add Maven dependencies for null safety and static analysis in Java, this skill uses a question-driven flow to scope JSpecify, Error Prone with NullAway, VAVR, and ArchUnit to your needs. It then updates your POM properties, dependencies, and plugin configurations accordingly.

The best way to configure JSpecify and Error Prone in a Maven project is through a structured workflow that updates your pom.xml, properties, and plugin configurations based on guided questions, ensuring dependencies are purposeful and scoped to improve code quality.

Yes, you need to run mvn validate before applying Maven dependency changes. This skill enforces running mvn validate as a prerequisite to ensure your project is validated before any new dependencies, properties, or plugin configurations are applied to your pom.xml.

Yes, you can use ArchUnit for architecture testing alongside VAVR in your Java project. This skill interactively scopes Maven dependencies for both ArchUnit and VAVR, updating your pom.xml and plugin configurations to support safer code and architecture validation.

NullAway integration with Maven plugins for Java code quality works by configuring Error Prone alongside NullAway through this skill's guided workflow. It updates your pom.xml properties and plugin configurations to enforce null safety during the build process.

To improve Java code safety, you should add Maven dependencies scoped by this skill including JSpecify for null safety, Error Prone with NullAway for static analysis, VAVR for functional data handling, and ArchUnit for architecture testing, all configured via a consultative flow.