You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Jason van Zyl (JIRA)" <ji...@codehaus.org> on 2007/11/04 17:18:12 UTC
[jira] Commented: (MNG-2443) Don't download pom if artifact is
already in the local repository
[ http://jira.codehaus.org/browse/MNG-2443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_112732 ]
Jason van Zyl commented on MNG-2443:
------------------------------------
That an artifact having been incorrectly deployed without a POM doesn't mean that a POM should not be added in the future. I just hit this with Velocity View Tools where there is no POM but I ask them to correct it. A POM simply should not be deployed without a POM in the first place but we assume that it may be corrected in the future, not that it will never be corrected. We really need to correct the projects without POMs, always make the attempt in the background, but not show this constant downloading to the user.
Once a POM is present it will never to downloaded again, but as long as this annoying message is not in your face all the time. A silent attempt in the background probably won't do much harm and is the safest approach with attempting but not annoying the user with the output.
> Don't download pom if artifact is already in the local repository
> -----------------------------------------------------------------
>
> Key: MNG-2443
> URL: http://jira.codehaus.org/browse/MNG-2443
> Project: Maven 2
> Issue Type: Bug
> Components: Artifacts and Repositories
> Affects Versions: 2.0.4
> Reporter: Carsten Ziegeler
> Fix For: 2.1
>
>
> There are many projects out there just providing their artifact without a pom (whether this is good or not is a different question). Now in this case m2 always tries to download a pom for those artifacts, even if the artifact itself is already in the local repository. And if you have several of those artifacts combined with more than one repository configured, then there are a lot of unnecessary download attempts.
> I think this falls into the same category as changing a pom in the repository (which should be forbidden) - so if for the first time the artifact is downloaded no pom available, then there will never be a pom for this specific artifact.
--
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