Hello,

On 08/27/2015 01:26 PM, Misagh Moayyed wrote:
> Also, this is really the first functional release candidate for v4.1;
> Please ignore 4.1.0 RC1. If you run into issues and anomalies, please
> discuss and submit issues.

I just changed the cas-version in my pom.xml to 4.1.0-RC2.

It still builds fine, but I now get this log4j error about multiple
loggers being present when deploying / starting the war in Jetty:

--- cut ---

SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in
[jar:file:/var/cache/jetty8/data/jetty-MYINSTANCE/webapp/WEB-INF/lib/cas-server-core-4.1.0-RC2.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in
[jar:file:/var/cache/jetty8/data/jetty-MYINSTANCE/webapp/WEB-INF/lib/log4j-slf4j-impl-2.3.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an
explanation.
SLF4J: ILoggerFactory to be used for logging is:
org.apache.logging.slf4j.Log4jLoggerFactory
SLF4J: Actual binding is of type [org.slf4j.impl.CasLoggerFactory]
SLF4J: The following set of substitute loggers may have been accessed
SLF4J: during the initialization phase. Logging calls during this
SLF4J: phase were not honored. However, subsequent logging calls to these
SLF4J: loggers will work as normally expected.
SLF4J: See also http://www.slf4j.org/codes.html#substituteLogger
--- cut ---


Did I overlook anything or do I need to change anything regarding the
dependencies?




Regards

Christian


-- 
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

Reply via email to