You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Karl Heinz Marbaise (JIRA)" <ji...@apache.org> on 2018/07/30 19:50:00 UTC
[jira] [Commented] (MDEP-616) New fuzziness to purge a branch
[ https://issues.apache.org/jira/browse/MDEP-616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16562417#comment-16562417 ]
Karl Heinz Marbaise commented on MDEP-616:
------------------------------------------
First this is great...do you have some integration tests for it ?
> New fuzziness to purge a branch
> -------------------------------
>
> Key: MDEP-616
> URL: https://issues.apache.org/jira/browse/MDEP-616
> Project: Maven Dependency Plugin
> Issue Type: Improvement
> Components: purge-local-repository
> Affects Versions: 3.1.1
> Reporter: Jordan COUTON
> Priority: Minor
> Labels: beginner, patch
> Attachments: branch_fuzziness.patch
>
>
> Hi,
> I would like to propose a patch in order to improve the dependency.purge-local-repository feature.
> Let's say there are 2 branches with the same base version number pattern :
> * develop : 3.X
> * product : 3.2.X
> If I run a purge-local-repository on the 3.2, the default fuzziness (version) will erase all the dependencies where the version number is 3.1 but also all the 3.2.X.
> I need a way to delete the old versions of one branch without affecting the other.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)