Re: [REMINDER][VOTE][RC1] Release Commons Rng 1.0

2016-09-14 Thread Gilles
On Wed, 14 Sep 2016 09:42:17 +, Benedikt Ritter wrote: Hello Gilles, sorry for the delay. I won't have the time to review this RC before Saturday :-( Could someone else please provide the missing vote earlier? Regards, Gilles Benedikt Gilles schrieb am

Build failed in Jenkins: commons-beanutils #9

2016-09-14 Thread Apache Jenkins Server
See Changes: [stain] [maven-release-plugin] prepare for next development iteration [stain] [maven-release-plugin] prepare release BEANUTILS_1_9_3_RC2 [stain] [maven-release-plugin] prepare for next development iteration [stain]

Build failed in Jenkins: commons-beanutils ยป Apache Commons BeanUtils #9

2016-09-14 Thread Apache Jenkins Server
See Changes: [stain] [maven-release-plugin] prepare for next development iteration [stain] [maven-release-plugin] prepare release BEANUTILS_1_9_3_RC2 [stain] [maven-release-plugin] prepare for next

Re: [REMINDER][VOTE][RC1] Release Commons Rng 1.0

2016-09-14 Thread Stian Soiland-Reyes
I'll have a go :) On 14 September 2016 at 13:49, Gilles wrote: > On Wed, 14 Sep 2016 09:42:17 +, Benedikt Ritter wrote: >> >> Hello Gilles, >> >> sorry for the delay. I won't have the time to review this RC before >> Saturday :-( > > > Could someone else please

[GitHub] commons-codec pull request #5: Do not leak file descriptors

2016-09-14 Thread SvetlinZarev
Github user SvetlinZarev closed the pull request at: https://github.com/apache/commons-codec/pull/5 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the

Re: [REMINDER][VOTE][RC1] Release Commons Rng 1.0

2016-09-14 Thread Stian Soiland-Reyes
On 14 September 2016 at 10:14, Gilles wrote: > This is a [VOTE] for releasing Apache Commons Rng 1.0 (from RC1). > Commit ID the tag points at: > f8d23082607b9f2c7be7f489eb09627722440ee5 Thanks, Gilles! I'm afraid my vote is: -0 as the source zip is missing

Re: commons-rng git commit: Update release howto.

2016-09-14 Thread Benedikt Ritter
schrieb am Mi., 14. Sep. 2016 um 16:36 Uhr: > Repository: commons-rng > Updated Branches: > refs/heads/master 6eb9a1eb1 -> 4bf4428cf > > > Update release howto. > > > Project: http://git-wip-us.apache.org/repos/asf/commons-rng/repo > Commit:

[VOTE] Release Commons BeanUtils 1.9.3 RC2

2016-09-14 Thread Stian Soiland-Reyes
This is a [VOTE] for releasing Apache Commons BeanUtils 1.9.3 (from RC2) SVN tag: https://svn.apache.org/repos/asf/commons/proper/beanutils/tags/BEANUTILS_1_9_3_RC2/ Site: https://stain.github.io/commons-beanutils/1.9.3-rc2/ Javadoc:

Re: [REMINDER][VOTE][RC1] Release Commons Rng 1.0

2016-09-14 Thread Gary Gregory
"I'd rather not redo the release steps just for files that are meaningful only when browsing the code repository mirror at Github." I know our release process is a pain, so maybe we should see if we can improve it. This needs a separate thread. It's rare to release without more than one RC. It

Re: [REMINDER][VOTE][RC1] Release Commons Rng 1.0

2016-09-14 Thread Gilles
On Wed, 14 Sep 2016 14:53:29 +0100, Stian Soiland-Reyes wrote: On 14 September 2016 at 10:14, Gilles wrote: This is a [VOTE] for releasing Apache Commons Rng 1.0 (from RC1). Commit ID the tag points at: f8d23082607b9f2c7be7f489eb09627722440ee5 Thanks, Gilles!

Re: [VOTE][RC1] Release Commons Rng 1.0

2016-09-14 Thread Emmanuel Bourg
Hi all, RNG is moving fast, that's nice. I got a quick look at the API and the site, here are my comments: - The main page (Overview) could be enhanced with a description of the API longer than a single sentence. It could mention the motivations for the API, the implementations supported, a

Re: [VOTE] Release Commons BeanUtils 1.9.3 RC2

2016-09-14 Thread Raviteja Lokineni
Why do the distribution files hashes have commons-rng? On Wed, Sep 14, 2016 at 11:45 AM, Stian Soiland-Reyes wrote: > This is a [VOTE] for releasing Apache Commons BeanUtils 1.9.3 (from RC2) > > > SVN tag: > https://svn.apache.org/repos/asf/commons/proper/beanutils/ >

Re: [VOTE] Release Commons BeanUtils 1.9.3 RC2

2016-09-14 Thread Henning Schmiedehausen
+1 for releasing. Compiled and tested on MacOS X running Java 8. -h [Seems I am still a committer. Haven't been here in a while. ] On Wed, Sep 14, 2016 at 8:45 AM, Stian Soiland-Reyes wrote: > This is a [VOTE] for releasing Apache Commons BeanUtils 1.9.3 (from RC2) > > > SVN

Re: [VOTE] Release Commons BeanUtils 1.9.3 RC2

2016-09-14 Thread Stian Soiland-Reyes
I think it's from the default config of picking up earlier version, e.g. so it would find 1.9.0. Sorry, I sent the wrong hashes, will resend. On 14 Sep 2016 11:34 p.m., "Gary Gregory" wrote: > Curious: what does "Semantic Versioning: 0.0.1" mean? And that what we >

Re: [VOTE] Release Commons BeanUtils 1.9.3 RC2

2016-09-14 Thread Stian Soiland-Reyes
On 14 September 2016 at 16:45, Stian Soiland-Reyes wrote: > This is a [VOTE] for releasing Apache Commons BeanUtils 1.9.3 (from RC2) > Distribution files hashes (SHA1): Sorry, previous hashes were copy-pasted wrong :-( Correct hashes (as can be verified by the dist area and

Re: svn commit: r1760391 - in /commons/proper/beanutils/trunk/src: main/java/org/apache/commons/beanutils/PropertyUtilsBean.java test/java/org/apache/commons/beanutils/bugs/Jira492TestCase.java

2016-09-14 Thread Benedikt Ritter
Hello, schrieb am Mo., 12. Sep. 2016 um 17:36 Uhr: > Author: stain > Date: Mon Sep 12 15:36:03 2016 > New Revision: 1760391 > > URL: http://svn.apache.org/viewvc?rev=1760391=rev > Log: > BEANUTILS-492: Document getPropertyType() no longer supporting List > > Added: > >

Re: [REMINDER][VOTE][RC1] Release Commons Rng 1.0

2016-09-14 Thread Benedikt Ritter
Hello Gilles, sorry for the delay. I won't have the time to review this RC before Saturday :-( Benedikt Gilles schrieb am Mi., 14. Sep. 2016 um 11:29 Uhr: > > > Original Message > Subject: [VOTE][RC1] Release Commons Rng 1.0 > Date: Sun, 11 Sep

Re: svn commit: r1760391 - in /commons/proper/beanutils/trunk/src: main/java/org/apache/commons/beanutils/PropertyUtilsBean.java test/java/org/apache/commons/beanutils/bugs/Jira492TestCase.java

2016-09-14 Thread Stian Soiland-Reyes
Yes, perhaps this tester method should be shared across the affected test cases. Now it's kind of copied to use the particular bean class under test, some of which were inner classes. On 14 Sep 2016 7:23 a.m., "Benedikt Ritter" wrote: > Hello, > > schrieb

[REMINDER][VOTE][RC1] Release Commons Rng 1.0

2016-09-14 Thread Gilles
Original Message Subject: [VOTE][RC1] Release Commons Rng 1.0 Date: Sun, 11 Sep 2016 16:55:42 +0200 From: Gilles To: Commons Developers List Reply-To: "Commons Developers List" Hi. This is a

Re: Another BeanUtils 1.9.3 RC?

2016-09-14 Thread Stian Soiland-Reyes
OK, I'll start :-) On 13 Sep 2016 7:34 p.m., "Gary Gregory" wrote: > On Tue, Sep 13, 2016 at 7:12 AM, Raviteja Lokineni < > raviteja.lokin...@gmail.com> wrote: > > > I guess then we are good for release of RC, right? > > > > It looks like it. :-) > > Gary > > > > > > On

Re: [VOTE] Release Commons BeanUtils 1.9.3 RC2

2016-09-14 Thread Stian Soiland-Reyes
On 14 September 2016 at 23:34, Gary Gregory wrote: > Curious: what does "Semantic Versioning: 0.0.1" mean? And that what we > really want? I guess you mean as in https://stain.github.io/commons-beanutils/1.9.3-rc2/japicmp.html It's showing the calculated version

Broken links on BCEL website

2016-09-14 Thread Stian Soiland-Reyes
Hi, There were quite a few broken links on the front page of https://commons.apache.org/proper/commons-bcel/ I fixed directly in site-SVN (and in the source-SVN) on index.html: 6.0 Download link (!) Javadoc link release note links Still the menu shows two javadoc entries: Javadoc (Latest

Re: [VOTE] Release Commons BeanUtils 1.9.3 RC2

2016-09-14 Thread Gary Gregory
Curious: what does "Semantic Versioning: 0.0.1" mean? And that what we really want? Gary On Sep 14, 2016 8:46 AM, "Stian Soiland-Reyes" wrote: > This is a [VOTE] for releasing Apache Commons BeanUtils 1.9.3 (from RC2) > > > SVN tag: >

Re: [VOTE] Release Commons BeanUtils 1.9.3 RC2

2016-09-14 Thread Gary Gregory
>From the src zip: MD5, SHA1, ASC OK. -1 because I cannot run 'mvn clean site' not matter what version of Java I use: 6, 7, or 8. Users must be able to download the source zip or checkout this release tag, apply mods and rebuild and see that they did not cause regressions or break things.

Re: [RDF] Implementation class name style

2016-09-14 Thread Stian Soiland-Reyes
On 13 Sep 2016 2:15 a.m., "Gary Gregory" wrote: > > For names, I like CamelCaseEvenForAcronyms, like IbmXmlSaxParser instead of > IBMXMLSAXParser. As well :-) And I am not sure which class or package prefix to use for JSONLD-Java.. JsonLd is what is used within its

Re: [REMINDER][VOTE][RC1] Release Commons Rng 1.0

2016-09-14 Thread Stian Soiland-Reyes
On 14 Sep 2016 3:32 p.m., "Gilles" wrote: > The site can, and will be fixed, "live" (as it must be done anyway for > the link to the Javadoc, see below). I think it's good we keep the practice of reviewing the website as part of an RC, as otherwise it won't happen,

Re: [RDF] adaptation methods in RDFTermFactory

2016-09-14 Thread Stian Soiland-Reyes
You mean to add unwrap() to the implementation classes? So it would just do a cast? But we have an operator for that in Java... :-) If you mean to add it to RDFTermFactory as a different name/style for the many asSomething() methods, perhaps just as the name as()? That is how Jena does it, to

Re: [RDF] Implementation class name style

2016-09-14 Thread Peter Ansell
JSONLD-Java switched to JsonLd, after originally using uppercased versions, to match the terminology casing used by the final JSON-LD-API-1.0 specification: https://www.w3.org/TR/json-ld-api/#the-application-programming-interface The capitalisation in the project name is just kept for posterity

Re: [RDF] jena, rdf4j, json-ld integrations

2016-09-14 Thread Stian Soiland-Reyes
On 13 Sep 2016 5:14 a.m., "Peter Ansell" wrote: > Sesame-4 will not have any more releases due to the Eclipse migration, > so you will not have a large user-base for that. Even maintaining a > Sesame-2.8 module may not find many users, as users who are still > using it for