Re: checksum file Release Distribution Policy

> On Mar 5, 2018, at 2:18 PM, Gilles wrote: > > On Mon, 5 Mar 2018 11:35:27 -0500, Rob Tompkins wrote: >> The plugin only finds the assemblies, and the .asc files. We’ve been >> using the created signatures from nexus. So, I actually am creating >> the same

Re: checksum file Release Distribution Policy

Do guidelines on which algorithm to use for GPG signing need to be added? On 5 March 2018 at 13:18, Gilles wrote: > On Mon, 5 Mar 2018 11:35:27 -0500, Rob Tompkins wrote: > >> The plugin only finds the assemblies, and the .asc files. We’ve been >> using the created

Re: checksum file Release Distribution Policy

On Mon, 5 Mar 2018 11:35:27 -0500, Rob Tompkins wrote: The plugin only finds the assemblies, and the .asc files. We’ve been using the created signatures from nexus. So, I actually am creating the same signature files in the plugin. So, we have some leeway in deciding what sorts of signatures we

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

Thanks Hasan, I did read the API doc, but that is more towards using a filesystem, I’m thinking about creating a new provider. On March 5, 2018 at 12:28:41, Hasan Diwan (hasan.di...@gmail.com) wrote: Otto, On 5 March 2018 at 07:53, Otto Fowler wrote: > Is there any

Re: [commons-release-plugin] Git Push Summary

Not voted on in email. > On Mar 5, 2018, at 12:42 PM, chtom...@apache.org wrote: > > Repository: commons-release-plugin > Updated Tags: refs/tags/commons-release-plugin-1.1-RC1 [deleted] b45d5bb6a - To unsubscribe, e-mail:

Re: [commons-release-plugin] Git Push Summary

Not voted on in dev list. > On Mar 5, 2018, at 12:42 PM, chtom...@apache.org wrote: > > Repository: commons-release-plugin > Updated Tags: refs/tags/commons-release-plugin-1.1-RC3 [deleted] e8219ec15 - To unsubscribe, e-mail:

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

Otto, On 5 March 2018 at 07:53, Otto Fowler 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 recommend an existing

Re: checksum file Release Distribution Policy

> On Mar 5, 2018, at 11:52 AM, Gary Gregory wrote: > >> On Mon, Mar 5, 2018 at 8:51 AM, Rob Tompkins wrote: >> >> The current version, 1.1, uploads .asc, .sha1, and .md5. Should we pull >> that back in leu of adding sha512 and removing sha1, md5? I

Re: checksum file Release Distribution Policy

On Mon, Mar 5, 2018 at 8:51 AM, Rob Tompkins wrote: > The current version, 1.1, uploads .asc, .sha1, and .md5. Should we pull > that back in leu of adding sha512 and removing sha1, md5? I haven’t > promoted the RC yet. > I would move the release along, then consider how do

Re: checksum file Release Distribution Policy

The plugin only finds the assemblies, and the .asc files. We’ve been using the created signatures from nexus. So, I actually am creating the same signature files in the plugin. So, we have some leeway in deciding what sorts of signatures we want to upload to the “dist” svn repo. The m2

Re: checksum file Release Distribution Policy

Surely the plugin should upload whatever it finds? Or does the plugin create the hashes as well? On 5 March 2018 at 15:51, Rob Tompkins wrote: > The current version, 1.1, uploads .asc, .sha1, and .md5. Should we pull that > back in leu of adding sha512 and removing sha1,

[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: checksum file Release Distribution Policy

The current version, 1.1, uploads .asc, .sha1, and .md5. Should we pull that back in leu of adding sha512 and removing sha1, md5? I haven’t promoted the RC yet. -Rob > On Mar 5, 2018, at 10:27 AM, Gary Gregory wrote: > > Rob: How does this affect your release plugin?

Fwd: checksum file Release Distribution Policy

Rob: How does this affect your release plugin? Gary -- Forwarded message -- From: Henk P. Penning Date: Mon, Mar 5, 2018 at 4:18 AM Subject: checksum file Release Distribution Policy To: he...@apache.org Hi Pmcs, The Release Distribution Policy[1] changed

[RESULT][VOTE][LAZY] Release Commons Release Plugin 1.1 based on RC4

The vote passes with no down votes, and +1’s from: Gary Gregory, and Rob Tompkins. I will proceed with promoting the release. Cheers, -Rob > On Mar 2, 2018, at 8:03 AM, Rob Tompkins wrote: > > Hello all, > > This is a [VOTE][LAZY] for releasing Apache Commons Release

Re: [VOTE][LAZY] Release Commons Release Plugin 1.1 based on RC4

Here’s my +1. > On Mar 2, 2018, at 8:03 AM, Rob Tompkins wrote: > > Hello all, > > This is a [VOTE][LAZY] for releasing Apache Commons Release Plugin 1.1 (from > RC4). > > Tag name: > commons-release-plugin-1.1-RC4 (signature can be checked from git using > 'git tag >

[GitHub] commons-pool issue #4: POOL-337: EvictionTimer does not remove cancelled tas...

Github user coveralls commented on the issue: https://github.com/apache/commons-pool/pull/4 [](https://coveralls.io/builds/15805552) Coverage increased (+0.06%) to 84.784% when pulling

[GitHub] commons-pool issue #4: POOL-337: EvictionTimer does not remove cancelled tas...

Github user coveralls commented on the issue: https://github.com/apache/commons-pool/pull/4 [](https://coveralls.io/builds/15805552) Coverage increased (+0.06%) to 84.784% when pulling

[GitHub] commons-pool pull request #4: POOL-337: EvictionTimer does not remove cancel...

GitHub user cdeneux opened a pull request: https://github.com/apache/commons-pool/pull/4 POOL-337: EvictionTimer does not remove cancelled tasks EvictionTimer does not remove cancelled tasks from the executor, and so a memory leak occurs. Thanks to Reinald Verheij for the