It appears like it's necessary to add these lines to pom.xml in order to
prevent the dependency chain from downloading:
<dependency>
<groupId>org.jasig.cas.client</groupId>
<artifactId>cas-client-core</artifactId>
<version>3.2.1</version>
<exclusions>
<exclusion>
<artifactId>commons-logging</artifactId>
<groupId>commons-logging</groupId>
</exclusion>
</exclusions>
</dependency>
Does this seem a bit off to anybody else? I guess CAS client doesn't
like SLF4j. :-(
Eric
-----Original Message-----
From: Stein, Eric
Sent: Tuesday, December 11, 2012 12:44 PM
To: [email protected]
Subject: RE: [cas-user] Tomcat 7.0.25 and cas-client-core-3.2.1.jar
Thanks. I'm sorry I forgot to include my pom in the last message, but
you can find it below. The only explicit dependency is on
cas-client-core-3.2.1.jar. Are you proposing that I make that dependency
provided? That seems a little odd, but I guess I could do that.
<project xmlns="http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd";>
<modelVersion>4.0.0</modelVersion>
<groupId>com.locustec</groupId>
<artifactId>hello-world-webapp</artifactId>
<packaging>war</packaging>
<version>1.0.0</version>
<name>hello-world-webapp Maven Webapp</name>
<url>http://maven.apache.org</url>
<build>
<finalName>hello-world</finalName>
</build>
<properties>
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
</properties>
<dependencies>
<dependency>
<groupId>org.jasig.cas.client</groupId>
<artifactId>cas-client-core</artifactId>
<version>3.2.1</version>
</dependency>
</dependencies>
</project>
-----Original Message-----
From: Trenton D. Adams [mailto:[email protected]]
Sent: Tuesday, December 11, 2012 12:28 PM
To: [email protected]
Cc: Stein, Eric
Subject: Re: [cas-user] Tomcat 7.0.25 and cas-client-core-3.2.1.jar
Yeah, don't include that jar file, cause you're not supposed to. You'll
see entries in your tomcat log saying that it shouldn't be there.
If using maven, set your scope to "provided".
On 12-12-11 10:13 AM, Stein, Eric wrote:
> Hi,
> I'm playing around with CAS with a trivial hello-world web
> application. I was originally using
> edu.yale.its.tp.cas.client.filter.CASFilter
> as the authentication filter, and just switched to using the filters
> in cas-client-core-3.2.1.jar, which I believe are more recent. What
> I'm finding is that I can't do a clean uninstall of hello-world.war
> from Tomcat 70.25 any more. The file
> hello-world/WEB-INF/lib/servlet-api-2.3.jar isn't getting deleted -
> apparently Tomcat is gettings its hooks in and not letting go. Is this
> a know issue with a workaround/fix, or am I Special?
>
> Thanks,
> Eric
>
--
Trenton D. Adams
Senior Systems Analyst/Web Software Developer Navy Penguins at your
service!
Athabasca University
(780) 675-6195
:wq!
--
This communication is intended for the use of the recipient to whom
it
is addressed, and may contain confidential, personal, and or
privileged
information. Please contact us immediately if you are not the
intended
recipient of this communication, and do not copy, distribute, or
take
action relying on it. Any communications received in error, or
subsequent reply, should be deleted or destroyed.
---
--
You are currently subscribed to [email protected] as:
[email protected]
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/cas-user
