Please export a jar

[SalusaSecondus]

Please modify the build system (and ideally source layout) such that it is easy to build a JAR which other tests can easily depend on.

[thaidn]

Do you need just the test cases or also the test runners?

[SalusaSecondus]

I think we'd need the runners as well.

[thaidn]

We can build and upload a JAR to Maven.

[SalusaSecondus]

This won't actually solve my problem. I really need a build-target which outputs the jar.

[SalusaSecondus]

Pinging this again. I have some code which I really want to test with Wycheproof, but for various reasons it is much easier for this code to consume Wycheproof as a test dependency than have Wycheproof depend on it. I experimented, and it seems a tad tricky to get bazel to include junit as a normal dependency (so that it can just build a jar containing all of the tests and runners). It looks like we could build an empty test case and then use the jar generated by that as the artifact.

[thaidn]

Quan, could you please take a look?

[cryptosubtlety]

I'm sorry, I'm pretty overwhelmed right now. I don't have cycles to work on it in a month or two

[thaidn]

Hey @SalusaSecondus just so you know that I'm actively working on this and will have something on Mave n soon.

[amanvir]

@thaidn any updates on this? Let me know if I can assist

[SalusaSecondus]

Just bumping this as it's been a while and we could really use a consumable version of this to test various libraries.

[cpu]

Closing as no longer applicable since this seemed to be a request for packaging the runners in addition to testdata. See #105, #127.

If folks are interested in a Java-ecosystem-friendly way to distribute the raw test data (e.g. similar in scope to #109) I think that would be reasonable (but would also require someone versed in those environments to contribute the work). Likely best to file that request as a new issue, or pull request.