Gateway 3253 - Switched over to local maven repo, removed connectdir property.

This completes steps 1-5 in Steve M's recommendation. See:

https://issues.connectopensource.org/browse/GATEWAY-3253?focusedCommentId=16327&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16327

This way we have a single approach for local repo dependencies that can't otherwise be pulled from standard maven repositories. No more sym links and no connectdir property needed. I used the following script to migrate the jars into the repo:

    #!/bin/sh

    export BASEDIR=/full/path/to/repos/git/CONNECT/ThirdParty

    mvn deploy:deploy-file -Durl=file:///$BASEDIR/repo/ -Dfile=jms1.1/lib/javax.jms.jar -DgroupId=javax.jms -DartifactId=jms -Dversion=1.1 -Dpackaging=jar 
    mvn deploy:deploy-file -Durl=file:///$BASEDIR/repo/ -Dfile=JTA/javax.transaction.jar -DgroupId=javax.transaction -DartifactId=jta -Dversion=1.0.1B -Dpackaging=jar 
    mvn deploy:deploy-file -Durl=file:///$BASEDIR/repo/ -Dfile=jmx-1_2_1-bin/lib/jmxri.jar -DgroupId=com.sun.jmx -DartifactId=jmxri -Dversion=1.2.1 -Dpackaging=jar 
    mvn deploy:deploy-file -Durl=file:///$BASEDIR/repo/ -Dfile=jmx-1_2_1-bin/lib/jmxtools.jar -DgroupId=com.sun.jdmk -DartifactId=jmxtools -Dversion=1.2.1 -Dpackaging=jar 
    mvn deploy:deploy-file -Durl=file:///$BASEDIR/repo/ -Dfile=OpenSSO/ssoAdminTools/lib/opensso.jar -DgroupId=com.sun.identity -DartifactId=opensso -Dversion=1.0 -Dpackaging=jar 
    mvn deploy:deploy-file -Durl=file:///$BASEDIR/repo/ -Dfile=OpenSSO/ssoAdminTools/lib/opensso-sharedlib.jar -DgroupId=com.sun.identity -DartifactId=opensso-sharedlib -Dversion=1.0 -Dpackaging=jar 
    mvn deploy:deploy-file -Durl=file:///$BASEDIR/repo/ -Dfile=OpenSSO/openssoclientsdk.jar -DgroupId=com.sun.identity -DartifactId=openssoclientsdk -Dversion=1.0 -Dpackaging=jar 
    mvn deploy:deploy-file -Durl=file:///$BASEDIR/repo/ -Dfile=jsf/jsfcl.jar -DgroupId=org.connectopensource.thirdparty.com.sun.jsf -DartifactId=jsfcl -Dversion=1.0 -Dpackaging=jar 
    mvn deploy:deploy-file -Durl=file:///$BASEDIR/repo/ -Dfile=jsf/appbase.jar -DgroupId=org.connectopensource.thirdparty.com.sun.jsf -DartifactId=appbase -Dversion=1.0 -Dpackaging=jar 
    mvn deploy:deploy-file -Durl=file:///$BASEDIR/repo/ -Dfile=jsf/sqlx.jar -DgroupId=org.connectopensource.thirdparty.com.sun.jsf -DartifactId=sqlx -Dversion=1.0 -Dpackaging=jar 
    mvn deploy:deploy-file -Durl=file:///$BASEDIR/repo/ -Dfile=jsf/dataprovider.jar -DgroupId=org.connectopensource.thirdparty.com.sun.jsf -DartifactId=dataprovider -Dversion=1.0 -Dpackaging=jar 
    mvn deploy:deploy-file -Durl=file:///$BASEDIR/repo/ -Dfile=jsf/errorhandler.jar -DgroupId=org.connectopensource.thirdparty.com.sun.jsf -DartifactId=errorhandler -Dversion=1.0 -Dpackaging=jar 
    mvn deploy:deploy-file -Durl=file:///$BASEDIR/repo/ -Dfile=jsf/webui-jsf.jar -DgroupId=org.connectopensource.thirdparty.com.sun.jsf -DartifactId=webui-jsf -Dversion=1.0 -Dpackaging=jar 
    mvn deploy:deploy-file -Durl=file:///$BASEDIR/repo/ -Dfile=jsf/webui-jsf-suntheme.jar -DgroupId=org.connectopensource.thirdparty.com.sun.jsf -DartifactId=webui-jsf-suntheme -Dversion=1.0 -Dpackaging=jar 

...This was tested in the GFE (weblogic + linux) against the complete suite of soapui validation tests.

There are also instructions in the README for adding new local repo dependencies if it comes up again.