You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Carsten Ziegeler (JIRA)" <ji...@codehaus.org> on 2006/07/14 10:26:58 UTC
[jira] Created: (MNG-2443) Don't download pom if artifact is
already in the local repository
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
Type: Bug
Versions: 2.0.4
Reporter: Carsten Ziegeler
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
[jira] Commented: (MNG-2443) Don't download pom if artifact is
already in the local repository
Posted by "Jason van Zyl (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Updated: (MNG-2443) Don't download pom if artifact is
already in the local repository
Posted by "Jason van Zyl (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason van Zyl updated MNG-2443:
-------------------------------
Fix Version/s: (was: 3.x)
3.0-alpha-7
> 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 & 3
> Issue Type: Bug
> Components: Artifacts and Repositories
> Affects Versions: 2.0.4
> Reporter: Carsten Ziegeler
> Assignee: Jason van Zyl
> Fix For: 3.0-alpha-7
>
>
> 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
[jira] Closed: (MNG-2443) Don't download pom if artifact is already
in the local repository
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann closed MNG-2443.
----------------------------------
Resolution: Duplicate
Fix Version/s: (was: 3.0-alpha-8)
Assignee: Benjamin Bentmann (was: Jason van Zyl)
> 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 & 3
> Issue Type: Bug
> Components: Artifacts and Repositories
> Affects Versions: 2.0.4
> Reporter: Carsten Ziegeler
> Assignee: Benjamin Bentmann
>
> 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
[jira] Commented: (MNG-2443) Don't download pom if artifact is
already in the local repository
Posted by "Carsten Ziegeler (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_112776 ]
Carsten Ziegeler commented on MNG-2443:
---------------------------------------
I totally agree that it would be much better/correct if everything in the repository is deployed correctly (including a *correct* pom).
The main problem with the current behaviour is:
a) too many messages for the user who is just a client of the artifact. The message is send to the wrong people. The maintainers of the lib should get these messages (which is of course not really feasable)
b) It takes time during build, especially if you have configured several repositories as each repo is tried for the pom
Now, I see your point that checking the availability of poms allows to add the pom later on - but I'm not sure if this is a good argument :) Following this line I could argue that updating/correcting the pom at a future time should be possible - and this is not done today. Once a pom is in the local repository this one is used. So I think for symmetrie it makes more sense to not check the availability of the pom once the artifact is in the local repository.
I can imagine that adding a pom later on might create build problems as people have used the artifact without a pom for some time and from one day to another a pom with possible new (transitive) dependencies arrives. Not a big deal perhaps, but it can cause trouble.
> 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
> Assignee: Jason van Zyl
> 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
[jira] Updated: (MNG-2443) Don't download pom if artifact is
already in the local repository
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MNG-2443:
------------------------------
Fix Version/s: (was: Reviewed Pending Version Assignment)
2.1.x
Component/s: Artifacts and Repositories
> 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.x
>
>
> 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
[jira] Commented: (MNG-2443) Don't download pom if artifact is
already in the local repository
Posted by "Matthew Buckett (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=132631#action_132631 ]
Matthew Buckett commented on MNG-2443:
--------------------------------------
One issue is that if a POM isn't present for a artifact then the download of this POM is attempted every build even if the repository is configured to only be checked for updates less frequently, this can make a large build slow down considerably.
> 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
> Assignee: Jason van Zyl
> 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