[ https://issues.apache.org/jira/browse/MINSTALL-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17965847#comment-17965847 ]
Olivier Lamy commented on MINSTALL-79: -------------------------------------- This project has moved from Jira to GitHub Issues. This issue was migrated to [apache/maven-install-plugin#250|https://github.com/apache/maven-install-plugin/issues/250]. > install:install should remove leftovers from local repository > ------------------------------------------------------------- > > Key: MINSTALL-79 > URL: https://issues.apache.org/jira/browse/MINSTALL-79 > Project: Maven Install Plugin (Moved to GitHub Issues) > Issue Type: Bug > Reporter: Petr Kozelka > Priority: Major > Attachments: pom.xml > > > It happens that we need to change the set of output artifacts. When this > happens, the install mojo does not bother to remove older artifacts that are > no longer produced by this module. > The bad effect is, that other modules depending on the obsolete artifacts can > still use it. Much better behavior in this situation would be, to remove the > obsolete files from the local repository's directory dedicated for given > module. > h4. reproducing the problem > # download the sample pom to an empty directory > # execute {{mvn clean install -Dc=obsolete-demo}} - this represents the > "older version" of a module > # execute {{mvn clean install}} - this represents the "newer version" of a > module, after changing the classifier > # now, look in the local repo using {{ls -1 > $HOME/.m2/repository/demo/sample-zip-module/1-SNAPSHOT}} - you will see this: > {quote} > maven-metadata-local.xml > sample-zip-module-1-SNAPSHOT-demo.zip > {color:red}sample-zip-module-1-SNAPSHOT-obsolete-demo.zip{color} > sample-zip-module-1-SNAPSHOT.pom > {quote} > h4. possible solutions > I see two approaches > # *drop the installdir first* - straightforward > # *list installdir, install, drop leftovers* - slightly more complicated but > maximizes the time of installed module existence -- This message was sent by Atlassian Jira (v8.20.10#820010)