You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Petr Kozelka (JIRA)" <ji...@codehaus.org> on 2010/09/24 00:55:33 UTC
[jira] Created: (MANTRUN-153) install:install should remove
leftovers from local repository
install:install should remove leftovers from local repository
-------------------------------------------------------------
Key: MANTRUN-153
URL: http://jira.codehaus.org/browse/MANTRUN-153
Project: Maven 2.x Antrun Plugin
Issue Type: Bug
Affects Versions: 1.5
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 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 is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Reopened: (MINSTALL-79) install:install should remove
leftovers from local repository
Posted by "Paul Gier (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MINSTALL-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Gier reopened MINSTALL-79:
-------------------------------
> install:install should remove leftovers from local repository
> -------------------------------------------------------------
>
> Key: MINSTALL-79
> URL: http://jira.codehaus.org/browse/MINSTALL-79
> 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 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 is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (MINSTALL-79) install:install should remove leftovers
from local repository
Posted by "Paul Gier (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MINSTALL-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Gier moved MANTRUN-153 to MINSTALL-79:
-------------------------------------------
Affects Version/s: (was: 1.5)
Key: MINSTALL-79 (was: MANTRUN-153)
Project: Maven 2.x Install Plugin (was: Maven 2.x Antrun Plugin)
> install:install should remove leftovers from local repository
> -------------------------------------------------------------
>
> Key: MINSTALL-79
> URL: http://jira.codehaus.org/browse/MINSTALL-79
> 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 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 is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MINSTALL-79) install:install should remove
leftovers from local repository
Posted by "Paul Gier (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MINSTALL-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Gier closed MINSTALL-79.
-----------------------------
Resolution: Duplicate
> install:install should remove leftovers from local repository
> -------------------------------------------------------------
>
> Key: MINSTALL-79
> URL: http://jira.codehaus.org/browse/MINSTALL-79
> 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 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 is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MANTRUN-153) install:install should remove
leftovers from local repository
Posted by "Petr Kozelka (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MANTRUN-153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Petr Kozelka closed MANTRUN-153.
--------------------------------
Resolution: Won't Fix
> install:install should remove leftovers from local repository
> -------------------------------------------------------------
>
> Key: MANTRUN-153
> URL: http://jira.codehaus.org/browse/MANTRUN-153
> Project: Maven 2.x Antrun Plugin
> Issue Type: Bug
> Affects Versions: 1.5
> 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 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 is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira