I don’t need to run jacoco to know the coverage is almost zero for the classes added to support the new Java 9+ attributes. I could cobble something up if there was some way to add a Java 11 .class file to use as input to a test.
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 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. The profile might not be required but it will make sure the right thing happens. Gary On Fri, Sep 6, 2019, 19:58 Mark Roberts <mar...@cs.washington.edu> 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 <dev@commons.apache.org> Subject: 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 <mar...@cs.washington.edu> 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 set. > > Thanks, > Mark > > -----Original Message----- > From: Gary Gregory [mailto:garydgreg...@gmail.com] > Sent: Sunday, September 1, 2019 3:25 PM > To: Commons Developers List <dev@commons.apache.org> > Subject: [BCEL] Release 6.4.0 > > Hi All and Mark in particular, > > Is there anything more we need for 6.4.0? > > Gary > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > >
