Re: Re: Re: [BCEL] Latest Clirr report

2016-06-13 Thread Andrey Loskutov
> From: "Benedikt Ritter" > To: "Commons Developers List" > Subject: Re: Re: [BCEL] Latest Clirr report > > So from my limited FindBugs point of view we can release BCEL6 as it is > > today on trunk. > > > > Okay, so you would like to see an

Re: Re: [BCEL] Latest Clirr report

2016-06-13 Thread Jochen Wiedmann
On Tue, Jun 14, 2016 at 8:24 AM, Benedikt Ritter wrote: > Andrey Loskutov schrieb am Mo., 13. Juni 2016 um > 14:15 Uhr: > Okay, so you would like to see an RC with the current state of trunk?! +1 Jochen -- The next time you hear: "Don't reinvent the wheel!" http://www.keystonedevelopment.

Re: Re: [BCEL] Latest Clirr report

2016-06-13 Thread Benedikt Ritter
BCEL API state we "exported" to downstream since 3 years :-( > > Kind regards, > Andrey Loskutov > > http://google.com/+AndreyLoskutov > > > > Gesendet: Sonntag, 12. Juni 2016 um 14:12 Uhr > > Von: sebb > > An: "Commons Developers List" &

Re: [BCEL] Latest Clirr report

2016-06-13 Thread Jochen Wiedmann
On Mon, Jun 13, 2016 at 12:03 AM, sebb wrote: >> I'd suggest to leave the java.io.Serializable stuff, as it is. In >> practice, this will only be noticed, if anyone is actually >> serializing/deserializing these items, and I assume that the interface >> has been removed for a reason. (Meaning: Al

Re: Re: [BCEL] Latest Clirr report

2016-06-13 Thread Andrey Loskutov
is the BCEL API state we "exported" to downstream since 3 years :-( Kind regards, Andrey Loskutov http://google.com/+AndreyLoskutov > Gesendet: Sonntag, 12. Juni 2016 um 14:12 Uhr > Von: sebb > An: "Commons Developers List" > Betreff: Re: [BCEL] Latest Clirr re

Re: [BCEL] Latest Clirr report

2016-06-12 Thread sebb
On 12 June 2016 at 15:21, Jochen Wiedmann wrote: > On Sun, Jun 12, 2016 at 1:00 PM, Benedikt Ritter wrote: > >> I've uploaded the verbose Clirr report to my space at home.apache.org [1]. >> Do we have to fix all of this in order to release 6.0? > > > I'd suggest to leave the java.io.Serializable

Re: [BCEL] Latest Clirr report

2016-06-12 Thread Jochen Wiedmann
On Sun, Jun 12, 2016 at 1:00 PM, Benedikt Ritter wrote: > I've uploaded the verbose Clirr report to my space at home.apache.org [1]. > Do we have to fix all of this in order to release 6.0? I'd suggest to leave the java.io.Serializable stuff, as it is. In practice, this will only be noticed, if

Re: [BCEL] Latest Clirr report

2016-06-12 Thread sebb
On 12 June 2016 at 12:43, Benedikt Ritter wrote: > sebb schrieb am So., 12. Juni 2016 um 13:38 Uhr: > >> On 12 June 2016 at 12:00, Benedikt Ritter wrote: >> > Hi, >> > >> > I've uploaded the verbose Clirr report to my space at home.apache.org >> [1]. >> > Do we have to fix all of this in order t

Re: [BCEL] Latest Clirr report

2016-06-12 Thread Benedikt Ritter
sebb schrieb am So., 12. Juni 2016 um 13:38 Uhr: > On 12 June 2016 at 12:00, Benedikt Ritter wrote: > > Hi, > > > > I've uploaded the verbose Clirr report to my space at home.apache.org > [1]. > > Do we have to fix all of this in order to release 6.0? > > No, most of the changes don't break stri

Re: [BCEL] Latest Clirr report

2016-06-12 Thread sebb
On 12 June 2016 at 12:00, Benedikt Ritter wrote: > Hi, > > I've uploaded the verbose Clirr report to my space at home.apache.org [1]. > Do we have to fix all of this in order to release 6.0? No, most of the changes don't break strict BC. The main changes to the interfaces don't break BC and are

Re: [BCEL] Latest Clirr report

2016-06-12 Thread Benedikt Ritter
Hi, I've uploaded the verbose Clirr report to my space at home.apache.org [1]. Do we have to fix all of this in order to release 6.0? Benedikt [1] http://home.apache.org/~britter/commons/bcel/6.0-SNAPSHOT/clirr-report.html sebb schrieb am Mi., 8. Juni 2016 um 11:54 Uhr: > On 8 June 2016 at 10

Re: [BCEL] Latest Clirr report

2016-06-08 Thread sebb
On 8 June 2016 at 10:46, Benedikt Ritter wrote: > Hello sebb, > > sebb schrieb am Mi., 8. Juni 2016 um 11:21 Uhr: > >> Was that the full report, or the 'quietened' one? >> There's a Clirr suppression file which removes some diffs that are >> considered non-breaking (as per the changes description

Re: [BCEL] Latest Clirr report

2016-06-08 Thread Benedikt Ritter
Hello sebb, sebb schrieb am Mi., 8. Juni 2016 um 11:21 Uhr: > Was that the full report, or the 'quietened' one? > There's a Clirr suppression file which removes some diffs that are > considered non-breaking (as per the changes description) > (otherwise the report is rather difficult to read) > >

Re: [BCEL] Latest Clirr report

2016-06-08 Thread sebb
Was that the full report, or the 'quietened' one? There's a Clirr suppression file which removes some diffs that are considered non-breaking (as per the changes description) (otherwise the report is rather difficult to read) To show all the errors, use -P!quieten-clirr or -Dclirr.allDifferences O

[BCEL] Latest Clirr report

2016-06-08 Thread Benedikt Ritter
Hi all, I've published the BCEL website after reverting the package rename. Here [1] is the Clirr report of the current code base. Benedikt [1] http://commons.apache.org/proper/commons-bcel/clirr-report.html