Re: [BCEL] Release 6.4.0

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

RE: [BCEL] Release 6.4.0

[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 to 100

Re: [BCEL] Release 6.4.0

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 unit te

RE: [BCEL] Release 6.4.0

] 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 tests

Re: [BCEL] Release 6.4.0

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 List &g

Re: [BCEL] Release 6.4.0

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 ou

RE: [BCEL] Release 6.4.0

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

[BCEL] Release 6.4.0

Hi All and Mark in particular, Is there anything more we need for 6.4.0? Gary

Re: [BCEL] Release

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

Re: [BCEL] Release

+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

[BCEL] Release

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

[BCEL] Release?

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

RE: How tell which BCEL release?

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? >

Re: How tell which BCEL release?

t; > Date: 7/8/16 6:43 PM (GMT-05:00) > > To: 'Commons Developers List' <dev@commons.apache.org> > > Subject: How tell which BCEL release? > > > > Now that BCEL 6.0 looks close, I'm wondering how a client can tell - > programmatically - which version o

Re: How tell which BCEL release?

e version in the manifest > > Original message > From: Mark Roberts <mar...@cs.washington.edu> > Date: 7/8/16 6:43 PM (GMT-05:00) > To: 'Commons Developers List' <dev@commons.apache.org> > Subject: How tell which BCEL release? > > Now that BCEL 6.0 loo

RE: How tell which BCEL release?

ts <mar...@cs.washington.edu> > Date: 7/8/16 6:43 PM (GMT-05:00) > To: 'Commons Developers List' <dev@commons.apache.org> > Subject: How tell which BCEL release? > > Now that BCEL 6.0 looks close, I'm wondering how a client can tell - > programmatically - which

RE: How tell which BCEL release?

Typicaly one puts the version in the manifest Original message From: Mark Roberts <mar...@cs.washington.edu> Date: 7/8/16 6:43 PM (GMT-05:00) To: 'Commons Developers List' <dev@commons.apache.org> Subject: How tell which BCEL release? Now that BCEL 6.0 look

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. 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

RE: [BCEL] Release Candidate on Thursday

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 Mark, &

Re: [BCEL] Release Candidate on Thursday

edu>: > > >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: Tuesd

RE: [BCEL] Release Candidate on Thursday

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) The bcel

RE: [BCEL] Release Candidate on Thursday

an [mailto:ja...@carmanconsulting.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 >> &

Re: [BCEL] Release Candidate on Thursday

: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 > > <mar...@cs.washington.edu> > > wrote: > > >

RE: [BCEL] Release Candidate on Thursday

rom: Benedikt 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 tr

Re: [BCEL] Release Candidate on Thursday

t...@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 > >

Re: [BCEL] Release Candidate on Thursday

g/jira/browse/BCEL-195 is fixed, > 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

RE: [BCEL] Release Candidate on Thursday

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 state o

[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 state of the code base and report any issues you see. Thank you! Benedikt

Re: BCEL release?

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

Re: BCEL release?

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

Re: BCEL release?

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

BCEL release?

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