commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary Gregory <>
Subject Re: [VFS] release preparation: clirr report
Date Fri, 02 May 2014 13:42:13 GMT
I'm not sure how fine grained control we have or want to get over Clirr.

For now, I'd rather know about all the differences. We can document how to
interpret the Clirr report on the site and release notes as well.


On Thu, May 1, 2014 at 3:23 PM, Bernd Eckenfels <>wrote:

> Hello,
> in preparation of the VFS2.1 release I was reviewing the Clirr report.
> It has quite a number of errors, especially in regard to new Interface
> methods.
> # Method 'public long write(org.apache.commons.vfs2.FileContent)' has
> been added to an interface
> # Method 'public boolean isFile()' has been added to an interface
> # Method 'public int deleteAll()' has been added to an interface
> I think those are all compatible in normal usage since implementors
> would expand a abstract base class.
> Is there a way to cover that in Clirr? Would we keep the "errors" in
> the release and describe it in the release notes?
> There are also some changes to providers. They look less clear but most
> of them are protected methods. Why does that show up in the clirr
> report at all?
> I have a sample site here (not sure if it is correctly released but it
> is enough to look at the Clirr)
> Gruss
> Bernd
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

E-Mail: |
Java Persistence with Hibernate, Second Edition<>
JUnit in Action, Second Edition <>
Spring Batch in Action <>

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message