You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shindig.apache.org by be...@apache.org on 2008/07/20 06:49:34 UTC

svn commit: r678248 - /incubator/shindig/trunk/pom.xml

Author: beaton
Date: Sat Jul 19 21:49:33 2008
New Revision: 678248

URL: http://svn.apache.org/viewvc?rev=678248&view=rev
Log:
We're throwing "class not found" exceptions on startup for apache 
commons io classes.  For reasons that I don't understand, conflicting 
commons-io dependencies between htmlunit (1.3.1) and shindig (1.4) cause
maven to decide not to include either version in our generate war files.

Regardless of how weird the symptom, excluding the conflicting 
dependency seems like a reasonable fix for the root cause.

Modified:
    incubator/shindig/trunk/pom.xml

Modified: incubator/shindig/trunk/pom.xml
URL: http://svn.apache.org/viewvc/incubator/shindig/trunk/pom.xml?rev=678248&r1=678247&r2=678248&view=diff
==============================================================================
--- incubator/shindig/trunk/pom.xml (original)
+++ incubator/shindig/trunk/pom.xml Sat Jul 19 21:49:33 2008
@@ -852,6 +852,16 @@
         <groupId>net.sourceforge.htmlunit</groupId>
         <artifactId>htmlunit</artifactId>
         <version>2.1</version>
+        <!-- 
+          htmlunit depends on an out of date rev of commons-io, which ends
+          up causing classpath problems in generated war files.
+        -->
+        <exclusions>
+          <exclusion>
+            <groupId>commons-io</groupId>
+            <artifactId>commons-io</artifactId>
+          </exclusion>
+        </exclusions>
       </dependency>
       <dependency>
         <groupId>log4j</groupId>