I have not forgotten about the todo list. Have been swamped at work and hope
to get some of it done over the holidays.
-Original Message-
From: Bernd Eckenfels [mailto:e...@zusammenkunft.net]
Sent: Friday, December 19, 2014 5:48 PM
To: dev@commons.apache.org
Subject: [vfs] next release
Hello,
sorry for coming back to this topic, but I did not really received any
oppinions or help on it, and I really want to do a release.
I would like to release the VFS trunk as 2.1, because it contains a lot
of bug fixes and is asked for by people. If we decide to release it as
3.0 (with the ch
I think you have it summed up, we need to wrap things up and tie up loose
ends.
I've done other releases for Commons so I could do this one as well.
Gary
On Wed, Apr 23, 2014 at 3:58 PM, Bernd Eckenfels wrote:
> Hello,
>
> I can do some preparation work like reviewing the open issue, verifying
Hello,
I can do some preparation work like reviewing the open issue, verifying
the completeness of the changelog, maybe writing some release/upgrade
notes and checking the dependency versions.
I dont feel fit in doing the actual release, maybe you can assist me
with that gary. What else would you
On 17 July 2012 19:03, Gary Gregory wrote:
> On Tue, Jul 17, 2012 at 11:08 AM, sebb wrote:
>
>> On 17 July 2012 15:15, Gary Gregory wrote:
>> > On Tue, Jul 17, 2012 at 5:47 AM, sebb wrote:
>> >
>> >> On 16 July 2012 22:58, sebb wrote:
>> >> > On 16 July 2012 21:31, Gary Gregory wrote:
>> >> >
On Tue, Jul 17, 2012 at 11:08 AM, sebb wrote:
> On 17 July 2012 15:15, Gary Gregory wrote:
> > On Tue, Jul 17, 2012 at 5:47 AM, sebb wrote:
> >
> >> On 16 July 2012 22:58, sebb wrote:
> >> > On 16 July 2012 21:31, Gary Gregory wrote:
> >> >> Hi All:
> >> >>
> >> >> With the addition of many n
On 17 July 2012 15:15, Gary Gregory wrote:
> On Tue, Jul 17, 2012 at 5:47 AM, sebb wrote:
>
>> On 16 July 2012 22:58, sebb wrote:
>> > On 16 July 2012 21:31, Gary Gregory wrote:
>> >> Hi All:
>> >>
>> >> With the addition of many new methods to the FileObject interface and
>> other
>> >> TAR ch
On Tue, Jul 17, 2012 at 5:47 AM, sebb wrote:
> On 16 July 2012 22:58, sebb wrote:
> > On 16 July 2012 21:31, Gary Gregory wrote:
> >> Hi All:
> >>
> >> With the addition of many new methods to the FileObject interface and
> other
> >> TAR changes reported by Clirr [1], the next release will bre
On 16 July 2012 22:58, sebb wrote:
> On 16 July 2012 21:31, Gary Gregory wrote:
>> Hi All:
>>
>> With the addition of many new methods to the FileObject interface and other
>> TAR changes reported by Clirr [1], the next release will break BC for VFS
>> providers (those not provided by VFS itself.
On 16 July 2012 21:31, Gary Gregory wrote:
> Hi All:
>
> With the addition of many new methods to the FileObject interface and other
> TAR changes reported by Clirr [1], the next release will break BC for VFS
> providers (those not provided by VFS itself.)
>
> For normal call sites of the interfac
I think you guys missed what the suggestion was. If it is possible we could
just add a subproject to vfs2 that provides the needed glue between the
existing providers and the Java 7 api. I would imagine this subproject would
only be included when compiling with a java 7 compiler, otherwise it
On Dec 8, 2011, at 9:46, sebb wrote:
> On 8 December 2011 13:35, Jörg Schaible wrote:
>> sebb wrote:
>>
>>> On 8 December 2011 11:01, Jörg Schaible
>>> wrote:
sebb wrote:
> On 8 December 2011 07:11, Jörg Schaible
> wrote:
>> Hi,
>>
>> Gary Gregory wrote:
>>
>>
On 8 December 2011 13:35, Jörg Schaible wrote:
> sebb wrote:
>
>> On 8 December 2011 11:01, Jörg Schaible
>> wrote:
>>> sebb wrote:
>>>
On 8 December 2011 07:11, Jörg Schaible
wrote:
> Hi,
>
> Gary Gregory wrote:
>
>> I am thinking of a different package name, not j
sebb wrote:
> On 8 December 2011 11:01, Jörg Schaible
> wrote:
>> sebb wrote:
>>
>>> On 8 December 2011 07:11, Jörg Schaible
>>> wrote:
Hi,
Gary Gregory wrote:
> I am thinking of a different package name, not just version for VFS on
> Java 7 because we might want to r
On 8 December 2011 11:01, Jörg Schaible wrote:
> sebb wrote:
>
>> On 8 December 2011 07:11, Jörg Schaible
>> wrote:
>>> Hi,
>>>
>>> Gary Gregory wrote:
>>>
I am thinking of a different package name, not just version for VFS on
Java 7 because we might want to release more VFS2-based vers
On Dec 8, 2011, at 6:01, "Jörg Schaible" wrote:
> sebb wrote:
>
>> On 8 December 2011 07:11, Jörg Schaible
>> wrote:
>>> Hi,
>>>
>>> Gary Gregory wrote:
>>>
I am thinking of a different package name, not just version for VFS on
Java 7 because we might want to release more VFS2-based ve
sebb wrote:
> On 8 December 2011 07:11, Jörg Schaible
> wrote:
>> Hi,
>>
>> Gary Gregory wrote:
>>
>>> I am thinking of a different package name, not just version for VFS on
>>> Java 7 because we might want to release more VFS2-based versions that do
>>> break binary compatibility.
>>>
>>> We can
On 8 December 2011 07:11, Jörg Schaible wrote:
> Hi,
>
> Gary Gregory wrote:
>
>> I am thinking of a different package name, not just version for VFS on
>> Java 7 because we might want to release more VFS2-based versions that do
>> break binary compatibility.
>>
>> We can retain the VFS name and b
Hi,
Gary Gregory wrote:
> I am thinking of a different package name, not just version for VFS on
> Java 7 because we might want to release more VFS2-based versions that do
> break binary compatibility.
>
> We can retain the VFS name and brand for the project, but I'd prefer
> o.a.c.vfs to be for
That might be a reasonable approach, but it will depend on what changes might
need to be made to the providers.
Ralph
On Dec 7, 2011, at 4:11 PM, James Carman wrote:
> How about creating a new package that has adapters for java7?
>
> o.a.c.vfs3.nio
> On Dec 7, 2011 6:32 PM, "sebb" wrote:
>
>
How about creating a new package that has adapters for java7?
o.a.c.vfs3.nio
On Dec 7, 2011 6:32 PM, "sebb" wrote:
> On 7 December 2011 21:07, Ralph Goers
> top-posted:
> > I'm much less concerned with the package name than I am that it appear
> to be part of the VFS subproject. By necessity,
On 7 December 2011 21:07, Ralph Goers top-posted:
> I'm much less concerned with the package name than I am that it appear to be
> part of the VFS subproject. By necessity, it won't be binary compatible -
> and presumably users won't interact with the commons vfs code directly anyway.
Package
I'm much less concerned with the package name than I am that it appear to be
part of the VFS subproject. By necessity, it won't be binary compatible - and
presumably users won't interact with the commons vfs code directly anyway.
Ralph
On Dec 7, 2011, at 10:01 AM, Gary Gregory wrote:
> I am t
I am thinking of a different package name, not just version for VFS on Java
7 because we might want to release more VFS2-based versions that do break
binary compatibility.
We can retain the VFS name and brand for the project, but I'd prefer
o.a.c.vfs to be for VFS2 based work and to create o.a.c.f
On 5 December 2011 22:45, Jörg Schaible wrote:
> Hi Gary,
>
> Gary Gregory wrote:
>
>> Hi All:
>>
>> I've made several improvements to VFS over the last couple of months which
>> feels ready for a release soon.
>>
>> One important internal change is that the builds runs almost all unit
>> tests
>>
With all the changes you've made a release of VFS is warranted.
I'm not sure why a renae would be required instead of just calling it VFS3. To
be honest, I've never much liked the VFS API, expecially the
ConfigurationBuilder stuff. Losing the API in favor of the Java API seems like
a good way t
On Mon, Dec 5, 2011 at 5:45 PM, Jörg Schaible wrote:
> Hi Gary,
>
> Gary Gregory wrote:
>
> > Hi All:
> >
> > I've made several improvements to VFS over the last couple of months
> which
> > feels ready for a release soon.
> >
> > One important internal change is that the builds runs almost all u
Hi Gary,
Gary Gregory wrote:
> Hi All:
>
> I've made several improvements to VFS over the last couple of months which
> feels ready for a release soon.
>
> One important internal change is that the builds runs almost all unit
> tests
> :)
I saw your efforts and this is really a great improvem
> -Original Message-
> From: Ralph Goers [mailto:ralph.go...@dslextreme.com]
> Sent: Saturday, April 04, 2009 10:08 PM
> To: Commons Developers List
> Subject: Re: [vfs] next release?
>
> The next release of VFS will be 2.0. I've been working on cleaning the
&
The next release of VFS will be 2.0. I've been working on cleaning the
code in preparation for a release. Have you tried checking out trunk
and using it? Your feedback would be most welcome. Are you saying
that there are no Jira issues with regard to the problem you are
having? If there
Hello:
I am using VFS in another corner of our server and had to workaround file URLs
not working with relative paths from the current directory
(file:path/to/file.ext.) Looking at JIRA, I do not see this being addressed,
which is fine for now but got me to wonder when the next release might co
31 matches
Mail list logo
