On Mon, Feb 9, 2015 at 1:36 PM, James Ring wrote:
> I'm working to bring re2j into the open, it will take some time
> because Google's internal procedures for this kind of thing are pretty
> lengthy. I'm hopeful it could be done in the next month or so.
That is lovely news. Thanks!
>
> On Tue, F
I'm working to bring re2j into the open, it will take some time
because Google's internal procedures for this kind of thing are pretty
lengthy. I'm hopeful it could be done in the next month or so.
On Tue, Feb 3, 2015 at 12:14 PM, Benson Margulies wrote:
> On Tue, Feb 3, 2015 at 2:39 AM, Thomas N
Great, thanks for the update!
Btw, for those not familiar with which issues those are, here's a list of
the ones Mark raised that are not yet resolved:
https://issues.apache.org/jira/browse/BCEL-79
https://issues.apache.org/jira/browse/BCEL-195
https://issues.apache.org/jira/browse/BCEL-196
https:
Le 09/02/2015 11:56, sebb a écrit :
> However we distribute the pom, which may download the JMH code.
Our pom already triggers the download of LGPL and GPL softwares like
jdiff, clirr, checkstyle and cobertura.
> I think the JMH pom also needs to be excluded.
> Both because of the licensing iss
On 9 February 2015 at 08:14, Emmanuel Bourg wrote:
> Le 09/02/2015 02:40, sebb a écrit :
>
>> -1
>>
>> This has broken the Continuum build.
>
> I'm going to fix this.
>
>
>> Also the JMH website says:
>>
>> "The recommended way to run a JMH benchmark is to use Maven to setup a
>> standalone projec
Le 09/02/2015 02:40, sebb a écrit :
> -1
>
> This has broken the Continuum build.
I'm going to fix this.
> Also the JMH website says:
>
> "The recommended way to run a JMH benchmark is to use Maven to setup a
> standalone project that depends on the jar files of your application.
> This appro
