[
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
