Using servlet-api 3.0.x and excluding it from war artifact
Inserting log messages and stack trace if IP configuration files are not found.
Installing/Configuration of Thredds 4.3.16 - updated jars
Minor upgrade in logging libs - matches versions used in esg-security
Upgrade Spring libs to 3.2.2
Updates spring-security* jars and spring-asm jars to latest 3.1.4

In the previous commit the org.springframework jars were updated to
3.2.2 (as of this commit they are actually at 3.2.3!)

The org.springframework.security jars were also updated but they only
version as far ahead as 3.1.4

This commit sets those security (and asm) jars to the 3.1.4 version
values.

See links:
http://mvnrepository.com/artifact/org.springframework
http://mvnrepository.com/artifact/org.springframework.security
http://mvnrepository.com/artifact/org.springframework/spring-asm

The build seems okay though there are now a few deprecated calls
showing up:

make:
     [echo] Java compiling esg-orp...
    [mkdir] Created dir: /Users/bell51/projects/esg-orp/build
    [javac] Compiling 35 source files to /Users/bell51/projects/esg-orp/build
    [javac] /Users/bell51/projects/esg-orp/src/java/main/esg/orp/orp/MyAuthenticationProvider.java:34: warning: [deprecation] org.springframework.security.core.authority.GrantedAuthorityImpl in org.springframework.security.core.authority has been deprecated
    [javac] import org.springframework.security.core.authority.GrantedAuthorityImpl;
    [javac]                                                   ^
    [javac] /Users/bell51/projects/esg-orp/src/java/main/esg/orp/orp/MyUserDetailsService.java:30: warning: [deprecation] org.springframework.security.core.authority.GrantedAuthorityImpl in org.springframework.security.core.authority has been deprecated
    [javac] import org.springframework.security.core.authority.GrantedAuthorityImpl;
    [javac]                                                   ^
    [javac] /Users/bell51/projects/esg-orp/src/java/main/esg/orp/orp/MyAuthenticationProvider.java:68: warning: [deprecation] org.springframework.security.core.authority.GrantedAuthorityImpl in org.springframework.security.core.authority has been deprecated
    [javac] 			authorities.add( new GrantedAuthorityImpl(ROLES[0]) );
    [javac] 			                     ^
    [javac] /Users/bell51/projects/esg-orp/src/java/main/esg/orp/orp/MyAuthenticationProvider.java:69: warning: [deprecation] org.springframework.security.core.authority.GrantedAuthorityImpl in org.springframework.security.core.authority has been deprecated
    [javac] 			authorities.add( new GrantedAuthorityImpl(ROLES[1]) );
    [javac] 			                     ^
    [javac] /Users/bell51/projects/esg-orp/src/java/main/esg/orp/orp/MyOpenID4JavaConsumer.java:67: warning: [deprecation] OpenID4JavaConsumer(java.util.List<org.springframework.security.openid.OpenIDAttribute>) in org.springframework.security.openid.OpenID4JavaConsumer has been deprecated
    [javac] 		super(attributes);
    [javac] 		^
    [javac] /Users/bell51/projects/esg-orp/src/java/main/esg/orp/orp/MyUserDetailsService.java:58: warning: [deprecation] org.springframework.security.core.authority.GrantedAuthorityImpl in org.springframework.security.core.authority has been deprecated
    [javac] 				authorities.add( new GrantedAuthorityImpl(authority) );
    [javac] 				                     ^
    [javac] 6 warnings
     [copy] Copying 16 files to /Users/bell51/projects/esg-orp/build

BUILD SUCCESSFUL
Total time: 16 seconds

Luca and ORP team... can you address these deprecated calls... :-)

-ESGF Project Janitor ;-)
Fix setting the right version for current spring reference to 3.2 version

Yes, we have normalized across the board on Spring 3.2.2 RELEASE

Nicolas was testing and found this issue...
Made the changes accordingly

----email------

1- These 2 files below still need to be modifed (Replace each occurence of 3.0.xsd and 3.1.xsd with 3.2.xsd) or esg-orp will not start
/usr/local/tomcat/webapps/esg-orp/WEB-INF/classes/esg/orp/orp/config/security-context-auth.xml
/usr/local/tomcat/webapps/esg-orp/WEB-INF/classes/esg/orp/orp/config/web-context.xml

---------------
Thanks Nicolas
Fix - No need for spring-asm under spring 3.2.2 RELEASE

Nicolas discovered this oversight... Thanks!

>
> 2- As explained here (http://stackoverflow.com/questions/16801639/spring-core-3-2-2-spring-security-3-1-4-java-lang-incompatibleclasschangeerro) ;
> this jar should be removed  from esg-orp: /usr/local/tomcat/webapps/esg-orp/WEB-INF/lib/spring-asm-3.1.4.RELEASE.jar as it is now integrated into spring-core.3.2.2 (or dependency should be reviewed)
> This is the same problem we had before for webapp esgf-dashboard.
Changes to xml files associated with orp authentication to make xsd versions congruous with new Spring jar updates

Nicolas' tests yeilded the following recommendations:

-----email-----
Hi Gavin,

OK, I could solve these problems on my test data/compute node. All of this should be good soon!

I started this morning from a fresh clean server and installed what is in devel.

1/ - I did not get the errors you posted below because I do not have a
test IDP/Index node yet. I just have the production one for now. I am
working on it... But, I would say that the first exception below is
due to a spring-asm dependency. Could you try to remove every
spring-asm jar from your webapps and try again? On my side, I will set
up a test env soon...

2/ - As you upgraded spring-security to 3.1.4 all over the board, here
is what should be done on esg-orp configuration files:

/usr/local/tomcat/webapps/esg-orp/WEB-INF/classes/esg/orp/orp/config/security-context-auth.xml
-> Replace each occurence of 3.2.xsd with 3.1.xsd, despite what I said
last time...
/usr/local/tomcat/webapps/esg-orp/WEB-INF/classes/esg/orp/orp/config/web-context.xml
-> Replace each occurence of 3.2.xsd with 3.0.xsd, despite what I said
last time...
/usr/local/tomcat/webapps/esg-orp/WEB-INF/classes/esg/orp/orp/config/security-context-authz.xml
-> Replace each occurence of 3.0.xsd with 3.1.xsd, this one is a NEW
modif !!!
---------------

These summarize the changes in this commit.
Spring migration growing pains...

Changes in home.jsp because of recent upgrade of spring...

-----email-----
(from Nicolas)

3/ - As SPRING_SECURITY_LAST_EXCEPTION_KEY is now deprecated,

In the file: /usr/local/tomcat/webapps/esg-orp/WEB-INF/views/jsp/home.jsp

Replace line 8
<c:set var="last_exception_key" value="<%= org.springframework.security.web.authentication.AbstractProcessingFilter.SPRING_SECURITY_LAST_EXCEPTION_KEY %>"/>
With
<c:set var="last_exception_key" value="<%= org.springframework.security.web.WebAttributes.AUTHENTICATION_EXCEPTION %>"/>

If not changed, I can not access any endpoint...
---------------

Thanks Nicolas! :-)
Updating Eclipse classpath.
Updating Spring XSD to 3.1.
Added Licenses for CORDEX groups and modified registratin-request.jsp accordingly.
updated java version used in build (to 1.7)
need to explicitly point to devel host for building
esgf.org is now just for github resources. devel.esgf.org is still where the development infrastructure lives
pointing to github site location for ivy ref files