commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bernd Eckenfels <>
Subject [VFS] release preparation: clirr report
Date Thu, 01 May 2014 19:23:47 GMT

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

# 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)


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message