Missing groovy engine jar file in IDP 2.4

[Glanville, Larry]

When deploying a new IDP instance, version 2.4,  I receive the following messages in the catalina.out.

I also noticed in the downloaded package there is no groovy-engine-yyyymmdd.jar file.


11:17:14,223 |-INFO in ch.qos.logback.classic.joran.JoranConfigurator at 344113f8 - Registering current configuration as safe fallback point
11:17:13,148 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could NOT find resource [logback.groovy]
11:17:13,148 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could NOT find resource [logback-test.xml]
11:17:13,148 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Found resource [logback.xml] at [jar:file:/opt/shibboleth/apache-tomcat-6.0.37/endorsed/shibboleth-identityprovider-2.4.0.jar!/logback.xml]
11:17:13,154 |-INFO in ch.qos.logback.core.joran.spi.ConfigurationWatchList at 2f344e23 - URL [jar:file:/opt/shibboleth/apache-tomcat-6.0.37/endorsed/shibboleth-identityprovider-2.4.0.jar!/logback.xml] is not of type file
11:17:13,194 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - debug attribute not set
11:17:13,195 |-ERROR in ch.qos.logback.core.joran.spi.Interpreter at 3:16 - RuntimeException in Action for tag [configuration] java.lang.NullPointerException
        at java.lang.NullPointerException
        at      at ch.qos.logback.classic.util.EnvUtil.isGroovyAvailable(EnvUtil.java:25)
        at      at ch.qos.logback.classic.joran.action.ConfigurationAction.begin(ConfigurationAction.java:59)
        at      at ch.qos.logback.core.joran.spi.Interpreter.callBeginAction(Interpreter.java:276)


Has anyone run into this?  Is there a proven workaround?   As a result of this, the context fails to deploy.


Thanks,
Larry

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/users/attachments/20131112/9ead87dc/attachment.html