Commons-logging is a completely different artifact from log4j. But there is a possibility that c-l is pulling in log4j as a transitive dependency.
Try adding <scope>provided</scope> to the c-l dep, see what happens, and report back. Wayne On 1/24/08, Holt, Jack C. <[EMAIL PROTECTED]> wrote: > > I would like to not include the jar file for log4j when producing a WAR > file but allow it to be used when running my web app in Jetty. > > You see, JBoss includes a jar for log4j (a different version than I have > set up a dependency for in my POM file) and it causes errors when the > WAR file is deployed in JBoss. I have been manually removing the log4j > file after the WAR file is generated. > > I have the following dependency in my POM file which I believe is the > reason the log4j jar file is showing: > > <dependency> > <groupId>commons-logging</groupId> > <artifactId>commons-logging</artifactId> > <version>1.1</version> > </dependency> > > Do I need to somehow configure this as a dependency of the Jetty plugin > and remove it as a dependency of the project? > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
