equwal
commented
1 year ago I made a pull addressing it with documentation. Perhaps it is possibly to package the a jar that shows up in the root directory, which would have the dependencies internal to it. Then, that could be published so all users don't have to build the source.
Finally, It's kind of confusing that the maven build puts the briss2 jar in the
target/but not the dependencies, which are put in a zip. This means that if the user tries to just use that jar as-is it won't work (there's an old issue on that from a user wanting support which has been closed. However, I think it should be fixed in the source).