Re: [VFS] Breaking BC in provider

Can you start over? :) On January 17, 2019 at 13:33:49, Gary Gregory (garydgreg...@gmail.com) wrote: With SVN trunk, Clirr currently reports:

[VFS] Breaking BC in provider

With SVN trunk, Clirr currently reports:

Re: [VFS] Breaking BC in provider

r.ftp.FtpClient: Method > 'public int getReplyCode()' has been added to an interface > > Do we have a policy to keep BC on providers as opposed to the higher level > VFS API? > > Gary > > On Thu, Jan 17, 2019 at 1:26 PM Gary Gregory > wrote: > >> With SVN trunk, Clirr currently reports: >> >>

Re: [VFS] Breaking BC in provider

[Sent too soon, sorry] With SVN trunk, Clirr currently reports: [ERROR] 7012: org.apache.commons.vfs2.provider.ftp.FtpClient: Method 'public int getReplyCode()' has been added to an interface Do we have a policy to keep BC on providers as opposed to the higher level VFS API? Gary On Thu, Jan

Re: [vfs] new http4 provider, not replace http?

Thanks again, Gary! Just as heads-up, I've created two tickets: VFS-686 and VFS-687. The former is about upgrading Jackrabbit dependency on which the webdav FS provider depends, and the latter is about adding "http5(s)" FS provider as a new http library option. I will try to submit pul

Re: [VFS] Java 8

ber 3, 2018 at 10:55:08, Gary Gregory (garydgreg...@gmail.com) > > wrote: > > > > I propose we update the Java requirement for [vfs] from Java 7 to Java 8. > > > > Gary >

Re: [VFS] Java 8

I can’t see why not to do this. +1 to the idea > On Nov 4, 2018, at 7:08 AM, Otto Fowler wrote: > > +1 > > > On November 3, 2018 at 10:55:08, Gary Gregory (garydgreg...@gmail.com) > wrote: > > I propose we update the Java requirement for [vfs] from

Re: [VFS] Java 8

+1 On November 3, 2018 at 10:55:08, Gary Gregory (garydgreg...@gmail.com) wrote: I propose we update the Java requirement for [vfs] from Java 7 to Java 8. Gary

Re: [VFS] Java 8

+1 On Sat, 3 Nov 2018 at 07:55, Gary Gregory wrote: > > I propose we update the Java requirement for [vfs] from Java 7 to Java 8. > > Gary -- Eitan Adler - To unsubscribe, e-mail: dev-unsubscr...@common

[VFS] Java 8

I propose we update the Java requirement for [vfs] from Java 7 to Java 8. Gary

Re: [vfs] new http4 provider, not replace http?

ased) to both "http3" and "http". "http3s" and "https" > > > for the corresponding one accordingly. > > > - At some moment later, when deciding which one to be the default > > > "http" or "https" provider, we

Re: [vfs] new http4 provider, not replace http?

p". "http3s" and "https" > > for the corresponding one accordingly. > > - At some moment later, when deciding which one to be the default > > "http" or "https" provider, we can simply change the providers.xml. > > > > I wil

Re: [vfs] new http4 provider, not replace http?

; I will submit another simple PR to set the default ones to [ "http3", > "http" ] and [ "http3s", "https" ] soon. > > Am I in the right track? > I think so :-) Gary > > Woonsan > > > > > Thoughts? > > > > Gar

Re: [vfs] new http4 provider, not replace http?

can simply change the providers.xml. I will submit another simple PR to set the default ones to [ "http3", "http" ] and [ "http3s", "https" ] soon. Am I in the right track? Woonsan > > Thoughts? > > Gary > > On Wed, Oct 31, 2018 at 6:42 PM

Re: [vfs] new http4 provider, not replace http?

"http3" so that we can create the underlying toggle and test it. Thoughts? Gary On Wed, Oct 31, 2018 at 6:42 PM Woonsan Ko wrote: > Could someone please review my PR? > - https://github.com/apache/commons-vfs/pull/38 > > Woonsan > > > On Wed, Aug 15, 2018 at 9:11 A

AW: svn commit: r1845521 - in /commons/proper/vfs/trunk:commons-vfs2-examples/src/main/java/org/apache/commons/vfs2/example/commons-vfs2/src/main/java/org/apache/commons/vfs2/commons-vfs2/src/main/jav

Yes toString is better, forgot about this. -- http://bernd.eckenfels.net Von: Gary Gregory Gesendet: Freitag, 2. November 2018 00:25 An: Commons Developers List Betreff: Re: svn commit: r1845521 - in /commons/proper/vfs/trunk:commons-vfs2-examples/src/main/java/org/apache/commons/vfs2/example

Re: svn commit: r1845524 - /commons/proper/vfs/trunk/commons-vfs2-examples/src/main/java/org/apache/commons/vfs2/example/Shell.java

Aren't there a few of those? G On Thu, Nov 1, 2018 at 5:38 PM wrote: > Author: ecki > Date: Thu Nov 1 23:38:03 2018 > New Revision: 1845524 > > URL: http://svn.apache.org/viewvc?rev=1845524=rev > Log: > [VFS-678] Use Arrays.toString > > Modified: > > comm

Re: svn commit: r1845521 - in /commons/proper/vfs/trunk: commons-vfs2-examples/src/main/java/org/apache/commons/vfs2/example/ commons-vfs2/src/main/java/org/apache/commons/vfs2/ commons-vfs2/src/main/

p://svn.apache.org/viewvc?rev=1845521=rev > Log: > [VFS-678] fix various LGTM.com warnings. > > Modified: > > commons/proper/vfs/trunk/commons-vfs2-examples/src/main/java/org/apache/commons/vfs2/example/Shell.java > > commons/proper/vfs/trunk/commons-vfs2/src/main/java/org/apa

Re: [vfs] new http4 provider, not replace http?

Could someone please review my PR? - https://github.com/apache/commons-vfs/pull/38 Woonsan On Wed, Aug 15, 2018 at 9:11 AM Woonsan Ko wrote: > > Hi Bernd / Experts, > > I've submitted a PR for VFS-360. Find my summary in the comment as well. > - https://github.com/apache/comm

Re: [vfs] new http4 provider, not replace http?

Hi Bernd / Experts, I've submitted a PR for VFS-360. Find my summary in the comment as well. - https://github.com/apache/commons-vfs/pull/38 Could you please review the changes? Thanks in advance, Woonsan On Wed, Aug 8, 2018 at 6:09 PM, Woonsan Ko wrote: > Hi Bernd, > > Thanks

Re: [vfs] new http4 provider, not replace http?

. Kind regards, Woonsan > > Gruss > Bernd > > -- > http://bernd.eckenfels.net > > Von: Woonsan Ko > Gesendet: Mittwoch, 8. August 2018 18:35 > An: Commons Developers List > Betreff: [vfs] new http4 provider, not replace http? > > Hi, > > I'm tryin

Re: [vfs] new http4 provider, not replace http?

also (only?) should consider the new JDK httpclient api? Gruss Bernd -- http://bernd.eckenfels.net Von: Woonsan Ko Gesendet: Mittwoch, 8. August 2018 18:35 An: Commons Developers List Betreff: [vfs] new http4 provider, not replace http? Hi, I'm trying to contribute for VFS-360. What a nice

[vfs] new http4 provider, not replace http?

Hi, I'm trying to contribute for VFS-360. What a nice ticket number! After a brief look, I'm considering to add a new provider in a separate package, 'http4' (based on HttpComponents HttpClient), keeping the old one, 'http' (based on the old Commons HttpClient), as-is. The reason is that I don't

Re: [VFS] Review for PR-30

https://travis-ci.org/apache/commons-vfs/jobs/342781180 On May 15, 2018 at 13:44:25, Gary Gregory (garydgreg...@gmail.com) wrote: Hopefully I can take a look this week. Do all tests pass? Like 'mvn clean test'. Gary On Mon, May 14, 2018 at 7:44 AM, Otto Fowler <ottobackwa...@gmail.com>

Re: [VFS] Review for PR-30

Hopefully I can take a look this week. Do all tests pass? Like 'mvn clean test'. Gary On Mon, May 14, 2018 at 7:44 AM, Otto Fowler <ottobackwa...@gmail.com> wrote: > https://github.com/apache/commons-vfs/pull/30 > > Any chance getting some eyes on this? >

[VFS] Review for PR-30

https://github.com/apache/commons-vfs/pull/30 Any chance getting some eyes on this?

Re: [VFS] -> a couple of questions

VFS is open for a big update or rewrite. I and others have proposed a rewrite using the NIO API from Java 7, though there haven't been any committed efforts that I've seen. As for it using Subversion, that's mainly because nobody has migrated it to Git yet. We've been migrating repos one

[VFS] -> a couple of questions

Is there committer’s guide for VFS ( or any svn based project ) and working with github PR’s? Who can review the PRs and +1 them to commit? If some of these PR *did* actually land, who would do the release? It seems that VFS is in a ‘maintenance’ state, is that true and official? Thanks. ottO

Re: [VFS] FILE_OR_FOLDER breaking tests

You need someone from cold storage! ;-) Gary On Tue, Mar 20, 2018 at 3:53 PM, Otto Fowler <ottobackwa...@gmail.com> wrote: > Anybody from VFS-past around? > > > On March 8, 2018 at 23:55:54, Gary Gregory (garydgreg...@gmail.com) wrote: > > On Thu, Mar 8, 2018 at 8:54 AM,

Re: [VFS] FILE_OR_FOLDER breaking tests

Anybody from VFS-past around? On March 8, 2018 at 23:55:54, Gary Gregory (garydgreg...@gmail.com) wrote: On Thu, Mar 8, 2018 at 8:54 AM, Otto Fowler <ottobackwa...@gmail.com> wrote: > FILE_OR_FOLDER just doesn’t seem to be supported in the system completely. > Does anyone remember

Re: [VFS] FILE_OR_FOLDER breaking tests

wrote: > > Those tests should be behind a capability for sure, but I thought they are > already (as the resource and URL fikesystem already passes the tests). > > What filesystem do you have in mind and what are examples of failing > testcases? I think I had fixed a few for WebDav

Re: [VFS] FILE_OR_FOLDER breaking tests

urce and URL fikesystem already passes the tests). What filesystem do you have in mind and what are examples of failing testcases? I think I had fixed a few for WebDav back in the days. Gruss Bernd Von: Otto Fowler Gesendet: Dienstag, 6. März 2018 13:41 An: Commons Developers List Betreff: [VFS] FI

Re: [VFS] FILE_OR_FOLDER breaking tests

Otto Fowler Gesendet: Dienstag, 6. März 2018 13:41 An: Commons Developers List Betreff: [VFS] FILE_OR_FOLDER breaking tests If you have a filesystem, where everything could be a FILE_OR_FOLDER type ( or VIRTUAL until attached ), then it seems like you need to replace some of the testcases in

Re: [VFS] FILE_OR_FOLDER breaking tests

think I had fixed a few for WebDav back in the days. Gruss Bernd Von: Otto Fowler Gesendet: Dienstag, 6. März 2018 13:41 An: Commons Developers List Betreff: [VFS] FILE_OR_FOLDER breaking tests If you have a filesystem, where everything could be a FILE_OR_FOLDER type ( or VIRTUAL un

Re: [VFS] FILE_OR_FOLDER breaking tests

Von: Otto Fowler Gesendet: Dienstag, 6. März 2018 13:41 An: Commons Developers List Betreff: [VFS] FILE_OR_FOLDER breaking tests If you have a filesystem, where everything could be a FILE_OR_FOLDER type ( or VIRTUAL until attached ), then it seems like you need to replace some of the testcases

[VFS] FILE_OR_FOLDER breaking tests

If you have a filesystem, where everything could be a FILE_OR_FOLDER type ( or VIRTUAL until attached ), then it seems like you need to replace some of the testcases in the provider suites, since they assume or check for FILE and FOLDER explicitly. I guess my question is, are the tests as they

Re: [VFS] Is there any documentation on creating a new provider?

there any documentation on what is required for creating support for a > new filesystem? > Perhaps https://commons.apache.org/proper/commons-vfs/api.html may be useful? > Or would anyone recommend an existing one in common or sandbox that is a > good simple example? There are a few s

Re: [VFS] Is there any documentation on creating a new provider?

Otto, On 5 March 2018 at 07:53, Otto Fowler <ottobackwa...@gmail.com> wrote: > Is there any documentation on what is required for creating support for a > new filesystem? > Perhaps https://commons.apache.org/proper/commons-vfs/api.html may be useful? > Or would anyone rec

[VFS] Is there any documentation on creating a new provider?

Is there any documentation on what is required for creating support for a new filesystem? Or would anyone recommend an existing one in common or sandbox that is a good simple example? Thanks ottO

Re: [VFS] HttpClient version 3, 4 and 5

On Sun, Feb 18, 2018 at 9:21 PM, Gary Gregory wrote: > - Create a new package org.apache.commons.vfs2.provider.http4, or > - Break BC on the classes in org.apache.commons.vfs2.provider.http Break BC, and do it right: Don't expose HttpClient in the API. Emphasis being on

Re: [VFS][LANG] Jira rights

Thanks! On February 19, 2018 at 14:14:11, Gilles (gil...@harfang.homelinux.org) wrote: On Sun, 18 Feb 2018 20:48:34 -0600, Matt Sicker wrote: > On 17 February 2018 at 12:09, Otto Fowler > wrote: > >> I am familiar with the differences between a contributor or a >>

Re: [VFS][LANG] Jira rights

On Sun, 18 Feb 2018 20:48:34 -0600, Matt Sicker wrote: On 17 February 2018 at 12:09, Otto Fowler wrote: I am familiar with the differences between a contributor or a committer both in the foundation and jira. I would like _contributor_ rights, not commit rights.

Re: [VFS][LANG] Jira rights

ng or mentioning commit rights. I just want to have > everything in my dashboard. > > But since commit rights keeps coming up. Is there a link to commit > procedures and requirements for VFS and or LANG or a guide for committers > etc? > I don’t imagine ‘just committing’ to eit

Re: [VFS][LANG] Jira rights

he issues > that I didn’t create but will > be creating Pull Requests for to myself. > > I am not requesting or mentioning commit rights. I just want to have > everything in my dashboard. > > But since commit rights keeps coming up. Is there a link to commit > procedures

Re: [VFS][LANG] Jira rights

but will be creating Pull Requests for to myself. I am not requesting or mentioning commit rights. I just want to have everything in my dashboard. But since commit rights keeps coming up. Is there a link to commit procedures and requirements for VFS and or LANG or a guide for committers etc? I

Re: [VFS][LANG] Jira rights

everything in my dashboard. But since commit rights keeps coming up. Is there a link to commit procedures and requirements for VFS and or LANG or a guide for committers etc? I don’t imagine ‘just committing’ to either LANG or VFS. I would feel more comfortable with the standard submit until we trust

Re: [VFS][LANG] Jira rights

On 17 February 2018 at 12:09, Otto Fowler wrote: > I am familiar with the differences between a contributor or a committer > both in the foundation and jira. > I would like _contributor_ rights, not commit rights. > In what context? You already have commit rights if

Re: [VFS] HttpClient version 3, 4 and 5

less optional), so having a http4 package and an optional >> dependency on http3+http4 sounds like the better solution. >> > > I am more concerned about not breaking BC in a non-major release. It's > just was not clear to me if a _provider's_ API is part of the public > Common

Re: [VFS] HttpClient version 3, 4 and 5

solution. > I am more concerned about not breaking BC in a non-major release. It's just was not clear to me if a _provider's_ API is part of the public Commons VFS API. I suppose that it is since the options builder provide features that would otherwise not be available. This tells me that w

Re: [VFS] HttpClient version 3, 4 and 5

. Februar 2018 21:21 An: Commons Developers List Betreff: [VFS] HttpClient version 3, 4 and 5 Hi All, Our HTTP provider org.apache.commons.vfs2.provider.http still uses Apache HttpClient 3.1. Some of these classes surface the HttpClient class from 3.1 in APIs marked public. Looking forward

Re: [VFS] trunk build failing in travis

Hello, for my accidential commit I opeend a Infra Task (since I canot rename the branches) https://issues.apache.org/jira/browse/INFRA-16054 Gruss Bernd -- http://bernd.eckenfels.net Von: Bernd Eckenfels Gesendet: Freitag, 16. Februar 2018 03:08 An: Commons Developers List Betreff: Re: [VFS

[VFS] HttpClient version 3, 4 and 5

Hi All, Our HTTP provider org.apache.commons.vfs2.provider.http still uses Apache HttpClient 3.1. Some of these classes surface the HttpClient class from 3.1 in APIs marked public. Looking forward to HttpClient 4 and 5-Alpha/Beta, I wonder how to move forward. We could: - Create a new package

Re: [VFS][LANG] Jira rights

On Sat, Feb 17, 2018 at 11:09 AM, Otto Fowler <ottobackwa...@gmail.com> wrote: > Thanks! Please assign VFS-614, VFS-398, LANG-1373 to me. > > I am familiar with the differences between a contributor or a committer > both in the foundation and jira. > I would like _contributo

Re: [VFS][LANG] Jira rights

On Sat, 17 Feb 2018 13:09:40 -0500, Otto Fowler wrote: Thanks! Please assign VFS-614, VFS-398, LANG-1373 to me. I am familiar with the differences between a contributor or a committer both in the foundation and jira. I would like _contributor_ rights, not commit rights. Given the info here

Re: [VFS][LANG] Jira rights

Thanks! Please assign VFS-614, VFS-398, LANG-1373 to me. I am familiar with the differences between a contributor or a committer both in the foundation and jira. I would like _contributor_ rights, not commit rights. Cheers! On February 17, 2018 at 12:33:22, Gary Gregory (garydgreg

Re: [VFS][LANG] Jira rights

il.com> wrote: I would like to assign the jiras for my PR’s to myself. And I pleased be given contributor rights to LANG and VFS? Thanks.

[VFS][LANG] Jira rights

I would like to assign the jiras for my PR’s to myself. And I pleased be given contributor rights to LANG and VFS? Thanks.

Re: [VFS] trunk build failing in travis

And only fails java8, which is what i’m using local On February 16, 2018 at 14:26:10, Otto Fowler (ottobackwa...@gmail.com) wrote: https://travis-ci.org/ottobackwards/commons-vfs/builds/342485419 So this builds locally with mvn clean package, but fails in travis, anyone familiar? On February

Re: [VFS] trunk build failing in travis

https://travis-ci.org/ottobackwards/commons-vfs/builds/342485419 So this builds locally with mvn clean package, but fails in travis, anyone familiar? On February 16, 2018 at 14:23:31, Bernd Eckenfels (e...@zusammenkunft.net) wrote: There is something fishy going on with the way testdatan

Re: [VFS] trunk build failing in travis

ary 16, 2018 8:18:44 PM To: Gary Gregory; Commons Developers List Cc: Bernd Eckenfels Subject: Re: [VFS] trunk build failing in travis That did the trick. Thank you. I’m going to submit pr’s for VFS-398 and VFS-614 soon. On February 16, 2018 at 13:54:53, Gary Gregory (garydgreg...@gma

Re: [VFS] trunk build failing in travis

That did the trick. Thank you. I’m going to submit pr’s for VFS-398 and VFS-614 soon. On February 16, 2018 at 13:54:53, Gary Gregory (garydgreg...@gmail.com) wrote: Note that the Travis build is now green: https://travis-ci.org/apache/commons-vfs/ Gary On Fri, Feb 16, 2018 at 11:34 AM, Gary

Re: [VFS] trunk build failing in travis

Note that the Travis build is now green: https://travis-ci.org/apache/commons-vfs/ Gary On Fri, Feb 16, 2018 at 11:34 AM, Gary Gregory <garydgreg...@gmail.com> wrote: > Make sure you have the latest from trunk. The build works for me locally > using 'mvn clean package' using Oracle

Re: [VFS] trunk build failing in travis

Make sure you have the latest from trunk. The build works for me locally using 'mvn clean package' using Oracle Java 7 and 8: Apache Maven 3.5.2 (138edd61fd100ec658bfa2d307c43b76940a5d7d; 2017-10-18T01:58:13-06:00) Maven home: C:\Java\apache-maven-3.5.2\bin\.. Java version: 1.8.0_162, vendor:

Re: [VFS] trunk build failing in travis

Any ideas on this? Even with the old pom, I’m seeing failures I cannot explain. I have a couple of PR’s I think I’d like to submit, but building seems a bit of mess. On February 15, 2018 at 22:03:06, Bernd Eckenfels (e...@zusammenkunft.net) wrote: Hello, I digged a bit deeper, and on my

Re: [VFS] trunk build failing in travis

Hello, I digged a bit deeper, and on my Windows System surefire 1.20.1 is failing because of this new „ping“ behavior: http://maven.apache.org/surefire/maven-surefire-plugin/examples/shutdown.html Looks like a bug that surefire is not falling back when wmic is not found (or better search for

Re: [VFS] trunk build failing in travis

the Version downgrade? Gruss Bernd -- http://bernd.eckenfels.net Von: Gary Gregory Gesendet: Freitag, 16. Februar 2018 02:57 An: Commons Developers List Betreff: Re: [VFS] trunk build failing in travis On Thu, Feb 15, 2018 at 6:42 PM, Bernd Eckenfels <e...@zusammenkunft.net> wrote: > H

Re: [VFS] trunk build failing in travis

surefire is not started and the build suceeds. > Error Messages are however different from your Travis logs. > > Setting the old surefire Version (and the new parent) works for me: > > 2.19.1 fails --> > > Should we revert the parent Version or add the property (for now)? >

Re: [VFS] trunk build failing in travis

the old surefire Version (and the new parent) works for me: 2.19.1 Should we revert the parent Version or add the property (for now)? Gruss Bernd -- http://bernd.eckenfels.net Von: Otto Fowler Gesendet: Donnerstag, 15. Februar 2018 18:07 An: Commons Developers List Betreff: Re: [VFS] trunk build

[VFS] commons-parent 43 breaks VFS build : (was) trunk build failing in travis

on github On February 15, 2018 at 11:59:22, Otto Fowler (ottobackwa...@gmail.com) wrote: I have forked VFS and tried to build it in my personal travis, and it is failing. https://travis-ci.org/ottobackwards/commons-vfs/builds/341963824 It also fails testing locally as well. Is this expected? I

Re: [VFS] trunk build failing in travis

It is also failed on github On February 15, 2018 at 11:59:22, Otto Fowler (ottobackwa...@gmail.com) wrote: I have forked VFS and tried to build it in my personal travis, and it is failing. https://travis-ci.org/ottobackwards/commons-vfs/builds/341963824 It also fails testing locally as well

[VFS] trunk build failing in travis

I have forked VFS and tried to build it in my personal travis, and it is failing. https://travis-ci.org/ottobackwards/commons-vfs/builds/341963824 It also fails testing locally as well. Is this expected? I can’t get the the apache/commons-vfs travis site to check if it is building there. ottO

[vfs] Jenkins enabled for commons-vfs

FYI: I've enable the build on Jenkins: https://builds.apache.org/job/commons-vfs-trunk/ Gary

[compress] zstandard and [vfs]

If we get a new version of [compress] out with Zstandard, then we can update [vfs] to support it as well. Thoughts? Gary

[ANNOUNCEMENT] Apache Commons VFS 2.2 Released

The Apache Commons team is pleased to announce the release of Commons VFS 2.2. Commons VFS provides a single API for accessing various different file systems. It presents a uniform view of the files from various different sources, such as the files on local disk, on an HTTP server, or inside

[RESULT][VOTE] Release Apache Commons VFS 2.2 from RC2.

significant enhancements > since Apache Commons VFS 2.1 was released, so I would like to release > Apache Commons VFS 2.2. > > Apache Commons VFS 2.2 RC2 is available for review here: > https://dist.apache.org/repos/dist/dev/commons/vfs/ (svn revision > 22084) > Get it: svn

Re: [VOTE] Release Apache Commons VFS 2.2 from RC2.

wrote: > >> >> We have fixed quite a few bugs and added some significant enhancements >> since Apache Commons VFS 2.1 was released, so I would like to release >> Apache Commons VFS 2.2. >> >> Apache Commons VFS 2.2 RC2 is available for review here: >&

Re: [VOTE] Release Apache Commons VFS 2.2 from RC2.

>> We have fixed quite a few bugs and added some significant enhancements >> since Apache Commons VFS 2.1 was released, so I would like to release >> Apache Commons VFS 2.2. >> >> Apache Commons VFS 2.2 RC2 is available for review here: >>https://dist.apache.o

Re: [VOTE] Release Apache Commons VFS 2.2 from RC2.

Hi, can I get at least one more review please? Gary On Tue, Oct 3, 2017 at 12:30 PM, Gary Gregory <garydgreg...@gmail.com> wrote: > > We have fixed quite a few bugs and added some significant enhancements > since Apache Commons VFS 2.1 was released, so I would like to release &

Re: [VOTE] Release Apache Commons VFS 2.2 from RC2.

My +1 Gary On Tue, Oct 3, 2017 at 12:30 PM, Gary Gregory <garydgreg...@gmail.com> wrote: > > We have fixed quite a few bugs and added some significant enhancements > since Apache Commons VFS 2.1 was released, so I would like to release > Apache Commons VFS 2.2. > > Ap

Re: [VOTE] Release Apache Commons VFS 2.2 from RC2.

, the other one contains some warnings which are probably not too difficult to fix. No blockers, so +1 Oliver Am 03.10.2017 um 20:30 schrieb Gary Gregory: > We have fixed quite a few bugs and added some significant enhancements > since Apache Commons VFS 2.1 was released, so I would like to r

[VOTE] Release Apache Commons VFS 2.2 from RC2.

We have fixed quite a few bugs and added some significant enhancements since Apache Commons VFS 2.1 was released, so I would like to release Apache Commons VFS 2.2. Apache Commons VFS 2.2 RC2 is available for review here: https://dist.apache.org/repos/dist/dev/commons/vfs/ (svn revision 22084

Re: [vfs] VFS 2.2 and Java 9

t4Provider.invoke(JUnit >> 4Provider.java:161) >> at >> org.apache.maven.surefire.booter.ForkedBooter.invokeProvider >> InSameClassLoader(ForkedBooter.java:290) >> at >> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInPr

Re: [vfs] VFS 2.2 and Java 9

kedBooter.java:242) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121) Caused by: org.apache.commons.vfs2.FileSystemException: Could not retrieve the certificates of "jar:jar:file:///C:/vcs/svn/apache/commons/trunks-proper/vfs/commons-vfs2/target/test-classes/test-data/nested.jar!/test.jar!

[vfs] VFS 2.2 and Java 9

r.java:121) Caused by: org.apache.commons.vfs2.FileSystemException: Could not retrieve the certificates of "jar:jar:file:///C:/vcs/svn/apache/commons/trunks-proper/vfs/commons-vfs2/target/test-classes/test-data/nested.jar!/test.jar!/code/ClassToLoad.class". at org.apache.commons.vfs2.provider.Defaul

Re: [VOTE] Release Apache Commons VFS 2.2 from RC1.

uite.run:137->setUp:98 » NoClassDefFound > > I building with: > > ~ > mvn -version > Java HotSpot(TM) 64-Bit Server VM warning: ignoring option > MaxPermSize=128m; support was removed in 8.0 > Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426; > 2017-04-03T2

[CANCEL][VOTE] Release Apache Commons VFS 2.2 from RC1.

org.apache.commons.vfs2.provider.hdfs.test.HdfsFileProviderT >> est.org.apache.commons.vfs2.provider.hdfs.test.HdfsFileProviderTest >> Run 1: HdfsFileProviderTest.setUp:91 » ExceptionInInitializer >> Run 2: HdfsFileProviderTest.tearDown:135 NullPointer >> >> >> H

Re: [VOTE] Release Apache Commons VFS 2.2 from RC1.

I building with: > > ~ > mvn -version > Java HotSpot(TM) 64-Bit Server VM warning: ignoring option > MaxPermSize=128m; support was removed in 8.0 > Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426; > 2017-04-03T21:39:06+02:00) > Maven home: /usr/local/Ce

Re: [VOTE] Release Apache Commons VFS 2.2 from RC1.

0.12.6", arch: "x86_64", family: "mac" So I’m -1 on this release. Benedikt > Am 23.09.2017 um 18:43 schrieb Gary Gregory <ggreg...@apache.org>: > > We have fixed quite a few bugs and added some significant enhancements > since Apache Commons VFS 2.1 was

Re: [VOTE] Release Apache Commons VFS 2.2 from RC1.

ot;10.12.6", arch: "x86_64", family: "mac" So I’m -1 on this release. Benedikt > Am 23.09.2017 um 18:43 schrieb Gary Gregory <ggreg...@apache.org>: > > We have fixed quite a few bugs and added some significant enhancements > since Apache Commons VFS 2.1

Re: [VOTE] Release Apache Commons VFS 2.2 from RC1.

e: > > > >> We have fixed quite a few bugs and added some significant enhancements > >> since Apache Commons VFS 2.1 was released, so I would like to release > >> Apache Commons VFS 2.2. > >> > >> Apache Commons VFS 2.2 RC1 is available for review he

Re: [VOTE] Release Apache Commons VFS 2.2 from RC1.

or your input, > Gary > > On Sat, Sep 23, 2017 at 10:43 AM, Gary Gregory <ggreg...@apache.org> wrote: > >> We have fixed quite a few bugs and added some significant enhancements >> since Apache Commons VFS 2.1 was released, so I would like to release >>

Re: [VOTE] Release Apache Commons VFS 2.2 from RC1.

Would a few of you please find the time to review this RC? Thank you in advance for your input, Gary On Sat, Sep 23, 2017 at 10:43 AM, Gary Gregory <ggreg...@apache.org> wrote: > We have fixed quite a few bugs and added some significant enhancements > since Apache Commons VFS 2.1

Re: [VOTE] Release Apache Commons VFS 2.2 from RC1.

May I please have more VOTEs? Thank you in advance for your review, Gary On Sat, Sep 23, 2017 at 10:43 AM, Gary Gregory <ggreg...@apache.org> wrote: > We have fixed quite a few bugs and added some significant enhancements > since Apache Commons VFS 2.1 was released, so I would lik

Re: [VOTE] Release Apache Commons VFS 2.2 from RC1.

are probably not too difficult to fix. No blockers, so +1 Oliver Am 23.09.2017 um 18:43 schrieb Gary Gregory: > We have fixed quite a few bugs and added some significant enhancements > since Apache Commons VFS 2.1 was released, so I would like to release > Apache Commons VFS 2.2. &g

Re: [VOTE] Release Apache Commons VFS 2.2 from RC1.

On travis-ci there are three unit test failures for the build of the tag: ZipFileObjectTestCase.testReadingFilesInZipFile ZipFileObjectTestCase.testReadingOneAfterClosingAnotherFile ZipFileObjectTestCase.testReadingOneAfterClosingAnotherStream:see: https://travis-ci.org/apache/commons-vfs

Re: [VOTE] Release Apache Commons VFS 2.2 from RC1.

My +1 Gary On Sat, Sep 23, 2017 at 10:43 AM, Gary Gregory <ggreg...@apache.org> wrote: > We have fixed quite a few bugs and added some significant enhancements > since Apache Commons VFS 2.1 was released, so I would like to release > Apache Commons VFS 2.2. > > Apach

Re: [VOTE] Release Apache Commons VFS 2.2 from RC1.

apache.org> > Sent: Saturday, September 23, 2017 5:43:03 PM > To: Commons Developers List > Subject: [VOTE] Release Apache Commons VFS 2.2 from RC1. > > We have fixed quite a few bugs and added some significant enhancements > since Apache Commons VFS 2.1 was released, so I would l

Re: [VOTE] Release Apache Commons VFS 2.2 from RC1.

reg...@apache.org> Sent: Saturday, September 23, 2017 5:43:03 PM To: Commons Developers List Subject: [VOTE] Release Apache Commons VFS 2.2 from RC1. We have fixed quite a few bugs and added some significant enhancements since Apache Commons VFS 2.1 was released, so I would like to release

[VOTE] Release Apache Commons VFS 2.2 from RC1.

We have fixed quite a few bugs and added some significant enhancements since Apache Commons VFS 2.1 was released, so I would like to release Apache Commons VFS 2.2. Apache Commons VFS 2.2 RC1 is available for review here: https://dist.apache.org/repos/dist/dev/commons/vfs/ (svn revision 21925

Re: [VFS] toward releasing 2.2

; >> >> >> From: Gary Gregory <garydgreg...@gmail.com> >> To: Commons Developers List <dev@commons.apache.org> >> Sent: Tuesday, 5 September 2017 5:39 AM >> Subject: [VFS] toward releasing 2.2 >> >> >> &

<    1   2   3   4   5   6   7   8   9   10   >