[Pki-devel] [PATCH] Removal of version numbers from jar file names

The attached patch addresses the following PKI issue: * TRAC Ticket #350 - Dogtag 10: Remove version numbers from PKI jar files . . . This patch was checked against the following PKI services (CA/KRA/OCSP/TKS as a single merged instance): * The Dogtag 10 versions of 'dogtag-pki-theme', 'pki-core', and 'pki-console' were all built, installed, and tested on a 64-bit Fedora 17 machine * None of the java jars under /usr/share/java/pki contain any embedded versions in their names, and there are no more symbolic links * The JNI 'symkey.jar' is a file and contains no embedded version in its name * CA o after reporting the previously encountered 'certutil -a' problem on the admin cert, and manually correcting it, I successfully requested, approved, and issued a certificate using the 'Maual User Dual-Use Certificate Enrollment' profile * KRA o after launching a standalone browser profile (since the KRA admin certificate will not be prompted for since it is running on the same port), the keys were successfully archived using the 'Manual User Signing and Encryption Certificates Enrollment' profile<https://dogtag17-clone.usersys.redhat.com:8443/ca/ee/ca/profileSelect?profileId=caDualCert> * OCSP o after launching another standalone browser profile (since the KRA admin certificate will not be prompted for since it is running on the same port), the command 'OCSPClient server.example.com 8080 /var/lib/pki/pki-tomcat/alias/ "ocspSigningCert cert-pki-tomcat" 23 22.res 1 /ocsp/ee/ocsp' was executed from the command line while performing a 'tail -f /var/log/pki/pki-tomcat/ocsp/debug' which showed communication with the OCSP server * TKS o I successfully launched the URL 'http://server.example.com:8080/tks/services' from a browser * PKI Console o No GUI was presented for the PKI console when invoking 'pkiconsole https://server.example.com:8443/ca';, but this appeared to be a display issue, not a problem with the newly named jars If this patch is found to be acceptable in its current incarnation, please feel free to push it to the 'master' branch so that it may be included in the upcoming Beta 2 builds. -- Matt