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
s; 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 un
]
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 versi
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 Devel
Hi All and Mark in particular,
Is there anything more we need for 6.4.0?
Gary
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.
Hi All:
I need the fix for BCEL-315 ASAP. I plan on creating on RC later today I
hope.
Based on changes.xml I think the next version should be 6.3.1 instead of
6.4.
Gary
Hi All,
A project (spotbugs) is currently depending on a 6.1 SNAPSHOT jar to pick
up a fix.
See https://github.com/spotbugs/spotbugs/pull/69
Does anyone want to volunteer to review BCEL for a 6.1 release?
Gary
--
E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
Java Persistence with Hiber
Great - thanks for all the suggestions. I will investigate on Monday.
Mark
> -Original Message-
> From: Gary Gregory [mailto:garydgreg...@gmail.com]
> Sent: Friday, July 08, 2016 4:18 PM
> To: Commons Developers List
> Subject: Re: How tell which BCEL release?
>
on.
>
>
>
> On 8 July 2016 at 23:49, dbrosIus wrote:
> > Typicaly one puts the version in the manifest
> >
> > Original message
> > From: Mark Roberts
> > Date: 7/8/16 6:43 PM (GMT-05:00)
> > To: 'Commons Developers List&#
Original message
> From: Mark Roberts
> Date: 7/8/16 6:43 PM (GMT-05:00)
> To: 'Commons Developers List'
> Subject: How tell which BCEL release?
>
> Now that BCEL 6.0 looks close, I'm wondering how a client can tell -
> programmatically - which vers
GMT-05:00)
> To: 'Commons Developers List'
> Subject: How tell which BCEL release?
>
> Now that BCEL 6.0 looks close, I'm wondering how a client can tell -
> programmatically - which version of BCEL he is running against in order to
> verify it is correct. Curren
Typicaly one puts the version in the manifest
Original message
From: Mark Roberts
Date: 7/8/16 6:43 PM (GMT-05:00)
To: 'Commons Developers List'
Subject: How tell which BCEL release?
Now that BCEL 6.0 looks close, I'm wondering how a client can tell -
p
Now that BCEL 6.0 looks close, I'm wondering how a client can tell -
programmatically - which version of BCEL he is running against in order to
verify it is correct. Currently, we at PLSE add an extra, dummy class to the
release in order to do this. Our goal is to stop shipping our own versi
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:
>>
>
Roberts
> > >
> > > > -Original Message-
> > > > From: Benedikt Ritter [mailto:brit...@apache.org]
> > > > Sent: Monday, June 13, 2016 11:49 PM
> > > > To: Commons Developers List
> > > > Subject: [BCEL] Release Candidate on Th
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
: Monday, June 13, 2016 11:49 PM
> > To: Commons Developers List
> > Subject: [BCEL] Release Candidate on Thursday
> >
> > Hi,
> >
> > I'm going to try to create an RC for BCEL 6.0 on friday. Please have a
> look at
> >
d,
> but has not been closed.
>
>
> Thank you,
> Mark Roberts
>
> > -Original Message-
> > From: Benedikt Ritter [mailto:brit...@apache.org]
> > Sent: Monday, June 13, 2016 11:49 PM
> > To: Commons Developers List
> > Subject: [BCEL] Release C
nedikt Ritter [mailto:brit...@apache.org]
> Sent: Monday, June 13, 2016 11:49 PM
> To: Commons Developers List
> Subject: [BCEL] Release Candidate on Thursday
>
> Hi,
>
> I'm going to try to create an RC for BCEL 6.0 on friday. Please have a look at
> the current st
Hi,
I'm going to try to create an RC for BCEL 6.0 on friday. Please have a look
at the current state of the code base and report any issues you see.
Thank you!
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
Hi,
Last release is from 2006.
Fixes for java 8 are here for a while.
Any ETA on releasing BCEL one day?
Regards
--
Olivier Lamy
http://twitter.com/olamy | http://linkedin.com/in/olamy
32 matches
Mail list logo
