Hi Bernd.
I can confirm that issue was gone after VFS-426 fix.
Thank you.
WBR, Alex.
On 19.08.2015 11:29, Bernd Eckenfels wrote:
Hello Alexander,
there is no ETA but there is work towards a release (latest update
yesterday), see here: https://wiki.apache.org/commons/VfsReleaseState
I havent noticed the patch before, so it is good that you mention it.
I guess it can be merged, it needs some polishing in regards to code
style (and the super.equals/getClass is rather inconventional, but I
guess works correctly). It misses a unit test, I think the attached
sample project could be turned into one.
It is currently not considered a blocker for the next release, but if
we get the patch cleaned up it can be merged before that,
The project is in some form of "hyperactive" state, since it was not
released in a long time but had a lot of changes it currently makes
lots of work to get it released.
Gruss
Bernd
Am Wed, 19 Aug 2015 07:57:07 +0000
schrieb Alexander Buloichik <alexander_buloic...@epam.com>:
Hi All.
When new release of commons-vfs planned ?
There is critical bug https://issues.apache.org/jira/browse/VFS-503?,
with patch, but patch is not integrated into svn about 2 years, and
commons-vfs was not released 4 years.
Is it dead project ?
WBR, Alex.
--
*Alexander Buloichik*
*Lead Software Engineer*
*Office: *+375 17 389 0100 <tel:+375%2017%20389%200100> *x* 50617
<tel:50617>*Cell: *+375 29 33 22 44 1
<tel:+375%2029%2033%2022%2044%201>*Email: *alexander_buloic...@epam.com
<mailto:alexander_buloic...@epam.com>
*Miensk**,* *Belarus *(GMT+3)*epam.com <http://www.epam.com>*
CONFIDENTIALITY CAUTION AND DISCLAIMER
This message is intended only for the use of the individual(s) or
entity(ies) to which it is addressed and contains information that is
legally privileged and confidential. If you are not the intended
recipient, or the person responsible for delivering the message to the
intended recipient, you are hereby notified that any dissemination,
distribution or copying of this communication is strictly prohibited.
All unintended recipients are obliged to delete this message and destroy
any printed copies.
