tidy-up and rework release notes automation about mockito HOT 4 CLOSED

Btw, why do you plan to convert that code to Java? AFAIR there is a lot operations on collections which are much simpler in Groovy. A plugin written for Gradle 2.x can use @CompileStatic which makes it more resistant to various errors.

from mockito.

Main reason is that I want to open source it as a java library :)

from mockito.

I was just curious what is your motivation to make a port. Your argument is very strong :).

The library will be useful. Maybe also for Scala people :).

from mockito.

btw. Sorry I asked you to contribute work to this part of the build. It was in bad state, hard to test, hard to work with. I was surprised you made any progress in it. I've just pushed major clean up. It's almost ready to be open sourced separately. The only thing missing is ditching dependency on Gradle, which basically means implement new ProcessRunner interface without gradle.

In general I plan to create separate read-only outh token for querying tickets and I will simply commit that to the codebase. This way, anyone can build notes locally and test this stuff.

from mockito.