Lally Singh wrote:
Is there a similar situation with avalon-framework-impl?
Make sure by using exclusions that you don't get any other Avalon or Excalibur
dependencies than those that are coming from cocoon-core. If there are still
wrong dependencies showing up, build by using the -X switch and look at the
dependency graph resolution logs and find out which dependency is responsible
and add an exclusion there.
Also be aware that commons-logging and commons-jxpath come with poms of poor
quality. If you add them explicitly, take care of removing all unnecessary
dependencies (see
http://svn.apache.org/repos/asf/cocoon/trunk/core/cocoon-core/pom.xml and
http://svn.apache.org/repos/asf/cocoon/trunk/core/cocoon-sitemap/cocoon-sitemap-impl/pom.xml)
--
Reinhard Pötz Independent Consultant, Trainer & (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
--------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
