a. Where do I
> find the code coverage report?
>
>
>
> Thanks,
>
> Mark
>
>
>
> *From:* Gary Gregory [mailto:garydgreg...@gmail.com]
> *Sent:* Friday, September 06, 2019 5:01 PM
> *To:* Mark Roberts; Commons Developers List
> *Subject:* Re: [BCEL] Release
[mailto:garydgreg...@gmail.com]
Sent: Friday, September 06, 2019 5:01 PM
To: Mark Roberts; Commons Developers List
Subject: Re: [BCEL] Release 6.4.0
Run:
mvn clean site -P jacoco
Then look at the generate site's JaCoCo report and make sure the new code has
as close to possible t
ge mean?
>
> mark
>
> -Original Message-----
> From: Gary Gregory [mailto:garydgreg...@gmail.com]
> Sent: Friday, September 6, 2019 3:09 PM
> To: Commons Developers List
> Subject: Re: [BCEL] Release 6.4.0
>
> I might have some time over the weekend. Would you
]
Sent: Friday, September 06, 2019 5:01 PM
To: Mark Roberts; Commons Developers List
Subject: Re: [BCEL] Release 6.4.0
Run:
mvn clean site -P jacoco
Then look at the generate site's JaCoCo report and make sure the new code has
as close to possible to 100% code coverage by the unit
Mark Roberts wrote:
> Sorry - not familiar with the release process. What does check for code
> coverage mean?
>
> mark
>
> -Original Message-
> From: Gary Gregory [mailto:garydgreg...@gmail.com]
> Sent: Friday, September 6, 2019 3:09 PM
> To: Commons Developers Lis
I might have some time over the weekend. Would you mind double checking you
recent work for code coverage.
Gary
On Fri, Sep 6, 2019, 09:07 Mark Roberts wrote:
> I'm good. From our standpoint it would be nice to make a BCEL release so
> we don't need to include a special version with our tool s
I'm good. From our standpoint it would be nice to make a BCEL release so we
don't need to include a special version with our tool set.
Thanks,
Mark
-Original Message-
From: Gary Gregory [mailto:garydgreg...@gmail.com]
Sent: Sunday, September 1, 2019 3:25 PM
To: Commons Developers List
Thanks Bruno!
Gary
On Wed, Mar 20, 2019 at 10:01 PM Bruno P. Kinoshita
wrote:
> +1 Gary. Will make sure to review and vote on the RC as soon as I see it
> coming. Or if I don't vote within the 72hours, feel free to remind me and I
> will quickly do so.
> Cheers
>
> On Thursday, 21 March 20
+1 Gary. Will make sure to review and vote on the RC as soon as I see it
coming. Or if I don't vote within the 72hours, feel free to remind me and I
will quickly do so.
Cheers
On Thursday, 21 March 2019, 10:33:47 am NZDT, Gary Gregory
wrote:
Hi All:
I need the fix for BCEL-315 ASAP.
I think sebb already took care of these two issues.
> -Original Message-
> From: Benedikt Ritter [mailto:benerit...@gmail.com]
> Sent: Friday, June 17, 2016 9:50 AM
> To: Commons Developers List
> Subject: Re: [BCEL] Release Candidate on Thursday
>
> Hello Ma
rds, and again thank you for your help and your patience.
Benedikt
>
> > -Original Message-
> > From: Andrey Loskutov [mailto:losku...@gmx.de]
> > Sent: Tuesday, June 14, 2016 9:27 AM
> > To: Commons Developers List; Mark Roberts; 'Commons Developers List&#x
skutov [mailto:losku...@gmx.de]
> Sent: Tuesday, June 14, 2016 9:27 AM
> To: Commons Developers List; Mark Roberts; 'Commons Developers List'
> Subject: RE: [BCEL] Release Candidate on Thursday
>
> 1) You mentioned "private Daikon" build. Can you propose a patch?
> 2
ing.com]
>> Sent: Tuesday, June 14, 2016 8:51 AM
>> To: Commons Developers List
>> Subject: Re: [BCEL] Release Candidate on Thursday
>>
>> Are they show stoppers?
>>
>> On Tue, Jun 14, 2016 at 11:50 AM Mark Roberts
>>
>> wrote:
>>
>
s a show stopper for Daikon. It will continue to be shipped with our
> private version of BCEL if it is not fixed.
>
> > -Original Message-
> > From: James Carman [mailto:ja...@carmanconsulting.com]
> > Sent: Tuesday, June 14, 2016 8:51 AM
> > To: Commons Devel
243 is a show stopper for Daikon. It will continue to be shipped with our
private version of BCEL if it is not fixed.
> -Original Message-
> From: James Carman [mailto:ja...@carmanconsulting.com]
> Sent: Tuesday, June 14, 2016 8:51 AM
> To: Commons Developers List
> Sub
Hello Mark,
thank you for pointing this out. Saves me a lot of time :-)
I will have a look when Jira is reachable again.
Benedikt
Mark Roberts schrieb am Di., 14. Juni 2016 um
17:50:
> I can tell you right now I would vote -1 as you have not picked up the fix
> for https://issues.apache.org/ji
Are they show stoppers?
On Tue, Jun 14, 2016 at 11:50 AM Mark Roberts
wrote:
> I can tell you right now I would vote -1 as you have not picked up the fix
> for https://issues.apache.org/jira/browse/BCEL-243.
>
> Also, I think https://issues.apache.org/jira/browse/BCEL-195 is fixed,
> but has not
I can tell you right now I would vote -1 as you have not picked up the fix for
https://issues.apache.org/jira/browse/BCEL-243.
Also, I think https://issues.apache.org/jira/browse/BCEL-195 is fixed, but has
not been closed.
Thank you,
Mark Roberts
> -Original Message-
> From: Benedikt
On 2 June 2016 at 00:50, Olivier Lamy wrote:
> My problem is the maven coordinate changed
That was done as part of BCEL-222.
This will have to be reverted in order to release a compatible version of BCEL.
I did not get around to doing that when I reworked the code.
> I use bcel in a maven pl
My problem is the maven coordinate changed
I use bcel in a maven plugin.
So ideally I would have been happy to simply override in the dependencies
section of the plugin with the new bcel version.
But due this non compatible change on the maven coordinate I cannot do
that
On 1 June 2016 a
Hi Olivier,
Can you validate what is in trunk? That would help. It seems like there are
clean ups and unfinished business since this is a major release.
(See the deprecated org.apache.commons.bcel6.generic.InstructionConstants
email thread I just started)
Can you go through JIRA and help out wha
21 matches
Mail list logo
