-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi #3
Comments
Hi Borislav, Thanks for your email. I'm quite happy to merge in most of what you've Many thanks, "Those who say it cannot be done should not interrupt those doing it."
On Wed, Nov 25, 2015 at 8:19 PM, Borislav Ivanov [email protected]
|
Hi Ian, My comments are in #4 |
The resulting Test.jar from "make test" should be runnable with "java -jar build/test.jar", but currently this fails because of the wrong main class, and the jar mainfest's classpath not finding the junit jars. |
I will check it out . On Fri, 27 Nov 2015 21:05 Ian Preston [email protected] wrote:
|
Hello @ianopolous .
I'm writing you because I have forked your repo and wanted to let you know about it.
The main reason for forking was using Gradle as a build tool. It will make
artifact publishing to maven central ,cross platform testing and integration with http://openjdk.java.net/projects/code-tools/jmh/ an easy task.
The other reason for forking was to document the methods ( the most tedious one as well...) .
And the third, but not last reason was to apply a set of checkstyle rules and formatting to the code.
P.S I have made some micro benchmarks , and here are the results
P.P.S I guess that you will be reserved against me making a PR because of the code formatting and the replacement of three for loops with System.arrayCopy , but I just wanted to let you know about my work :)
P.P.P.S all tests are passing correctly.
Have a nice one.
Bobby.
The text was updated successfully, but these errors were encountered: