You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Grzegorz Kossakowski <gr...@tuffmail.com> on 2007/01/02 22:36:54 UTC

Re: [jira] Commented: (COCOON-1975) cocoon-core-M2 could not be runned because of missing dependencies on avalon-framework-api-4.3 and excalibur-instrument-api-2.1

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

Re: [jira] Commented: (COCOON-1975) cocoon-core-M2 could not be runned because of missing dependencies on avalon-framework-api-4.3 and excalibur-instrument-api-2.1

Posted by Grzegorz Kossakowski <gr...@tuffmail.com>.
Reinhard Poetz napisał(a):
> ok, I will release the archetypes again with the next series of module 
> releases that I plan to do in about 2 or 3 weeks.
>
> Thanks for your work!!!

No problem. I'm going to fix the issue in Maven, but the code where the 
bug seems to lay in is piece of crap (opinion of Maven dev ;)) so it's 
quite difficult to figure out exact place of faluty code. I'm also 
having exams on University so I won't be able to do this now, though. 
I'll report on progress (if any) in 3 weeks or so.

-- 
Grzegorz Kossakowski

Re: [jira] Commented: (COCOON-1975) cocoon-core-M2 could not be runned because of missing dependencies on avalon-framework-api-4.3 and excalibur-instrument-api-2.1

Posted by Reinhard Poetz <re...@apache.org>.
Grzegorz Kossakowski wrote:
> Grzegorz Kossakowski napisał(a):
>> Reinhard Poetz napisał(a):
>>   
>> I've haunted some Maven insider (Kenney Westerhof) for us on IRC. :)
>> After quite long discussion, we agreed that there is some kind of bug in
>> Maven. The result is that he has filled report in JIRA and I've managed
>> to focus some interest on it. I'll watch this issues and do my best to
>> resolve it. If it's confirmed, I think the best workaround for now is to
>> release new artifacts that contain directly declaration of apache.snapshot.
>>   
> I meant "release new archetypes".

ok, I will release the archetypes again with the next series of module releases 
that I plan to do in about 2 or 3 weeks.

Thanks for your work!!!

-- 
Reinhard Pötz           Independent Consultant, Trainer & (IT)-Coach 

{Software Engineering, Open Source, Web Applications, Apache Cocoon}

                                        web(log): http://www.poetz.cc
--------------------------------------------------------------------

Re: [jira] Commented: (COCOON-1975) cocoon-core-M2 could not be runned because of missing dependencies on avalon-framework-api-4.3 and excalibur-instrument-api-2.1

Posted by Grzegorz Kossakowski <gr...@tuffmail.com>.
Grzegorz Kossakowski napisał(a):
> Reinhard Poetz napisał(a):
>   
> I've haunted some Maven insider (Kenney Westerhof) for us on IRC. :)
> After quite long discussion, we agreed that there is some kind of bug in
> Maven. The result is that he has filled report in JIRA and I've managed
> to focus some interest on it. I'll watch this issues and do my best to
> resolve it. If it's confirmed, I think the best workaround for now is to
> release new artifacts that contain directly declaration of apache.snapshot.
>   
I meant "release new archetypes".

-- 
Grzegorz Kossakowski

Re: [jira] Commented: (COCOON-1975) cocoon-core-M2 could not be runned because of missing dependencies on avalon-framework-api-4.3 and excalibur-instrument-api-2.1

Posted by Grzegorz Kossakowski <gr...@tuffmail.com>.
Reinhard Poetz napisał(a):
> avalon-framework-impl is also available at central
> (http://repo1.maven.org/maven2/avalon-framework/avalon-framework-impl/4.3/avalon-framework-impl-4.3.pom)
> and has a dependency on avalon-framework-api or is this something
> different?
I've haunted some Maven insider (Kenney Westerhof) for us on IRC. :)
After quite long discussion, we agreed that there is some kind of bug in
Maven. The result is that he has filled report in JIRA and I've managed
to focus some interest on it. I'll watch this issues and do my best to
resolve it. If it's confirmed, I think the best workaround for now is to
release new artifacts that contain directly declaration of apache.snapshot.

-- 
Grzegorz Kossakowski


Re: [jira] Commented: (COCOON-1975) cocoon-core-M2 could not be runned because of missing dependencies on avalon-framework-api-4.3 and excalibur-instrument-api-2.1

Posted by Reinhard Poetz <re...@apache.org>.
Grzegorz Kossakowski wrote:
> 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. 

avalon-framework-impl is also available at central 
(http://repo1.maven.org/maven2/avalon-framework/avalon-framework-impl/4.3/avalon-framework-impl-4.3.pom) 
and has a dependency on avalon-framework-api or is this something different?


-- 
Reinhard Pötz           Independent Consultant, Trainer & (IT)-Coach 

{Software Engineering, Open Source, Web Applications, Apache Cocoon}

                                        web(log): http://www.poetz.cc
--------------------------------------------------------------------