[
https://issues.apache.org/jira/browse/PIRK-7?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15390699#comment-15390699
]
ASF GitHub Bot commented on PIRK-7:
-----------------------------------
Github user jacobwil commented on the issue:
https://github.com/apache/incubator-pirk/pull/15
We are going to continue to use JMH for now. My justification shared [on
the mailing
list](http://mail-archives.apache.org/mod_mbox/incubator-pirk-dev/201607.mbox/%3cCAD637oNk_P7he14RtAYpN6X=izh8rur5kswfa5emvjrpfgd...@mail.gmail.com%3e)
is:
> I'll put forward my vote that we stick with JMH and separate out any
benchmarks that depend on it if/when we distribute binary artifacts. JMH
seems to be better maintained (starting from the fact that it's possible to
use it without needing to modify what you get from the source repo) and it
seems to be easier to use.
> Replace JMH with Google Caliper
> -------------------------------
>
> Key: PIRK-7
> URL: https://issues.apache.org/jira/browse/PIRK-7
> Project: PIRK
> Issue Type: Improvement
> Reporter: Suneel Marthi
> Assignee: Suneel Marthi
>
> Pirk is now using JMH for Paillier benchmarking.
> I had seen other Apache projects move away from JMH as the license terms for
> JMH are not compatible with Apache -
> http://openjdk.java.net/legal/gplv2+ce.html
> See https://issues.apache.org/jira/browse/FLINK-2973
> Proposing that we replace JMH with Google Caliper
> -https://github.com/google/caliper
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
