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 (aka g[R]eK) (JIRA)" <ji...@apache.org> on 2006/12/29 12:18:21 UTC
[jira] Created: (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
cocoon-core-M2 could not be runned because of missing dependencies on avalon-framework-api-4.3 and excalibur-instrument-api-2.1
-------------------------------------------------------------------------------------------------------------------------------
Key: COCOON-1975
URL: http://issues.apache.org/jira/browse/COCOON-1975
Project: Cocoon
Issue Type: Bug
Components: - Build System: Maven
Affects Versions: 2.2-dev (Current SVN)
Reporter: Grzegorz Kossakowski (aka g[R]eK)
Priority: Blocker
Using clean (empty ~/.m2/repository directory) maven instalation it is not possible to try cocoon-core-M2 following this tutorial: http://cocoon.zones.apache.org/daisy/documentation/g1/1159.html (really BIG thanks goes to Reinhard Pötz for improving docs last days!). It's due to somehow missing (or badly resovled) on avalon-framework-api-4.3 and excalibur-instrument-api-2.1 and results in error I've reported earlier:
http://article.gmane.org/gmane.text.xml.cocoon.devel/68960
If I copy manully missing jars into myWebapp/target/myWebapp-1.0-SNAPSHOT/WEB-INF/lib and start myWebapp using:
mvn package jetty:run everything works as expected.
On other hand, if you build whole trunk and install all blocks into local repository dependencies are resolved correctly.
I'm trying to investigate futher but any help would be desired as I'm not Maven nor Cocoon expert :)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (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 (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/COCOON-1975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Grzegorz Kossakowski closed COCOON-1975.
----------------------------------------
Resolution: Fixed
Fix Version/s: 2.2-dev (Current SVN)
Assignee: Grzegorz Kossakowski (was: Reinhard Poetz)
It seems that we are no longer affected by this issue (with workarounds, though) so I close it for now.
> cocoon-core-M2 could not be runned because of missing dependencies on avalon-framework-api-4.3 and excalibur-instrument-api-2.1
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: COCOON-1975
> URL: https://issues.apache.org/jira/browse/COCOON-1975
> Project: Cocoon
> Issue Type: Bug
> Components: - Build System: Maven
> Affects Versions: 2.2-dev (Current SVN)
> Reporter: Grzegorz Kossakowski
> Assigned To: Grzegorz Kossakowski
> Priority: Blocker
> Fix For: 2.2-dev (Current SVN)
>
>
> Using clean (empty ~/.m2/repository directory) maven instalation it is not possible to try cocoon-core-M2 following this tutorial: http://cocoon.zones.apache.org/daisy/documentation/g1/1159.html (really BIG thanks goes to Reinhard Pötz for improving docs last days!). It's due to somehow missing (or badly resovled) on avalon-framework-api-4.3 and excalibur-instrument-api-2.1 and results in error I've reported earlier:
> http://article.gmane.org/gmane.text.xml.cocoon.devel/68960
> If I copy manully missing jars into myWebapp/target/myWebapp-1.0-SNAPSHOT/WEB-INF/lib and start myWebapp using:
> mvn package jetty:run everything works as expected.
> On other hand, if you build whole trunk and install all blocks into local repository dependencies are resolved correctly.
> I'm trying to investigate futher but any help would be desired as I'm not Maven nor Cocoon expert :)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: Releasing Avalon and Excalibur
Posted by Reinhard Poetz <re...@apache.org>.
Jorg Heymans wrote:
> Reinhard Poetz wrote:
>
>> Jorg,
>>
>> IIRC it was you who worked on providing proper Avalon and Excalibur
>> artifacts to central. What's the status of your work?
>>
>
> The status can be found here:
> http://thread.gmane.org/gmane.comp.apache.excalibur.devel/1980/focus=1980
>
> I figured Cocoon was fully moving away from avalon/excalibur and thus
> lost interest a bit in doing the release.
That's our long term goal and we maybe reach it with 3.0. 2.2 will definitly use
Avalon/Excalibur libs.
> On the release side, there isn't that much left to do. I guess calling a
> vote and go through the formalities should be enough to get the binaries
> released to ibiblio.
>
> Also, note that i primarily focussed on getting things to work and
> compile. I did not do any work on cleaning up the transitive
> dependencies of the poms.
At a first glance the dependencies don't look bad - everything which is optional
is set to "provided" (e.g. logkit, sourceresolve).
IMO it is very important to get an Avalon/Excalibur release, that will be pushed
to the central Maven repository, out of the door. I don't think it is a good
idea to do a non-milestone release which depends on the Apache snapshot repository.
Would it be possible to link Cocoon to your versions of Avalaon/Excalibur
artifacts in order to test them more widely?
--
Reinhard Pötz Independent Consultant, Trainer & (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
--------------------------------------------------------------------
___________________________________________________________
Der fr�he Vogel f�ngt den Wurm. Hier gelangen Sie zum neuen Yahoo! Mail: http://mail.yahoo.de
Re: Releasing Avalon and Excalibur
Posted by Jorg Heymans <jh...@apache.org>.
Reinhard Poetz wrote:
> Jorg,
>
> IIRC it was you who worked on providing proper Avalon and Excalibur
> artifacts to central. What's the status of your work?
>
The status can be found here:
http://thread.gmane.org/gmane.comp.apache.excalibur.devel/1980/focus=1980
I figured Cocoon was fully moving away from avalon/excalibur and thus
lost interest a bit in doing the release.
On the release side, there isn't that much left to do. I guess calling a
vote and go through the formalities should be enough to get the binaries
released to ibiblio.
Also, note that i primarily focussed on getting things to work and
compile. I did not do any work on cleaning up the transitive
dependencies of the poms.
Regards
Jorg
Re: Releasing Avalon and Excalibur
Posted by Grzegorz Kossakowski <gr...@tuffmail.com>.
Reinhard Poetz napisał(a):
> Is anybody subscribed to the Excalibur mailing list and can ask over
> there?
I would only like to point out that this does not solve problem in
general, and not sure if in particular case. Of course having more jars
and poms on central repo is right thing, but problem lays in Maven
really. Do we have more dependencies that cannot be satisfied from
central repo? If so, adding information about repositories to the
archetypes if only an option IMHO. Fixing one issue (by declaring
dependencies explicitly, releasing some artifact on central) is only
shifting the wall farther but we'll hit it soon or later.
--
Grzegorz Kossakowski
Re: Releasing Avalon and Excalibur
Posted by Reinhard Poetz <re...@apache.org>.
Reinhard Poetz wrote:
> Kenney Westerhof (JIRA) wrote:
>> [
>> https://issues.apache.org/jira/browse/COCOON-1975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12462717
>> ]
>> Kenney Westerhof commented on COCOON-1975:
>> ------------------------------------------
>>
>> Correction: Avalon is _not_ available on central, sorry.
>>
>> The issue is totally different, but my recommendation above for
>> putting avalon @ ibiblio still goes.
>>
>> Please see http://jira.codehaus.org/browse/MNG-2743 for a full
>> description.
>>
>> Another workaround for this bug is to pull the <repositories> tag from
>> o.a.c:cocoon to cocoon-core.
>
> Jorg,
>
> IIRC it was you who worked on providing proper Avalon and Excalibur
> artifacts to central. What's the status of your work?
Is anybody subscribed to the Excalibur mailing list and can ask over there?
--
Reinhard Pötz Independent Consultant, Trainer & (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
--------------------------------------------------------------------
___________________________________________________________
Der fr�he Vogel f�ngt den Wurm. Hier gelangen Sie zum neuen Yahoo! Mail: http://mail.yahoo.de
Releasing Avalon and Excalibur
Posted by Reinhard Poetz <re...@apache.org>.
Kenney Westerhof (JIRA) wrote:
> [ https://issues.apache.org/jira/browse/COCOON-1975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12462717 ]
>
> Kenney Westerhof commented on COCOON-1975:
> ------------------------------------------
>
> Correction: Avalon is _not_ available on central, sorry.
>
> The issue is totally different, but my recommendation above for putting avalon @ ibiblio still goes.
>
> Please see http://jira.codehaus.org/browse/MNG-2743 for a full description.
>
> Another workaround for this bug is to pull the <repositories> tag from o.a.c:cocoon to cocoon-core.
Jorg,
IIRC it was you who worked on providing proper Avalon and Excalibur artifacts to
central. What's the status of your work?
--
Reinhard Pötz Independent Consultant, Trainer & (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
--------------------------------------------------------------------
[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 "Kenney Westerhof (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/COCOON-1975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12462717 ]
Kenney Westerhof commented on COCOON-1975:
------------------------------------------
Correction: Avalon is _not_ available on central, sorry.
The issue is totally different, but my recommendation above for putting avalon @ ibiblio still goes.
Please see http://jira.codehaus.org/browse/MNG-2743 for a full description.
Another workaround for this bug is to pull the <repositories> tag from o.a.c:cocoon to cocoon-core.
> cocoon-core-M2 could not be runned because of missing dependencies on avalon-framework-api-4.3 and excalibur-instrument-api-2.1
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: COCOON-1975
> URL: https://issues.apache.org/jira/browse/COCOON-1975
> Project: Cocoon
> Issue Type: Bug
> Components: - Build System: Maven
> Affects Versions: 2.2-dev (Current SVN)
> Reporter: Grzegorz Kossakowski (aka g[R]eK)
> Assigned To: Reinhard Poetz
> Priority: Blocker
>
> Using clean (empty ~/.m2/repository directory) maven instalation it is not possible to try cocoon-core-M2 following this tutorial: http://cocoon.zones.apache.org/daisy/documentation/g1/1159.html (really BIG thanks goes to Reinhard Pötz for improving docs last days!). It's due to somehow missing (or badly resovled) on avalon-framework-api-4.3 and excalibur-instrument-api-2.1 and results in error I've reported earlier:
> http://article.gmane.org/gmane.text.xml.cocoon.devel/68960
> If I copy manully missing jars into myWebapp/target/myWebapp-1.0-SNAPSHOT/WEB-INF/lib and start myWebapp using:
> mvn package jetty:run everything works as expected.
> On other hand, if you build whole trunk and install all blocks into local repository dependencies are resolved correctly.
> I'm trying to investigate futher but any help would be desired as I'm not Maven nor Cocoon expert :)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (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 (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/COCOON-1975?page=all ]
Reinhard Poetz reassigned COCOON-1975:
--------------------------------------
Assignee: Reinhard Poetz
> cocoon-core-M2 could not be runned because of missing dependencies on avalon-framework-api-4.3 and excalibur-instrument-api-2.1
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: COCOON-1975
> URL: http://issues.apache.org/jira/browse/COCOON-1975
> Project: Cocoon
> Issue Type: Bug
> Components: - Build System: Maven
> Affects Versions: 2.2-dev (Current SVN)
> Reporter: Grzegorz Kossakowski (aka g[R]eK)
> Assigned To: Reinhard Poetz
> Priority: Blocker
>
> Using clean (empty ~/.m2/repository directory) maven instalation it is not possible to try cocoon-core-M2 following this tutorial: http://cocoon.zones.apache.org/daisy/documentation/g1/1159.html (really BIG thanks goes to Reinhard Pötz for improving docs last days!). It's due to somehow missing (or badly resovled) on avalon-framework-api-4.3 and excalibur-instrument-api-2.1 and results in error I've reported earlier:
> http://article.gmane.org/gmane.text.xml.cocoon.devel/68960
> If I copy manully missing jars into myWebapp/target/myWebapp-1.0-SNAPSHOT/WEB-INF/lib and start myWebapp using:
> mvn package jetty:run everything works as expected.
> On other hand, if you build whole trunk and install all blocks into local repository dependencies are resolved correctly.
> I'm trying to investigate futher but any help would be desired as I'm not Maven nor Cocoon expert :)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[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 "Kenney Westerhof (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/COCOON-1975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12462713 ]
Kenney Westerhof commented on COCOON-1975:
------------------------------------------
This issue is caused by the fact that avalon-framework-impl:jar:4.3 is present at central, but the pom is not.
Since central is searched first, it will mark the artifact as coming from there and doesn't check the snapshot repo
for the accompanying pom.
Since the pom cannot be found, none of avalon-framework-impl's dependencies are used and this breaks stuff.
Artifacts should only be present at one repository - the first repo containing that artifact will be used.
I suggest you do not deploy releases to the apache snapshot repository and get avalon properly deployed
on central: zip up the pom and jar from the snapshot repo and file an issue at http://jira.codehaus.org/browse/MAVENUPLOAD.
When it's deployed, remove avalon releases from the snapshot repo.
The workaround is to put the avalon-framework-impl pom from the snapshot repo next to the jar in the local repository.
> cocoon-core-M2 could not be runned because of missing dependencies on avalon-framework-api-4.3 and excalibur-instrument-api-2.1
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: COCOON-1975
> URL: https://issues.apache.org/jira/browse/COCOON-1975
> Project: Cocoon
> Issue Type: Bug
> Components: - Build System: Maven
> Affects Versions: 2.2-dev (Current SVN)
> Reporter: Grzegorz Kossakowski (aka g[R]eK)
> Assigned To: Reinhard Poetz
> Priority: Blocker
>
> Using clean (empty ~/.m2/repository directory) maven instalation it is not possible to try cocoon-core-M2 following this tutorial: http://cocoon.zones.apache.org/daisy/documentation/g1/1159.html (really BIG thanks goes to Reinhard Pötz for improving docs last days!). It's due to somehow missing (or badly resovled) on avalon-framework-api-4.3 and excalibur-instrument-api-2.1 and results in error I've reported earlier:
> http://article.gmane.org/gmane.text.xml.cocoon.devel/68960
> If I copy manully missing jars into myWebapp/target/myWebapp-1.0-SNAPSHOT/WEB-INF/lib and start myWebapp using:
> mvn package jetty:run everything works as expected.
> On other hand, if you build whole trunk and install all blocks into local repository dependencies are resolved correctly.
> I'm trying to investigate futher but any help would be desired as I'm not Maven nor Cocoon expert :)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
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
--------------------------------------------------------------------
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):
> 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):
> Reinhard Poetz (JIRA) wrote:
>> [
>> http://issues.apache.org/jira/browse/COCOON-1975?page=comments#action_12461377
>> ] Reinhard Poetz commented on COCOON-1975:
>> ----------------------------------------
>>
>> Stupid Maven. It doesn't resolve the transitive dependencies
>> correctly. We have to release cocoon-core again where we set the
>> dependencies on avalon-framework-api and excalibur-instrument
>> explicitly.
>
> 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?
It would be great understand what is the reason for this behavior in
order to avoid such situations in the future. I can invest some time
(this free time was meant to be spent on writing docs, but now there is
nothing working to document...) in this issue but I'm not sure what
should I start from.
Any hints how to debug Maven's dependency resolution? Do you have idea
why installing trunk version of modules impacts resolving dependencies
of core-M2?
--
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>.
Reinhard Poetz (JIRA) wrote:
> [ http://issues.apache.org/jira/browse/COCOON-1975?page=comments#action_12461377 ]
>
> Reinhard Poetz commented on COCOON-1975:
> ----------------------------------------
>
> Stupid Maven. It doesn't resolve the transitive dependencies correctly. We have to release cocoon-core again where we set the dependencies on avalon-framework-api and excalibur-instrument explicitly.
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?
--
Reinhard Pötz Independent Consultant, Trainer & (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
--------------------------------------------------------------------
[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 (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/COCOON-1975?page=comments#action_12461377 ]
Reinhard Poetz commented on COCOON-1975:
----------------------------------------
Stupid Maven. It doesn't resolve the transitive dependencies correctly. We have to release cocoon-core again where we set the dependencies on avalon-framework-api and excalibur-instrument explicitly.
Any better options?
> cocoon-core-M2 could not be runned because of missing dependencies on avalon-framework-api-4.3 and excalibur-instrument-api-2.1
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: COCOON-1975
> URL: http://issues.apache.org/jira/browse/COCOON-1975
> Project: Cocoon
> Issue Type: Bug
> Components: - Build System: Maven
> Affects Versions: 2.2-dev (Current SVN)
> Reporter: Grzegorz Kossakowski (aka g[R]eK)
> Assigned To: Reinhard Poetz
> Priority: Blocker
>
> Using clean (empty ~/.m2/repository directory) maven instalation it is not possible to try cocoon-core-M2 following this tutorial: http://cocoon.zones.apache.org/daisy/documentation/g1/1159.html (really BIG thanks goes to Reinhard Pötz for improving docs last days!). It's due to somehow missing (or badly resovled) on avalon-framework-api-4.3 and excalibur-instrument-api-2.1 and results in error I've reported earlier:
> http://article.gmane.org/gmane.text.xml.cocoon.devel/68960
> If I copy manully missing jars into myWebapp/target/myWebapp-1.0-SNAPSHOT/WEB-INF/lib and start myWebapp using:
> mvn package jetty:run everything works as expected.
> On other hand, if you build whole trunk and install all blocks into local repository dependencies are resolved correctly.
> I'm trying to investigate futher but any help would be desired as I'm not Maven nor Cocoon expert :)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira