maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Gier (JIRA)" <>
Subject [jira] Closed: (MINSTALL-79) install:install should remove leftovers from local repository
Date Fri, 01 Oct 2010 19:06:33 GMT


Paul Gier closed MINSTALL-79.

    Resolution: Duplicate

> install:install should remove leftovers from local repository
> -------------------------------------------------------------
>                 Key: MINSTALL-79
>                 URL:
>             Project: Maven 2.x Install Plugin
>          Issue Type: Bug
>            Reporter: Petr Kozelka
>         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
> 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
> {color:red}{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 is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message