Reinhard Poetz napisał(a):
I can reproduce this, today. I could swear that it worked when I cut
the release two weeks ago also with an empty local repository.
Any idea what's going on here?
After reading debug log of Maven I can describe what happens partly:
In some parent poms (like cocoon's root pom) there is declaration of
apache.snapshot repository where avalon stuff is stored in. For some
reason when it comes that Maven should get pom of
avalon-framework-impl-4.3 it "forgets" about apache.snapshot and checks
only central. She fails to download POM so it uses default pom.
Processing other part of dependency graph Maven suddenly "recalls" about
apache.snapshot repo but it's too late. Default pom is being used so she
does not try to download real pom, and also does not try to resolve
dependencies.
So what the avalon-framework-api-4.3.jar comes from? It seems (I'm not
sure!) that default pom means also "search the jar default location on
all repositories", and surprisingly Maven manages to find right jar on
apache.snapshot ;-)
I think it's no point to release new version of core because
*dependencies seem to be correct*. It's only question how to make Maven
to not forget about repository, I think the easiest way is to add
information about repository to the archetypes (tested and it works).
Few sentences of _speculation_: I'm not Maven expert so it's my guessing
(and only guessing) but I think Maven goes crazy when pom has declared
parent explicitly and at other place is referenced by other pom as
dependency. Then the situation looks like pom has two parents and one of
them is being rejected. I had no time to verify this hypothesis but if
I'm wrong you can shout at me and save some of my time :)
I'll try to clarify situation by debugging Maven but I feel it won't be
piece of cake for me (any hints appreciated!). You can expect some
results on Friday.
--
Best regards
Grzegorz Kossakowski
