apache / apache/maven-dependency-plugin

[MDEP-619] snapshotsOnly is not respected when fuzziness is artifactId or groupId

Open
#1,053 2 comments 0 reactions 0 assignees View on GitHub
bug priority:major
Dominant language
Java
Stars
175
Forks
196
Avg merge
19h 30m
Merged PRs (30d)
5

Description

**[Joerg Schaible](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=joehni)** opened **[MDEP-619](https://issues.apache.org/jira/browse/MDEP-619?redirect=false)** and commented

The configuration parameter snapshotsOnly is not always repected. We use a profile that can be activated in the root of a multi-project with following settings:

```xml



purge


purge-group



org.apache.maven.plugins
maven-dependency-plugin


purge-local-repository
clean

purge-local-repository


${project.groupId}
groupId
${purge}





```

We'd like to handle all artifacts with the same groupId. The purge parameter should be used to purge only the snapshots or anything. However, the snapshotOnly parameter is not respected. The goal will wipe always all artifacts with the same groupId.

---

**Affects:** 3.1.1

Contributor guide

No contributing guide indexed for this repository

Research direction

Reproduce the purge-local-repository goal with the shown profile, using snapshotsOnly together with resolutionFuzziness set to groupId or artifactId. Trace how the goal handles the snapshotsOnly parameter during group-level matching; done means snapshot-only purges remove snapshots without wiping release artifacts, while unrestricted purges retain current behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
build-system
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.