java-dependency-versioning

To get a version-neutral dependency snippet, this Skill identifies the groupId and artifactId and emits the smallest Maven or Gradle snippet using a repository-managed version reference or placeholder instead of a hardcoded version.

Resolving Java dependency coordinates offline involves identifying the groupId and artifactId first. This Skill generates version-neutral install guidance safely without requiring network access, ensuring you get valid dependency snippets even offline.

You can verify the current public release from Maven Central only when online access is available. The Skill optionally checks the public release in a separate online branch after providing the initial version-neutral snippet.

Yes, distinguishing library vs plugin or BOM dependencies is enforced. The Skill applies specific rules to identify the dependency type first, ensuring the generated Maven or Gradle snippet matches the correct format for each type.

To add a Java dependency without a version number, provide the target groupId and artifactId. The Skill then generates a minimal, version-neutral snippet with a placeholder or repository-managed reference for Maven or Gradle.

Version-neutral Maven or Gradle snippets prevent hardcoded version conflicts by using placeholders or repository-managed references. This approach keeps your dependency coordinates clean and allows optional online verification from Maven Central later.