http://yennicktrevels.com/blog/2013/10/11/automated-gradle-project-deployment-to-sonatype-oss-repository/ Using a 'spongycastle' subgroup (ie com.madgag.spongycastle) to give a useful grouping, apparently this is legit: https://docs.sonatype.org/display/Repository/Choosing+your+Coordinates Also guard against missing gradle.properties for travis, which doesn't have to do signing or uploading to sonatype.
I think "BC" here is a KeyStore format, not a provider. Would be nice to not have to make this correction, but without code changes, I think it wouldn't be easy to write a distingushing ssed expression.
Version: heads/spongy-scripts-0-gd79423a-dirty https://github.com/rtyley/spongycastle/tree/spongy-scripts
``` org.bouncycastle.pqc.jcajce.provider.test.AllTests > org.bouncycastle.pqc.jcajce.provider.test.McElieceKobaraImaiCipherTest.testEnDecryption_SHA256_11_50 FAILED junit.framework.AssertionFailedError at McElieceKobaraImaiCipherTest.java:40 ``` With this commit, `$ gradle check` passes locally.
Pretty sure BouncyCastle needs OpenJDK to build and run tests I don't know how to register the unsigned JCE provider on Oracle JDK, OpenJDK doesn't seem to check. try to make travis output clearer http://stackoverflow.com/a/17942820/438886 The '--info' flag hopefully will stop travis builds from dying from the no-output-in-10-minutes problem, but weirdly is also the only thing that makes spongycastle tests pass... https://twitter.com/rtyley/status/425373078084784128 https://travis-ci.org/rtyley/spongycastle/builds/17299026 Also use container-based infrastructure: http://docs.travis-ci.com/user/workers/container-based-infrastructure/
If you run the Gradle build, you'd see TlsTestCase & DTLSTestCase cause a build failure: ``` junit.framework.AssertionFailedError: Class org.bouncycastle.crypto.tls.test.DTLSTestCase has no public constructor TestCase(String name) or TestCase() ``` The reason is that both these testcases actually have two-arg constructors (because they need a bunch of extra configuration data), so don't fit the normal no-arg or one-arg constructor requirement of classes extending `TestCase`. The fix used here is to employ JUnit 'parameterized tests', rather than a TestSuite: https://github.com/junit-team/junit/wiki/Parameterized-tests P.S. You can see also see the Gradle build failure in Travis CI here: https://travis-ci.org/rtyley/spongycastle/builds/29981411#L1052-L1056 (this is why BC needs bcgit#80 !)
… issue in X9.31.