On Mon, May 14, 2012 at 9:20 AM, Ralph Goers <rgo...@apache.org> wrote:

> Thanks. We to we're taken by surprise by this as it was not discussed
> prior to the change. A


This has been backed out of SVN for now.

(from the JIRA:)

Whys:
- Make VFS more attractive for new user/developers, new committers in the
21st century. No one can force anyone to upgrade to the next version.
- Keep VFS relevant. The older versions are still there for volunteers to
patch.
- Open the door for newer versions of jars that required Java 6, like
commons-io 2.3.

Gary


> s a rule the minimum version should only be changed if something requires
> it. I'm waiting for a response from Gary as to why this was necessary
> before asking him to revert it.
>
> Ralph
>
> On May 14, 2012, at 2:50 AM, Andreas Persson <
> andreas.pers...@idainfront.se> wrote:
>
> >> FYI: I've updated VFS trunk to Java 6 to avoid getting stuck on older
> >> versions of jars and further moving VFS in the 21st century ;) Tasked
> >> as VFS-415.
> >
> > I was happy to see VFS-414 and VFS-313 being fixed, thank you very much
> for that! The change in VFS-415 however makes it impossible for us to use
> VFS 2.1 (we have several jboss 4 installations left, and jboss 4 doesn't
> support jdk 6). I just wanted you to know that there still are VFS users
> that depend on jdk 1.5 compatibility.
> >
> > /Andreas
> >
> >
> Т���������������������������������������������������������������������ХF�
> V�7V'67&�&R� R�� �â FWb�V�7V'67&�&T 6�����2�   6�R��&pФf�"  FF�F��� � 6���
> �G2� R�� �â FWbֆV�  6�����2�   6�R��&p�
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>


-- 
E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
JUnit in Action, 2nd Ed: <http://goog_1249600977>http://bit.ly/ECvg0
Spring Batch in Action: <http://s.apache.org/HOq>http://bit.ly/bqpbCK
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

Reply via email to