Details
-
Bug
-
Status: Closed
-
Blocker
-
Resolution: Fixed
-
2.2
-
None
Description
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 :)
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 :)