IDP 3.2, startup involving scan of jar files, etc

[Steven Carmody]

Hi,

I've pulled the current src from git and subversion, and compiled it. 
Ive deployed it with java 8, and jetty 9.3. I followed the jetty 9.3 
config instructions in the shib wiki.

When I start up jetty, it produces a large log file. Its scanning 
classes from jar files. Many many classes and jar files. Eventually it 
settles into what appears to be a loop:

17:08:17.716 - DEBUG [org.eclipse.jetty.util.Scanner:562] - scan 
accepted /opt/shibboleth-idp/jetty-base/webapps/idp.xml

17:08:17.716 - DEBUG [org.eclipse.jetty.util.Scanner:562] - scan 
accepted /opt/shibboleth-idp/jetty-base/webapps/static.xml

17:08:17.717 - DEBUG [org.eclipse.jetty.util.Scanner:503] - scanned 
[/opt/shibboleth-idp/jetty-base/webapps]: {}

17:08:18.726 - DEBUG [org.eclipse.jetty.util.Scanner:562] - scan 
accepted /opt/shibboleth-idp/jetty-base/webapps/idp.xml

17:08:18.726 - DEBUG [org.eclipse.jetty.util.Scanner:562] - scan 
accepted /opt/shibboleth-idp/jetty-base/webapps/static.xml

17:08:18.726 - DEBUG [org.eclipse.jetty.util.Scanner:503] - scanned 
[/opt/shibboleth-idp/jetty-base/webapps]: {}

Two questions --

1) suggestions on how to suppress the scans ?

2) suggestions on what I might have done to cause that scna loop ?

thanks !