Mike, You can use Maven's exclusions to to exclude dependencies of a dependency if you feel you don't need them:
http://maven.apache.org/pom.html#Exclusions -Scott On 10/5/07, Mike Kennedy <[EMAIL PROTECTED]> wrote: > > Hello, > > > > I'm attempting to get CAS 3.1 clustering to work with JBoss. In the CAS > user manual it says that adding this dependency to the cas-server-webapp > pom.xml isn't necessary because I'm using the JBoss AS: > > > > <dependency> > > <groupId>org.jasig.cas</groupId> > > <artifactId>cas-server-integration-jboss</artifactId> > > <version>3.1</version> > > <scope>runtime</scope> > > </dependency> > > > > I found this to be partially incorrect however. But, I might be doing > something wrong here. If I don't include this dependency then the class > files for JBossCacheTicketRegistry and JBossCacheFactoryBean aren't included > in the war and I cannot include these beans in my applicationContext.xml: > > > > <bean id="ticketRegistry" > > class="org.jasig.cas.ticket.registry.JBossCacheTicketRegistry"> > > <property name="cache" ref="cache" /> > > </bean> > > > > <bean id="cache" class="org.jasig.cas.util.JBossCacheFactoryBean"> > > <property name="configLocation" > > value="classpath:jbossTicketCacheReplicationConfig.xml" /> > > </bean> > > > > However, if I do include this dependency then I also get all the jars for > JBossCache that are already included in JBoss AS. While it doesn't seem to > break anything if I do this, I'd rather not have them in there twice if I > don't need to. > > > > In CAS 3.0.7, since I had to include the JBoss jars manually I didn't have > this problem. Any suggestions? > > > > Mike > > _______________________________________________ > Yale CAS mailing list > [email protected] > http://tp.its.yale.edu/mailman/listinfo/cas > > -- -Scott Battaglia LinkedIn: http://www.linkedin.com/in/scottbattaglia
_______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
