I feel your pain and am very frustrated by the lack of support from the Commons 
team. I have brought up the subject multiple times[1,2,3] and have even 
volunteered to do the release. FWIW, I am using the features of the new 
classloader in production with little issue (using the 2.1 snapshot code). A 
few months ago I discussed this with Christopher and the topic of forking did 
come up. Also note that Benson just went through the release process for 
Commons IO and it was not pain free. Apparently they are willing to work with 
some people and not others. 

[1] 
http://markmail.org/message/4iczynn2tqbtwdhd?q=VFS+2.1+release+list:org.apache.commons.dev/+from:%22dlmarion%40comcast.net%22&page=1
 
[2] 
http://markmail.org/search/?q=VFS%202.1%20release%20list%3Aorg.apache.commons.dev%2F#query:VFS%202.1%20release%20list%3Aorg.apache.commons.dev%2F%20from%3A%22dlmarion%40comcast.net%22+page:1+mid:zkjkgvpsrh4blvtj+state:results
 
[3] 
http://markmail.org/message/ojgizsfevkjjl6jv?q=VFS+2.1+release+list:org.apache.commons.dev/+from:%22dlmarion%40comcast.net%22&page=1
 

----- Original Message -----

From: "Mike Drob" <[email protected]> 
To: [email protected] 
Sent: Monday, April 25, 2016 11:37:25 AM 
Subject: Re: On the future of our commons-vfs2 dynamic classloading 
implementation 

Have we asked them about making a release? 

On Mon, Apr 25, 2016 at 10:35 AM, Josh Elser <[email protected]> wrote: 

> I was trying to test out Dylan's patch this weekend and was met with a 
> repeated failure of another VFS unit test due to the same race condition 
> we've been fighting against for years. 
> 
> A cursory glance to vfs' website show still shows that they haven't made 
> the 2.1 release which supposedly fixes this issue. In other words, they 
> have no made a release since 2011. 
> 
> I'm now under the assumption that we cannot rely on them to make a 
> release. As such, if the community wishes to continue to support this 
> feature, something needs to happen before 1.8.0 -- fork vfs, use/build some 
> other library for this functionality, or remove the dynamic-classloader 
> functionality from Accumulo completely. 
> 
> I've tried to be very patient waiting for this to happen, but I'm rather 
> frustrated having wasted significant time over the past years (not even 
> exaggerating which is even crazier) working around known broken code that 
> is unusable by users. 
> 
> Thoughts? 
> 
> - Josh 
> 

Reply via email to