[BCEL] Clirr report setting

[sebb <se...@gmail.com>]

I think we are all agreed that it's not a problem that the classes no
longer implement Serializable.

I did a Clirr run with just the Serializable errors suppressed, and it
now looks quite reasonable[1].

I think it would make sense to release that as the Clirr report, and
make sure that the changes/release-notes cover all the remaining error
reports. i.e. I think we should not suppress the other errors.

[1] http://home.apache.org/~sebb/BCEL/clirr-report.html

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org

Re: [BCEL] Clirr report setting

[Gary Gregory <ga...@gmail.com>]

On Thu, Jun 23, 2016 at 8:25 AM, sebb <se...@gmail.com> wrote:

> I think we are all agreed that it's not a problem that the classes no
> longer implement Serializable.
>
> I did a Clirr run with just the Serializable errors suppressed, and it
> now looks quite reasonable[1].
>
> I think it would make sense to release that as the Clirr report, and
> make sure that the changes/release-notes cover all the remaining error
> reports. i.e. I think we should not suppress the other errors.
>

+1 to the report and to full disclosure.

Gary


>
> [1] http://home.apache.org/~sebb/BCEL/clirr-report.html
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>


-- 
E-Mail: garydgregory@gmail.com | ggregory@apache.org
Java Persistence with Hibernate, Second Edition
<http://www.manning.com/bauer3/>
JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
Spring Batch in Action <http://www.manning.com/templier/>
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory