[CRYPTO] Is there anyone can help add Crypto 1.0.0 to reporter tool

Hello Is there anyone can help add Crypto to the reporter? https://reporter.apache.org/addrelease.html?commons Full version name: CRYPTO-1.0.0 Date of release: 2016-08-09 Thanks, Dapeng

Re: [CRYPTO] Is there anyone can help add Crypto 1.0.0 to reporter tool

On 10/08/2016 08:44, Sun, Dapeng wrote: > Hello > > Is there anyone can help add Crypto to the reporter? > > https://reporter.apache.org/addrelease.html?commons > Full version name: CRYPTO-1.0.0 > Date of release: 2016-08-09 Done. Mark -

RE: [CRYPTO] Is there anyone can help add Crypto 1.0.0 to reporter tool

Hi Mark, Thank you for your help :) Regards Dapeng -Original Message- From: Mark Thomas [mailto:ma...@apache.org] Sent: Wednesday, August 10, 2016 4:41 PM To: Commons Developers List Subject: Re: [CRYPTO] Is there anyone can help add Crypto 1.0.0 to reporter tool On 10/08/2016 08:44,

Re: [rng] JIRA "pid" ?

The URL https://issues.apache.org/jira/browse/RNG works, so I guess its RNG. Jochen On Tue, Aug 9, 2016 at 6:28 PM, Gilles wrote: > Hello. > > How does one find the project identifier to be used in links such as > > http://issues.apache.org/jira/secure/CreateIssueDetails!init.jspa?pid=12310485&

Re: [rng] JIRA "pid" ?

On Wed, 10 Aug 2016 12:24:24 +0200, Jochen Wiedmann wrote: The URL https://issues.apache.org/jira/browse/RNG works, so I guess its RNG. IIUC, "RNG" is the JIRA "projectKey". The "pid" is a number (see the URL below). Gilles Jochen On Tue, Aug 9, 2016 at 6:28 PM, Gilles wrote: Hello. Ho

Re: [configuration] Checkstyle settings

Do you guys need any help in this? I can volunteer my time to help push this release, just let me know what needs to be done. On Sun, Aug 7, 2016 at 10:12 AM, Dennis Kieselhorst wrote: > Am 06.08.2016 um 17:51 schrieb Emmanuel Bourg: > > Le 2/08/2016 à 21:17, Oliver Heger a écrit : > > > >> Well

Jenkins build is back to normal : commons-csv » Apache Commons CSV #20

See - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org

Jenkins build is back to normal : commons-csv #20

See - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org

Jenkins build is back to normal : Commons-configuration #21

See - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org

Jenkins build is back to normal : commons-imaging #13

See - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org

Jenkins build is back to normal : commons-imaging » Apache Commons Imaging #13

See - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org

Help for a Newbie

Hi All, I am new to this list. Please help me with any newbie helper guide. How do I get work assigned here? Honestly, I am quite intimidated after reading the mailing list. I am not quite sure where do I begin. I am sorry if the same question was raised before. ---

Re: Help for a Newbie

Look through Jira for open bugs and features, submit patches, discuss larger features and how to implement them on the dev list. On 10 August 2016 at 09:47, Utsav Oza wrote: > Hi All, > > I am new to this list. Please help me with any newbie helper guide. > > How do I get work assigned here? Hon

Re: [VOTE] Release commons-parent 41 based on RC2

Has this vote been tabulated? Gary On Wed, Aug 3, 2016 at 9:17 PM, Charles Honton wrote: > We have added a significant enhancements since commons-parent 40 was > released, > so I would like to release commons-parent 41. > > commons-parent 41 RC2 is available for review here: > https://dist.

Re: [VOTE] Release commons-parent 41 based on RC2

No votes. Will work on release tonight. Chas > On Aug 10, 2016, at 9:27 AM, Gary Gregory wrote: > > Has this vote been tabulated? > > Gary > >> On Wed, Aug 3, 2016 at 9:17 PM, Charles Honton wrote: >> >> We have added a significant enhancements since commons-parent 40 was >> released, >>

Re: Help for a Newbie

Hello, great that you want to contribute. Apache Commons is kind of a kitchen-sink project, and you are probably best positioned when you look at aspecific sub-project. If you check out the (maven) sites for the projects you typically find a page to instructions for contribution or you look at CO

Re: [configuration] Checkstyle settings

Hi, Am 10.08.2016 um 16:05 schrieb Raviteja Lokineni: > Do you guys need any help in this? I can volunteer my time to help push > this release, just let me know what needs to be done. thank you for the offering. I think, after the latest fix of Dennis, the codebase is now ready to cut another RC

Re: [VOTE] Release Configuration 2.1 based on RC2

Hi Oliver! > so do we have a confirmation that the current state in trunk builds > correctly on the problematic platforms? Then I could start preparing > another RC in the next days. > As the checkstyle config is now adapted, please prepare another RC. Cheers Dennis --

Re: commons-rng git commit: CheckStyle.

Why not use "catch (InvocationTargetException | InstantiationException | IllegalAccessException e) {..." ? On Wed, Aug 10, 2016 at 1:25 PM, wrote: > Repository: commons-rng > Updated Branches: > refs/heads/master 16144a47a -> 42ca85b3d > > > CheckStyle. > > > Project: http://git-wip-us.apach

Re: commons-rng git commit: CheckStyle.

Le 10/08/2016 à 22:37, Gary Gregory a écrit : > Why not use "catch (InvocationTargetException | InstantiationException | > IllegalAccessException e) {..." > > ? Because the language level is Java 6 Emmanuel Bourg - To unsubsc

Re: commons-rng git commit: CheckStyle.

Why not Java 7 at least? Java 6 was EOL 5 years ago now. On Wed, Aug 10, 2016 at 1:39 PM, Emmanuel Bourg wrote: > Le 10/08/2016 à 22:37, Gary Gregory a écrit : >> Why not use "catch (InvocationTargetException | InstantiationException | >> IllegalAccessException e) {..." >> >> ? > > Because the l

Re: commons-rng git commit: CheckStyle.

Yeah, I'm kind of wondering why a new project is being made with Java 6 at this point. On 10 August 2016 at 15:42, James Ring wrote: > Why not Java 7 at least? Java 6 was EOL 5 years ago now. > > On Wed, Aug 10, 2016 at 1:39 PM, Emmanuel Bourg wrote: > > Le 10/08/2016 à 22:37, Gary Gregory a éc

Re: commons-rng git commit: CheckStyle.

Le 10/08/2016 à 22:42, James Ring a écrit : > Why not Java 7 at least? Java 6 was EOL 5 years ago now. RNG doesn't need more than Java 6 for now, so that's fine. And Java 6 is still supported by Oracle (end of extended support in December 2018). Emmanuel Bourg --

Re: commons-rng git commit: CheckStyle.

On Wed, 10 Aug 2016 15:44:45 -0500, Matt Sicker wrote: Yeah, I'm kind of wondering why a new project is being made with Java 6 at this point. There is a rationale; see messages for the following commits: bb0886f84ba23032306c6376987f92ce653f181d ed083eaf22c4c8403660c48bee7945d40edee6d9 But i

[rng] Update .gitignore to ignore MacOS related files.

Hi, Will it be possible to apply patch for .gitignore file to skip Mac related files? >From 30356710069fa340323485e5a10ee7fcb489617e Mon Sep 17 00:00:00 2001 From: Artem Barger Date: Thu, 11 Aug 2016 01:10:51 +0300 Subject: [PATCH] Update .gitignore to skip MacOs related folders --- .gitignore

Re: [rng] Update .gitignore to ignore MacOS related files.

On Thu, 11 Aug 2016 01:14:53 +0300, Artem Barger wrote: Hi, Will it be possible to apply patch for .gitignore file to skip Mac related files? Done. Gilles From 30356710069fa340323485e5a10ee7fcb489617e Mon Sep 17 00:00:00 2001 From: Artem Barger Date: Thu, 11 Aug 2016 01:10:51 +0300 Subj

Re: [rng] Update .gitignore to ignore MacOS related files.

On Thu, Aug 11, 2016 at 1:12 AM, Gilles wrote: > Hi, >> >> Will it be possible to apply patch for .gitignore file to skip Mac related >> files? >> > > Done. ​Thanks.​ Best regards, Artem Barger.

Re: commons-rng git commit: CheckStyle.

On Wed, Aug 10, 2016 at 11:58 PM, Gilles wrote: > But if all are happy to require Java 7, I wouldn't certainly > oppose it! > ​And what about going forward and switching to Java 8? Or this sort of decision should be received broadly across ​all commons projects? Best regards,

Re: commons-rng git commit: CheckStyle.

> On Aug 10, 2016, at 6:43 PM, Artem Barger wrote: > > On Wed, Aug 10, 2016 at 11:58 PM, Gilles > wrote: > >> But if all are happy to require Java 7, I wouldn't certainly >> oppose it! > > ​And what about going forward and switching to Java 8? Or this sort of > decision > should be received

Re: [VOTE] Release commons-parent 41 based on RC2

This VOTE passed with lazy consensus. No explicit votes. No vetoes. chas > On Aug 3, 2016, at 9:17 PM, Charles Honton wrote: > > We have added a significant enhancements since commons-parent 40 was released, > so I would like to release commons-parent 41. > > commons-parent 41 RC2 is availabl

Re: commons-rng git commit: CheckStyle.

> 11 авг. 2016 г., в 2:08, Rob Tompkins написал(а): > > I would guess that we would want to be compatible with the oldest version of > Java possible dictated out of necessity. By that I mean if there's something > of considerable substance that a newer version affords us, then we should > up