I just got the following failures in the kerberos shared module after the merge.  Perhaps
this is due to the new encryption types which may require some additional configuration.

For brevity I have snipped the tests that have passed.

[INFO] ----------------------------------------------------------------------------
[INFO] Building ApacheDS Protocol Kerberos Shared

SNIP ...

 T E S T S
Running org.apache.directory.server.kerberos.shared.crypto.encryption.CipherTextHandlerTest
Tests run: 9, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.296 sec <<< FAILURE!
Running org.apache.directory.server.kerberos.shared.crypto.encryption.KerberosKeyFactoryTest
Tests run: 7, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.07 sec <<< FAILURE!
Running org.apache.directory.server.kerberos.shared.keytab.KeytabTest
Tests run: 3, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.025 sec <<< FAILURE!
Running org.apache.directory.server.kerberos.shared.service.LockBoxTest
Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.011 sec <<< FAILURE!

Results :

Tests in error:
  testAes256GoodPasswordDecrypt(org.apache.directory.server.kerberos.shared.crypto.encryption.CipherTextHandlerTest )
  testKerberosKeyFactory(org.apache.directory.server.kerberos.shared.crypto.encryption.KerberosKeyFactoryTest )
  testBadPassword(org.apache.directory.server.kerberos.shared.service.LockBoxTest )

Tests run: 64, Failures: 0, Errors: 6, Skipped: 0

[INFO] ------------------------------------------------------------------------

Here's my java version:

akarasulu@stein:~/trunks/trunk-with-dependencies$ java -version
java version "1.5.0_08"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_08-b03)
Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_08-b03, mixed mode)

NOTE: No modifications were made to the JVM security provider at all.  This is a stock 1.5

Is there something required to make these tests pass that you have configured on your machine/jvm?

If additional configuration is required to make these tests pass then we need to figure out a way to
make the test case detect that and bypass the test.  Either that or we need to disable the test cases.
For now I will disable these tests until you figure out how to make the test cases pass on all configurations.