Re: [VOTE] Release Apache Commons CSV 1.6 based on RC1

[Sergio Fernández]

+1 (non-binding)

On Wed, Sep 19, 2018, 05:31 Benedikt Ritter  wrote:

> Hi,
>
> we have fixed some bugs and added some features since Commons CSV 1.5 has
> been released, so I would like to release Commons CSV 1.6 based on RC1
>
> Commons CSV 1.6 is available for review here:
>   https://dist.apache.org/repos/dist/dev/commons/csv/1.6-RC1/ (r29508)
>
> The tag is here:
>
>
> https://git-wip-us.apache.org/repos/asf?p=commons-csv.git;a=tag;h=3c2d7919f325d1f046dff55e139455693cc68005
>
> The Maven Artifacts are here:
>
>
> https://repository.apache.org/content/repositories/orgapachecommons-1380/org/apache/commons/commons-csv/1.6/
>
> These are the Maven Artifacts and their hashes:
> /org/apache/commons/commons-csv/1.6/commons-csv-1.6-sources.jar.asc
> <
> https://repository.apache.org/content/repositories/orgapachecommons-1380/org/apache/commons/commons-csv/1.6/commons-csv-1.6-sources.jar.asc
> >
> (SHA1: 5ca098877478f554085dace80ef4bf484ec422c0)
> /org/apache/commons/commons-csv/1.6/commons-csv-1.6.jar.asc
> <
> https://repository.apache.org/content/repositories/orgapachecommons-1380/org/apache/commons/commons-csv/1.6/commons-csv-1.6.jar.asc
> >
> (SHA1: 2c637fa312b01e091b6bf5388bca4c40890b6f8a)
> /org/apache/commons/commons-csv/1.6/commons-csv-1.6-test-sources.jar.asc
> <
> https://repository.apache.org/content/repositories/orgapachecommons-1380/org/apache/commons/commons-csv/1.6/commons-csv-1.6-test-sources.jar.asc
> >
> (SHA1: 3ac363851526e57f0b833faf9ae58d93769df377)
> /org/apache/commons/commons-csv/1.6/commons-csv-1.6.jar
> <
> https://repository.apache.org/content/repositories/orgapachecommons-1380/org/apache/commons/commons-csv/1.6/commons-csv-1.6.jar
> >
> (SHA1: 22b3c2f901af973a8ec4f24e80c8c0c77a600b79)
> /org/apache/commons/commons-csv/1.6/commons-csv-1.6.pom
> <
> https://repository.apache.org/content/repositories/orgapachecommons-1380/org/apache/commons/commons-csv/1.6/commons-csv-1.6.pom
> >
> (SHA1: 7d6919d5b7f35a736631b37cf07c6e146e02e2d6)
> /org/apache/commons/commons-csv/1.6/commons-csv-1.6-javadoc.jar
> <
> https://repository.apache.org/content/repositories/orgapachecommons-1380/org/apache/commons/commons-csv/1.6/commons-csv-1.6-javadoc.jar
> >
> (SHA1: 1a912bc6e79af7903600cbc9ee7c365ee356c9af)
> /org/apache/commons/commons-csv/1.6/commons-csv-1.6.pom.asc
> <
> https://repository.apache.org/content/repositories/orgapachecommons-1380/org/apache/commons/commons-csv/1.6/commons-csv-1.6.pom.asc
> >
> (SHA1: 122fd1dd76797a3df6e21de7269f65843ade912c)
> /org/apache/commons/commons-csv/1.6/commons-csv-1.6-tests.jar
> <
> https://repository.apache.org/content/repositories/orgapachecommons-1380/org/apache/commons/commons-csv/1.6/commons-csv-1.6-tests.jar
> >
> (SHA1: 25316661324eacc7f8f61a9f389cb9efe034e43f)
> /org/apache/commons/commons-csv/1.6/commons-csv-1.6-sources.jar
> <
> https://repository.apache.org/content/repositories/orgapachecommons-1380/org/apache/commons/commons-csv/1.6/commons-csv-1.6-sources.jar
> >
> (SHA1: 7163d5c8c70c71d32507583a3f6297302b32fa71)
> /org/apache/commons/commons-csv/1.6/commons-csv-1.6-tests.jar.asc
> <
> https://repository.apache.org/content/repositories/orgapachecommons-1380/org/apache/commons/commons-csv/1.6/commons-csv-1.6-tests.jar.asc
> >
> (SHA1: 0f148adef1676bb532170a6e4fffbbcf98f69dd5)
> /org/apache/commons/commons-csv/1.6/commons-csv-1.6-test-sources.jar
> <
> https://repository.apache.org/content/repositories/orgapachecommons-1380/org/apache/commons/commons-csv/1.6/commons-csv-1.6-test-sources.jar
> >
> (SHA1: 5c5d54b48c86d4972a9894dbf35edcdc5656930f)
> /org/apache/commons/commons-csv/1.6/commons-csv-1.6-javadoc.jar.asc
> <
> https://repository.apache.org/content/repositories/orgapachecommons-1380/org/apache/commons/commons-csv/1.6/commons-csv-1.6-javadoc.jar.asc
> >
> (SHA1: 2f03131beeab5cf5c38e0b19e85bd0d8dfe14fd2)
>
> I have tested this with Java 8 using Maven 3.5.4.
>
> Details of changes since 1.1 are in the release notes:
>
>
> https://dist.apache.org/repos/dist/dev/commons/csv/1.6-RC1/RELEASE-NOTES.txt
>
>
> http://home.apache.org/~britter/commons/commons-csv-1.6-RC1/changes-report.html
>
> Site:
>   http://home.apache.org/~britter/commons/commons-csv-1.6-RC1/
> (note some *relative* links are broken and the 1.6 directories are not yet
> created - these will be OK once the site is deployed)
>
> Clirr Report (compared to 1.5):
>
>
> http://home.apache.org/~britter/commons/commons-csv-1.6-RC1/clirr-report.html
>
> RAT Report:
>
> http://home.apache.org/~britter/commons/commons-csv-1.6-RC1/rat-report.html
>
> KEYS:
>   https://www.apache.org/dist/commons/KEYS
>
> Please review this release candidate and vote. This vote will close no
> sooner than 72 hours from now, i.e. sometime after 14:30 CEST 22-September
> 2018
>
>   [ ] +1 Release these artifacts
>   [ ] +0 OK, but...
>   [ ] -0 OK, but really should fix...
>   [ ] -1 I oppose this release because...
>
> Thanks!
> Benedikt
>

Re: [VOTE] Release Apache Commons DBCP 2.4.0 based on RC1

[Sergio Fernández]

+1 (non-binding)

On Wed, Jun 13, 2018, 12:51 Gary Gregory  wrote:

> We have fixed quite a few bugs and added some significant enhancements
> since Apache Commons DBCP 2.3.0 was released, so I would like to release
> Apache Commons DBCP 2.4.0.
>
> Apache Commons DBCP 2.4.0 RC1 is available for review here:
> https://dist.apache.org/repos/dist/dev/commons/dbcp/2.4.0-RC1 (svn
> revision 27438)
>
> The Git tag commons-dbcp-2.4.0-RC1 commit for this RC is
> d7aa662fbbb99e536ae28c47d0c4e1d51e39d5b9 which you can browse here:
>
>
> https://git-wip-us.apache.org/repos/asf?p=commons-dbcp.git;a=tag;h=refs/tags/commons-dbcp-2.4.0-RC1
>
> Maven artifacts are here:
>
>
> https://repository.apache.org/content/repositories/orgapachecommons-1333/org/apache/commons/commons-dbcp2/2.4.0/
>
> These are the Maven artifacts and their hashes in Nexus:
>
> #Release SHA-1s
> #Wed Jun 13 13:32:41 MDT 2018
> commons-dbcp2-2.4.0-bin-tar.gz.asc=064e744553fddd0c8c45aeb998429546c773eefc
> commons-dbcp2-2.4.0-src-zip=fb3157fa431b3dd059c8bed81c93f93160daba75
>
> commons-dbcp2-2.4.0-javadoc-jar.asc=a2fbc96c6b8553b13b4f2ed653d9aa5717e89842
>
> commons-dbcp2-2.4.0-test-sources-java-source=a8cb680bd20e46b548413ab4f3159a1b6af370fc
>
> commons-dbcp2-2.4.0-test-sources-jar.asc=e073bc4700757d6b6d66a84989ba9f72b85fa2d4
> commons-dbcp2-2.4.0-bin-zip.asc=74d108cbbbc0099f87d1536f92b59b5eb1b3657c
> commons-dbcp2-2.4.0-bin-zip=fda0585ae3d6cdb64091ffac630806cf1f781e7f
>
> commons-dbcp2-2.4.0-sources-java-source=f3a963f855209e9b4a18ea642a3a01adb95d8946
> commons-dbcp2-2.4.0-src-tar.gz=fef764329584d12053c20e50ed628822f22d2728
>
> commons-dbcp2-2.4.0-javadoc-javadoc=46cfd110cc0002c5f37bc6965e0149ec208ef458
> commons-dbcp2-2.4.0-bin-tar.gz=382feff1078882750981b91d810117fefe590047
> commons-dbcp2-2.4.0-src-tar.gz.asc=00d53b490f2631b2b7515e673cd6063c58c9b4fc
> commons-dbcp2-2.4.0-src-zip.asc=7aeaba88bf4a7459e8f20515ba6f26886a0f9702
> commons-dbcp2-2.4.0-null-pom.asc=df3fbc3dc6460cba003b16f8eba13ed3ffd8beef
> commons-dbcp2-2.4.0-tests-jar.asc=51051e26c5eb6c76e4dbf9523e9c9f22be548343
>
> commons-dbcp2-2.4.0-sources-jar.asc=b3a3467cf022728806eb2db63ca0c1fa76f9a5f4
> commons-dbcp2-2.4.0-tests-test-jar=8546d77cf33dbe35145fbcbd4890f29a673b6e97
> commons-dbcp2-2.4.0-null-jar.asc=3352f1b1ab04452445709d19272449bc5238d735
>
> #Release SHA-256s
> #Wed Jun 13 13:32:41 MDT 2018
>
> commons-dbcp2-2.4.0-bin-tar.gz.asc=530eec11fd24e47a9ef0917f6b2e34f7d3eef7e83089b421fab907c54ebcec8d
>
> commons-dbcp2-2.4.0-src-zip=eb1ee5760dd9e8875f2950297c20dee7307eff09e02a348c621cb5fad9d44a63
>
> commons-dbcp2-2.4.0-javadoc-jar.asc=48c4e82ed05f6ba2c0aafcddc810ef5388c5ab063cd982bec0708fe0d09f75a8
>
> commons-dbcp2-2.4.0-test-sources-java-source=da10f54b4705e706b57b372581b982bc1dcec21ee574864785c54c201fd0
>
> commons-dbcp2-2.4.0-test-sources-jar.asc=7952567ebe6071ebc95bf9c50ad07f2fb0188876130b770d063bf81170657107
>
> commons-dbcp2-2.4.0-bin-zip.asc=95aaa78797145eac624b03389c44a1e0f77c4babb53cf5b2cd436f342ae3a2da
>
> commons-dbcp2-2.4.0-bin-zip=7f87a408dcfaf9ff94fbbd7c1fa6b21a071c0a61ca869c44e749a1fe579b6ca8
>
> commons-dbcp2-2.4.0-sources-java-source=fd36da64513813e6c12a9f101ed6f8b7838834283893dd5654a76f4c39a9
>
> commons-dbcp2-2.4.0-src-tar.gz=a9b305f623f8c45e6bb392aaf5c045248ff7f326aba69bc6db0869947179ce0e
>
> commons-dbcp2-2.4.0-javadoc-javadoc=27ec0b63947ba5e3bdc5a7fdac592590ca74aa35ece35e5eacee73a5cfc61dce
>
> commons-dbcp2-2.4.0-bin-tar.gz=7a88aca498cd1547e4e15f80ce7dfa89425a6a00c9fe93bbd6f94afee2150c4d
>
> commons-dbcp2-2.4.0-src-tar.gz.asc=115344f789d33094b6d8e8be50562337dc9f62881105b61fedeca17f9b9c20e4
>
> commons-dbcp2-2.4.0-src-zip.asc=2f9a10da8df8bb1d283afb3a7f6567fe1354c60fb97b4bce7766dff3041c1a64
>
> commons-dbcp2-2.4.0-null-pom.asc=a841c9899ef5c341a26b2e4145f7c215c568e577a417d5641201a24686e33450
>
> commons-dbcp2-2.4.0-tests-jar.asc=fbe62bf9d4c0d3db92bfa53215d640d5677f7403665ccdee8f0fab6f205e42fa
>
> commons-dbcp2-2.4.0-sources-jar.asc=550a5fd3427da1aec9fe9c6bcb2935aaf4daf68f098dd2769cab4089cc373c48
>
> commons-dbcp2-2.4.0-tests-test-jar=6f5f5114aa25905a88f2912e2c3425dbb97ae4a6c79daaf5ee5ed98a95dfaca7
>
> commons-dbcp2-2.4.0-null-jar.asc=a8c4e8405ecc14b9aeba997c2886bfe740dd074333bd7164bc4489ce0470bf4b
>
> I have tested this with ***'mvn clean install site'*** using:
> Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297;
> 2018-02-24T12:49:05-07:00)
> Maven home: C:\Java\apache-maven-3.5.3\bin\..
> Java version: 1.8.0_172, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk1.8.0_172\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
>
> Details of changes since 2.3.0 are in the release notes:
>
>
> https://dist.apache.org/repos/dist/dev/commons/dbcp/2.4.0-RC1/RELEASE-NOTES.txt
>
>
> https://dist.apache.org/repos/dist/dev/commons/dbcp/2.4.0-RC1/site/changes-report.html
>
> Site:
> https://dist.apache.org/repos/dist/dev/commons/dbcp/2.4.0-RC1/site
> (note 

Re: Fwd: [jira] [Created] (COMDEV-248) add /dist/ health issues

[Sergio Fernández]

betwixt removed from the dist area in r24307

On Tue, Jan 16, 2018 at 9:15 AM, Sergio Fernández <wik...@apache.org> wrote:

> Hi Gilles,
>
> On Thu, Jan 11, 2018 at 3:41 AM, Gilles <gil...@harfang.homelinux.org>
> wrote:
>
>> On Thu, 11 Jan 2018 12:35:35 +0100, Sergio Fernández wrote:
>>
>>> From ComDev, just discovered checker.a.o, and got into the following
>>> report
>>> with problems:
>>>
>>> https://checker.apache.org/projs/commons.html
>>>
>>> What do we usually do with such problems on dormant components?
>>>
>>
>> IIUC, this
>>   http://www.apache.org/legal/release-policy.html#when-to-archive
>> says that they must be removed from the "dist" area.
>>
>
> Then I'll do so later from home, if I have enough karma.
>
> Cheers,
>
>
>

Re: Fwd: [jira] [Created] (COMDEV-248) add /dist/ health issues

[Sergio Fernández]

Hi Gilles,

On Thu, Jan 11, 2018 at 3:41 AM, Gilles <gil...@harfang.homelinux.org>
wrote:

> On Thu, 11 Jan 2018 12:35:35 +0100, Sergio Fernández wrote:
>
>> From ComDev, just discovered checker.a.o, and got into the following
>> report
>> with problems:
>>
>> https://checker.apache.org/projs/commons.html
>>
>> What do we usually do with such problems on dormant components?
>>
>
> IIUC, this
>   http://www.apache.org/legal/release-policy.html#when-to-archive
> says that they must be removed from the "dist" area.
>

Then I'll do so later from home, if I have enough karma.

Cheers,

Re: [Statistics] Language level

[Sergio Fernández]

I think the de facto rule for all new components should be the current JDK
LTS.

So +1 for Java 8.

On Jan 15, 2018 15:01, "Gilles"  wrote:

> Hi
>
> Which should we target for that component?
> IOW, has someone a case for less than Java 8?
>
> Gilles
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>

Re: [Net] When should we update net from Java 6 to 7?

[Sergio Fernández]

Is the any implementation requiring to upgrade? IMO always the lower, the
better.

On Jan 12, 2018 18:54, "Gary Gregory"  wrote:

> Hi All:
>
> When should we update Commons Net from Java 6 to 7?
>
> Gary
>

Fwd: [jira] [Created] (COMDEV-248) add /dist/ health issues

[Sergio Fernández]

>From ComDev, just discovered checker.a.o, and got into the following report
with problems:

https://checker.apache.org/projs/commons.html

What do we usually do with such problems on dormant components?




-- Forwarded message --
From: Henk Penning (JIRA) 
Date: Thu, Jan 11, 2018 at 10:47 AM
Subject: [jira] [Created] (COMDEV-248) add /dist/ health issues
To: d...@community.apache.org


Henk Penning created COMDEV-248:
---

 Summary: add /dist/ health issues
 Key: COMDEV-248
 URL: https://issues.apache.org/jira/browse/COMDEV-248
 Project: Community Development
  Issue Type: Improvement
  Components: Reporter Tool
Reporter: Henk Penning


checker.apache.org reports /dist/ health issues, summarized in
https://checker.apache.org/json/

Perhaps this info can be included in the project's report.

I believe checker.apache.org only reports real problems ;
problems that the PMC should (and can) fix.

Of course I hope that including this info in the report, will result a
healtier /dist/.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

Re: [VOTE] Release Commons Release Plugin 1.0 base on RC1

[Sergio Fernández]

What about casting this first release as 0.1?

Then we solve the chicken & egg problem: we can verify it the actual
components before releasing 1.0 (which semantically speaking has a strong
meaning.


On Jan 11, 2018 04:35, "Gary Gregory"  wrote:

I wonder if:
- This should be a LAZY VOTE since this is not an official component but
rather a tool
- We should release it as 1.0 anyway (unless obvious bugs are found) to
avoid the chicken and egg problem: To really test this, I want to create an
RC for Commons Collection (for example). But that means using a
commons-release-plugin 1.0 version in my POM - which we cannot release as a
repeatable build since 1.0 is not out yet. And cutting an RC with a
1.0-SNAPSHOT is not acceptable (not repeatable.)

Gary

On Wed, Jan 10, 2018 at 7:50 PM, Rob Tompkins  wrote:

> Hello all,
>
> This is a [VOTE] for releasing Apache commons-release-plugin 1.0 (from
> RC1).
>
> Tag name:
>commons-release-plugin-1.0-RC1 (signature can be checked from git using
> 'git tag -v')
>
> Tag URL:
>https://git-wip-us.apache.org/repos/asf?p=commons-release-
> plugin.git;a=tag;h=6b05b8bee894ad471c5e1eda979550b344c21020
>
> Commit ID the tag points at:
>2f48a0ebd07318419b4d92a7e7b594f4fca47428
>
> Site:
>https://dist.apache.org/repos/dist/dev/commons/commons-
> release-plugin/site.zip
>
> Distribution files (committed at revision 24125):
>https://dist.apache.org/repos/dist/dev/commons/commons-release-plugin/
>
> Distribution files hashes (SHA1):
>   commons-release-plugin-1.0-bin.tar.gz
>   (SHA1: 02a0e034ed89c87e620ceaf4aef879121d4b87de)
>   commons-release-plugin-1.0-bin.zip
>   (SHA1: e0c4cf6449f6baab4c52c98c1e577512486d8fba)
>   commons-release-plugin-1.0-src.tar.gz
>   (SHA1: e48b67b70b154b7dc69914752814512225024504)
>   commons-release-plugin-1.0-src.zip
>   (SHA1: bc9a6c847899b2700e5873c4ac1a8d983476b255)
>
> These are the Maven artifacts and their hashes:
>   commons-release-plugin-1.0-javadoc.jar
>   (SHA1: bc2cdfa56f55ee538087038a1194ea2789863ca9)
>   commons-release-plugin-1.0-sources.jar
>   (SHA1: eb20eec8580fd5a2633bd2822e951d57043d3d4e)
>   commons-release-plugin-1.0-test-sources.jar
>   (SHA1: 61aa51b44025ced470b0e21b19a3eb65e154df1f)
>   commons-release-plugin-1.0-tests.jar
>   (SHA1: a81f42e01ca77a86048e07963d4ea496a69251f6)
>   commons-release-plugin-1.0.jar
>   (SHA1: 2897ab01d2e8460d100d196db55e53b2a1bab73e)
>   commons-release-plugin-1.0.pom
>   (SHA1: 2bcc663eb212f9a2233acc21773ef80883ac0881)
>
> KEYS file to check signatures:
>http://www.apache.org/dist/commons/KEYS
>
> Maven artifacts:
>https://repository.apache.org/content/repositories/
> orgapachecommons-1302
>
> Please select one of the following options[1]:
>   [ ] +1 Release it.
>   [ ] +0 Go ahead; I don't care.
>   [ ] -0 There are a few minor glitches: ...
>   [ ] -1 No, do not release it because ...
>
>
> This vote will be open at least 72 hours, i.e. until
> 2018-01-14T03:00:00Z
> (this is UTC time).
>
> 
>
> Cheers,
> -Rob
>
> [1] http://apache.org/foundation/voting.html
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>

[collections] new fluent/builder api

[Sergio Fernández]

As Gary just did for iterator/iterable methods, I'd like to discuss the
idea of adding fluent/builder api.

I can draft the methods if people agree on that addition.

Re: [math][statistics] StatUtils

[Sergio Fernández]

Me neither. But, on the other hand, is not StringUtils the most used class
across all the Commons components? Just to understand how people will
actually make use of the new library.

On Jan 5, 2018 02:35, "Gary Gregory"  wrote:

I am not a fan of call classes SomethingUtils, it feels like a cop out.

Gary

On Jan 4, 2018 5:55 PM, "Gilles"  wrote:

> On Thu, 4 Jan 2018 17:25:17 -0700, Gary Gregory wrote:
>
>> Hi All,
>>
>> I'm not sure where we are WRT [math] spawning [statistics] but it would
be
>> nice if the StatUtils classs would work with Objects like
>> java.time.Duration, as in StatUtils.mean(Duration[])
>>
>
> Waiting for JIRA to be set up:
>   https://issues.apache.org/jira/servicedesk/agent/INFRA/issue/INFRA-15768
>
> [Then we can start populating it with feature requests.]
>
> Regards,
> Gilles
>
> P.S. We should probably rethink "StatUtils"...
>  And "Duration" being quite specific, it would warrant utilities
>  in their own module.
>
>
>> Gary
>>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>

Re: [VOTE] Create new component commons-release-plugin

[Sergio Fernández]

+1

On Jan 4, 2018 17:56, "Rob Tompkins"  wrote:

> Hello all,
>
> I propose that we create a new component [commons-release-plugin] to be
> managed in the same fashion as the commons-build-plugin, and by that I mean:
>
> * Use COMMONSSITE as the jira area
> * Create a git repo
> * Include it in the same portion of the site as the build-plugin (i.e. not
> a formal component.
>
> . Upon this vote completion (assuming it passes), I will create a git
> repository and migrate the code that I have currently in
> https://github.com/chtompki/commons-release-plugin <
> https://github.com/chtompki/commons-release-plugin> into this repository.
>
> Please review the release proposal and vote.
> This vote will close no sooner that 72 hours from now,
> i.e. sometime after 17:00 UTC 7-January 2018
>
>   [ ] +1 Create the component
>   [ ] +0 OK, but...
>   [ ] -0 OK, but really should fix...
>   [ ] -1 I oppose this component because…
>
> Cheers,
> -Rob

Re: [ALL] Who want's access to @ApacheCommons

[Sergio Fernández]

On Dec 30, 2017 12:01, "Benedikt Ritter" <brit...@apache.org> wrote:

> Am 27.12.2017 um 18:10 schrieb Sergio Fernández <wik...@apache.org>:
> I'm happy to help on that, but I'm just a raw committer, not sure if it
> would be appropriate.

Sure thing! Just give me your twitter handle and I’ll add you.


@wikier

Re: [ALL] Who want's access to @ApacheCommons

[Sergio Fernández]

I guess if the people managing the account could just RT the
project-related tweets (particularly announcements), I think that would be
great.

I'm happy to help on that, but I'm just a raw committer, not sure if it
would be appropriate.

On Tue, Dec 26, 2017 at 2:22 AM, Benedikt Ritter  wrote:

> Hi,
>
> I’ve created the Apache Commons twitter account [1] a few years ago. I try
> to announce anything that might be of interest for Commons users. Since my
> activity for the project varies a bit depending on what is going on in my
> life, I think it would be good if more people would have access to the
> twitter account.
> Twitter has ha nice feature, called Teams, where you can give other
> Twitter users access to a team account. So if anybody wants to have access,
> just ping me with your Twitter user name and I can grant you access.
>
> Regards,
> Benedikt
>
> [1] https://twitter.com/ApacheCommons
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>

[ANNOUNCE] Apache Commons RDF 0.5.0 released

[Sergio Fernández]

The Apache Commons RDF team is pleased to announce the release of Apache
Commons RDF 0.5.0.

Commons RDF aims to provide a common library for RDF 1.1 that could be
implemented by systems on the Java Virtual Machine.

The Apache Commons RDF distribution includes bindings for different
implementations: Commons RDF Simple, Apache Jena, Eclipse RDF4J (formerly
OpenRDF Sesame) and JSONLD-Java.

No client code changes are required to migrate from version
0.3.0-incubating
to version 0.5.0.

For complete information on Apache Commons RDF, including downloads,
instructions on how to submit bug reports, patches, or suggestions for
improvement,
see the Apache Apache Commons RDF website:

https://commons.apache.org/rdf

Enjoy!
Sergio Fernández, on behalf of the Apache Commons Team

[RESULT] [VOTE] Release Apache Commons RDF 0.5.0 based on RC3

[Sergio Fernández]

Hi,

This VOTE passes with 3 +1 VOTEs from the following PMC members:

- Gary Gregory
- Jörg Schaible
- Bruno P. Kinoshita

In addition, thank you to the following for casting 3 +1 non-binding VOTEs:

- Aaron Coburn
- Adam Soroka
- Sergio Fernández

I will proceed with the release.

Thank you all,
Sergio



On Thu, Dec 7, 2017 at 8:51 PM, Sergio Fernández <wik...@apache.org> wrote:

> Hi,
>
> once we addressed most of the issues from RC1 and RC2, I'd like to propose
> to release Apache Commons RDF 0.5.0 based on RC.
>
> Apache Commons RDF aims to provide a common Java API for RDF 1.1 graphs
> and datasets. API bindings in Commons RDF 0.5.0 include Apache Jena,
> Eclipse RDF4J, JSON-LD Java as well as a standalone implementation (simple).
>
> Apache Commons RDF 0.5.0 RC3 is available for review at (r23441):
>
> https://dist.apache.org/repos/dist/dev/commons/rdf/apache-co
> mmons-rdf-0.5.0-RC3/
>
> The source code for this RC is available from git tagged as 0.5.0-RC3
> (commit e82eaa0b7d67f5a1afdf4cdecc19589fbe1654d6):
>
> https://git-wip-us.apache.org/repos/asf?p=commons-rdf.git;a=
> commit;h=e82eaa0b7d67f5a1afdf4cdecc19589fbe1654d6
>
> Mirrored at https://github.com/apache/commons-rdf/commit/e82eaa0b7d67f5a
> 1afdf4cdecc19589fbe1654d6
>
> This source release produces the following binary artifacts:
>
> commons-rdf-parent-0.5.0
> commons-rdf-api-0.5.0
> commons-rdf-simple-0.5.0
> commons-rdf-jena-0.5.0
> commons-rdf-rdf4j-0.5.0
> commons-rdf-jsonld-java-0.5.0
> commons-rdf-integration-tests-0.5.0
>
> The Maven Staging repository can be found at:
>
> https://repository.apache.org/content/repositories/orgapachecommons-1295
>
> containing the following artifacts:
>
> commons-rdf-rdf4j-0.5.0.pom (SHA1: 1cdc74b7205fa06531bd59e1ee24f1
> d15999ab1b)
> commons-rdf-rdf4j-0.5.0.jar (SHA1: 265549b98b423c075f4a186dec76ef
> b815c03649)
> commons-rdf-rdf4j-0.5.0-tests.jar (SHA1: 9aab05dceefde27d79bc79f4b3c80d
> aeeb01cb52)
> commons-rdf-rdf4j-0.5.0-javadoc.jar (SHA1: 4254ac42dd569a45ab3b95c3d16cb8
> f47508039a)
> commons-rdf-rdf4j-0.5.0-test-sources.jar (SHA1:
> 39eb4a6b10cafa4cfb87b4e48827006332ceaed3)
> commons-rdf-rdf4j-0.5.0-sources.jar (SHA1: f8a0ea29f31f501df05686abfd171f
> 35fd39ed71)
> commons-rdf-api-0.5.0-sources.jar (SHA1: 02735a136e206408f75507fbf27af1
> 230a99f61b)
> commons-rdf-api-0.5.0.jar (SHA1: df2d4451dee5b311cb4f51ced214dfaab5838291)
> commons-rdf-api-0.5.0-tests.jar (SHA1: 025730515d0e66043b6483710a9638
> e1f71ff917)
> commons-rdf-api-0.5.0-javadoc.jar (SHA1: 3e15be3c7d018225aa6bafd9186147
> 4780c3ad8e)
> commons-rdf-api-0.5.0-test-sources.jar (SHA1:
> 5f2554c926de52b5661f430b69c92dac2056a029)
> commons-rdf-api-0.5.0.pom (SHA1: cc3382c3a60d815a20bba1763933434f41d85598)
> commons-rdf-simple-0.5.0-tests.jar (SHA1: 472e43e582ddcf1a7f06f9184f4bf2
> 6fad3b65fc)
> commons-rdf-simple-0.5.0.pom (SHA1: b5aa51f49cbbdb9f39fa70d8cf183f
> 63ae0c3a6a)
> commons-rdf-simple-0.5.0-javadoc.jar (SHA1: 87941fc168b6011fb003288eb39257
> 7fc4519be0)
> commons-rdf-simple-0.5.0-sources.jar (SHA1: 7232c14775db216efc85a1a7fabb90
> c6a456950c)
> commons-rdf-simple-0.5.0.jar (SHA1: c6b5038624d860129e273538d18dd5
> 2c5adcfd70)
> commons-rdf-simple-0.5.0-test-sources.jar (SHA1:
> 8028e8f20ebc465a6cd5a32fd9b8447eb4cf48dc)
> commons-rdf-parent-0.5.0-src.tar.gz (SHA1: 5b3788cb6b647f3663839fd0737a5a
> 85a75d19fa)
> commons-rdf-parent-0.5.0-src.zip (SHA1: 519891322ed75f3ae4ef5cf7e8df60
> c65b797634)
> commons-rdf-parent-0.5.0.pom (SHA1: 4186153db162b4382f73be1ce2ff97
> a98ee5d442)
> commons-rdf-parent-0.5.0-site.xml (SHA1: 26fd1dc487f5f002d35841ba8dcc53
> 704652d3b8)
> commons-rdf-integration-tests-0.5.0-test-sources.jar (SHA1:
> d7ad7ad0c09c3ae46d8da9c1ed989a9615369dcf)
> commons-rdf-integration-tests-0.5.0-tests.jar (SHA1:
> 0db5cb5a32afcad51decae42c6a7d4dc7e62f15a)
> commons-rdf-integration-tests-0.5.0.pom (SHA1:
> dc8b7754e2069b8c19c507a59a665ba12fd60007)
> commons-rdf-jena-0.5.0.pom (SHA1: a4a0f39e0428d0484074d1dde5368a
> 9f9ba2b065)
> commons-rdf-jena-0.5.0-sources.jar (SHA1: 51c8127914e5d7f3d8922375af08c5
> 24f1a5d403)
> commons-rdf-jena-0.5.0-test-sources.jar (SHA1:
> fb9cc23fd01210ec32c2c79a70204689359ab8c5)
> commons-rdf-jena-0.5.0-tests.jar (SHA1: e26df331facb7dff0ef837ba8fa390
> 00a2082048)
> commons-rdf-jena-0.5.0-javadoc.jar (SHA1: 3b8a9fc8aa8238b72c2ebd582a7778
> 24660dbdfe)
> commons-rdf-jena-0.5.0.jar (SHA1: a66e6c9e49082ceb14e98541fabf8b
> e060128853)
> commons-rdf-jsonld-java-0.5.0-test-sources.jar (SHA1:
> 26026e8f03e464b5601cb4eefeb32766352fe688)
> commons-rdf-jsonld-java-0.5.0.pom (SHA1: c6d30844d93a42761a0c54a25655b7
> cdc34bcfa5)
> commons-rdf-jsonld-java-0.5.0-javadoc.jar (SHA1:
> 3fc6b506ac788

Re: [VOTE] Release Apache Commons RDF 0.5.0 based on RC3

[Sergio Fernández]

Yeah, we'll try to prepare a 0.6 release to verify all those missing
details before moving to 1.0 somewhen in 2018.

Thanks for all the votes! I'll send inmediatelly the result mail.

On Thu, Dec 21, 2017 at 11:05 AM, Bruno P. Kinoshita 
wrote:

> +1 didn't take into consideration it was still a 0.x release. And happy to
> test it again or review pull requests later.
> ThanksBruno
>
> Sent from Yahoo Mail on Android
>
>   On Fri, 22 Dec 2017 at 7:57, ajs6f wrote:   I have
> some PRs in now for some of these issues, which I mention merely as
> reassurance that they will get looked at.
>
> ajs6f
>
> > On Dec 21, 2017, at 1:45 PM, Jörg Schaible 
> wrote:
> >
> > Hi Bruno,
> >
> > Am Wed, 13 Dec 2017 09:53:35 + schrieb Bruno P. Kinoshita:
> >
> > [snip]
> >
> >> I went through the  FindBugs/PMD reports in each module, and found the
> >> following warnings:
> >>
> >>
> >> * main module:
> >>- Double checked locking is not thread safe in Java. (saw it in
> >>another part, not sure if it's really possibe to fix as we need
> >>cannot create a model twice...)
> >>
> >> * commons-df-api:
> >>- Initialization of org.apache.commons.rdf.api.RDFSyntax accesses
> >>class
> >> org.apache.commons.rdf.api.W3CRDFSyntax, which isn't initialized yet
> >> (this one seems easy to reproduce. Always returns null?)
> >>
> >> * commons-rdf-simple:
> >>- org.apache.commons.rdf.simple.DatasetGraphView.unionOrNamedGraph()
> >>has Optional return type and returns explicit null (shouldn't it be
> >>Optional.empty() or something similar?)
> >>
> >>
> >> Are any of these blockers? The second one is the only one that if
> >> confirmed seems annoying to users.
> >>
> >>
> >> Everything looks OK, and I'm OK to vote to release in case others think
> >> this release is not actually causing any of these warnings, and that we
> >> should release as-is and fix it later.
> >
> > Since it it a 0.5 release, we can address that later. So, do you vote?
> >
> > Cheers,
> > Jörg
> >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> > For additional commands, e-mail: dev-h...@commons.apache.org
> >
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>

Re: [VOTE] Release Apache Commons DBCP 2.2.0 based on RC3

[Sergio Fernández]

+1 (non-binding)

So far I've checked:

* signatures and digests
* source releases file layouts,
* matched git tag and commit ids
* NOTICE and LICENSE files
* license headers
* build sources in a clean environment  (Maven 3.5.0, OpenJDK 1.8.0_144
64-Bit, Debian amd64)


On Thu, Dec 21, 2017 at 10:23 AM, Gary Gregory  wrote:

> We have fixed quite a few bugs and added some enhancements since Apache
> Commons DBCP 2.1.1 was released, so I would like to release Apache Commons
> DBCP 2.2.0.
>
> This is RC3 as we have tags in git for RC1 and RC2 which must have been a
> while back and failed.
>
> Apache Commons DBCP 2.2.0 RC3 is available for review here:
> https://dist.apache.org/repos/dist/dev/commons/dbcp/ (svn revision
> 23854)
>
> The tag is here:
>
> https://git-wip-us.apache.org/repos/asf?p=commons-dbcp.git;
> a=tag;h=refs/tags/DBCP_2_2_0_RC3
> commit c5b86d834a53b4891487e62671873d054a6f38d8
>
> Maven artifacts are here:
>
> https://repository.apache.org/content/repositories/
> orgapachecommons-1300/org/apache/commons/commons-dbcp2/2.2.0/
>
> These are the Maven artifacts and their hashes
>
> /org/apache/commons/commons-dbcp2/2.2.0/commons-dbcp2-2.2.
> 0-test-sources.jar.asc
> (SHA1: fc955715943f3140dd08bf32fd39a15e9c45cb68)
> /org/apache/commons/commons-dbcp2/2.2.0/commons-dbcp2-2.2.0.jar
> (SHA1: 88763be2c54a37dd0b2d5d735d268bd6a202a207)
> /org/apache/commons/commons-dbcp2/2.2.0/commons-dbcp2-2.2.0-tests.jar
> (SHA1: 4a643a2c2971392b614e5cd3724ae2605d885c14)
> /org/apache/commons/commons-dbcp2/2.2.0/commons-dbcp2-2.2.0-bin.zip
> (SHA1: f5701e71d6a22408f9084bd6745b2a7af491bd2e)
> /org/apache/commons/commons-dbcp2/2.2.0/commons-dbcp2-2.2.0-bin.zip.asc
> (SHA1: 4b9271766f40cfe7090c68b76f645b823b815035)
> /org/apache/commons/commons-dbcp2/2.2.0/commons-dbcp2-2.2.
> 0-sources.jar.asc
> (SHA1: 35f49997869eec9a142452aca5e80b65eb74bfc5)
> /org/apache/commons/commons-dbcp2/2.2.0/commons-dbcp2-2.2.0-bin.tar.gz.asc
> (SHA1: bd15765592e2bfef4d8ccb1ced8ef76fbef611b7)
> /org/apache/commons/commons-dbcp2/2.2.0/commons-dbcp2-2.2.0-src.zip
> (SHA1: 7f126d53d99180628c01697ee82c5b110f5a07e9)
> /org/apache/commons/commons-dbcp2/2.2.0/commons-dbcp2-2.2.0-javadoc.jar
> (SHA1: 7e2cec7febfab7fdb8d4d5f019be95b4cbb45054)
> /org/apache/commons/commons-dbcp2/2.2.0/commons-dbcp2-2.2.0-src.tar.gz.asc
> (SHA1: bc563a13704ada936cabcafe42bb050ac02e0d20)
> /org/apache/commons/commons-dbcp2/2.2.0/commons-dbcp2-2.2.0.jar.asc
> (SHA1: c8c71653d67b2e43b8b2f863cf068d43fa85e861)
> /org/apache/commons/commons-dbcp2/2.2.0/commons-dbcp2-2.2.0-src.tar.gz
> (SHA1: 1c0be2cebf9814b6e884aae2521862b3a80921a6)
> /org/apache/commons/commons-dbcp2/2.2.0/commons-dbcp2-2.2.
> 0-test-sources.jar
> (SHA1: f2817cf6fe0d527d643e322158b48d4053babdbd)
> /org/apache/commons/commons-dbcp2/2.2.0/commons-dbcp2-2.2.0-tests.jar.asc
> (SHA1: d45a46b33e7dbcc69097b00b808393a9bc57722f)
> /org/apache/commons/commons-dbcp2/2.2.0/commons-dbcp2-2.2.0-src.zip.asc
> (SHA1: 2803199436b1049672fd7e4b6f4e4ff9fd9dc5dd)
> /org/apache/commons/commons-dbcp2/2.2.0/commons-dbcp2-2.2.0.pom
> (SHA1: 187d6aea2c62b29ef9b41d86a4f79b7098659225)
> /org/apache/commons/commons-dbcp2/2.2.0/commons-dbcp2-2.2.
> 0-javadoc.jar.asc
> (SHA1: e703855abdf406c5f33f219e32c28d3a18b01763)
> /org/apache/commons/commons-dbcp2/2.2.0/commons-dbcp2-2.2.0-sources.jar
> (SHA1: 24ac7915f8a1cc224ae5bcc24022307179158bd3)
> /org/apache/commons/commons-dbcp2/2.2.0/commons-dbcp2-2.2.0.pom.asc
> (SHA1: 98d948d580280a7a85cc4605a0bec22109ab196a)
> /org/apache/commons/commons-dbcp2/2.2.0/commons-dbcp2-2.2.0-bin.tar.gz
> (SHA1: 258a4c43e1cd4fbc23f379b7157c93a652667378)
>
> I tested 'mvn clean verify' with:
>
> 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.7.0_80, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk1.7.0_80\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 8.1", version: "6.3", arch: "amd64", family: "windows"
>
> 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_152, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk1.8.0_152\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
>
> 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: 9.0.1, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk-9.0.1
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
>
> 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: 10-ea, vendor: Oracle Corporation
> Java home: 

Re: [VOTE] Release Apache Commons RDF 0.5.0 based on RC3

[Sergio Fernández]

Polite ping. We still need two binding votes to move forward with this RC.

On Dec 17, 2017 08:27, "Sergio Fernández" <wik...@apache.org> wrote:

> I'd like to kindly ask other Commons PMC members to check this release
> candidate, which VOTE is open for 10 days now. Thanks.
>
> On Dec 14, 2017 17:32, "Sergio Fernández" <wik...@apache.org> wrote:
>
>> Thanks Gary and Bruno; I'll register those things to be fixed for
>> upcoming releases.
>>
>> On Thu, Dec 14, 2017 at 8:42 AM, Gary Gregory <garydgreg...@gmail.com>
>> wrote:
>>
>>> I forgot to mention that a command line RAT check passed and a CLIRR
>>> check
>>> is irrelevant.
>>>
>>> Gary
>>>
>>> On Thu, Dec 14, 2017 at 9:17 AM, Gary Gregory <garydgreg...@gmail.com>
>>> wrote:
>>>
>>> > From sources zip: ASC, MD5, SHA1 OK.
>>> >
>>> > 'mvn clean install' and 'mvn site' build OK with:
>>> >
>>> > 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_152, vendor: Oracle Corporation
>>> > Java home: C:\Program Files\Java\jdk1.8.0_152\jre
>>> > Default locale: en_US, platform encoding: Cp1252
>>> > OS name: "windows 10", version: "10.0", arch: "amd64", family:
>>> "windows"
>>> >
>>> > The code needs clean up next, for example "Avoid modifiers which are
>>> > implied by the context". This means for example, that method decls in
>>> > interfaces do not need to be 'public', it is implied.
>>> >
>>> > You should also provide a site with the RC, either a full site on your
>>> > home.apache.org folder or as a zip file.
>>> >
>>> > +1
>>> >
>>> > Gary
>>> >
>>> > On Thu, Dec 7, 2017 at 9:51 PM, Sergio Fernández <wik...@apache.org>
>>> > wrote:
>>> >
>>> >> Hi,
>>> >>
>>> >> once we addressed most of the issues from RC1 and RC2, I'd like to
>>> propose
>>> >> to release Apache Commons RDF 0.5.0 based on RC.
>>> >>
>>> >> Apache Commons RDF aims to provide a common Java API for RDF 1.1
>>> graphs
>>> >> and
>>> >> datasets. API bindings in Commons RDF 0.5.0 include Apache Jena,
>>> Eclipse
>>> >> RDF4J, JSON-LD Java as well as a standalone implementation (simple).
>>> >>
>>> >> Apache Commons RDF 0.5.0 RC3 is available for review at (r23441):
>>> >>
>>> >> https://dist.apache.org/repos/dist/dev/commons/rdf/apache-
>>> >> commons-rdf-0.5.0-RC3/
>>> >>
>>> >> The source code for this RC is available from git tagged as 0.5.0-RC3
>>> >> (commit e82eaa0b7d67f5a1afdf4cdecc19589fbe1654d6):
>>> >>
>>> >> https://git-wip-us.apache.org/repos/asf?p=commons-rdf.git;a=commit;h=
>>> >> e82eaa0b7d67f5a1afdf4cdecc19589fbe1654d6
>>> >> <https://git-wip-us.apache.org/repos/asf?p=commons-rdf.git;a
>>> =commit;h=e82eaa0b7d67f5a1afdf4cdecc19589fbe1654d6>
>>> >>
>>> >> Mirrored at https://github.com/apache/commons-rdf/commit/
>>> >> e82eaa0b7d67f5a1afdf4cdecc19589fbe1654d6
>>> >>
>>> >> This source release produces the following binary artifacts:
>>> >>
>>> >> commons-rdf-parent-0.5.0
>>> >> commons-rdf-api-0.5.0
>>> >> commons-rdf-simple-0.5.0
>>> >> commons-rdf-jena-0.5.0
>>> >> commons-rdf-rdf4j-0.5.0
>>> >> commons-rdf-jsonld-java-0.5.0
>>> >> commons-rdf-integration-tests-0.5.0
>>> >>
>>> >> The Maven Staging repository can be found at:
>>> >>
>>> >> https://repository.apache.org/content/repositories/orgapache
>>> commons-1295
>>> >>
>>> >> containing the following artifacts:
>>> >>
>>> >> commons-rdf-rdf4j-0.5.0.pom (SHA1: 1cdc74b7205fa06531bd59e1ee24f1
>>> >> d15999ab1b)
>>> >> commons-rdf-rdf4j-0.5.0.jar (SHA1: 265549b98b423c075f4a186dec76ef
>>> >> b815c03649)
>>> >> commons-rdf-rdf4j-0.5.0-tests.jar (SHA1:
>>> >> 9aab05dceefde27d79bc79f4b3c80daeeb01c

Re: [VOTE] Release Apache Commons RDF 0.5.0 based on RC3

[Sergio Fernández]

I'd like to kindly ask other Commons PMC members to check this release
candidate, which VOTE is open for 10 days now. Thanks.

On Dec 14, 2017 17:32, "Sergio Fernández" <wik...@apache.org> wrote:

> Thanks Gary and Bruno; I'll register those things to be fixed for upcoming
> releases.
>
> On Thu, Dec 14, 2017 at 8:42 AM, Gary Gregory <garydgreg...@gmail.com>
> wrote:
>
>> I forgot to mention that a command line RAT check passed and a CLIRR check
>> is irrelevant.
>>
>> Gary
>>
>> On Thu, Dec 14, 2017 at 9:17 AM, Gary Gregory <garydgreg...@gmail.com>
>> wrote:
>>
>> > From sources zip: ASC, MD5, SHA1 OK.
>> >
>> > 'mvn clean install' and 'mvn site' build OK with:
>> >
>> > 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_152, vendor: Oracle Corporation
>> > Java home: C:\Program Files\Java\jdk1.8.0_152\jre
>> > Default locale: en_US, platform encoding: Cp1252
>> > OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
>> >
>> > The code needs clean up next, for example "Avoid modifiers which are
>> > implied by the context". This means for example, that method decls in
>> > interfaces do not need to be 'public', it is implied.
>> >
>> > You should also provide a site with the RC, either a full site on your
>> > home.apache.org folder or as a zip file.
>> >
>> > +1
>> >
>> > Gary
>> >
>> > On Thu, Dec 7, 2017 at 9:51 PM, Sergio Fernández <wik...@apache.org>
>> > wrote:
>> >
>> >> Hi,
>> >>
>> >> once we addressed most of the issues from RC1 and RC2, I'd like to
>> propose
>> >> to release Apache Commons RDF 0.5.0 based on RC.
>> >>
>> >> Apache Commons RDF aims to provide a common Java API for RDF 1.1 graphs
>> >> and
>> >> datasets. API bindings in Commons RDF 0.5.0 include Apache Jena,
>> Eclipse
>> >> RDF4J, JSON-LD Java as well as a standalone implementation (simple).
>> >>
>> >> Apache Commons RDF 0.5.0 RC3 is available for review at (r23441):
>> >>
>> >> https://dist.apache.org/repos/dist/dev/commons/rdf/apache-
>> >> commons-rdf-0.5.0-RC3/
>> >>
>> >> The source code for this RC is available from git tagged as 0.5.0-RC3
>> >> (commit e82eaa0b7d67f5a1afdf4cdecc19589fbe1654d6):
>> >>
>> >> https://git-wip-us.apache.org/repos/asf?p=commons-rdf.git;a=commit;h=
>> >> e82eaa0b7d67f5a1afdf4cdecc19589fbe1654d6
>> >> <https://git-wip-us.apache.org/repos/asf?p=commons-rdf.git;
>> a=commit;h=e82eaa0b7d67f5a1afdf4cdecc19589fbe1654d6>
>> >>
>> >> Mirrored at https://github.com/apache/commons-rdf/commit/
>> >> e82eaa0b7d67f5a1afdf4cdecc19589fbe1654d6
>> >>
>> >> This source release produces the following binary artifacts:
>> >>
>> >> commons-rdf-parent-0.5.0
>> >> commons-rdf-api-0.5.0
>> >> commons-rdf-simple-0.5.0
>> >> commons-rdf-jena-0.5.0
>> >> commons-rdf-rdf4j-0.5.0
>> >> commons-rdf-jsonld-java-0.5.0
>> >> commons-rdf-integration-tests-0.5.0
>> >>
>> >> The Maven Staging repository can be found at:
>> >>
>> >> https://repository.apache.org/content/repositories/orgapache
>> commons-1295
>> >>
>> >> containing the following artifacts:
>> >>
>> >> commons-rdf-rdf4j-0.5.0.pom (SHA1: 1cdc74b7205fa06531bd59e1ee24f1
>> >> d15999ab1b)
>> >> commons-rdf-rdf4j-0.5.0.jar (SHA1: 265549b98b423c075f4a186dec76ef
>> >> b815c03649)
>> >> commons-rdf-rdf4j-0.5.0-tests.jar (SHA1:
>> >> 9aab05dceefde27d79bc79f4b3c80daeeb01cb52)
>> >> commons-rdf-rdf4j-0.5.0-javadoc.jar (SHA1:
>> >> 4254ac42dd569a45ab3b95c3d16cb8f47508039a)
>> >> commons-rdf-rdf4j-0.5.0-test-sources.jar (SHA1:
>> >> 39eb4a6b10cafa4cfb87b4e48827006332ceaed3)
>> >> commons-rdf-rdf4j-0.5.0-sources.jar (SHA1:
>> >> f8a0ea29f31f501df05686abfd171f35fd39ed71)
>> >> commons-rdf-api-0.5.0-sources.jar (SHA1:
>> >> 02735a136e206408f75507fbf27af1230a99f61b)
>> >> commons-rdf-api-0.5.0.jar (SHA1: df2d4451dee5b311cb4f51ced214df
>> >> aab583

Re: [VOTE] Release Apache Commons Pool 2.5.0 based on RC1

[Sergio Fernández]

+1 (non-binding)

So far I've check:

* Source release matches with source repository.
* Signatures and digests.
* Checked headers, LICENSE and NOTICE files.
* Build (OpenJDK 1.8.0_144 with Maven 3.5.0)

On Dec 16, 2017 14:35, "Gary Gregory"  wrote:

> We have fixed quite a few bugs and added some  enhancements since Apache
> Commons Pool 2.4.3 was released, so I would like to release Apache Commons
> Pool 2.5.0.
>
> Apache Commons Pool 2.5.0 RC1 is available for review here:
> https://dist.apache.org/repos/dist/dev/commons/pool/ (svn revision
> 23755)
>
> The tag is here:
>
> https://git-wip-us.apache.org/repos/asf?p=commons-pool.git;a=tag;h=
> dac29bd1ce13349fd989ca279df178ff73935d1d
>
> Maven artifacts are here:
> https://repository.apache.org/content/repositories/
> orgapachecommons-1299
>
> These are the Maven artifacts and their hashes
>
>
> /org/apache/commons/commons-pool2/2.5.0/commons-pool2-2.5.0.jar.asc
> (SHA1: 8c1f55975ebfef185209c12429f587bc1256636e)
> /org/apache/commons/commons-pool2/2.5.0/commons-pool2-2.5.
> 0-javadoc.jar.asc
> (SHA1: 83d3316533c776413f2a0dd42526a6a31ac46e46)
> /org/apache/commons/commons-pool2/2.5.0/commons-pool2-2.5.0-sources.jar
> (SHA1: e2aae3697db27fd0de4d26c7d370e7d802eea3f6)
> /org/apache/commons/commons-pool2/2.5.0/commons-pool2-2.5.0.pom
> (SHA1: 2e13032776a6d3a641a58e1c1ea64bd605661130)
> /org/apache/commons/commons-pool2/2.5.0/commons-pool2-2.5.0-tests.jar
> (SHA1: af3d96706a0a45d143e5b479cfa8da8d3835ab47)
> /org/apache/commons/commons-pool2/2.5.0/commons-pool2-2.5.0-bin.zip.asc
> (SHA1: 3b54c00d08748dcbe7ab9a65d510bfa86f81f700)
> /org/apache/commons/commons-pool2/2.5.0/commons-pool2-2.5.0-tests.jar.asc
> (SHA1: 647578272eb02c850143965888f70d2e1d5e161e)
> /org/apache/commons/commons-pool2/2.5.0/commons-pool2-2.5.0-src.zip
> (SHA1: 6baf8c229e09252b3e158dcde61cfdbe21b31920)
> /org/apache/commons/commons-pool2/2.5.0/commons-pool2-2.5.
> 0-sources.jar.asc
> (SHA1: 7671f1a41493442091a87bea06ded52efe149af8)
> /org/apache/commons/commons-pool2/2.5.0/commons-pool2-2.5.0.jar
> (SHA1: cb7d05e6308ad795decc4a12ede671113c11dd98)
> /org/apache/commons/commons-pool2/2.5.0/commons-pool2-2.5.0-javadoc.jar
> (SHA1: ca115b4c6777d03cd5e172c517e14010719dd9fd)
> /org/apache/commons/commons-pool2/2.5.0/commons-pool2-2.5.0-src.tar.gz
> (SHA1: bd4fbc00e7ce2d294ffeda9d12ebda5265ad2fe3)
> /org/apache/commons/commons-pool2/2.5.0/commons-pool2-2.5.0-src.zip.asc
> (SHA1: 9ec1d48c147e5646ff39b61d14c5abefac401edc)
> /org/apache/commons/commons-pool2/2.5.0/commons-pool2-2.5.0.pom.asc
> (SHA1: 39f587b18ec6df7dbf5341f1e7b9da6353400578)
> /org/apache/commons/commons-pool2/2.5.0/commons-pool2-2.5.0-bin.zip
> (SHA1: 43b1b0b5662696f701c2be63cfc2f42fbc8f238e)
> /org/apache/commons/commons-pool2/2.5.0/commons-pool2-2.5.
> 0-test-sources.jar
> (SHA1: e7bfd87691e44a91c6ef19ba9076c1d7cc9f4147)
> /org/apache/commons/commons-pool2/2.5.0/commons-pool2-2.5.0-bin.tar.gz
> (SHA1: 00828dfb4830c2f69208d51e5db30737cbef44a3)
> /org/apache/commons/commons-pool2/2.5.0/commons-pool2-2.5.0-bin.tar.gz.asc
> (SHA1: 7b7e9ebfc54962aa5fd77b8847ac01caa527a644)
> /org/apache/commons/commons-pool2/2.5.0/commons-pool2-2.5.0-src.tar.gz.asc
> (SHA1: 09c73953f752cbe382ff862b15809e7c9be4ecd3)
> /org/apache/commons/commons-pool2/2.5.0/commons-pool2-2.5.
> 0-test-sources.jar.asc
> (SHA1: 1a09c518ea54bc9e5792091fddcdccdc18b58b61)
>
> I have tested 'mvn clean install' with:
>
> 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.7.0_80, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk1.7.0_80\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 8.1", version: "6.3", arch: "amd64", family: "windows"
>
> 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_152, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk1.8.0_152\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
>
> 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: 9.0.1, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk-9.0.1
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
>
> 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: 10-ea, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk-10
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
> Java(TM) SE Runtime Environment (build 10-ea+29)
> Java HotSpot(TM) 64-Bit Server VM 

Re: [VOTE] Release Apache Commons RDF 0.5.0 based on RC3

[Sergio Fernández]

Thanks Gary and Bruno; I'll register those things to be fixed for upcoming
releases.

On Thu, Dec 14, 2017 at 8:42 AM, Gary Gregory <garydgreg...@gmail.com>
wrote:

> I forgot to mention that a command line RAT check passed and a CLIRR check
> is irrelevant.
>
> Gary
>
> On Thu, Dec 14, 2017 at 9:17 AM, Gary Gregory <garydgreg...@gmail.com>
> wrote:
>
> > From sources zip: ASC, MD5, SHA1 OK.
> >
> > 'mvn clean install' and 'mvn site' build OK with:
> >
> > 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_152, vendor: Oracle Corporation
> > Java home: C:\Program Files\Java\jdk1.8.0_152\jre
> > Default locale: en_US, platform encoding: Cp1252
> > OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
> >
> > The code needs clean up next, for example "Avoid modifiers which are
> > implied by the context". This means for example, that method decls in
> > interfaces do not need to be 'public', it is implied.
> >
> > You should also provide a site with the RC, either a full site on your
> > home.apache.org folder or as a zip file.
> >
> > +1
> >
> > Gary
> >
> > On Thu, Dec 7, 2017 at 9:51 PM, Sergio Fernández <wik...@apache.org>
> > wrote:
> >
> >> Hi,
> >>
> >> once we addressed most of the issues from RC1 and RC2, I'd like to
> propose
> >> to release Apache Commons RDF 0.5.0 based on RC.
> >>
> >> Apache Commons RDF aims to provide a common Java API for RDF 1.1 graphs
> >> and
> >> datasets. API bindings in Commons RDF 0.5.0 include Apache Jena, Eclipse
> >> RDF4J, JSON-LD Java as well as a standalone implementation (simple).
> >>
> >> Apache Commons RDF 0.5.0 RC3 is available for review at (r23441):
> >>
> >> https://dist.apache.org/repos/dist/dev/commons/rdf/apache-
> >> commons-rdf-0.5.0-RC3/
> >>
> >> The source code for this RC is available from git tagged as 0.5.0-RC3
> >> (commit e82eaa0b7d67f5a1afdf4cdecc19589fbe1654d6):
> >>
> >> https://git-wip-us.apache.org/repos/asf?p=commons-rdf.git;a=commit;h=
> >> e82eaa0b7d67f5a1afdf4cdecc19589fbe1654d6
> >> <https://git-wip-us.apache.org/repos/asf?p=commons-rdf.git;a=commit;h=
> e82eaa0b7d67f5a1afdf4cdecc19589fbe1654d6>
> >>
> >> Mirrored at https://github.com/apache/commons-rdf/commit/
> >> e82eaa0b7d67f5a1afdf4cdecc19589fbe1654d6
> >>
> >> This source release produces the following binary artifacts:
> >>
> >> commons-rdf-parent-0.5.0
> >> commons-rdf-api-0.5.0
> >> commons-rdf-simple-0.5.0
> >> commons-rdf-jena-0.5.0
> >> commons-rdf-rdf4j-0.5.0
> >> commons-rdf-jsonld-java-0.5.0
> >> commons-rdf-integration-tests-0.5.0
> >>
> >> The Maven Staging repository can be found at:
> >>
> >> https://repository.apache.org/content/repositories/
> orgapachecommons-1295
> >>
> >> containing the following artifacts:
> >>
> >> commons-rdf-rdf4j-0.5.0.pom (SHA1: 1cdc74b7205fa06531bd59e1ee24f1
> >> d15999ab1b)
> >> commons-rdf-rdf4j-0.5.0.jar (SHA1: 265549b98b423c075f4a186dec76ef
> >> b815c03649)
> >> commons-rdf-rdf4j-0.5.0-tests.jar (SHA1:
> >> 9aab05dceefde27d79bc79f4b3c80daeeb01cb52)
> >> commons-rdf-rdf4j-0.5.0-javadoc.jar (SHA1:
> >> 4254ac42dd569a45ab3b95c3d16cb8f47508039a)
> >> commons-rdf-rdf4j-0.5.0-test-sources.jar (SHA1:
> >> 39eb4a6b10cafa4cfb87b4e48827006332ceaed3)
> >> commons-rdf-rdf4j-0.5.0-sources.jar (SHA1:
> >> f8a0ea29f31f501df05686abfd171f35fd39ed71)
> >> commons-rdf-api-0.5.0-sources.jar (SHA1:
> >> 02735a136e206408f75507fbf27af1230a99f61b)
> >> commons-rdf-api-0.5.0.jar (SHA1: df2d4451dee5b311cb4f51ced214df
> >> aab5838291)
> >> commons-rdf-api-0.5.0-tests.jar (SHA1:
> >> 025730515d0e66043b6483710a9638e1f71ff917)
> >> commons-rdf-api-0.5.0-javadoc.jar (SHA1:
> >> 3e15be3c7d018225aa6bafd91861474780c3ad8e)
> >> commons-rdf-api-0.5.0-test-sources.jar (SHA1:
> >> 5f2554c926de52b5661f430b69c92dac2056a029)
> >> commons-rdf-api-0.5.0.pom (SHA1: cc3382c3a60d815a20bba176393343
> >> 4f41d85598)
> >> commons-rdf-simple-0.5.0-tests.jar (SHA1:
> >> 472e43e582ddcf1a7f06f9184f4bf26fad3b65fc)
> >> commons-rdf-simple-0.5.0.pom (SHA1:
> >> b5aa51f49cbbdb9f3

Re: [VOTE] Release Apache Commons RDF 0.5.0 based on RC3

[Sergio Fernández]

Oliver, for me the site builds just fine (Maven 3.5.0, OpenJDK 1.8.0_151,
Debian amd64). Iĺl try to reproduce the issue when I could get my hands on
a Windows.

In the meantime, I'd like to ask the Commons PMC to vote on this RC. So far
we have only non-binding votes :-/

On Sat, Dec 9, 2017 at 12:29 PM, Oliver Heger <oliver.he...@oliver-heger.de>
wrote:

> Hi,
>
> build works fine with Java 8 on Windows 10. Artifacts look good.
>
> I am still not able to build the site locally; I get the error below.
> Can you somehow provide a zip with the site for inspection?
>
> Thanks
> Oliver
>
> [INFO]
> 
> [INFO] BUILD FAILURE
> [INFO]
> 
> [INFO] Total time: 47.759 s
> [INFO] Finished at: 2017-12-09T21:20:00+01:00
> [INFO] Final Memory: 63M/662M
> [INFO]
> 
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.6:site (default-site) on
> project commons-rdf-parent: Error generating
> maven-checkstyle-plugin:2.12.1:checkstyle-aggregate: Failed during
> checkstyle configuration: cannot initialize module TreeWalker - Property
> 'ignoreAnnotationCanonicalNames' in module VisibilityModifier does not
> exist, please check the documentation -> [Help 1]
> [ERROR]
>
> $ mvn --version
> Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
> 2015-11-10T17:41:47+01:00)
> Maven home: C:\data\dev\tools\apache-maven-3.3.9
> Java version: 1.8.0_144, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk1.8.0_144\jre
> Default locale: de_DE, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "dos"
>
>
> Am 08.12.2017 um 05:51 schrieb Sergio Fernández:
> > Hi,
> >
> > once we addressed most of the issues from RC1 and RC2, I'd like to
> propose
> > to release Apache Commons RDF 0.5.0 based on RC.
> >
> > Apache Commons RDF aims to provide a common Java API for RDF 1.1 graphs
> and
> > datasets. API bindings in Commons RDF 0.5.0 include Apache Jena, Eclipse
> > RDF4J, JSON-LD Java as well as a standalone implementation (simple).
> >
> > Apache Commons RDF 0.5.0 RC3 is available for review at (r23441):
> >
> > https://dist.apache.org/repos/dist/dev/commons/rdf/apache-
> > commons-rdf-0.5.0-RC3/
> >
> > The source code for this RC is available from git tagged as 0.5.0-RC3
> > (commit e82eaa0b7d67f5a1afdf4cdecc19589fbe1654d6):
> >
> > https://git-wip-us.apache.org/repos/asf?p=commons-rdf.git;a=commit;h=
> > e82eaa0b7d67f5a1afdf4cdecc19589fbe1654d6
> >
> > Mirrored at https://github.com/apache/commons-rdf/commit/
> > e82eaa0b7d67f5a1afdf4cdecc19589fbe1654d6
> >
> > This source release produces the following binary artifacts:
> >
> > commons-rdf-parent-0.5.0
> > commons-rdf-api-0.5.0
> > commons-rdf-simple-0.5.0
> > commons-rdf-jena-0.5.0
> > commons-rdf-rdf4j-0.5.0
> > commons-rdf-jsonld-java-0.5.0
> > commons-rdf-integration-tests-0.5.0
> >
> > The Maven Staging repository can be found at:
> >
> > https://repository.apache.org/content/repositories/orgapachecommons-1295
> >
> > containing the following artifacts:
> >
> > commons-rdf-rdf4j-0.5.0.pom (SHA1: 1cdc74b7205fa06531bd59e1ee24f1
> d15999ab1b)
> > commons-rdf-rdf4j-0.5.0.jar (SHA1: 265549b98b423c075f4a186dec76ef
> b815c03649)
> > commons-rdf-rdf4j-0.5.0-tests.jar (SHA1:
> > 9aab05dceefde27d79bc79f4b3c80daeeb01cb52)
> > commons-rdf-rdf4j-0.5.0-javadoc.jar (SHA1:
> > 4254ac42dd569a45ab3b95c3d16cb8f47508039a)
> > commons-rdf-rdf4j-0.5.0-test-sources.jar (SHA1:
> > 39eb4a6b10cafa4cfb87b4e48827006332ceaed3)
> > commons-rdf-rdf4j-0.5.0-sources.jar (SHA1:
> > f8a0ea29f31f501df05686abfd171f35fd39ed71)
> > commons-rdf-api-0.5.0-sources.jar (SHA1:
> > 02735a136e206408f75507fbf27af1230a99f61b)
> > commons-rdf-api-0.5.0.jar (SHA1: df2d4451dee5b311cb4f51ced214df
> aab5838291)
> > commons-rdf-api-0.5.0-tests.jar (SHA1:
> > 025730515d0e66043b6483710a9638e1f71ff917)
> > commons-rdf-api-0.5.0-javadoc.jar (SHA1:
> > 3e15be3c7d018225aa6bafd91861474780c3ad8e)
> > commons-rdf-api-0.5.0-test-sources.jar (SHA1:
> > 5f2554c926de52b5661f430b69c92dac2056a029)
> > commons-rdf-api-0.5.0.pom (SHA1: cc3382c3a60d815a20bba176393343
> 4f41d85598)
> > commons-rdf-simple-0.5.0-tests.jar (SHA1:
> > 472e43e582ddcf1a7f06f9184f4bf26fad3b65fc)
> > commons-rdf-simple-0.5.0.

Re: [VOTE] Release Apache Commons BCEL based on RC1

[Sergio Fernández]

+1 (non-binding)

On Thu, Dec 7, 2017 at 12:34 PM, Gary Gregory 
wrote:

> I am looking for more reviews from PMC members please.
>
> Gary
>
> On Dec 7, 2017 13:33, "Oliver Heger"  wrote:
>
> >
> >
> > Am 06.12.2017 um 22:26 schrieb Gary Gregory:
> > > Oliver, how do you feel about installing Java 9 and trying again?
> > >
> > > Gary
> > >
> > > On Tue, Dec 5, 2017 at 1:48 PM, Gary Gregory 
> > wrote:
> > >
> > >> The test calls the registryGetKeys Windows API and that throws an
> > >> exception because Java 9 is not installed on that machine. This is a
> > bug in
> > >> the test only. Fixed in trunk. Not a showstopper IMO.
> > >>
> > >> Gary
> >
> > Agreed that this is not a blocker. Artifacts and site look good. You
> > will probably update the Release Information section on index.html.
> > There are some checkstyle and findbugs finding, but I assume nothing new
> > or critical.
> >
> > So +1
> >
> > Oliver
> >
> > >>
> > >> On Sun, Dec 3, 2017 at 1:44 PM, Oliver Heger <
> > oliver.he...@oliver-heger.de
> > >>> wrote:
> > >>
> > >>> Here is the stack trace:
> > >>>
> > >>> 
> > >>> ---
> > >>> Test set: org.apache.bcel.generic.JDKGenericDumpTestCase
> > >>> 
> > >>> ---
> > >>> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.657
> > >>> sec <<< FAILURE! - in org.apache.bcel.generic.JDKGenericDumpTestCase
> > >>> initializationError(org.apache.bcel.generic.JDKGenericDumpTestCase)
> > >>> Time elapsed: 0 sec  <<< ERROR!
> > >>> com.sun.jna.platform.win32.Win32Exception: Das System kann die
> > >>> angegebene Datei nicht finden.
> > >>> at
> > >>> org.apache.bcel.generic.JDKGenericDumpTestCase.addAllJavaHom
> > >>> esOnWindows(JDKGenericDumpTestCase.java:65)
> > >>> at
> > >>> org.apache.bcel.generic.JDKGenericDumpTestCase.findJavaHomes
> > >>> OnWindows(JDKGenericDumpTestCase.java:97)
> > >>> at
> > >>> org.apache.bcel.generic.JDKGenericDumpTestCase.findJavaHomes
> > >>> (JDKGenericDumpTestCase.java:87)
> > >>> at
> > >>> org.apache.bcel.generic.JDKGenericDumpTestCase.data(JDKGener
> > >>> icDumpTestCase.java:82)
> > >>>
> > >>> Oliver
> > >>>
> > >>> Am 03.12.2017 um 16:58 schrieb Gary Gregory:
> >  Do you have a full stack trace? It smells like the code that looks
> for
> > >>> JDK
> >  and JRE locations is failing.
> > 
> >  Gary
> > 
> >  On Dec 3, 2017 08:33, "Oliver Heger" 
> > >>> wrote:
> > 
> > > Hi,
> > >
> > > when building on Windows 10 with both Java 1.7 and 1.8 I get the
> test
> > > failure below. Does anybody else see this?
> > >
> > > Oliver
> > >
> > > Results :
> > >
> > > Tests in error:
> > >
> > > JDKGenericDumpTestCase.data:82->findJavaHomes:87->
> > > findJavaHomesOnWindows:97->addAllJavaHomesOnWindows:65
> > > ▒ Win32
> > >
> > > Tests run: 107, Failures: 0, Errors: 1, Skipped: 0
> > >
> > > $ mvn --version
> > > Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
> > > 2015-11-10T17:41:47+01:00)
> > > Maven home: C:\data\dev\tools\apache-maven-3.3.9
> > > Java version: 1.8.0_144, vendor: Oracle Corporation
> > > Java home: C:\Program Files\Java\jdk1.8.0_144\jre
> > > Default locale: de_DE, platform encoding: Cp1252
> > > OS name: "windows 10", version: "10.0", arch: "amd64", family:
> "dos"
> > >
> > >
> > > Am 01.12.2017 um 05:17 schrieb Gary Gregory:
> > >> We fixed a few bugs and added some enhancements since we released
> > >>> Apache
> > >> Commons BCEL 6.1, so I would like to release Commons BCEL 6.2.
> > >>
> > >> Commons BCEL 6.2 RC1 is available for review here:
> > >> https://dist.apache.org/repos/dist/dev/commons/bcel at svn
> > >>> revision:
> > >> 23349
> > >>
> > >> The tag is here:
> > >> http://svn.apache.org/repos/asf/commons/proper/bcel/tags/
> > > BCEL_6_2_RC1/
> > >> (svn revision 1816763)
> > >> N.B. the SVN revision is required because SVN tags are not
> > >>> immutable.
> > >>
> > >> Maven artifacts are here:
> > >> https://repository.apache.org/content/repositories/
> > > orgapachecommons-1294
> > >>
> > >> These are the Maven artifacts and their hashes
> > >>
> > >> /org/apache/bcel/bcel/6.2/bcel-6.2-test-sources.jar
> > >> (SHA1: feef9dc39b67bf76d90a16abf3b5711d894bdafc)
> > >> /org/apache/bcel/bcel/6.2/bcel-6.2.jar.asc
> > >> (SHA1: 10911db34eabbf5ed77175147d890431815a66e9)
> > >> /org/apache/bcel/bcel/6.2/bcel-6.2-tests.jar.asc
> > >> (SHA1: dd32ec245d2d664ee69a70bde304df5f577c3e8b)
> > >> /org/apache/bcel/bcel/6.2/bcel-6.2-src.tar.gz.asc
> > >> (SHA1: 

Re: [VOTE] Release Apache Commons RDF 0.5.0 based on RC3

[Sergio Fernández]

my +1 (non-binding)

On Thu, Dec 7, 2017 at 8:51 PM, Sergio Fernández <wik...@apache.org> wrote:

> Hi,
>
> once we addressed most of the issues from RC1 and RC2, I'd like to propose
> to release Apache Commons RDF 0.5.0 based on RC.
>
> Apache Commons RDF aims to provide a common Java API for RDF 1.1 graphs
> and datasets. API bindings in Commons RDF 0.5.0 include Apache Jena,
> Eclipse RDF4J, JSON-LD Java as well as a standalone implementation (simple).
>
> Apache Commons RDF 0.5.0 RC3 is available for review at (r23441):
>
> https://dist.apache.org/repos/dist/dev/commons/rdf/apache-co
> mmons-rdf-0.5.0-RC3/
>
> The source code for this RC is available from git tagged as 0.5.0-RC3
> (commit e82eaa0b7d67f5a1afdf4cdecc19589fbe1654d6):
>
> https://git-wip-us.apache.org/repos/asf?p=commons-rdf.git;a=
> commit;h=e82eaa0b7d67f5a1afdf4cdecc19589fbe1654d6
>
> Mirrored at https://github.com/apache/commons-rdf/commit/e82eaa0b7d67f5a
> 1afdf4cdecc19589fbe1654d6
>
> This source release produces the following binary artifacts:
>
> commons-rdf-parent-0.5.0
> commons-rdf-api-0.5.0
> commons-rdf-simple-0.5.0
> commons-rdf-jena-0.5.0
> commons-rdf-rdf4j-0.5.0
> commons-rdf-jsonld-java-0.5.0
> commons-rdf-integration-tests-0.5.0
>
> The Maven Staging repository can be found at:
>
> https://repository.apache.org/content/repositories/orgapachecommons-1295
>
> containing the following artifacts:
>
> commons-rdf-rdf4j-0.5.0.pom (SHA1: 1cdc74b7205fa06531bd59e1ee24f1
> d15999ab1b)
> commons-rdf-rdf4j-0.5.0.jar (SHA1: 265549b98b423c075f4a186dec76ef
> b815c03649)
> commons-rdf-rdf4j-0.5.0-tests.jar (SHA1: 9aab05dceefde27d79bc79f4b3c80d
> aeeb01cb52)
> commons-rdf-rdf4j-0.5.0-javadoc.jar (SHA1: 4254ac42dd569a45ab3b95c3d16cb8
> f47508039a)
> commons-rdf-rdf4j-0.5.0-test-sources.jar (SHA1:
> 39eb4a6b10cafa4cfb87b4e48827006332ceaed3)
> commons-rdf-rdf4j-0.5.0-sources.jar (SHA1: f8a0ea29f31f501df05686abfd171f
> 35fd39ed71)
> commons-rdf-api-0.5.0-sources.jar (SHA1: 02735a136e206408f75507fbf27af1
> 230a99f61b)
> commons-rdf-api-0.5.0.jar (SHA1: df2d4451dee5b311cb4f51ced214dfaab5838291)
> commons-rdf-api-0.5.0-tests.jar (SHA1: 025730515d0e66043b6483710a9638
> e1f71ff917)
> commons-rdf-api-0.5.0-javadoc.jar (SHA1: 3e15be3c7d018225aa6bafd9186147
> 4780c3ad8e)
> commons-rdf-api-0.5.0-test-sources.jar (SHA1:
> 5f2554c926de52b5661f430b69c92dac2056a029)
> commons-rdf-api-0.5.0.pom (SHA1: cc3382c3a60d815a20bba1763933434f41d85598)
> commons-rdf-simple-0.5.0-tests.jar (SHA1: 472e43e582ddcf1a7f06f9184f4bf2
> 6fad3b65fc)
> commons-rdf-simple-0.5.0.pom (SHA1: b5aa51f49cbbdb9f39fa70d8cf183f
> 63ae0c3a6a)
> commons-rdf-simple-0.5.0-javadoc.jar (SHA1: 87941fc168b6011fb003288eb39257
> 7fc4519be0)
> commons-rdf-simple-0.5.0-sources.jar (SHA1: 7232c14775db216efc85a1a7fabb90
> c6a456950c)
> commons-rdf-simple-0.5.0.jar (SHA1: c6b5038624d860129e273538d18dd5
> 2c5adcfd70)
> commons-rdf-simple-0.5.0-test-sources.jar (SHA1:
> 8028e8f20ebc465a6cd5a32fd9b8447eb4cf48dc)
> commons-rdf-parent-0.5.0-src.tar.gz (SHA1: 5b3788cb6b647f3663839fd0737a5a
> 85a75d19fa)
> commons-rdf-parent-0.5.0-src.zip (SHA1: 519891322ed75f3ae4ef5cf7e8df60
> c65b797634)
> commons-rdf-parent-0.5.0.pom (SHA1: 4186153db162b4382f73be1ce2ff97
> a98ee5d442)
> commons-rdf-parent-0.5.0-site.xml (SHA1: 26fd1dc487f5f002d35841ba8dcc53
> 704652d3b8)
> commons-rdf-integration-tests-0.5.0-test-sources.jar (SHA1:
> d7ad7ad0c09c3ae46d8da9c1ed989a9615369dcf)
> commons-rdf-integration-tests-0.5.0-tests.jar (SHA1:
> 0db5cb5a32afcad51decae42c6a7d4dc7e62f15a)
> commons-rdf-integration-tests-0.5.0.pom (SHA1:
> dc8b7754e2069b8c19c507a59a665ba12fd60007)
> commons-rdf-jena-0.5.0.pom (SHA1: a4a0f39e0428d0484074d1dde5368a
> 9f9ba2b065)
> commons-rdf-jena-0.5.0-sources.jar (SHA1: 51c8127914e5d7f3d8922375af08c5
> 24f1a5d403)
> commons-rdf-jena-0.5.0-test-sources.jar (SHA1:
> fb9cc23fd01210ec32c2c79a70204689359ab8c5)
> commons-rdf-jena-0.5.0-tests.jar (SHA1: e26df331facb7dff0ef837ba8fa390
> 00a2082048)
> commons-rdf-jena-0.5.0-javadoc.jar (SHA1: 3b8a9fc8aa8238b72c2ebd582a7778
> 24660dbdfe)
> commons-rdf-jena-0.5.0.jar (SHA1: a66e6c9e49082ceb14e98541fabf8b
> e060128853)
> commons-rdf-jsonld-java-0.5.0-test-sources.jar (SHA1:
> 26026e8f03e464b5601cb4eefeb32766352fe688)
> commons-rdf-jsonld-java-0.5.0.pom (SHA1: c6d30844d93a42761a0c54a25655b7
> cdc34bcfa5)
> commons-rdf-jsonld-java-0.5.0-javadoc.jar (SHA1:
> 3fc6b506ac7887275cac9aeef65b1f87a089c1d1)
> commons-rdf-jsonld-java-0.5.0-sources.jar (SHA1:
> e031d0bb4e128b949260ce61ac3af1287a0b6efe)
> commons-rdf-jsonld-java-0.5.0-tests.jar (SHA1:
> ff66a1731e25d53d1f9967b2524afa2cf705640f)
> commons-rdf-jsonld-java-0.5.0.jar (SHA1: 59c09bf7787d4c78c7564b383f4eed
> bcca165756)
>
>
> So, please, vote on releasing this release candidate as:
>
>   Apache Commons RDF 0.5.0
>
> The vote is open for at least 72 hours/
>
> [ ] +1 Release this package
> [ ] 0 I don't feel strongly about it, but don't object
> [ ] -1 Do not release this package because...
>
> Thanks
>

[VOTE] Release Apache Commons RDF 0.5.0 based on RC3

[Sergio Fernández]

Hi,

once we addressed most of the issues from RC1 and RC2, I'd like to propose
to release Apache Commons RDF 0.5.0 based on RC.

Apache Commons RDF aims to provide a common Java API for RDF 1.1 graphs and
datasets. API bindings in Commons RDF 0.5.0 include Apache Jena, Eclipse
RDF4J, JSON-LD Java as well as a standalone implementation (simple).

Apache Commons RDF 0.5.0 RC3 is available for review at (r23441):

https://dist.apache.org/repos/dist/dev/commons/rdf/apache-
commons-rdf-0.5.0-RC3/

The source code for this RC is available from git tagged as 0.5.0-RC3
(commit e82eaa0b7d67f5a1afdf4cdecc19589fbe1654d6):

https://git-wip-us.apache.org/repos/asf?p=commons-rdf.git;a=commit;h=
e82eaa0b7d67f5a1afdf4cdecc19589fbe1654d6

Mirrored at https://github.com/apache/commons-rdf/commit/
e82eaa0b7d67f5a1afdf4cdecc19589fbe1654d6

This source release produces the following binary artifacts:

commons-rdf-parent-0.5.0
commons-rdf-api-0.5.0
commons-rdf-simple-0.5.0
commons-rdf-jena-0.5.0
commons-rdf-rdf4j-0.5.0
commons-rdf-jsonld-java-0.5.0
commons-rdf-integration-tests-0.5.0

The Maven Staging repository can be found at:

https://repository.apache.org/content/repositories/orgapachecommons-1295

containing the following artifacts:

commons-rdf-rdf4j-0.5.0.pom (SHA1: 1cdc74b7205fa06531bd59e1ee24f1d15999ab1b)
commons-rdf-rdf4j-0.5.0.jar (SHA1: 265549b98b423c075f4a186dec76efb815c03649)
commons-rdf-rdf4j-0.5.0-tests.jar (SHA1:
9aab05dceefde27d79bc79f4b3c80daeeb01cb52)
commons-rdf-rdf4j-0.5.0-javadoc.jar (SHA1:
4254ac42dd569a45ab3b95c3d16cb8f47508039a)
commons-rdf-rdf4j-0.5.0-test-sources.jar (SHA1:
39eb4a6b10cafa4cfb87b4e48827006332ceaed3)
commons-rdf-rdf4j-0.5.0-sources.jar (SHA1:
f8a0ea29f31f501df05686abfd171f35fd39ed71)
commons-rdf-api-0.5.0-sources.jar (SHA1:
02735a136e206408f75507fbf27af1230a99f61b)
commons-rdf-api-0.5.0.jar (SHA1: df2d4451dee5b311cb4f51ced214dfaab5838291)
commons-rdf-api-0.5.0-tests.jar (SHA1:
025730515d0e66043b6483710a9638e1f71ff917)
commons-rdf-api-0.5.0-javadoc.jar (SHA1:
3e15be3c7d018225aa6bafd91861474780c3ad8e)
commons-rdf-api-0.5.0-test-sources.jar (SHA1:
5f2554c926de52b5661f430b69c92dac2056a029)
commons-rdf-api-0.5.0.pom (SHA1: cc3382c3a60d815a20bba1763933434f41d85598)
commons-rdf-simple-0.5.0-tests.jar (SHA1:
472e43e582ddcf1a7f06f9184f4bf26fad3b65fc)
commons-rdf-simple-0.5.0.pom (SHA1:
b5aa51f49cbbdb9f39fa70d8cf183f63ae0c3a6a)
commons-rdf-simple-0.5.0-javadoc.jar (SHA1:
87941fc168b6011fb003288eb392577fc4519be0)
commons-rdf-simple-0.5.0-sources.jar (SHA1:
7232c14775db216efc85a1a7fabb90c6a456950c)
commons-rdf-simple-0.5.0.jar (SHA1:
c6b5038624d860129e273538d18dd52c5adcfd70)
commons-rdf-simple-0.5.0-test-sources.jar (SHA1:
8028e8f20ebc465a6cd5a32fd9b8447eb4cf48dc)
commons-rdf-parent-0.5.0-src.tar.gz (SHA1:
5b3788cb6b647f3663839fd0737a5a85a75d19fa)
commons-rdf-parent-0.5.0-src.zip (SHA1:
519891322ed75f3ae4ef5cf7e8df60c65b797634)
commons-rdf-parent-0.5.0.pom (SHA1:
4186153db162b4382f73be1ce2ff97a98ee5d442)
commons-rdf-parent-0.5.0-site.xml (SHA1:
26fd1dc487f5f002d35841ba8dcc53704652d3b8)
commons-rdf-integration-tests-0.5.0-test-sources.jar (SHA1:
d7ad7ad0c09c3ae46d8da9c1ed989a9615369dcf)
commons-rdf-integration-tests-0.5.0-tests.jar (SHA1:
0db5cb5a32afcad51decae42c6a7d4dc7e62f15a)
commons-rdf-integration-tests-0.5.0.pom (SHA1:
dc8b7754e2069b8c19c507a59a665ba12fd60007)
commons-rdf-jena-0.5.0.pom (SHA1: a4a0f39e0428d0484074d1dde5368a9f9ba2b065)
commons-rdf-jena-0.5.0-sources.jar (SHA1:
51c8127914e5d7f3d8922375af08c524f1a5d403)
commons-rdf-jena-0.5.0-test-sources.jar (SHA1:
fb9cc23fd01210ec32c2c79a70204689359ab8c5)
commons-rdf-jena-0.5.0-tests.jar (SHA1:
e26df331facb7dff0ef837ba8fa39000a2082048)
commons-rdf-jena-0.5.0-javadoc.jar (SHA1:
3b8a9fc8aa8238b72c2ebd582a777824660dbdfe)
commons-rdf-jena-0.5.0.jar (SHA1: a66e6c9e49082ceb14e98541fabf8be060128853)
commons-rdf-jsonld-java-0.5.0-test-sources.jar (SHA1:
26026e8f03e464b5601cb4eefeb32766352fe688)
commons-rdf-jsonld-java-0.5.0.pom (SHA1:
c6d30844d93a42761a0c54a25655b7cdc34bcfa5)
commons-rdf-jsonld-java-0.5.0-javadoc.jar (SHA1:
3fc6b506ac7887275cac9aeef65b1f87a089c1d1)
commons-rdf-jsonld-java-0.5.0-sources.jar (SHA1:
e031d0bb4e128b949260ce61ac3af1287a0b6efe)
commons-rdf-jsonld-java-0.5.0-tests.jar (SHA1:
ff66a1731e25d53d1f9967b2524afa2cf705640f)
commons-rdf-jsonld-java-0.5.0.jar (SHA1:
59c09bf7787d4c78c7564b383f4eedbcca165756)


So, please, vote on releasing this release candidate as:

  Apache Commons RDF 0.5.0

The vote is open for at least 72 hours/

[ ] +1 Release this package
[ ] 0 I don't feel strongly about it, but don't object
[ ] -1 Do not release this package because...

Thanks

[CANCELLED} [VOTE] Release Apache Commons RDF 0.5.0 based on RC2

[Sergio Fernández]

Thanks, Stian, that's exactlywas I was expecting.

So I formally CANCEL this VOTE, and I'll prepare a RC3 in the next few
days. includihe fix for COMMONSRDF-69..



On Wed, Dec 6, 2017 at 4:59 AM, Stian Soiland-Reyes <st...@apache.org>
wrote:

> Good effort, Sergio! Sorry for late review.
> I guess you didn't get to many replies as there was confusion with the
> dist/svn revision.. :-(
>
>
> Sorry, my vote is -1 (binding)
>
> .. as META-INF/LICENSE and META-INF/NOTICE are missing in the binary
> JARs in the maven repo.
>
> (Not sure how I missed this before, is this caused by a change in
> commons-parent affecting submodules?)
>
>
> +1 gpg signatures dist & staging
> +1 dist svn (revision 23205 and 23227 are equal in this subtree)
> +1 git commit == tag ~= dist ~= staging  (except .gitignore / .travis.yml)
> -0 NOTICE has wrong Copyright year
> +1 builds with mvn clean install -T1.0C
> -1 META-INF/LICENSE and META-INF/NOTICE missing from JARs (except -api
> and -impl)
>
>
> Built with:
>
> Apache Maven 3.3.9
> Maven home: /usr/share/maven
> Java version: 1.8.0_151, vendor: Oracle Corporation
> Java home: /usr/lib/jvm/java-8-openjdk-amd64/jre
> Default locale: en_GB, platform encoding: UTF-8
> OS name: "linux", version: "4.10.0-40-generic", arch: "amd64", family:
> "unix"
>
> On 4 December 2017 at 11:13, Sergio Fernández <wik...@apache.org> wrote:
> > I'd like to bring up this vote, which is waiting for votes for two weeks
> :-/
> >
> >
> > On Nov 26, 2017 13:21, "Sergio Fernández" <wik...@apache.org> wrote:
> >
> > I'd like to ask the Commons PMC to cast a, any, vote for this RC. Because
> > it's stuck. It's fine to get -1s, but at least something to move forward.
> > Thanks.
> >
> > On Nov 22, 2017 17:52, "Sergio Fernández" <wik...@apache.org> wrote:
> >
> >> Hi Oliver,
> >>
> >> thanks for the feedback on RC2. Please, find my answers inline.
> >>
> >> On Wed, Nov 22, 2017 at 1:25 PM, Oliver Heger <
> >> oliver.he...@oliver-heger.de> wrote:
> >>>
> >>> [ERROR] Failed to execute goal
> >>> org.apache.maven.plugins:maven-site-plugin:3.6:site (default-cli) on
> >>> project commons-rdf-parent: Error generating
> >>> maven-checkstyle-plugin:2.12.1:checkstyle-aggregate: Failed during
> >>> checkstyle configuration: cannot initialize module TreeWalker -
> Property
> >>> 'ignoreAnnotationCanonicalNames' in module VisibilityModifier does not
> >>> exist, please check the documentation -> [Help 1]
> >>>
> >>> A problem with the version of the checkstyle plugin?
> >>>
> >>
> >>  Maybe..., the version comes from Commons Parent. The issue is that I'm
> >> not able to reproduce the problem in Unix, neither in Linux nor OSX.
> >>
> >> Some other notes:
> >>> * NOTICE has the wrong copyright year. I think this needs to be fixed.
> >>>
> >>
> >> Yeah, I reported that as https://issues.apache.org/j
> >> ira/browse/COMMONSRDF-69
> >>
> >>
> >>> * The project does not release binary artifacts. This is probably okay,
> >>> but unusual for Commons. It would be nice if you could add a binary
> >>> distribution - maybe for the 1.0 release.
> >>>
> >>
> >> Afterwards I updated the vote to include the binary release, too:
> >>
> >> https://lists.apache.org/thread.html/23cf46d92c2afa191690edc
> >> a5ea76c0882c108c1a9dc1709a9d9ee52@%3Cdev.commons.apache.org%3E
> >>
> >> Thanks.
> >>
> >>
> >>
> >> Am 19.11.2017 um 23:08 schrieb Sergio Fernández:
> >> > Hi,
> >> >
> >> > once we addressed most of the issues from RC1, I'd like to propose to
> >> > release Apache Commons RDF 0.5.0 based on RC2.
> >> >
> >> > Apache Commons RDF aims to provide a common Java API for RDF 1.1
> graphs
> >> and
> >> > datasets. API bindings in Commons RDF 0.5.0 include Apache Jena,
> Eclipse
> >> > RDF4J, JSON-LD Java as well as a standalone implementation (simple).
> >> >
> >> > Apache Commons RDF 0.5.0 RC2 is available for review at (r23205):
> >> >
> >> > https://dist.apache.org/repos/dist/dev/commons/rdf/apache-co
> >> mmons-rdf-0.5.0-RC2/
> >> >
> >> > The source code for this RC is available from git tagged as 0.5.0-RC2
> >> > (commit

Re: [VOTE] Release Apache Commons RDF 0.5.0 based on RC2

[Sergio Fernández]

I'd like to bring up this vote, which is waiting for votes for two weeks :-/


On Nov 26, 2017 13:21, "Sergio Fernández" <wik...@apache.org> wrote:

I'd like to ask the Commons PMC to cast a, any, vote for this RC. Because
it's stuck. It's fine to get -1s, but at least something to move forward.
Thanks.

On Nov 22, 2017 17:52, "Sergio Fernández" <wik...@apache.org> wrote:

> Hi Oliver,
>
> thanks for the feedback on RC2. Please, find my answers inline.
>
> On Wed, Nov 22, 2017 at 1:25 PM, Oliver Heger <
> oliver.he...@oliver-heger.de> wrote:
>>
>> [ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-site-plugin:3.6:site (default-cli) on
>> project commons-rdf-parent: Error generating
>> maven-checkstyle-plugin:2.12.1:checkstyle-aggregate: Failed during
>> checkstyle configuration: cannot initialize module TreeWalker - Property
>> 'ignoreAnnotationCanonicalNames' in module VisibilityModifier does not
>> exist, please check the documentation -> [Help 1]
>>
>> A problem with the version of the checkstyle plugin?
>>
>
>  Maybe..., the version comes from Commons Parent. The issue is that I'm
> not able to reproduce the problem in Unix, neither in Linux nor OSX.
>
> Some other notes:
>> * NOTICE has the wrong copyright year. I think this needs to be fixed.
>>
>
> Yeah, I reported that as https://issues.apache.org/j
> ira/browse/COMMONSRDF-69
>
>
>> * The project does not release binary artifacts. This is probably okay,
>> but unusual for Commons. It would be nice if you could add a binary
>> distribution - maybe for the 1.0 release.
>>
>
> Afterwards I updated the vote to include the binary release, too:
>
> https://lists.apache.org/thread.html/23cf46d92c2afa191690edc
> a5ea76c0882c108c1a9dc1709a9d9ee52@%3Cdev.commons.apache.org%3E
>
> Thanks.
>
>
>
> Am 19.11.2017 um 23:08 schrieb Sergio Fernández:
> > Hi,
> >
> > once we addressed most of the issues from RC1, I'd like to propose to
> > release Apache Commons RDF 0.5.0 based on RC2.
> >
> > Apache Commons RDF aims to provide a common Java API for RDF 1.1 graphs
> and
> > datasets. API bindings in Commons RDF 0.5.0 include Apache Jena, Eclipse
> > RDF4J, JSON-LD Java as well as a standalone implementation (simple).
> >
> > Apache Commons RDF 0.5.0 RC2 is available for review at (r23205):
> >
> > https://dist.apache.org/repos/dist/dev/commons/rdf/apache-co
> mmons-rdf-0.5.0-RC2/
> >
> > The source code for this RC is available from git tagged as 0.5.0-RC2
> > (commit 186df0c36981a308338792f02d93fc59776b0b7c):
> >
> > https://git-wip-us.apache.org/repos/asf?p=commons-rdf.git;a=
> commit;h=186df0c36981a308338792f02d93fc59776b0b7c
> >
> > Mirrored at
> > https://github.com/apache/commons-rdf/commit/186df0c36981a30
> 8338792f02d93fc59776b0b7c
> >
> > This source release produces the following binary artifacts:
> >
> > commons-rdf-parent-0.5.0
> > commons-rdf-api-0.5.0
> > commons-rdf-simple-0.5.0
> > commons-rdf-jena-0.5.0
> > commons-rdf-rdf4j-0.5.0
> > commons-rdf-jsonld-java-0.5.0
> > commons-rdf-integration-tests-0.5.0
> >
> > The Maven Staging repository can be found at:
> >
> > https://repository.apache.org/content/repositories/orgapachecommons-1293
> >
> > Please vote on releasing this release candidate as:
> >
> > Apache Commons RDF 0.5.0
> >
> > The vote is open for at least 72 hours/
> >
> > [ ] +1 Release this package
> > [ ] 0 I don't feel strongly about it, but don't object
> > [ ] -1 Do not release this package because...
> >
> > Anyone can participate in testing and voting, not just committers,
> > please feel free to try out the release candidate and provide your
> > votes!
> >
> > Thanks
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>
>

Re: [VOTE] Release Apache Commons RDF 0.5.0 based on RC2

[Sergio Fernández]

I'd like to ask the Commons PMC to cast a, any, vote for this RC. Because
it's stuck. It's fine to get -1s, but at least something to move forward.
Thanks.

On Nov 22, 2017 17:52, "Sergio Fernández" <wik...@apache.org> wrote:

> Hi Oliver,
>
> thanks for the feedback on RC2. Please, find my answers inline.
>
> On Wed, Nov 22, 2017 at 1:25 PM, Oliver Heger <
> oliver.he...@oliver-heger.de> wrote:
>>
>> [ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-site-plugin:3.6:site (default-cli) on
>> project commons-rdf-parent: Error generating
>> maven-checkstyle-plugin:2.12.1:checkstyle-aggregate: Failed during
>> checkstyle configuration: cannot initialize module TreeWalker - Property
>> 'ignoreAnnotationCanonicalNames' in module VisibilityModifier does not
>> exist, please check the documentation -> [Help 1]
>>
>> A problem with the version of the checkstyle plugin?
>>
>
>  Maybe..., the version comes from Commons Parent. The issue is that I'm
> not able to reproduce the problem in Unix, neither in Linux nor OSX.
>
> Some other notes:
>> * NOTICE has the wrong copyright year. I think this needs to be fixed.
>>
>
> Yeah, I reported that as https://issues.apache.org/
> jira/browse/COMMONSRDF-69
>
>
>> * The project does not release binary artifacts. This is probably okay,
>> but unusual for Commons. It would be nice if you could add a binary
>> distribution - maybe for the 1.0 release.
>>
>
> Afterwards I updated the vote to include the binary release, too:
>
> https://lists.apache.org/thread.html/23cf46d92c2afa191690edca5ea76c
> 0882c108c1a9dc1709a9d9ee52@%3Cdev.commons.apache.org%3E
>
> Thanks.
>
>
>
> Am 19.11.2017 um 23:08 schrieb Sergio Fernández:
> > Hi,
> >
> > once we addressed most of the issues from RC1, I'd like to propose to
> > release Apache Commons RDF 0.5.0 based on RC2.
> >
> > Apache Commons RDF aims to provide a common Java API for RDF 1.1 graphs
> and
> > datasets. API bindings in Commons RDF 0.5.0 include Apache Jena, Eclipse
> > RDF4J, JSON-LD Java as well as a standalone implementation (simple).
> >
> > Apache Commons RDF 0.5.0 RC2 is available for review at (r23205):
> >
> > https://dist.apache.org/repos/dist/dev/commons/rdf/apache-co
> mmons-rdf-0.5.0-RC2/
> >
> > The source code for this RC is available from git tagged as 0.5.0-RC2
> > (commit 186df0c36981a308338792f02d93fc59776b0b7c):
> >
> > https://git-wip-us.apache.org/repos/asf?p=commons-rdf.git;a=
> commit;h=186df0c36981a308338792f02d93fc59776b0b7c
> >
> > Mirrored at
> > https://github.com/apache/commons-rdf/commit/186df0c36981a30
> 8338792f02d93fc59776b0b7c
> >
> > This source release produces the following binary artifacts:
> >
> > commons-rdf-parent-0.5.0
> > commons-rdf-api-0.5.0
> > commons-rdf-simple-0.5.0
> > commons-rdf-jena-0.5.0
> > commons-rdf-rdf4j-0.5.0
> > commons-rdf-jsonld-java-0.5.0
> > commons-rdf-integration-tests-0.5.0
> >
> > The Maven Staging repository can be found at:
> >
> > https://repository.apache.org/content/repositories/orgapachecommons-1293
> >
> > Please vote on releasing this release candidate as:
> >
> > Apache Commons RDF 0.5.0
> >
> > The vote is open for at least 72 hours/
> >
> > [ ] +1 Release this package
> > [ ] 0 I don't feel strongly about it, but don't object
> > [ ] -1 Do not release this package because...
> >
> > Anyone can participate in testing and voting, not just committers,
> > please feel free to try out the release candidate and provide your
> > votes!
> >
> > Thanks
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>
>

Re: [VOTE] Release Apache Commons RDF 0.5.0 based on RC2

[Sergio Fernández]

Hi Oliver,

thanks for the feedback on RC2. Please, find my answers inline.

On Wed, Nov 22, 2017 at 1:25 PM, Oliver Heger <oliver.he...@oliver-heger.de>
wrote:
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.6:site (default-cli) on
> project commons-rdf-parent: Error generating
> maven-checkstyle-plugin:2.12.1:checkstyle-aggregate: Failed during
> checkstyle configuration: cannot initialize module TreeWalker - Property
> 'ignoreAnnotationCanonicalNames' in module VisibilityModifier does not
> exist, please check the documentation -> [Help 1]
>
> A problem with the version of the checkstyle plugin?
>

 Maybe..., the version comes from Commons Parent. The issue is that I'm not
able to reproduce the problem in Unix, neither in Linux nor OSX.

Some other notes:
> * NOTICE has the wrong copyright year. I think this needs to be fixed.
>

Yeah, I reported that as https://issues.apache.org/jira/browse/COMMONSRDF-69


> * The project does not release binary artifacts. This is probably okay,
> but unusual for Commons. It would be nice if you could add a binary
> distribution - maybe for the 1.0 release.
>

Afterwards I updated the vote to include the binary release, too:

https://lists.apache.org/thread.html/23cf46d92c2afa191690edca5ea76c0882c108c1a9dc1709a9d9ee52@%3Cdev.commons.apache.org%3E


Thanks.



Am 19.11.2017 um 23:08 schrieb Sergio Fernández:
> Hi,
>
> once we addressed most of the issues from RC1, I'd like to propose to
> release Apache Commons RDF 0.5.0 based on RC2.
>
> Apache Commons RDF aims to provide a common Java API for RDF 1.1 graphs
and
> datasets. API bindings in Commons RDF 0.5.0 include Apache Jena, Eclipse
> RDF4J, JSON-LD Java as well as a standalone implementation (simple).
>
> Apache Commons RDF 0.5.0 RC2 is available for review at (r23205):
>
> https://dist.apache.org/repos/dist/dev/commons/rdf/apache-
commons-rdf-0.5.0-RC2/
>
> The source code for this RC is available from git tagged as 0.5.0-RC2
> (commit 186df0c36981a308338792f02d93fc59776b0b7c):
>
> https://git-wip-us.apache.org/repos/asf?p=commons-rdf.git;a=commit;h=
186df0c36981a308338792f02d93fc59776b0b7c
>
> Mirrored at
> https://github.com/apache/commons-rdf/commit/
186df0c36981a308338792f02d93fc59776b0b7c
>
> This source release produces the following binary artifacts:
>
> commons-rdf-parent-0.5.0
> commons-rdf-api-0.5.0
> commons-rdf-simple-0.5.0
> commons-rdf-jena-0.5.0
> commons-rdf-rdf4j-0.5.0
> commons-rdf-jsonld-java-0.5.0
> commons-rdf-integration-tests-0.5.0
>
> The Maven Staging repository can be found at:
>
> https://repository.apache.org/content/repositories/orgapachecommons-1293
>
> Please vote on releasing this release candidate as:
>
> Apache Commons RDF 0.5.0
>
> The vote is open for at least 72 hours/
>
> [ ] +1 Release this package
> [ ] 0 I don't feel strongly about it, but don't object
> [ ] -1 Do not release this package because...
>
> Anyone can participate in testing and voting, not just committers,
> please feel free to try out the release candidate and provide your
> votes!
>
> Thanks
>

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

Re: [VOTE] Release Apache Commons RDF 0.5.0 based on RC2

[Sergio Fernández]

BTW, my +1 (non-binding).

On Mon, Nov 20, 2017 at 7:31 PM, Sergio Fernández <wik...@apache.org> wrote:

> Hi,
>
> On Mon, Nov 20, 2017 at 5:39 PM, sebb <seb...@gmail.com> wrote:
>
>> On 20 November 2017 at 21:36, Sergio Fernández <wik...@apache.org> wrote:
>> > I read that Commons policy. The issues is that I didn't get that email,
>> and
>> > I couldn't find how to easily gather those checksums given the amount of
>> > binary artifacts this source release produces.
>>
>> You should be able to get the email from the mail-archives, e.g.
>>
>> http://mail-archives.apache.org/mod_mbox/commons-commits/201
>> 711.mbox/browser
>
>
> Thanks for the pointer, sebb!
>
> Then, I'd like to update the VOTE to include the following artifacts have
> been staged for Apache Commons RDF 0.5.0 RC2:
>
> commons-rdf-rdf4j-0.5.0-tests.jar.asc (SHA1:
> 04605bc88577af60fa0762ca279be80a57a85958)
> commons-rdf-rdf4j-0.5.0.pom (SHA1: 1cdc74b7205fa06531bd59e1ee24f1
> d15999ab1b)
> commons-rdf-rdf4j-0.5.0-javadoc.jar.asc (SHA1:
> 8f2f0ca7ed441d57638bff113331e2ea2582ce3e)
> commons-rdf-rdf4j-0.5.0-sources.jar.asc (SHA1:
> 3c556b3e00713e99032b47888743370142d681fa)
> commons-rdf-rdf4j-0.5.0.jar (SHA1: 9d820f278c80ad6948ae90e5684b79
> 29f0437cb3)
> commons-rdf-rdf4j-0.5.0-tests.jar (SHA1: e7d80cd6cb101c9b1132228e218d50
> 1be8e993af)
> commons-rdf-rdf4j-0.5.0-javadoc.jar (SHA1: ae587f243395da5ae868124651d227
> f581f8c219)
> commons-rdf-rdf4j-0.5.0.jar.asc (SHA1: 5f72ef133c0cb54c48f386c0b08789
> ae1f5b2945)
> commons-rdf-rdf4j-0.5.0-test-sources.jar (SHA1:
> 86f16a8af7d1c9635ef2f53df4db2e115b3c9c71)
> commons-rdf-rdf4j-0.5.0-test-sources.jar.asc (SHA1:
> e347de285e59484b2a099ce776a4901397f16a2c)
> commons-rdf-rdf4j-0.5.0-sources.jar (SHA1: dcc4d9c6a1f59a8c561c42b1d4b1b6
> c5851b851f)
> commons-rdf-rdf4j-0.5.0.pom.asc (SHA1: 3603993d3cdee09a59d3743cb831d8
> 1a9447eaa0)
> commons-rdf-api-0.5.0-sources.jar (SHA1: ab3d5097882ade36948da3850d3012
> b1618c7838)
> commons-rdf-api-0.5.0.jar (SHA1: f2c460dea59ce36ad06591a4e35670a4bd0aceb7)
> commons-rdf-api-0.5.0-javadoc.jar.asc (SHA1:
> f0dddb805b816ded5f1f3087561e24bbd8d1e4f9)
> commons-rdf-api-0.5.0-tests.jar.asc (SHA1: 0b7e622257b722d3cc47a6d81ab482
> 8d791159c4)
> commons-rdf-api-0.5.0-sources.jar.asc (SHA1:
> 589491a448232fed30815c0b5eb2880ad6dcea98)
> commons-rdf-api-0.5.0-tests.jar (SHA1: 745b0584a341e5b91a6fe03c1a9f95
> 026dbfd92d)
> commons-rdf-api-0.5.0-test-sources.jar.asc (SHA1:
> 851ce69fcbd42ce5bf1dc1ce8aca0e93eb2f767e)
> commons-rdf-api-0.5.0-javadoc.jar (SHA1: 7864c01900a60e3ccc33208faaa226
> 17b9461bdb)
> commons-rdf-api-0.5.0-test-sources.jar (SHA1:
> 347b29318e5b0dc4544035d077cb0d10a93e22f9)
> commons-rdf-api-0.5.0.pom (SHA1: cc3382c3a60d815a20bba1763933434f41d85598)
> commons-rdf-api-0.5.0.pom.asc (SHA1: cca3d4f34e229d5ddc672a75e75aec
> 135c3aaef8)
> commons-rdf-api-0.5.0.jar.asc (SHA1: 76aef667f3fd941fdea8567bfc4c71
> 009063affc)
> commons-rdf-simple-0.5.0-javadoc.jar.asc (SHA1:
> 2149f0a7b260f08fca4f7bbd90ddb5d727ae768e)
> commons-rdf-simple-0.5.0-sources.jar.asc (SHA1:
> 2e410296acdf351493973fb77ae96d478087ad19)
> commons-rdf-simple-0.5.0-tests.jar (SHA1: 95f0a02550a06f214533007af07dc5
> 7a50e9ed03)
> commons-rdf-simple-0.5.0.pom (SHA1: b5aa51f49cbbdb9f39fa70d8cf183f
> 63ae0c3a6a)
> commons-rdf-simple-0.5.0-test-sources.jar.asc (SHA1:
> f7de79994338ebc43659d3c3c727ec545aec389a)
> commons-rdf-simple-0.5.0.jar.asc (SHA1: 41d4558af80dc72e81533fae213549
> 31ba06b6b3)
> commons-rdf-simple-0.5.0-javadoc.jar (SHA1: 727cf414a2da46a7f0da751756bc74
> 844e5bc6fa)
> commons-rdf-simple-0.5.0-tests.jar.asc (SHA1:
> 84bbfe92be8aa42bfc6a1bb8cc6c4afb2ce1e71c)
> commons-rdf-simple-0.5.0-sources.jar (SHA1: 5a781e23952b7cb54c66b8c165b207
> 9a63b335bf)
> commons-rdf-simple-0.5.0.jar (SHA1: eb97fa986f400845f12cd47a48297d
> 30998c8fc2)
> commons-rdf-simple-0.5.0.pom.asc (SHA1: 2b633568c9bd640a5f02e761e364d5
> 8256c52fc5)
> commons-rdf-simple-0.5.0-test-sources.jar (SHA1:
> 1d6980982a77c46b404021e7545d037febfa5236)
> commons-rdf-parent-0.5.0.pom.asc (SHA1: 18216f499afca5b6effa0ac6644b07
> 64a9fe0d0c)
> commons-rdf-parent-0.5.0-src.zip.asc (SHA1: 794ca08dc118d1b4d5fcff9ba642f5
> 7d5f212faf)
> commons-rdf-parent-0.5.0-src.tar.gz.asc (SHA1:
> c3b5404d273ab3bcffebe3849d5c9bd80f93db71)
> commons-rdf-parent-0.5.0-src.tar.gz (SHA1: 3ea3de8d3e120eb2737fde3c6af50d
> 1e91fd395b)
> commons-rdf-parent-0.5.0-site.xml.asc (SHA1:
> c13a97d1d7a515fe215305ec32e02e5b779682c0)
> commons-rdf-parent-0.5.0-src.zip (SHA1: 155b95960f494c59739caab769ea9f
> 319e91ef9c)
> commons-rdf-parent-0.5.0.pom (SHA1: 4186153db162b4382f73be1c

Re: [VOTE] Release Apache Commons RDF 0.5.0 based on RC2

[Sergio Fernández]

Hi,

On Mon, Nov 20, 2017 at 5:39 PM, sebb <seb...@gmail.com> wrote:

> On 20 November 2017 at 21:36, Sergio Fernández <wik...@apache.org> wrote:
> > I read that Commons policy. The issues is that I didn't get that email,
> and
> > I couldn't find how to easily gather those checksums given the amount of
> > binary artifacts this source release produces.
>
> You should be able to get the email from the mail-archives, e.g.
>
> http://mail-archives.apache.org/mod_mbox/commons-commits/201
> 711.mbox/browser


Thanks for the pointer, sebb!

Then, I'd like to update the VOTE to include the following artifacts have
been staged for Apache Commons RDF 0.5.0 RC2:

commons-rdf-rdf4j-0.5.0-tests.jar.asc (SHA1:
04605bc88577af60fa0762ca279be80a57a85958)
commons-rdf-rdf4j-0.5.0.pom (SHA1: 1cdc74b7205fa06531bd59e1ee24f1d15999ab1b)
commons-rdf-rdf4j-0.5.0-javadoc.jar.asc (SHA1:
8f2f0ca7ed441d57638bff113331e2ea2582ce3e)
commons-rdf-rdf4j-0.5.0-sources.jar.asc (SHA1:
3c556b3e00713e99032b47888743370142d681fa)
commons-rdf-rdf4j-0.5.0.jar (SHA1: 9d820f278c80ad6948ae90e5684b7929f0437cb3)
commons-rdf-rdf4j-0.5.0-tests.jar (SHA1:
e7d80cd6cb101c9b1132228e218d501be8e993af)
commons-rdf-rdf4j-0.5.0-javadoc.jar (SHA1:
ae587f243395da5ae868124651d227f581f8c219)
commons-rdf-rdf4j-0.5.0.jar.asc (SHA1:
5f72ef133c0cb54c48f386c0b08789ae1f5b2945)
commons-rdf-rdf4j-0.5.0-test-sources.jar (SHA1:
86f16a8af7d1c9635ef2f53df4db2e115b3c9c71)
commons-rdf-rdf4j-0.5.0-test-sources.jar.asc (SHA1:
e347de285e59484b2a099ce776a4901397f16a2c)
commons-rdf-rdf4j-0.5.0-sources.jar (SHA1:
dcc4d9c6a1f59a8c561c42b1d4b1b6c5851b851f)
commons-rdf-rdf4j-0.5.0.pom.asc (SHA1:
3603993d3cdee09a59d3743cb831d81a9447eaa0)
commons-rdf-api-0.5.0-sources.jar (SHA1:
ab3d5097882ade36948da3850d3012b1618c7838)
commons-rdf-api-0.5.0.jar (SHA1: f2c460dea59ce36ad06591a4e35670a4bd0aceb7)
commons-rdf-api-0.5.0-javadoc.jar.asc (SHA1:
f0dddb805b816ded5f1f3087561e24bbd8d1e4f9)
commons-rdf-api-0.5.0-tests.jar.asc (SHA1:
0b7e622257b722d3cc47a6d81ab4828d791159c4)
commons-rdf-api-0.5.0-sources.jar.asc (SHA1:
589491a448232fed30815c0b5eb2880ad6dcea98)
commons-rdf-api-0.5.0-tests.jar (SHA1:
745b0584a341e5b91a6fe03c1a9f95026dbfd92d)
commons-rdf-api-0.5.0-test-sources.jar.asc (SHA1:
851ce69fcbd42ce5bf1dc1ce8aca0e93eb2f767e)
commons-rdf-api-0.5.0-javadoc.jar (SHA1:
7864c01900a60e3ccc33208faaa22617b9461bdb)
commons-rdf-api-0.5.0-test-sources.jar (SHA1:
347b29318e5b0dc4544035d077cb0d10a93e22f9)
commons-rdf-api-0.5.0.pom (SHA1: cc3382c3a60d815a20bba1763933434f41d85598)
commons-rdf-api-0.5.0.pom.asc (SHA1:
cca3d4f34e229d5ddc672a75e75aec135c3aaef8)
commons-rdf-api-0.5.0.jar.asc (SHA1:
76aef667f3fd941fdea8567bfc4c71009063affc)
commons-rdf-simple-0.5.0-javadoc.jar.asc (SHA1:
2149f0a7b260f08fca4f7bbd90ddb5d727ae768e)
commons-rdf-simple-0.5.0-sources.jar.asc (SHA1:
2e410296acdf351493973fb77ae96d478087ad19)
commons-rdf-simple-0.5.0-tests.jar (SHA1:
95f0a02550a06f214533007af07dc57a50e9ed03)
commons-rdf-simple-0.5.0.pom (SHA1:
b5aa51f49cbbdb9f39fa70d8cf183f63ae0c3a6a)
commons-rdf-simple-0.5.0-test-sources.jar.asc (SHA1:
f7de79994338ebc43659d3c3c727ec545aec389a)
commons-rdf-simple-0.5.0.jar.asc (SHA1:
41d4558af80dc72e81533fae21354931ba06b6b3)
commons-rdf-simple-0.5.0-javadoc.jar (SHA1:
727cf414a2da46a7f0da751756bc74844e5bc6fa)
commons-rdf-simple-0.5.0-tests.jar.asc (SHA1:
84bbfe92be8aa42bfc6a1bb8cc6c4afb2ce1e71c)
commons-rdf-simple-0.5.0-sources.jar (SHA1:
5a781e23952b7cb54c66b8c165b2079a63b335bf)
commons-rdf-simple-0.5.0.jar (SHA1:
eb97fa986f400845f12cd47a48297d30998c8fc2)
commons-rdf-simple-0.5.0.pom.asc (SHA1:
2b633568c9bd640a5f02e761e364d58256c52fc5)
commons-rdf-simple-0.5.0-test-sources.jar (SHA1:
1d6980982a77c46b404021e7545d037febfa5236)
commons-rdf-parent-0.5.0.pom.asc (SHA1:
18216f499afca5b6effa0ac6644b0764a9fe0d0c)
commons-rdf-parent-0.5.0-src.zip.asc (SHA1:
794ca08dc118d1b4d5fcff9ba642f57d5f212faf)
commons-rdf-parent-0.5.0-src.tar.gz.asc (SHA1:
c3b5404d273ab3bcffebe3849d5c9bd80f93db71)
commons-rdf-parent-0.5.0-src.tar.gz (SHA1:
3ea3de8d3e120eb2737fde3c6af50d1e91fd395b)
commons-rdf-parent-0.5.0-site.xml.asc (SHA1:
c13a97d1d7a515fe215305ec32e02e5b779682c0)
commons-rdf-parent-0.5.0-src.zip (SHA1:
155b95960f494c59739caab769ea9f319e91ef9c)
commons-rdf-parent-0.5.0.pom (SHA1:
4186153db162b4382f73be1ce2ff97a98ee5d442)
commons-rdf-parent-0.5.0-site.xml (SHA1:
26fd1dc487f5f002d35841ba8dcc53704652d3b8)
commons-rdf-integration-tests-0.5.0.pom.asc (SHA1:
7ba8e31e1470953bc23ff4b10f5e9cdd42f3b206)
commons-rdf-integration-tests-0.5.0-test-sources.jar (SHA1:
c72eb2184e57d433630eb5177cbdfef1c57613f8)
commons-rdf-integration-tests-0.5.0-tests.jar.asc (SHA1:
73b079eebff0bfd4ebbee64c16a0ecfd782be1ac)
commons-rdf-integration-tests-0.5.0-test-sources.jar.asc (SHA1:
fff692e49536d03416e22dee82ebb0c794dbf8e5)
commons-rdf-integration-tests-0.5.0-tests.jar (SHA1:
bc210de252cae2a4f9f6d6dce554dd00df06c8c2)
commons-rdf-integration-tests-0.5.0.pom (SHA1:
dc8b7754e2069b8c19c507a

Re: [VOTE] Release Apache Commons RDF 0.5.0 based on RC2

[Sergio Fernández]

Hi,

On Mon, Nov 20, 2017 at 10:54 AM, Gary Gregory <garydgreg...@gmail.com>
wrote:

> On Sun, Nov 19, 2017 at 3:08 PM, Sergio Fernández <wik...@apache.org>
> wrote:
> > Apache Commons RDF 0.5.0 RC2 is available for review at (r23205):
> >
> > https://dist.apache.org/repos/dist/dev/commons/rdf/apache-co
> > mmons-rdf-0.5.0-RC2/
>
> The current rev for this link is 23215, are you sure 23205 is correct?
>

And currently it's 23217 for me. But that doesn't mean much.

I'm pretty sure I did push the release on that revision:

$ svn log -l 1
https://dist.apache.org/repos/dist/dev/commons/rdf/apache-commons-rdf-0.5.0-RC2/

r23205 | wikier | 2017-11-19 13:54:15 -0800 (Sun, 19 Nov 2017) | 1 line

added correct source release for apache commons rdf 0.5.0 RC2



So rev. 23205 is still correct. Subversion handles revisions at a global
level. So the checked out revision will always be '>=', '=' only when no
changes in the overall repository, not just in the subpath.


> This source release produces the following binary artifacts:
> >
> > commons-rdf-parent-0.5.0
> > commons-rdf-api-0.5.0
> > commons-rdf-simple-0.5.0
> > commons-rdf-jena-0.5.0
> > commons-rdf-rdf4j-0.5.0
> > commons-rdf-jsonld-java-0.5.0
> > commons-rdf-integration-tests-0.5.0
>
> You should include the checksums from the email you received from Nexus.
>

I read that Commons policy. The issues is that I didn't get that email, and
I couldn't find how to easily gather those checksums given the amount of
binary artifacts this source release produces.

Since I only called to vote the source artifact, I understood the binaries
aren't being actually voted, that's why I didn't dig deeper. But I'm happy
to provide those if someone point me how to gather those checksums from
Nexus.

Cheers,

Re: [VOTE] Release Apache Commons Daemon 1.1.0 based on RC3

[Sergio Fernández]

+1 (non-binding)

So far I've check:

* Source release matches with source repository.
* Signatures and digests.
* Checked headers, LICENSE and NOTICE files.
* Build (OpenJDK 1.8.0_144 with Maven 3.5.0).


On Thu, Nov 16, 2017 at 6:06 AM, Mark Thomas  wrote:

> On 15/11/17 12:35, Mark Thomas wrote:
>
> 
>
> > The proposed 1.1.0 release based on RC3 is:
> > [ ] Broken   - do not release because...
> > [X] Approved - go ahead and release as 1.1.0
>
> Windows with Tomcat 7.0.82
> Tested by replacing the Windows binaries with those from Commons Daemon
> 1.1.0.
> - Digital signatures are valid (Symantec code signing)
> - Passed simple smoke test running on Java 6
> - Configuring Java 9 specific options didn't prevent running on Java 6
>   (as expected)
> - Java 9 options used when running on Java 9 (needed to remove
>endorsedDirs setting - as expected)
>
> Windows with Tomcat trunk
> - Passed simple smoke test running on Java 8
>
> Linux with Tomcat trunk
> - Warnings compiling jsvc
>   - same warnings as with 1.0.15 but now a few more due to DAEMON-377
> fix (not a release blocker in my view)
> - Runs under Java 8
> - Runs under Java 9
>
> Packaging
> - Detailed checks for RC 2 didn't turn up any issues
> - RC3 spot checks of
>   - commons-daemon-1.1.0-sources.jar
>   - commons-daemon-1.1.0-native-src.tar.gz
>   - commons-daemon-1.1.0.jar
>   No issues found
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>

[VOTE] Release Apache Commons RDF 0.5.0 based on RC2

[Sergio Fernández]

Hi,

once we addressed most of the issues from RC1, I'd like to propose to
release Apache Commons RDF 0.5.0 based on RC2.

Apache Commons RDF aims to provide a common Java API for RDF 1.1 graphs and
datasets. API bindings in Commons RDF 0.5.0 include Apache Jena, Eclipse
RDF4J, JSON-LD Java as well as a standalone implementation (simple).

Apache Commons RDF 0.5.0 RC2 is available for review at (r23205):

https://dist.apache.org/repos/dist/dev/commons/rdf/apache-commons-rdf-0.5.0-RC2/

The source code for this RC is available from git tagged as 0.5.0-RC2
(commit 186df0c36981a308338792f02d93fc59776b0b7c):

https://git-wip-us.apache.org/repos/asf?p=commons-rdf.git;a=commit;h=186df0c36981a308338792f02d93fc59776b0b7c

Mirrored at
https://github.com/apache/commons-rdf/commit/186df0c36981a308338792f02d93fc59776b0b7c

This source release produces the following binary artifacts:

commons-rdf-parent-0.5.0
commons-rdf-api-0.5.0
commons-rdf-simple-0.5.0
commons-rdf-jena-0.5.0
commons-rdf-rdf4j-0.5.0
commons-rdf-jsonld-java-0.5.0
commons-rdf-integration-tests-0.5.0

The Maven Staging repository can be found at:

https://repository.apache.org/content/repositories/orgapachecommons-1293

Please vote on releasing this release candidate as:

Apache Commons RDF 0.5.0

The vote is open for at least 72 hours/

[ ] +1 Release this package
[ ] 0 I don't feel strongly about it, but don't object
[ ] -1 Do not release this package because...

Anyone can participate in testing and voting, not just committers,
please feel free to try out the release candidate and provide your
votes!

Thanks

Re: [VOTE] Release Apache Commons RDF 0.5.0 from RC1

[Sergio Fernández]

Stian, I made a mistake, so we preferred to skip 0.4.0 for safety.

About the release itself, that's reason enough gor me for a RC2. The I can
also align with Jena's recent release and so on. I hope to have time to
prepare it within the next couple of days. Any further feedback will be
more than welcome.

Then, please, consider this vote CANCELLED.




On Nov 10, 2017 05:47, "Stian Soiland-Reyes" <st...@apache.org> wrote:

Thanks for the effort, Sergio! And also thanks for the clean-up, Gary!
About time for a release. (What happened to 0.4.0?)


My vote: +0 (binding): Extra files in the dist archive


Checked:  signatures, hashes, builds.


Tested with Ubuntu 16.04:
$ mvn -v
Apache Maven 3.3.9
Maven home: /usr/share/maven
Java version: 1.8.0_151, vendor: Oracle Corporation
Java home: /usr/lib/jvm/java-8-openjdk-amd64/jre
Default locale: en_GB, platform encoding: UTF-8
OS name: "linux", version: "4.10.0-38-generic", arch: "amd64", family:
"unix"




The commons-rdf-examples still says 0.3.0 in its pom - perhaps we
should look at a way to add the examples straight to the build so its
version numbers get updated by the release process -- however I think
it's good that it has a com.example pom.xml rather than implying to
fresh Maven users they need to use our  etc.

(btw, the examples compile and run well updated at 0.5.0)


About extra files:

I see release.properties and pom.xml.releaseBackup is included in the
zip file, which is a bit odd. This implies you zipped it up manually?
This is a bit fragile..


I would expect the release file to be the same as
commons-rdf-parent-0.5.0-src.zip in the Maven repo
https://repository.apache.org/content/repositories/
orgapachecommons-1287/org/apache/commons/commons-rdf-parent/0.5.0/

That archive does not include any releasePackup files or similar. It
should also be under target/checkout/target  after you released -
probably then called apache-commons-rdf-0.5.0-src.zip because the
release profile correctly overrides the local name.



stain@biggie:~/tmp$ diff -ur from-git from-dist/apache-commons-rdf-0.5.0
Only in from-dist/apache-commons-rdf-0.5.0/commons-rdf-api:
pom.xml.releaseBackup
Only in from-dist/apache-commons-rdf-0.5.0/commons-rdf-integration-tests:
pom.xml.releaseBackup
Only in from-dist/apache-commons-rdf-0.5.0/commons-rdf-jena:
pom.xml.releaseBackup
Only in from-dist/apache-commons-rdf-0.5.0/commons-rdf-jsonld-java:
pom.xml.releaseBackup
Only in from-dist/apache-commons-rdf-0.5.0/commons-rdf-rdf4j:
pom.xml.releaseBackup
Only in from-dist/apache-commons-rdf-0.5.0/commons-rdf-simple:
pom.xml.releaseBackup
Only in from-git: .git
Only in from-git: .gitignore
Only in from-dist/apache-commons-rdf-0.5.0: release.properties
Only in from-git: .travis.yml

stain@biggie:~/tmp$ diff -ur from-git from-repo/apache-commons-rdf-0.5.0
Only in from-git: .git
Only in from-git: .gitignore
Only in from-git: .travis.yml

So the one in Maven staging repo more closely match git -- also if
it's the very same file (although different filename) a pet love of me
to easily double-check that the staging repo covers directly the
source of the RC vote.


My preference would be to put the renamed -src.zip from the staging
repo in dist and re-run the VOTE as "RC2" with same staging repo

Of course in this case there is not any harm of those extra files (and
I verified it still matched git tag and repo archive) - so just a +0
from me.

On 7 November 2017 at 03:40, Sergio Fernández <wik...@apache.org> wrote:
> Hi,
>
> coming closed to the Commons PMC procedure, I'd like to update the vote
> with the following information:
>
> * Source release can be found in the office dist area:
> https://dist.apache.org/repos/dist/dev/commons/rdf/apache-
commons-rdf-0.5.0-RC1/
>
> * 0.5.0-RC1 tagged at git:
> https://git-wip-us.apache.org/repos/asf?p=commons-rdf.git;a=commit;h=
ebffdc5890a0f8523b07ff6df8afae461117f832
>
> * Hashes and signatures remain as the original email.
>
> * Added our GPG keys to the Commons file at
> https://www.apache.org/dist/commons/KEYS
>
> I hope these changes makes the PMC more conformable about voting the
> release. If not, please let me know and I'll try to cut a new RC
addressing
> any possible issue.
>
> Cheers,
>
>
>
>
> On Thu, Nov 2, 2017 at 6:27 PM, Sergio Fernández <wik...@apache.org>
wrote:
>
>> Hi,
>>
>> of course, my vote for Apache Commons RDF 0.5.0 from RC1: +1
(non-binding)
>>
>> Thanks for all feedback. I'll try to answer some of the comments received
>> so far.
>>
>> On Wed, Nov 1, 2017 at 9:49 PM, Aaron Coburn <acob...@amherst.edu> wrote:
>> >
>> > I did have some problems building with JDK9 (OS X), first with the
>> version of
>> > the JaCoCo plugin and then later (after changing to a more recent
>> version 

Re: [VOTE] Release Apache Commons Lang 3.7 based on RC1

[Sergio Fernández]

+1 (non-binding)

So far I've checked:

* signatures and digests
* source releases file layouts,
* matched git tag and commit ids
* NOTICE and LICENSE files
* license headers
* build sources in a clean environment  (Maven 3.5.0, OpenJDK 1.8.0_144
64-Bit, Debian amd64)




On Sun, Nov 5, 2017 at 7:45 PM, Gary Gregory  wrote:

> My +1
>
> Gary
>
> On Sat, Nov 4, 2017 at 12:50 PM, Gary Gregory 
> wrote:
>
> > We have fixed a few bugs since Apache Commons Lang 3.6 was released, so I
> > would like to release Apache Commons Lang 3.7.
> >
> > Apache Commons Lang 3.7 RC1 is available for review here:
> > https://dist.apache.org/repos/dist/dev/commons/lang at revision:
> 22853
> > Get it like this: svn co https://dist.apache.org/repos/
> > dist/dev/commons/lang
> >
> > The tag is here:
> > https://git-wip-us.apache.org/repos/asf?p=commons-lang.git;
> > a=tag;h=refs/tags/LANG_3_7_RC1
> > object 425d8085cfcaab5a78bf0632f9ae77b7e9127cf8
> >
> > Maven artifacts are here:
> > https://repository.apache.org/content/repositories/
> > orgapachecommons-1288
> >
> > These are the artifacts and their SHA1 hashes:
> >
> > /org/apache/commons/commons-lang3/3.7/commons-lang3-3.7-
> > test-sources.jar.asc
> > (SHA1: b9d6588eba0ee1cef9edf51283bf2004fcb71238)
> > /org/apache/commons/commons-lang3/3.7/commons-lang3-3.7-tests.jar.asc
> > (SHA1: e300353ba37288f4308534c38488792a57e52e3b)
> > /org/apache/commons/commons-lang3/3.7/commons-lang3-3.7-src.zip
> > (SHA1: 6316036a39e10dc61f7996672af13be0cddd03d5)
> > /org/apache/commons/commons-lang3/3.7/commons-lang3-3.7-sources.jar
> > (SHA1: e7e36219edde1c66c93495a75490d8f526c377cb)
> > /org/apache/commons/commons-lang3/3.7/commons-lang3-3.7-javadoc.jar.asc
> > (SHA1: deba56c5874a5c023ad209f0d7b9f7690830a6fd)
> > /org/apache/commons/commons-lang3/3.7/commons-lang3-3.7-src.zip.asc
> > (SHA1: 31f67cddf7f5bb5a933dcd2667da8af3a86c40ef)
> > /org/apache/commons/commons-lang3/3.7/commons-lang3-3.7-bin.zip.asc
> > (SHA1: dcee70c101432b6a61ec03f3282cf3512c61645d)
> > /org/apache/commons/commons-lang3/3.7/commons-lang3-3.7-tests.jar
> > (SHA1: e2b2ef23bf522cbfa9c49a905fb278ba1fd4eadb)
> > /org/apache/commons/commons-lang3/3.7/commons-lang3-3.7-bin.tar.gz.asc
> > (SHA1: ee9f3adcbe2b7bb93f1300ec843c9d3f25d215db)
> > /org/apache/commons/commons-lang3/3.7/commons-lang3-3.7-test-sources.jar
> > (SHA1: f51e03bffa2fd21efa309e562213803b38d3b5b2)
> > /org/apache/commons/commons-lang3/3.7/commons-lang3-3.7-src.tar.gz.asc
> > (SHA1: 7019c1310c9dcba3375ef03ea509b9caa2de8f6c)
> > /org/apache/commons/commons-lang3/3.7/commons-lang3-3.7-sources.jar.asc
> > (SHA1: 2bb88579e6ced65c30a9f5615f4a83584edba0ce)
> > /org/apache/commons/commons-lang3/3.7/commons-lang3-3.7-bin.tar.gz
> > (SHA1: b7ff9054614d9a3c58798fe93cab468b241b8496)
> > /org/apache/commons/commons-lang3/3.7/commons-lang3-3.7.pom
> > (SHA1: c445be3b6442b41cbea539d4218be3aea9428a55)
> > /org/apache/commons/commons-lang3/3.7/commons-lang3-3.7.jar
> > (SHA1: 557edd918fd41f9260963583ebf5a61a43a6b423)
> > /org/apache/commons/commons-lang3/3.7/commons-lang3-3.7-src.tar.gz
> > (SHA1: 1027d100c5099634a244a9c517e304518507c466)
> > /org/apache/commons/commons-lang3/3.7/commons-lang3-3.7-javadoc.jar
> > (SHA1: 08d6fb4d39bedef08da171550c73b5d84e8c1125)
> > /org/apache/commons/commons-lang3/3.7/commons-lang3-3.7.pom.asc
> > (SHA1: 43481d694125cced7ebba307634d716c96229c69)
> > /org/apache/commons/commons-lang3/3.7/commons-lang3-3.7-bin.zip
> > (SHA1: 18f12e2e26b820ec1680889c3afa0c6a9f65b68a)
> > /org/apache/commons/commons-lang3/3.7/commons-lang3-3.7.jar.asc
> > (SHA1: cdcce5ca9a5df3ee087148c815266ba8567ea7aa)
> >
> > I tested this RC using 'mvn clean verify' on Microsoft Windows [Version
> > 10.0.16299.19] with:
> >
> > - Oracle Java 7
> > - Oracle Java 8
> > - Oracle Java 9
> > - Oracle Java 10 EA b29
> > - IBM Java 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.7.0_80, vendor: Oracle Corporation
> > Java home: C:\Program Files\Java\jdk1.7.0_80\jre
> > Default locale: en_US, platform encoding: Cp1252
> > OS name: "windows 8.1", version: "6.3", arch: "amd64", family: "windows"
> >
> > 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_152, vendor: Oracle Corporation
> > Java home: C:\Program Files\Java\jdk1.8.0_152\jre
> > Default locale: en_US, platform encoding: Cp1252
> > OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
> >
> > 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: 9.0.1, vendor: Oracle Corporation
> > Java home: C:\Program Files\Java\jdk-9.0.1
> > Default locale: en_US, platform encoding: Cp1252
> > OS name: 

Re: [VOTE] Release Apache Commons RDF 0.5.0 from RC1

[Sergio Fernández]

Hi,

coming closed to the Commons PMC procedure, I'd like to update the vote
with the following information:

* Source release can be found in the office dist area:
https://dist.apache.org/repos/dist/dev/commons/rdf/apache-commons-rdf-0.5.0-RC1/

* 0.5.0-RC1 tagged at git:
https://git-wip-us.apache.org/repos/asf?p=commons-rdf.git;a=commit;h=ebffdc5890a0f8523b07ff6df8afae461117f832

* Hashes and signatures remain as the original email.

* Added our GPG keys to the Commons file at
https://www.apache.org/dist/commons/KEYS

I hope these changes makes the PMC more conformable about voting the
release. If not, please let me know and I'll try to cut a new RC addressing
any possible issue.

Cheers,




On Thu, Nov 2, 2017 at 6:27 PM, Sergio Fernández <wik...@apache.org> wrote:

> Hi,
>
> of course, my vote for Apache Commons RDF 0.5.0 from RC1: +1 (non-binding)
>
> Thanks for all feedback. I'll try to answer some of the comments received
> so far.
>
> On Wed, Nov 1, 2017 at 9:49 PM, Aaron Coburn <acob...@amherst.edu> wrote:
> >
> > I did have some problems building with JDK9 (OS X), first with the
> version of
> > the JaCoCo plugin and then later (after changing to a more recent
> version of
> > the plugin) with the japicmp plugin. These would be nice things to fix,
> but
> > I don't see any reason that they need to hold up this release, as the
> > JDK8-built artifacts work just fine when running in JDK9.
>
> I guess most of us we have quite some pending tasks regarding upgrade
> / make compatible our different source bases with JDK9.
>
> So I've registered the request as COMMONSRDF-67.
>
>
> On Thu, Nov 2, 2017 at 4:00 AM, Bruno P. Kinoshita <
> brunodepau...@yahoo.com.br.invalid> wrote:
> >
> > Any plans to use the changes.xml file for next releases?
>
> Sound like a good idea to me. Registwered as COMMONSRDF-68 for the next
> release.
>
> > I have an automated script that downloads the KEYS file from
> https://www.apache.org/dist/commons/KEYS,
> > and it failed. Then re-read the e-mail and found the KEYS here
> https://dist.apache.org/repos/dist/release/incubator/commonsrdf/KEYS:
> >
> > Does it matter which KEYS file is used after the component has been
> graduated?
> > I'm fine with the KEYS file location being in the vote thread, but just
> thought it
> > would be worth checking.
>
> As I pointed in a previous thread, although we graduated as a component,
> most of the team behind the RDF component we are not PMC members. I don't
> have karma for that, but someone should add our KEYS there. I just though
> the file we had during incubation was good enough.
>
>
> > Another minor nit pick: Notice file message was not updated to 2017.
>
> Do you think that could be blocking? Well, noted as COMMONSRDF-69 for now.
>
>
> Thanks.
>
>
>

Re: Maven release plugin?

[Sergio Fernández]

Just be sure you have pushChanges=false, so you can manually push the work
to your RC branch, but you don't push the tag.

Anyways, the commit id is binding for a vote, not the tag (because can be
changed).

On Mon, Nov 6, 2017 at 11:14 AM, Romain Manni-Bucau 
wrote:

> Will not recopy what i said in jcs vote thread but git solves it
> creating the tag locally so you can immediately copy it *locally* and
> only push the rc tag for the vote duration. That said most of
> communities push the tag on a fork and avoid any issue with the asf
> repo. This is how git can solve that issue.
>
> 2017-11-06 19:16 GMT+01:00 Thomas Vandahl :
> > On 06.11.17 09:01, Romain Manni-Bucau wrote:
> >> 2017-11-06 8:59 GMT+01:00 Jochen Wiedmann :
> >>> On Mon, Nov 6, 2017 at 7:27 AM, Romain Manni-Bucau
> >>>  wrote:
> >>>
>  due to the RCx procedure we cant use the maven release plugin, any
>  plan to make it working with commons release procedure or do we just
>  wait to move all to git?
> >>>
> >>> What problem is there when using the plugin?
> >>
> >> the plugin doesn't support the RCx branch creation without corrupting
> >> the final release - due to nexus. It would be fancy to be able to
> >> *automatically* create the right tag if flagged as such in the pom.
> >
> > There is nothing wrong with the plugin. If you read the commons release
> > docs, the chapter about the maven-release-plugin says nothing about RCs,
> > let alone tags. Moving to git would not help as long as the POM
> > scm-section still points to the original tag. (And I'm not suggesting to
> > change that!)
> >
> > Bye, Thomas.
> >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> > For additional commands, e-mail: dev-h...@commons.apache.org
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>

Re: [VOTE] Release Apache Commons RDF 0.5.0 from RC1

[Sergio Fernández]

Hi,

of course, my vote for Apache Commons RDF 0.5.0 from RC1: +1 (non-binding)

Thanks for all feedback. I'll try to answer some of the comments received
so far.

On Wed, Nov 1, 2017 at 9:49 PM, Aaron Coburn  wrote:
>
> I did have some problems building with JDK9 (OS X), first with the
version of
> the JaCoCo plugin and then later (after changing to a more recent version
of
> the plugin) with the japicmp plugin. These would be nice things to fix,
but
> I don't see any reason that they need to hold up this release, as the
> JDK8-built artifacts work just fine when running in JDK9.

I guess most of us we have quite some pending tasks regarding upgrade
/ make compatible our different source bases with JDK9.

So I've registered the request as COMMONSRDF-67.


On Thu, Nov 2, 2017 at 4:00 AM, Bruno P. Kinoshita <
brunodepau...@yahoo.com.br.invalid> wrote:
>
> Any plans to use the changes.xml file for next releases?

Sound like a good idea to me. Registwered as COMMONSRDF-68 for the next
release.

> I have an automated script that downloads the KEYS file from
https://www.apache.org/dist/commons/KEYS,
> and it failed. Then re-read the e-mail and found the KEYS here
https://dist.apache.org/repos/dist/release/incubator/commonsrdf/KEYS:
>
> Does it matter which KEYS file is used after the component has been
graduated?
> I'm fine with the KEYS file location being in the vote thread, but just
thought it
> would be worth checking.

As I pointed in a previous thread, although we graduated as a component,
most of the team behind the RDF component we are not PMC members. I don't
have karma for that, but someone should add our KEYS there. I just though
the file we had during incubation was good enough.


> Another minor nit pick: Notice file message was not updated to 2017.

Do you think that could be blocking? Well, noted as COMMONSRDF-69 for now.


Thanks.

[VOTE] Release Apache Commons RDF 0.5.0 from RC1

[Sergio Fernández]

Hi,

I am pleased to be calling this vote for releasing Apache Commons RDF 0.5.0
from RC1.


Apache Commons RDF aims to provide a common Java API for RDF 1.1
graphs and datasets. API bindings in Commons RDF 0.5.0 include Apache
Jena, Eclipse RDF4J, JSON-LD Java as well as a standalone
implementation (simple).

The release candidate to be voted over is available at:

http://people.apache.org/~wikier/apache-commons-rdf-0.5.0-RC1/

This is the source artifact and its checksums:
http://people.apache.org/~wikier/apache-commons-rdf-0.5.0-RC1/apache-commons-rdf-0.5.0-src.zip
sha1: 2ada00061090e9a92062271d4cba0f70823eab15
md5: 49d1866771696cf97ef796f8f5308b66

To build the release candidate (requires JDK 8, Maven 3.3), run:

mvn clean verify

To rebuild the site, use:

mvn package site

git commit: ebffdc5890a0f8523b07ff6df8afae461117f832

*https://git-wip-us.apache.org/repos/asf?p=commons-rdf.git;a=commit;h=ebffdc5890a0f8523b07ff6df8afae461117f832
*

KEYS:
https://dist.apache.org/repos/dist/release/incubator/commonsrdf/KEYS

Release notes:
*https://github.com/apache/commons-rdf/blob/ebffdc5890a0f8523b07ff6df8afae461117f832/RELEASE-NOTES.txt#L8
*

This source release produces the following binary artifacts:

commons-rdf-parent-0.5.0
commons-rdf-api-0.5.0
commons-rdf-simple-0.5.0
commons-rdf-jena-0.5.0
commons-rdf-rdf4j-0.5.0
commons-rdf-jsonld-java-0.5.0
commons-rdf-integration-tests-0.5.0

Available under the following Maven staging repository:
*https://repository.apache.org/content/repositories/orgapachecommons-1287
*

Please vote on releasing this release candidate as:

Apache Commons RDF 0.5.0

The vote is open for at least 72 hours/

[ ] +1 Release this package
[ ] 0 I don't feel strongly about it, but don't object
[ ] -1 Do not release this package because...

Anyone can participate in testing and voting, not just committers,
please feel free to try out the release candidate and provide your
votes!

Re: [RDF] Commons release?

[Sergio Fernández]

Just for your information, at
https://github.com/apache/commons-rdf/commits/0.5.0-RC I've resumed the
preparation of a new Commons RDF.



On Mon, Oct 30, 2017 at 3:46 AM, sebb <seb...@gmail.com> wrote:

> On 30 October 2017 at 03:26, Sergio Fernández <wik...@apache.org> wrote:
> > Hi,
> >
> > I started to prepare 0.4.0 release [1] at a RC branch [1]. But then I
> facea
> > with an unexpected problem: I have no permissions to write at the
> Commons'
> > dist area.
> >
> > That's because I shouldn't. After graduation, the Commons RDF PPMC wasn't
> > never voted for full Commons PMC (I think Stian was before).
> >
> > I'm not asking for that now. But, how can I get rights there for
> uploading
> > the RC?
>
> I think you would need to be a member of the Commons committer group
> to be able to write to the staging area, i.e.
>
> https://dist.apache.org/repos/dist/dev/commons/
>
> Only PMC members can write to the release area.
>
> > Thanks.
> >
> > [1] https://issues.apache.org/jira/projects/COMMONSRDF/versions/12342089
> > [2] https://github.com/apache/commons-rdf/tree/0.4.0-RC
> >
> >
> > On Wed, Oct 25, 2017 at 7:41 PM, Sergio Fernández <wik...@apache.org>
> wrote:
> >
> >> Sorry guys, I missed this thread.
> >>
> >> I'll take a look during the weekend, if nobody has jumped in before.
> >>
> >> On Oct 24, 2017 21:39, "Gary Gregory" <garydgreg...@gmail.com> wrote:
> >>
> >>> Maybe what is in master is enough?
> >>>
> >>> Gary
> >>>
> >>> On Tue, Oct 24, 2017 at 10:31 PM, Bruno P. Kinoshita <
> >>> brunodepau...@yahoo.com.br.invalid> wrote:
> >>>
> >>> > Not so familiar, more familiar with Jena, but they are related.
> >>> > If nobody else volunteers, I can try to spend a weekend triaging
> issues
> >>> > and seeing if I can catch up with the changes since the last release
> and
> >>> > volunteer to cut a new release.
> >>> > CheersBruno
> >>> >
> >>> >   From: Gary Gregory <garydgreg...@gmail.com>
> >>> >  To: Commons Developers List <dev@commons.apache.org>
> >>> >  Sent: Wednesday, 25 October 2017 4:25 PM
> >>> >  Subject: Re: [RDF] Commons release?
> >>> >
> >>> > Hopefully someone who is familiar with Commons RDF is reading this...
> >>> >
> >>> > Gary
> >>> >
> >>> > On Fri, Oct 20, 2017 at 2:25 PM, Aaron Coburn <acob...@amherst.edu>
> >>> wrote:
> >>> >
> >>> > > Hello,
> >>> > >
> >>> > > I wanted to check in on the status of a 0.4.0 release of Commons
> RDF.
> >>> It
> >>> > > seems that all of the open PRs have been merged. Any idea on a
> >>> timeframe
> >>> > > for the next release?
> >>> > >
> >>> > > Thanks,
> >>> > > Aaron
> >>> > >
> >>> > > On 9/19/17, 5:58 PM, "Aaron Coburn" <acob...@amherst.edu> wrote:
> >>> > >
> >>> > >Sergio,
> >>> > >
> >>> > >Thanks! The LDP server implementation is spread across quite a
> few
> >>> > > repositories in this github organization:
> >>> https://github.com/trellis-ldp
> >>> > > (everything is Apache2 licensed), but the core abstractions are
> found
> >>> in:
> >>> > >
> >>> > >API: https://github.com/trellis-ldp/trellis-api
> >>> > >SPI: https://github.com/trellis-ldp/trellis-spi
> >>> > >HTTP layer: https://github.com/trellis-ldp/trellis-http
> >>> > >
> >>> > >Most of the components have already been released to maven
> central,
> >>> > > but I'm still working on a few of them (particularly the HTTP layer
> >>> and
> >>> > the
> >>> > > persistence layer).
> >>> > >
> >>> > >The main difference between this and, say, Marmotta, is that
> this
> >>> > > implementation is designed to scale horizontally. And by making
> use of
> >>> > > Commons-RDF, the interfaces of this LDP server aren't tied to a
> >>> > particular
> >>> > > RDF library implementation -- e.g. Jena or RDF4

Re: [rdf] Apache Commons RDF 0.4.0 has NOT been approved by the Commons PMC

[Sergio Fernández]

Sure, I'll do a full check on the whole dependency tree.

Thanks for all the changes introduced to master.

On Mon, Oct 30, 2017 at 9:55 AM, Gary Gregory <garydgreg...@gmail.com>
wrote:

> Also, would you mind updating direct dependencies to their latest versions?
> This helps: 'mvn versions:display-dependency-updates'
>
> Gary
>
> On Mon, Oct 30, 2017 at 10:54 AM, Gary Gregory <garydgreg...@gmail.com>
> wrote:
>
> > On Mon, Oct 30, 2017 at 10:38 AM, Sergio Fernández <wik...@apache.org>
> > wrote:
> >
> >> Completely agree. Thanks, Gary!
> >>
> >> So, to wrap this up, the recommendation is that we should skip 0.4.0 and
> >> go
> >> directly to 0.5.0 to avoid any issue, right?
> >>
> >
> > Yes. Notice the src/changes/changes.xml file I added and that needs to be
> > filled in (ideally). Also, I took the liberty of updating the POMs to
> > version 0.5.0-SNAPSHOT. I also update the folder structure to match the
> > ArtifactID=ModuleName=DirectoryName convention. Actually, some plugins
> > might not behave properly if this is not followed IIRC.
> >
> > Gary
> >
> >
> >>
> >>
> >>
> >> On Mon, Oct 30, 2017 at 9:36 AM, Gary Gregory <garydgreg...@gmail.com>
> >> wrote:
> >>
> >> > Yep, all will be 100% OK once all 8 artifacts are gone from r.a.o and
> >> MC.
> >> >
> >> > Then you can do it again for 0.5.0.
> >> >
> >> > Based on my experience as a RM, this is not the last mistake you'll
> make
> >> > ;-) But heck, how are we supposed to learn? ;-)
> >> >
> >> > Gary
> >> >
> >> > On Mon, Oct 30, 2017 at 10:33 AM, Sergio Fernández <wik...@apache.org
> >
> >> > wrote:
> >> >
> >> > > Thanks, Gary.
> >> > >
> >> > > I know the process. We also have it documented at
> >> > > https://github.com/apache/commons-rdf/blob/master/
> RELEASE-PROCESS.md
> >> > >
> >> > > But I pressed the wrong button when I was rolling-back because the
> >> dist
> >> > > issue I faced. In short, I screwed-up.
> >> > >
> >> > > I tried to solve it as soon as it happened. Chatting again with
> INFRA,
> >> > > looks like we only removed one artifact, when my idea was to removed
> >> all.
> >> > >
> >> > > One again, I'm really sorry about the problem. Hopefully we catch it
> >> > early
> >> > > enough for not having further consequences, right?
> >> > >
> >> > > On Mon, Oct 30, 2017 at 9:27 AM, Gary Gregory <
> garydgreg...@gmail.com
> >> >
> >> > > wrote:
> >> > >
> >> > > > In case you had not seen it: http://commons.apache.org/
> >> > > > releases/prepare.html
> >> > > >
> >> > > > WRT to Nexus, all you need to do before a VOTE is to "Close" a
> >> > repository
> >> > > > on r.a.o. That makes it available for review.
> >> > > >
> >> > > > Gary
> >> > > >
> >> > > > On Mon, Oct 30, 2017 at 10:22 AM, Sergio Fernández <
> >> wik...@apache.org>
> >> > > > wrote:
> >> > > >
> >> > > > > As Joel commented at OSSRH-35574: They may temporary appear in
> >> > > directory
> >> > > > > listings as well as search results on search.maven.org, but
> they
> >> > > > shouldn't
> >> > > > > be download-able.
> >> > > > >
> >> > > > > I'll keep an eye on it on the next 48 hours, just in case
> anything
> >> > else
> >> > > > get
> >> > > > > synced or so.
> >> > > > >
> >> > > > > Once again, I'd like to apologize for the issue. I though what
> >> Gavin
> >> > > > early
> >> > > > > did was enough to stop the propagation of the non-voted
> artifacts.
> >> > I'll
> >> > > > > chat with him later to dig more in the causes.
> >> > > > >
> >> > > > > On Mon, Oct 30, 2017 at 8:29 AM, Gary Gregory <
> >> > garydgreg...@gmail.com>
> >> > > > > wrote:
> >> > > > >
> >> > > > > >

Re: [rdf] Apache Commons RDF 0.4.0 has NOT been approved by the Commons PMC

[Sergio Fernández]

Completely agree. Thanks, Gary!

So, to wrap this up, the recommendation is that we should skip 0.4.0 and go
directly to 0.5.0 to avoid any issue, right?



On Mon, Oct 30, 2017 at 9:36 AM, Gary Gregory <garydgreg...@gmail.com>
wrote:

> Yep, all will be 100% OK once all 8 artifacts are gone from r.a.o and MC.
>
> Then you can do it again for 0.5.0.
>
> Based on my experience as a RM, this is not the last mistake you'll make
> ;-) But heck, how are we supposed to learn? ;-)
>
> Gary
>
> On Mon, Oct 30, 2017 at 10:33 AM, Sergio Fernández <wik...@apache.org>
> wrote:
>
> > Thanks, Gary.
> >
> > I know the process. We also have it documented at
> > https://github.com/apache/commons-rdf/blob/master/RELEASE-PROCESS.md
> >
> > But I pressed the wrong button when I was rolling-back because the dist
> > issue I faced. In short, I screwed-up.
> >
> > I tried to solve it as soon as it happened. Chatting again with INFRA,
> > looks like we only removed one artifact, when my idea was to removed all.
> >
> > One again, I'm really sorry about the problem. Hopefully we catch it
> early
> > enough for not having further consequences, right?
> >
> > On Mon, Oct 30, 2017 at 9:27 AM, Gary Gregory <garydgreg...@gmail.com>
> > wrote:
> >
> > > In case you had not seen it: http://commons.apache.org/
> > > releases/prepare.html
> > >
> > > WRT to Nexus, all you need to do before a VOTE is to "Close" a
> repository
> > > on r.a.o. That makes it available for review.
> > >
> > > Gary
> > >
> > > On Mon, Oct 30, 2017 at 10:22 AM, Sergio Fernández <wik...@apache.org>
> > > wrote:
> > >
> > > > As Joel commented at OSSRH-35574: They may temporary appear in
> > directory
> > > > listings as well as search results on search.maven.org, but they
> > > shouldn't
> > > > be download-able.
> > > >
> > > > I'll keep an eye on it on the next 48 hours, just in case anything
> else
> > > get
> > > > synced or so.
> > > >
> > > > Once again, I'd like to apologize for the issue. I though what Gavin
> > > early
> > > > did was enough to stop the propagation of the non-voted artifacts.
> I'll
> > > > chat with him later to dig more in the causes.
> > > >
> > > > On Mon, Oct 30, 2017 at 8:29 AM, Gary Gregory <
> garydgreg...@gmail.com>
> > > > wrote:
> > > >
> > > > > I saw some there this morning. The parent POM is still there
> > > > > http://search.maven.org/#search%7Cga%7C1%7Cg%3A%22org.
> > > > > apache.commons%22%20AND%20a%3A%22commons-rdf-parent%22
> > > > >
> > > > > Gary
> > > > >
> > > > > On Mon, Oct 30, 2017 at 9:05 AM, Sergio Fernández <
> wik...@apache.org
> > >
> > > > > wrote:
> > > > >
> > > > > > Gary,
> > > > > >
> > > > > > as I said at INFRA-15404, I'm not really sure that the invalid
> > > > artifacts
> > > > > > landed to Maven Central.
> > > > > >
> > > > > > I'll chat about the issue with INFRA and update here.
> > > > > >
> > > > > > On Mon, Oct 30, 2017 at 8:03 AM, Gary Gregory <
> > > garydgreg...@gmail.com>
> > > > > > wrote:
> > > > > >
> > > > > > > Thank Rob, tracking at Sonatype:
> > > > > > > https://issues.sonatype.org/browse/OSSRH-35574
> > > > > > >
> > > > > > > Gary
> > > > > > >
> > > > > > > On Mon, Oct 30, 2017 at 8:36 AM, Rob Tompkins <
> > chtom...@gmail.com>
> > > > > > wrote:
> > > > > > >
> > > > > > > > Maven central issue tracker:
> > > > > > > >
> > > > > > > > https://issues.sonatype.org/projects/OSSRH/issues/OSSRH-
> > > > > > > > 27969?filter=allopenissues
> > > > > > > >
> > > > > > > > -Rob
> > > > > > > >
> > > > > > > > > On Oct 30, 2017, at 10:34 AM, Gary Gregory <
> > > > garydgreg...@gmail.com
> > > > > >
> > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > Tracking here:
>

Re: [rdf] Apache Commons RDF 0.4.0 has NOT been approved by the Commons PMC

[Sergio Fernández]

Thanks, Gary.

I know the process. We also have it documented at
https://github.com/apache/commons-rdf/blob/master/RELEASE-PROCESS.md

But I pressed the wrong button when I was rolling-back because the dist
issue I faced. In short, I screwed-up.

I tried to solve it as soon as it happened. Chatting again with INFRA,
looks like we only removed one artifact, when my idea was to removed all.

One again, I'm really sorry about the problem. Hopefully we catch it early
enough for not having further consequences, right?

On Mon, Oct 30, 2017 at 9:27 AM, Gary Gregory <garydgreg...@gmail.com>
wrote:

> In case you had not seen it: http://commons.apache.org/
> releases/prepare.html
>
> WRT to Nexus, all you need to do before a VOTE is to "Close" a repository
> on r.a.o. That makes it available for review.
>
> Gary
>
> On Mon, Oct 30, 2017 at 10:22 AM, Sergio Fernández <wik...@apache.org>
> wrote:
>
> > As Joel commented at OSSRH-35574: They may temporary appear in directory
> > listings as well as search results on search.maven.org, but they
> shouldn't
> > be download-able.
> >
> > I'll keep an eye on it on the next 48 hours, just in case anything else
> get
> > synced or so.
> >
> > Once again, I'd like to apologize for the issue. I though what Gavin
> early
> > did was enough to stop the propagation of the non-voted artifacts. I'll
> > chat with him later to dig more in the causes.
> >
> > On Mon, Oct 30, 2017 at 8:29 AM, Gary Gregory <garydgreg...@gmail.com>
> > wrote:
> >
> > > I saw some there this morning. The parent POM is still there
> > > http://search.maven.org/#search%7Cga%7C1%7Cg%3A%22org.
> > > apache.commons%22%20AND%20a%3A%22commons-rdf-parent%22
> > >
> > > Gary
> > >
> > > On Mon, Oct 30, 2017 at 9:05 AM, Sergio Fernández <wik...@apache.org>
> > > wrote:
> > >
> > > > Gary,
> > > >
> > > > as I said at INFRA-15404, I'm not really sure that the invalid
> > artifacts
> > > > landed to Maven Central.
> > > >
> > > > I'll chat about the issue with INFRA and update here.
> > > >
> > > > On Mon, Oct 30, 2017 at 8:03 AM, Gary Gregory <
> garydgreg...@gmail.com>
> > > > wrote:
> > > >
> > > > > Thank Rob, tracking at Sonatype:
> > > > > https://issues.sonatype.org/browse/OSSRH-35574
> > > > >
> > > > > Gary
> > > > >
> > > > > On Mon, Oct 30, 2017 at 8:36 AM, Rob Tompkins <chtom...@gmail.com>
> > > > wrote:
> > > > >
> > > > > > Maven central issue tracker:
> > > > > >
> > > > > > https://issues.sonatype.org/projects/OSSRH/issues/OSSRH-
> > > > > > 27969?filter=allopenissues
> > > > > >
> > > > > > -Rob
> > > > > >
> > > > > > > On Oct 30, 2017, at 10:34 AM, Gary Gregory <
> > garydgreg...@gmail.com
> > > >
> > > > > > wrote:
> > > > > > >
> > > > > > > Tracking here:
> > > > > > >
> > > > > > > https://issues.apache.org/jira/browse/INFRA-15404
> > > > > > >
> > > > > > > Gary
> > > > > > >
> > > > > > > On Mon, Oct 30, 2017 at 8:18 AM, Gary Gregory <
> > > > garydgreg...@gmail.com>
> > > > > > > wrote:
> > > > > > >
> > > > > > >> Hi All,
> > > > > > >>
> > > > > > >> It appears that Apache Commons RDF 0.4.0 has been released
> into
> > > the
> > > > > wild
> > > > > > >> (our Maven repo AND Maven Central) without approval by the
> > Apache
> > > > > > Commons
> > > > > > >> PMC.
> > > > > > >>
> > > > > > >> I will create an INFRA ticket to delete this release from
> Apache
> > > > > > >> repositories. If any one knows if there is a process for Maven
> > > > > Central,
> > > > > > >> please chime in.
> > > > > > >>
> > > > > > >> I propose that we burn the 0.4.0 version label and move
> > > immediately
> > > > to
> > > > > > >> 0.4.1-SNAPSHOT or 0.5.0-SNAPSHOT.
> > > > > > >>
> > > > > > >> Affected Maven Coords
> > > > > > >>
> > > > > > >> Version:
> > > > > > >> 0.4.0
> > > > > > >>
> > > > > > >> GroupID:
> > > > > > >> org.apache.commons.
> > > > > > >>
> > > > > > >> Artifact IDs:
> > > > > > >> commons-rdf-api
> > > > > > >> commons-rdf-examples
> > > > > > >> commons-rdf-integration-tests
> > > > > > >> commons-rdf-jena
> > > > > > >> commons-rdf-jsonld-java
> > > > > > >> commons-rdf-rdf4j
> > > > > > >> commons-rdf-simple
> > > > > > >>
> > > > > > >>
> > > > > > >> Gary
> > > > > > >>
> > > > > >
> > > > >
> > > >
> > >
> >
>

Re: [rdf] Apache Commons RDF 0.4.0 has NOT been approved by the Commons PMC

[Sergio Fernández]

As Joel commented at OSSRH-35574: They may temporary appear in directory
listings as well as search results on search.maven.org, but they shouldn't
be download-able.

I'll keep an eye on it on the next 48 hours, just in case anything else get
synced or so.

Once again, I'd like to apologize for the issue. I though what Gavin early
did was enough to stop the propagation of the non-voted artifacts. I'll
chat with him later to dig more in the causes.

On Mon, Oct 30, 2017 at 8:29 AM, Gary Gregory <garydgreg...@gmail.com>
wrote:

> I saw some there this morning. The parent POM is still there
> http://search.maven.org/#search%7Cga%7C1%7Cg%3A%22org.
> apache.commons%22%20AND%20a%3A%22commons-rdf-parent%22
>
> Gary
>
> On Mon, Oct 30, 2017 at 9:05 AM, Sergio Fernández <wik...@apache.org>
> wrote:
>
> > Gary,
> >
> > as I said at INFRA-15404, I'm not really sure that the invalid artifacts
> > landed to Maven Central.
> >
> > I'll chat about the issue with INFRA and update here.
> >
> > On Mon, Oct 30, 2017 at 8:03 AM, Gary Gregory <garydgreg...@gmail.com>
> > wrote:
> >
> > > Thank Rob, tracking at Sonatype:
> > > https://issues.sonatype.org/browse/OSSRH-35574
> > >
> > > Gary
> > >
> > > On Mon, Oct 30, 2017 at 8:36 AM, Rob Tompkins <chtom...@gmail.com>
> > wrote:
> > >
> > > > Maven central issue tracker:
> > > >
> > > > https://issues.sonatype.org/projects/OSSRH/issues/OSSRH-
> > > > 27969?filter=allopenissues
> > > >
> > > > -Rob
> > > >
> > > > > On Oct 30, 2017, at 10:34 AM, Gary Gregory <garydgreg...@gmail.com
> >
> > > > wrote:
> > > > >
> > > > > Tracking here:
> > > > >
> > > > > https://issues.apache.org/jira/browse/INFRA-15404
> > > > >
> > > > > Gary
> > > > >
> > > > > On Mon, Oct 30, 2017 at 8:18 AM, Gary Gregory <
> > garydgreg...@gmail.com>
> > > > > wrote:
> > > > >
> > > > >> Hi All,
> > > > >>
> > > > >> It appears that Apache Commons RDF 0.4.0 has been released into
> the
> > > wild
> > > > >> (our Maven repo AND Maven Central) without approval by the Apache
> > > > Commons
> > > > >> PMC.
> > > > >>
> > > > >> I will create an INFRA ticket to delete this release from Apache
> > > > >> repositories. If any one knows if there is a process for Maven
> > > Central,
> > > > >> please chime in.
> > > > >>
> > > > >> I propose that we burn the 0.4.0 version label and move
> immediately
> > to
> > > > >> 0.4.1-SNAPSHOT or 0.5.0-SNAPSHOT.
> > > > >>
> > > > >> Affected Maven Coords
> > > > >>
> > > > >> Version:
> > > > >> 0.4.0
> > > > >>
> > > > >> GroupID:
> > > > >> org.apache.commons.
> > > > >>
> > > > >> Artifact IDs:
> > > > >> commons-rdf-api
> > > > >> commons-rdf-examples
> > > > >> commons-rdf-integration-tests
> > > > >> commons-rdf-jena
> > > > >> commons-rdf-jsonld-java
> > > > >> commons-rdf-rdf4j
> > > > >> commons-rdf-simple
> > > > >>
> > > > >>
> > > > >> Gary
> > > > >>
> > > >
> > >
> >
>

Re: [rdf] Apache Commons RDF 0.4.0 has NOT been approved by the Commons PMC

[Sergio Fernández]

Gary,

as I said at INFRA-15404, I'm not really sure that the invalid artifacts
landed to Maven Central.

I'll chat about the issue with INFRA and update here.

On Mon, Oct 30, 2017 at 8:03 AM, Gary Gregory 
wrote:

> Thank Rob, tracking at Sonatype:
> https://issues.sonatype.org/browse/OSSRH-35574
>
> Gary
>
> On Mon, Oct 30, 2017 at 8:36 AM, Rob Tompkins  wrote:
>
> > Maven central issue tracker:
> >
> > https://issues.sonatype.org/projects/OSSRH/issues/OSSRH-
> > 27969?filter=allopenissues
> >
> > -Rob
> >
> > > On Oct 30, 2017, at 10:34 AM, Gary Gregory 
> > wrote:
> > >
> > > Tracking here:
> > >
> > > https://issues.apache.org/jira/browse/INFRA-15404
> > >
> > > Gary
> > >
> > > On Mon, Oct 30, 2017 at 8:18 AM, Gary Gregory 
> > > wrote:
> > >
> > >> Hi All,
> > >>
> > >> It appears that Apache Commons RDF 0.4.0 has been released into the
> wild
> > >> (our Maven repo AND Maven Central) without approval by the Apache
> > Commons
> > >> PMC.
> > >>
> > >> I will create an INFRA ticket to delete this release from Apache
> > >> repositories. If any one knows if there is a process for Maven
> Central,
> > >> please chime in.
> > >>
> > >> I propose that we burn the 0.4.0 version label and move immediately to
> > >> 0.4.1-SNAPSHOT or 0.5.0-SNAPSHOT.
> > >>
> > >> Affected Maven Coords
> > >>
> > >> Version:
> > >> 0.4.0
> > >>
> > >> GroupID:
> > >> org.apache.commons.
> > >>
> > >> Artifact IDs:
> > >> commons-rdf-api
> > >> commons-rdf-examples
> > >> commons-rdf-integration-tests
> > >> commons-rdf-jena
> > >> commons-rdf-jsonld-java
> > >> commons-rdf-rdf4j
> > >> commons-rdf-simple
> > >>
> > >>
> > >> Gary
> > >>
> >
>

Re: [rdf] Apache Commons RDF 0.4.0 has NOT been approved by the Commons PMC

[Sergio Fernández]

Hi Gary,

I had an issue with the staging repository while preparing RC1 (see another
thread why I didn't continue with the process). But I chatted with INFRA,
so they fixed my error last night few seconds after. So the artifacts
shouldn't continue, in theory. I'm going to double-check what happened
there and come back to you in the next hours.

Apologize for the mistake.

Best,



On Oct 30, 2017 07:18, "Gary Gregory"  wrote:

Hi All,

It appears that Apache Commons RDF 0.4.0 has been released into the wild
(our Maven repo AND Maven Central) without approval by the Apache Commons
PMC.

I will create an INFRA ticket to delete this release from Apache
repositories. If any one knows if there is a process for Maven Central,
please chime in.

I propose that we burn the 0.4.0 version label and move immediately to
0.4.1-SNAPSHOT or 0.5.0-SNAPSHOT.

Affected Maven Coords

Version:
0.4.0

GroupID:
org.apache.commons.

Artifact IDs:
commons-rdf-api
commons-rdf-examples
commons-rdf-integration-tests
commons-rdf-jena
commons-rdf-jsonld-java
commons-rdf-rdf4j
commons-rdf-simple


Gary

Re: [RDF] Commons release?

[Sergio Fernández]

Hi,

I started to prepare 0.4.0 release [1] at a RC branch [1]. But then I facea
with an unexpected problem: I have no permissions to write at the Commons'
dist area.

That's because I shouldn't. After graduation, the Commons RDF PPMC wasn't
never voted for full Commons PMC (I think Stian was before).

I'm not asking for that now. But, how can I get rights there for uploading
the RC?

Thanks.

[1] https://issues.apache.org/jira/projects/COMMONSRDF/versions/12342089
[2] https://github.com/apache/commons-rdf/tree/0.4.0-RC


On Wed, Oct 25, 2017 at 7:41 PM, Sergio Fernández <wik...@apache.org> wrote:

> Sorry guys, I missed this thread.
>
> I'll take a look during the weekend, if nobody has jumped in before.
>
> On Oct 24, 2017 21:39, "Gary Gregory" <garydgreg...@gmail.com> wrote:
>
>> Maybe what is in master is enough?
>>
>> Gary
>>
>> On Tue, Oct 24, 2017 at 10:31 PM, Bruno P. Kinoshita <
>> brunodepau...@yahoo.com.br.invalid> wrote:
>>
>> > Not so familiar, more familiar with Jena, but they are related.
>> > If nobody else volunteers, I can try to spend a weekend triaging issues
>> > and seeing if I can catch up with the changes since the last release and
>> > volunteer to cut a new release.
>> > CheersBruno
>> >
>> >   From: Gary Gregory <garydgreg...@gmail.com>
>> >  To: Commons Developers List <dev@commons.apache.org>
>> >  Sent: Wednesday, 25 October 2017 4:25 PM
>> >  Subject: Re: [RDF] Commons release?
>> >
>> > Hopefully someone who is familiar with Commons RDF is reading this...
>> >
>> > Gary
>> >
>> > On Fri, Oct 20, 2017 at 2:25 PM, Aaron Coburn <acob...@amherst.edu>
>> wrote:
>> >
>> > > Hello,
>> > >
>> > > I wanted to check in on the status of a 0.4.0 release of Commons RDF.
>> It
>> > > seems that all of the open PRs have been merged. Any idea on a
>> timeframe
>> > > for the next release?
>> > >
>> > > Thanks,
>> > > Aaron
>> > >
>> > > On 9/19/17, 5:58 PM, "Aaron Coburn" <acob...@amherst.edu> wrote:
>> > >
>> > >Sergio,
>> > >
>> > >Thanks! The LDP server implementation is spread across quite a few
>> > > repositories in this github organization:
>> https://github.com/trellis-ldp
>> > > (everything is Apache2 licensed), but the core abstractions are found
>> in:
>> > >
>> > >API: https://github.com/trellis-ldp/trellis-api
>> > >SPI: https://github.com/trellis-ldp/trellis-spi
>> > >HTTP layer: https://github.com/trellis-ldp/trellis-http
>> > >
>> > >Most of the components have already been released to maven central,
>> > > but I'm still working on a few of them (particularly the HTTP layer
>> and
>> > the
>> > > persistence layer).
>> > >
>> > >The main difference between this and, say, Marmotta, is that this
>> > > implementation is designed to scale horizontally. And by making use of
>> > > Commons-RDF, the interfaces of this LDP server aren't tied to a
>> > particular
>> > > RDF library implementation -- e.g. Jena or RDF4J -- though I do use
>> Jena
>> > in
>> > > the implementation code. I am also making significant use of ZooKeeper
>> > > (Curator), Kafka and Beam.
>> > >
>> > >Aaron
>> > >
>> > >> On Sep 19, 2017, at 5:27 PM, Sergio Fernández <wik...@apache.org
>> >
>> > > wrote:
>> > >>
>> > >> Hi Aaron,
>> > >>
>> > >> you're right, we have quite some things to release. But first I'
>> d
>> > > like to
>> > >> take a look to our backlog, because we have some open PRs.
>> Hopefully
>> > > I'll
>> > >> have some time later this week, at the latest on the weekend.
>> > >>
>> > >> Just for curiosity, can you provide us a pointer to your Commons
>> > > RDF-based
>> > >> LDP implementation?
>> > >>
>> > >> Thanks.
>> > >>
>> > >> Cheers,
>> > >>
>> > >>
>> > >>
>> > >> On Mon, Sep 18, 2017 at 2:24 PM, Aaron Coburn <
>> acob...@amherst.edu>
>> > > wrote:
>> > >>
>

Re: [RDF] Commons release?

[Sergio Fernández]

Sorry guys, I missed this thread.

I'll take a look during the weekend, if nobody has jumped in before.

On Oct 24, 2017 21:39, "Gary Gregory" <garydgreg...@gmail.com> wrote:

> Maybe what is in master is enough?
>
> Gary
>
> On Tue, Oct 24, 2017 at 10:31 PM, Bruno P. Kinoshita <
> brunodepau...@yahoo.com.br.invalid> wrote:
>
> > Not so familiar, more familiar with Jena, but they are related.
> > If nobody else volunteers, I can try to spend a weekend triaging issues
> > and seeing if I can catch up with the changes since the last release and
> > volunteer to cut a new release.
> > CheersBruno
> >
> >   From: Gary Gregory <garydgreg...@gmail.com>
> >  To: Commons Developers List <dev@commons.apache.org>
> >  Sent: Wednesday, 25 October 2017 4:25 PM
> >  Subject: Re: [RDF] Commons release?
> >
> > Hopefully someone who is familiar with Commons RDF is reading this...
> >
> > Gary
> >
> > On Fri, Oct 20, 2017 at 2:25 PM, Aaron Coburn <acob...@amherst.edu>
> wrote:
> >
> > > Hello,
> > >
> > > I wanted to check in on the status of a 0.4.0 release of Commons RDF.
> It
> > > seems that all of the open PRs have been merged. Any idea on a
> timeframe
> > > for the next release?
> > >
> > > Thanks,
> > > Aaron
> > >
> > > On 9/19/17, 5:58 PM, "Aaron Coburn" <acob...@amherst.edu> wrote:
> > >
> > >Sergio,
> > >
> > >Thanks! The LDP server implementation is spread across quite a few
> > > repositories in this github organization:
> https://github.com/trellis-ldp
> > > (everything is Apache2 licensed), but the core abstractions are found
> in:
> > >
> > >API: https://github.com/trellis-ldp/trellis-api
> > >SPI: https://github.com/trellis-ldp/trellis-spi
> > >HTTP layer: https://github.com/trellis-ldp/trellis-http
> > >
> > >Most of the components have already been released to maven central,
> > > but I'm still working on a few of them (particularly the HTTP layer and
> > the
> > > persistence layer).
> > >
> > >The main difference between this and, say, Marmotta, is that this
> > > implementation is designed to scale horizontally. And by making use of
> > > Commons-RDF, the interfaces of this LDP server aren't tied to a
> > particular
> > > RDF library implementation -- e.g. Jena or RDF4J -- though I do use
> Jena
> > in
> > > the implementation code. I am also making significant use of ZooKeeper
> > > (Curator), Kafka and Beam.
> > >
> > >Aaron
> > >
> > >> On Sep 19, 2017, at 5:27 PM, Sergio Fernández <wik...@apache.org>
> > > wrote:
> > >>
> > >> Hi Aaron,
> > >>
> > >> you're right, we have quite some things to release. But first I' d
> > > like to
> > >> take a look to our backlog, because we have some open PRs.
> Hopefully
> > > I'll
> > >> have some time later this week, at the latest on the weekend.
> > >>
> > >> Just for curiosity, can you provide us a pointer to your Commons
> > > RDF-based
> > >> LDP implementation?
> > >>
> > >> Thanks.
> > >>
> > >> Cheers,
> > >>
> > >>
> > >>
> > >> On Mon, Sep 18, 2017 at 2:24 PM, Aaron Coburn <
> acob...@amherst.edu>
> > > wrote:
> > >>
> > >>> Hi!
> > >>>
> > >>> The last release of commons-rdf was from last November, and there
> > > are some
> > >>> nice features in the master branch that I would really like to
> use
> > > --
> > >>> especially the improved OSGi support. It seems that there are a
> few
> > >>> unresolved jira issues, such that this wouldn't be a 1.0 release,
> > > but even
> > >>> a 0.4.0 release would be great.
> > >>>
> > >>> As a little background, over the last several months I've built a
> > > server
> > >>> implementation of the W3C Linked Data Platform in which
> commons-rdf
> > >>> provides all of the core RDF abstractions.
> > >>>
> > >>> Would it be possible to move forward with a release? I would be
> > > more than
> > >>> happy to help out.
> > >>>
> > >>> Thanks,
> > >>> Aaron
> > >>>
> > >>> acob...@apache.org
> > >>> 
> > > -
> > >>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> > >>> For additional commands, e-mail: dev-h...@commons.apache.org
> > >>>
> > >>>
> > >
> > >?B�
> > > CB�?�?[��X��ܚX�K??K[XZ[?�??]�][��X��ܚX�P?��[[ۜ˘\?
> > > X�?K�ܙ�B��܈?Y??]?[ۘ[??��[X[�?�??K[XZ[?�??]�Z?[???��[[ۜ˘\?X�?K�ܙ�B
> > >
> > >
> > >
> >
> >
>

Re: RDF Commons release?

[Sergio Fernández]

Hi Gary,

I already replied it:

https://lists.apache.org/thread.html/a6ff6e7823f6982afe3e6b13a53567aeb91320e58b1aafbb7c1a3e3d@


Maybe trying to correctly label the subject I actually broke the thread.
Sorry.

On Oct 5, 2017 16:25, "Gary Gregory"  wrote:

> Would anyone closely associated with Commons RDF care to comment?
>
> Gary
>
> On Mon, Sep 18, 2017 at 3:24 PM, Aaron Coburn  wrote:
>
> > Hi!
> >
> > The last release of commons-rdf was from last November, and there are
> some
> > nice features in the master branch that I would really like to use --
> > especially the improved OSGi support. It seems that there are a few
> > unresolved jira issues, such that this wouldn't be a 1.0 release, but
> even
> > a 0.4.0 release would be great.
> >
> > As a little background, over the last several months I've built a server
> > implementation of the W3C Linked Data Platform in which commons-rdf
> > provides all of the core RDF abstractions.
> >
> > Would it be possible to move forward with a release? I would be more than
> > happy to help out.
> >
> > Thanks,
> > Aaron
> >
> > acob...@apache.org
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> > For additional commands, e-mail: dev-h...@commons.apache.org
> >
> >
>

Re: [RDF] Commons release?

[Sergio Fernández]

Hi Aaron,

you're right, we have quite some things to release. But first I' d like to
take a look to our backlog, because we have some open PRs. Hopefully I'll
have some time later this week, at the latest on the weekend.

Just for curiosity, can you provide us a pointer to your Commons RDF-based
LDP implementation?

Thanks.

Cheers,



On Mon, Sep 18, 2017 at 2:24 PM, Aaron Coburn  wrote:

> Hi!
>
> The last release of commons-rdf was from last November, and there are some
> nice features in the master branch that I would really like to use --
> especially the improved OSGi support. It seems that there are a few
> unresolved jira issues, such that this wouldn't be a 1.0 release, but even
> a 0.4.0 release would be great.
>
> As a little background, over the last several months I've built a server
> implementation of the W3C Linked Data Platform in which commons-rdf
> provides all of the core RDF abstractions.
>
> Would it be possible to move forward with a release? I would be more than
> happy to help out.
>
> Thanks,
> Aaron
>
> acob...@apache.org
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>

Re: [RDF] Commons release?

[Sergio Fernández]

On Mon, Sep 18, 2017 at 2:24 PM, Aaron Coburn  wrote:

> Hi!
>
> The last release of commons-rdf was from last November, and there are some
> nice features in the master branch that I would really like to use --
> especially the improved OSGi support. It seems that there are a few
> unresolved jira issues, such that this wouldn't be a 1.0 release, but even
> a 0.4.0 release would be great.
>
> As a little background, over the last several months I've built a server
> implementation of the W3C Linked Data Platform in which commons-rdf
> provides all of the core RDF abstractions.
>
> Would it be possible to move forward with a release? I would be more than
> happy to help out.
>
> Thanks,
> Aaron
>
> acob...@apache.org
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>

Re: [VOTE] Release Apache Commons Configuration 2.1.1 based on RC1

[Sergio Fernández]

7 & 8 using Maven 3.3.9.
>
> Details of changes since 2.1 are in the release notes:
>   https://dist.apache.org/repos/dist/dev/commons/
> configuration/RELEASE-NOTES.txt
>   http://home.apache.org/~britter/commons/configuration/
> 2_1_1_RC1/changes-report.html
>
> Site:
> http://home.apache.org/~britter/commons/configuration/2_1_1_RC1/
>   (note some *relative* links are broken and the 2.1.1 directories are
>   not yet created - these will be OK once the site is deployed)
>
> Clirr Report (compared to 2.1):
> http://home.apache.org/~britter/commons/configuration/
> 2_1_1_RC1/clirr-report.html
>
> RAT Report:
> http://home.apache.org/~britter/commons/configuration/
> 2_1_1_RC1/rat-report.html
>
> KEYS:
>   https://www.apache.org/dist/commons/KEYS
>
> Please review the release candidate and vote.
> This vote will close no sooner that 72 hours from now,
> i.e. sometime after 15:30 CET 8-February 2017
>
>   [ ] +1 Release these artifacts
>   [ ] +0 OK, but...
>   [ ] -0 OK, but really should fix...
>   [ ] -1 I oppose this release because...
>
> Thanks!
>
> Benedikt




-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: RDF commons testing

[Sergio Fernández]

Thanks for the suggestion, Claude!

I agree with Stian, do a PR with how the test suite would change, so then
we are discussing about more concrete things.

On Mon, Jan 30, 2017 at 11:20 AM, Stian Soiland-Reyes <st...@apache.org>
wrote:

> On Mon, 30 Jan 2017 09:08:27 +1100, Peter Ansell <ansell.pe...@gmail.com>
> wrote:
> > Hi Claude,
> > Abstract test classes are working well for Commons RDF so far. Others
> > may benefit from your solution, so feel free to suggest the approach
> > to others who may be interested in exploring it.
>
> I would not dismiss Claude's suggestion out of hand. Apache Commons is
> for anyone who wants to participate! :-)
>
> Claude  - if you would like to have a go in a branch at what Commons RDF
> tests look like using contract testing, then feel free!
>
> >> https://www.linkedin.com/pulse/contract-testing-why-
> abstract-tests-enough-claude-warren-jr
>
> I liked this blog article which explains the problem. We in a way
> already have this problem twice in Commons RDF tests because we have the
> Triple/Quad duality (TripleLike) and Graph/Dataset duality (GraphLike)
> as well as the multiple implementations of the commons-rdf-api
> interfaces.
>
> So you will notice some of those tests have considerable duplication
> with subtle differences, e.g. along the lines of:
>
>
> graph.add(triple);
> assertTrue(graph.contains(triple)
> assertTrue(graph.contains(triple.getSubject(),
> triple.getPredicate(), triple.getObject());
>
> vs
>
> dataset.add(quad);
> assertTrue(dataset.contains(quad));
> assertTrue(dataset.contains(quad.getGraphName(),
>   quad.getSubject(), quad.getPredicate(), quad.getObject());
>
> This could in theory be harmonized so that there's a single abstract
> test class with an abstract method to make the triple/quad - and then
> extensions for Triple and Quad that adds the last decomposition
> assertion.
>
> But as we already use abstract classes to run the tests per RDF
> implementation, and so I thought it would get messy to try to reorganize
> it.
>
>
> Another thing is that now the tests are munged together
> into mainly AbstractRDFTest (which must create an RDF factory instance,
> that then can create the other things) - otherwise you will have to
> make many SomethingImplTest in each module (and easily forget to
> specialize one of the tests in one of the modules)
>
> With your approach, would you still have to make a such specialization,
> or is that automatic?
>
>
> BTW - in your approach, would it work to run the tests out of the box
> from an IDE like Eclipse? I think that is quite important so Commons RDF
> can be maintainable by many people in Apache Commons.
>
>
>
>
> --
> Stian Soiland-Reyes
> University of Manchester
> http://www.esciencelab.org.uk/
> http://orcid.org/-0001-9842-9718
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>


-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: [rdf] roles after graduation

[Sergio Fernández]

Fair enough. Thanks.

On Thu, Jan 19, 2017 at 6:07 PM, Stian Soiland-Reyes <st...@apache.org>
wrote:

> I agree on not expanding too much on the roles and would favour removing
> PPMC roles except for those who are listed only as emeritus.
>
> On 17 Jan 2017 10:30 am, "Jochen Wiedmann" <jochen.wiedm...@gmail.com>
> wrote:
>
> > Hi, Sergio,
> >
> > On Tue, Jan 17, 2017 at 8:31 AM, Sergio Fernández <wik...@apache.org>
> > wrote:
> >
> > > adjusting Stian's role [1} I realized we never had the discussion about
> > the
> > > roles of people on the component after graduation: who wants to keep in
> > the
> > > project, PPMC members need to be voted for Commons PMC, etc.
> > >
> > > Nothing urgent, but eventually needs to be discussed.
> >
> > given Commons history, and my personal experience, I'd strongly
> > discourage to fix any particular "roles" for an open source project. A
> > project works best, if anyone does, what she or he feels needs to be
> > done. (Assuming she, or he, has the necessary privileges, of course.)
> >
> > From reading through your POM, the component has three current
> > (hopefully active :-) PMC members. That's more, than most others have,
> > thus should be sufficient.
> >
> > Jochen
> >
> > -----
> > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> > For additional commands, e-mail: dev-h...@commons.apache.org
> >
> >
>



-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

[rdf] roles after graduation

[Sergio Fernández]

Hi,

adjusting Stian's role [1} I realized we never had the discussion about the
roles of people on the component after graduation: who wants to keep in the
project, PPMC members need to be voted for Commons PMC, etc.

Nothing urgent, but eventually needs to be discussed.

Cheers,

[1]
https://github.com/apache/commons-rdf/commit/b3a013f76520b55eb9d57d3d1a90293d5ba9d3ac

-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: [RDF] Graduating Commons RDF to Commons PMC

[Sergio Fernández]

Source code repository moved to
https://git-wip-us.apache.org/repos/asf/commons-rdf.git

Also the github mirror: https://github.com/apache/commons-rdf

Please, change to the new remote.

On Thu, Dec 1, 2016 at 1:23 AM, Stian Soiland-Reyes <st...@apache.org>
wrote:

> On 30 November 2016 at 03:58, Matt Sicker <boa...@gmail.com> wrote:
> > Is there anything to be done for jira? Also, don't forget to update the
> scm
> > URLs in the pom file.
>
> Yes, I've now changed the permissions of COMMONSRDF in Jira (should
> now match IO, all "Commons developers" are 'Admins'), and asked INFRA
> to change it to the commons notification scheme (issues@commons). I
> also put  Apache Commons Developers  (e.g. issues@commons) as the
> "Lead".
>
> I also renamed the Jenkins build from incubator-commonsrdf to
> commons-rdf (but did not change it's git repo setting yet).
>
> --
> Stian Soiland-Reyes
> http://orcid.org/-0001-9842-9718
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>


-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: [RDF] Graduating Commons RDF to Commons PMC

[Sergio Fernández]

On Wed, Nov 30, 2016 at 11:21 AM, Andy Seaborne <a...@apache.org> wrote:

> There are other RDF related projects in ASF. That's a confusing choice of
> key name.


I agree. But then, how do we accommodate to the current Apache Commons
naming in Jira? Feedback would be more than welcomed.


On 30/11/16 07:33, Sergio Fernández wrote:
>>
>> Well, that's a question I also had. So far we have been using COMMONSRDF
>> as
>> Jira key. All the current components simply use the component name a key
>> [1] (e.g., LANG).
>
>

-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: [RDF] Graduating Commons RDF to Commons PMC

[Sergio Fernández]

Hi,

On Wed, Nov 30, 2016 at 4:58 AM, Matt Sicker <boa...@gmail.com> wrote:

> Is there anything to be done for jira?


Well, that's a question I also had. So far we have been using COMMONSRDF as
Jira key. All the current components simply use the component name a key
[1] (e.g., LANG). I already requested the change to INFRA [2].

BTW, I've just created INFRA-13004 epic for all INFRA stuff [3]. Please,
add there whatever other subtask I've forgot.

Also, don't forget to update the scm URLs in the pom file.
>

Stian has already started with that [4]. We have a open issue with the
publication of the different maven components [5], but I'll try to take a
look later today.

Cheers,

[1] https://issues.apache.org/jira/secure/BrowseProjects.jspa#10260
[2] https://issues.apache.org/jira/browse/INFRA-13003
[3] https://issues.apache.org/jira/browse/INFRA-13004
[4] https://github.com/apache/incubator-commonsrdf/commit/
285a6c172fed01fc966b24621110e609321df021
[5] https://issues.apache.org/jira/browse/COMMONSRDF-50



On 28 November 2016 at 05:35, Stian Soiland-Reyes <st...@apache.org> wrote:
>
> > The Commons RDF graduation vote passed on Commons and Incubator, so
> > Commons RDF will now formally move to become a component of Apache
> > Commons. Thanks everyone who voted!
> >
> >
> > I will continue on Wednesday with doing the technical bureaucracy like
> > updating Incubator meta-files, moving repositories, websites and
> > "closing" the dev@commonsrdf mailing list (autoreply?), as well as
> > listing RDF on the Commons main pages.
> >
> >
> > I hope it won't be too much trouble with the empty commons-rdf
> > repository already existing: https://github.com/apache/commons-rdf --
> > I will ask INFRA to delete that so we can formally do a rename in
> > GitHub to keep all the pull requests and watchers. However I think the
> > new name will be just that, commons-rdf (not "commonsrdf").
> >
> > Likewise I'll ask for redirects for the website after deploying it at
> > https://commons.apache.org/proper/commons-rdf/ and similar for moving
> > the dist.apache.org artifacts to be under
> > http://www.apache.org/dist/commons/rdf/
> >
> >
> > Anything I forgot? Oh, and update our pom.xml to not say "-incubating"
> > anymore :)
> >
> >
> > From now, please post/reply any Commons RDF questions to
> > dev@commons.apache.org with the subject [RDF]. (I'll send a separate
> > reminder about this to the dev@commonsrdf list before it closes)
> >
> >
> > --
> > Stian Soiland-Reyes
> > http://orcid.org/-0001-9842-9718
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> > For additional commands, e-mail: dev-h...@commons.apache.org
> >
> >
>
>
> --
> Matt Sicker <boa...@gmail.com>
>



-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925 <+43%20660%202747925>
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: [VOTE] Accept Commons RDF as a new component

[Sergio Fernández]

Fair enough. Thanks.

On Thu, Nov 24, 2016 at 4:03 PM, Bernd Eckenfels <e...@zusammenkunft.net>
wrote:

> (... sorry got interrupted)
> ... there are arguments for a commons component, but it could also be
> arguments having a dedicated community. So I wanted to express that with an
> abstain.
>
> Gruss
> Bernd
> --
> http://bernd.eckenfels.net
>
>
>
>
> On Thu, Nov 24, 2016 at 4:02 PM +0100, "Bernd Eckenfels" <
> e...@zusammenkunft.net> wrote:
>
>
>
>
>
>
>
>
>
>
> Hello,
> Thank you for the summmary. I was aware of the incubation and the
> discussion on rdf-dev. There are arguments for a common component,
>
> Gruss
> Bernd
> --
> http://bernd.eckenfels.net
>
>
>
>
> On Thu, Nov 24, 2016 at 12:05 PM +0100, "Sergio Fernández" <
> wik...@apache.org> wrote:
>
>
>
>
>
>
>
>
>
>
> Hi Bern
>
> On Wed, Nov 23, 2016 at 8:12 PM, Bernd Eckenfels
> wrote:
>
> > +0 Undecided as there where no activity on commons-dev it feels to me
> > like an other home would be better
> >
>
> That topic was already discussed:
> http://markmail.org/message/u6wumpabst35xknn
>
> Basically we felt Commons RDF was in a too early stage that it'd require a
> dedicate mailing list for its conception. That's why the component was
> moved to incubation first, so all discussion actually happened at
> dev@commonsrdf.a.o. If the vote successes, we already agreed to
> accommodate
> the new component to the Commons PMC conventions (i.e., move all
> discussions to dev@commons.a.o using [RDF] as subjects' prefix).
>
> I hope that explanation would satisfy your question, and you'll cast again
> your vote.
>
> Thanks.
>
> Best,
>
>
>
>
> Am Wed, 23 Nov
> > 2016 13:47:03 + schrieb Stian Soiland-Reyes :
> >
> > > [Note: this is the Commons PMC vote on dev@commons - there's a
> > > concurrent IPMC VOTE thread on general@incubator]
> > >
> > > Since Commons RDF entered incubation, it has evolved the understanding
> > > of its purpose, developed and released code base that is now
> > > stabilizing, moving towards a 1.0.0 release.
> > >
> > > Although the Commons RDF developer community is small it has continued
> > > to grow interest, and Apache Commons feels like a natural home for the
> > > component; as intended when this podling was started. We appreciate
> > > all the help we have received from Commons while incubating, in
> > > particular Gary and Benedikt!
> > >
> > >
> > > The Commons RDF podling has voted to graduate from the Incubator
> > > to join Apache Commons as a new component:
> > >
> > > https://lists.apache.org/thread.html/886ed903b3649203c794f7b7409f31
> > 1b2391ebef1d9157177ba943b6@%3Cdev.commonsrdf.apache.org%3E
> > >
> > >
> > > This email carries over 3 Commons PMC binding votes from
> > > dev@commonsrdf:
> > >
> > >
> > > +1 Stian Soiland-Reyes (Commons PMC binding)
> > > +1 Benedikt Ritter (Commons PMC binding)
> > > +1 Gary Gregory (Commons PMC binding)
> > >
> > >
> > > Proposed component name: rdf
> > >
> > > Proposed package name: org.apache.commons.rdf
> > >
> > > Source code of RDF component:
> > > https://git-wip-us.apache.org/repos/asf?p=incubator-commonsrdf.git
> > > https://github.com/apache/incubator-commonsrdf
> > >
> > > Incubator releases:
> > > http://archive.apache.org/dist/incubator/commonsrdf/
> > >
> > > Website:
> > > http://commonsrdf.incubator.apache.org/
> > >
> > > Project Maturity report (more links from there):
> > > https://github.com/apache/incubator-commonsrdf/blob/master/MATURITY.md
> > >
> > >
> > > This email propose a VOTE to accept Commons RDF as a new component of
> > > Apache Commons.
> > >
> > >
> > > Formally the Apache Incubator PMC will also need to agree the
> > > graduation, a concurrent vote thread is on
> > >
> > > https://lists.apache.org/list.html?gene...@incubator.apache.org
> > >
> > >
> > >
> > >
> > > Please VOTE on graduating Commons RDF as new component:
> > >
> > > [ ] +1 Yes, accept Commons RDF as new component
> > > [ ]  0 Undecided
> > > [ ] -1 No, because...
> > >
> > >
> > > This vote will be open for at least 72 hours, let's say 2016-11-26
> > > 17:00 UTC.
> > >
> >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> > For additional commands, e-mail: dev-h...@commons.apache.org
> >
> >
>
>
> --
> Sergio Fernández
> Partner Technology Manager
> Redlink GmbH
> m: +43 6602747925
> e: sergio.fernan...@redlink.co
> w: http://redlink.co
>
>
>
>
>
>
>
>
>
>
>


-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: [VOTE] Accept Commons RDF as a new component

[Sergio Fernández]

Hi Bern

On Wed, Nov 23, 2016 at 8:12 PM, Bernd Eckenfels <e...@zusammenkunft.net>
wrote:

> +0 Undecided as there where no activity on commons-dev it feels to me
> like an other home would be better
>

That topic was already discussed:
http://markmail.org/message/u6wumpabst35xknn

Basically we felt Commons RDF was in a too early stage that it'd require a
dedicate mailing list for its conception. That's why the component was
moved to incubation first, so all discussion actually happened at
dev@commonsrdf.a.o. If the vote successes, we already agreed to accommodate
the new component to the Commons PMC conventions (i.e., move all
discussions to dev@commons.a.o using [RDF] as subjects' prefix).

I hope that explanation would satisfy your question, and you'll cast again
your vote.

Thanks.

Best,




Am Wed, 23 Nov
> 2016 13:47:03 + schrieb Stian Soiland-Reyes <st...@apache.org>:
>
> > [Note: this is the Commons PMC vote on dev@commons - there's a
> > concurrent IPMC VOTE thread on general@incubator]
> >
> > Since Commons RDF entered incubation, it has evolved the understanding
> > of its purpose, developed and released code base that is now
> > stabilizing, moving towards a 1.0.0 release.
> >
> > Although the Commons RDF developer community is small it has continued
> > to grow interest, and Apache Commons feels like a natural home for the
> > component; as intended when this podling was started. We appreciate
> > all the help we have received from Commons while incubating, in
> > particular Gary and Benedikt!
> >
> >
> > The Commons RDF podling has voted to graduate from the Incubator
> > to join Apache Commons as a new component:
> >
> > https://lists.apache.org/thread.html/886ed903b3649203c794f7b7409f31
> 1b2391ebef1d9157177ba943b6@%3Cdev.commonsrdf.apache.org%3E
> >
> >
> > This email carries over 3 Commons PMC binding votes from
> > dev@commonsrdf:
> >
> >
> > +1 Stian Soiland-Reyes (Commons PMC binding)
> > +1 Benedikt Ritter (Commons PMC binding)
> > +1 Gary Gregory (Commons PMC binding)
> >
> >
> > Proposed component name: rdf
> >
> > Proposed package name: org.apache.commons.rdf
> >
> > Source code of RDF component:
> > https://git-wip-us.apache.org/repos/asf?p=incubator-commonsrdf.git
> > https://github.com/apache/incubator-commonsrdf
> >
> > Incubator releases:
> > http://archive.apache.org/dist/incubator/commonsrdf/
> >
> > Website:
> > http://commonsrdf.incubator.apache.org/
> >
> > Project Maturity report (more links from there):
> > https://github.com/apache/incubator-commonsrdf/blob/master/MATURITY.md
> >
> >
> > This email propose a VOTE to accept Commons RDF as a new component of
> > Apache Commons.
> >
> >
> > Formally the Apache Incubator PMC will also need to agree the
> > graduation, a concurrent vote thread is on
> >
> > https://lists.apache.org/list.html?gene...@incubator.apache.org
> >
> >
> >
> >
> > Please VOTE on graduating Commons RDF as new component:
> >
> > [ ] +1 Yes, accept Commons RDF as new component
> > [ ]  0 Undecided
> > [ ] -1 No, because...
> >
> >
> > This vote will be open for at least 72 hours, let's say 2016-11-26
> > 17:00 UTC.
> >
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>


-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: How to publish multi-module site..?

[Sergio Fernández]

I believe with f6a80e6fcd39a8ee7426826e7b25e5cfe0628820 we've fixed the
COMMONSRDF-50 issue:

https://git1-us-west.apache.org/repos/asf?p=incubator-commonsrdf.git;a=commitdiff;h=f6a80e6fcd39a8ee7426826e7b25e5cfe0628820;hp=b05e3e6e6acad0baeeb7e19358093232119548bb

At list for the the result at target/staging looks good when executing: mvn
clean site site:stage

Please Stian, take a look to double check it.

Cheers,


On Thu, Nov 17, 2016 at 12:25 AM, Gilles <gil...@harfang.homelinux.org>
wrote:

> On Wed, 16 Nov 2016 11:26:41 +, Stian Soiland-Reyes wrote:
>
>> Hi, (in particular Gilles and Artem)
>>
>> What was the status of how to do a multi-site publish?  I just tried
>> now for the Commons RDF 0.3.0 site, and I could not get it to work
>> properly.
>>
>>
>> As mentioned in
>>
>> http://central.maven.org/maven2/org/apache/commons/commons-
>> parent/41/commons-parent-41.pom
>> I added a to  using
>> scm:svn:${commons.scmPubUrl}
>>
>>
>> Note that as Commons RDF is still in the incubator (watch this space)
>> it has a slightly different properties:
>>
>>
>> https://svn.apache.org/repos/infra/websit
>> es/production/commonsrdf/content/
>>
>>
>> ${project.build.directory}/
>> site-content
>>
>>
>> But I could not get it to publish the submodule sites correctly.
>>
>>
>> mvn clean package site-deploy
>>
>>   overwrites the main site with the last module's site instead! (Do not
>> use!)
>>
>>
>>
>>
>> mvn clean package site scm-publish:publish-scm
>>
>> seems to work - but does not publish the sub-sites (e.g.
>> commons-rdf-api/ subfolder)
>>
>>
>> mvn clean package site site:stage scm-publish:publish-scm
>>
>> seems to have the same problem.
>>
>
> In "Commons RNG" (most recent code is in branch "RNG-30__sampling"),
> I've been using the following:
>
> $ mvn clean install site site:stage
>
> It creates the all the (sub-)sites in
>   src//target
> and concatenates them under
>   src/target/staging
> (in the top-level directory).
>
> The problem is that the above command creates a
>   site-content
> svn repository inside each module's directory that contains all the
> (concatenated) web site; whereas IIUC that maven page:
>   https://maven.apache.org/plugins/maven-site-plugin/examples/
> multimodule.html
> it should not be that way (since the "artefactId" and module directory
> name _are_ the same).
> IOW, why does maven automatically create the _sub_-site in each
>   /target/site
> directory but does not copy its content under
>   /site-content//
> ?
>
> I wonder why have a "site-content" under each
>   
> directory, that would only duplicate whole (currently) or part of
> the "top-level"
>   site-content
> ?
>
> Regards,
> Gilles
>
>
> And so I had to do this manual hack to afterwards add the submodules
>> site folders to the SVN of the website:
>>
>> for a in api integration-tests jena jsonld-java rdf4j simple ;
>>   do cp -r $a/target/site target/site-content/commons-rdf-$a ;
>> done
>>
>> cd target/site-content/
>> svn add commons-rdf-*
>> svn commit -m "submodules"
>>
>>
>> Any ideas..?
>>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>


-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: [rng] Travis ?

[Sergio Fernández]

great

On Sun, Aug 21, 2016 at 10:11 PM, Gilles <gil...@harfang.homelinux.org>
wrote:

> On Sat, 20 Aug 2016 16:02:50 +0200, Sergio Fernández wrote:
>
>> Just add the build configuration (.travis.yml) to the repo and ask INFRA
>> to
>> enable it.
>>
>
> Issue filed:
>   https://issues.apache.org/jira/servicedesk/agent/INFRA/issue/INFRA-12463
>
> Gilles
>
>
>
>> On Aug 20, 2016 03:31, "Gilles" <gil...@harfang.homelinux.org> wrote:
>>
>> On Fri, 19 Aug 2016 20:44:46 -0400, Rob Tompkins wrote:
>>>
>>> I’m fairly familiar with build tools like travis, if you want me to
>>>> look into it I can.
>>>>
>>>>
>>> Sure!
>>>
>>> Thanks,
>>> Gilles
>>>
>>> -Rob
>>>
>>>>
>>>> On Aug 19, 2016, at 8:06 PM, Gilles <gil...@harfang.homelinux.org>
>>>> wrote:
>>>>
>>>>>
>>>>> Hi.
>>>>>
>>>>> Does someone know how this
>>>>>  https://travis-ci.org/apache/commons-rng
>>>>> appeared and how to make it reflect the reality?
>>>>>
>>>>>
>>>>> Thank you,
>>>>> Gilles
>>>>>
>>>>>
>>>>>
>>>
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>>> For additional commands, e-mail: dev-h...@commons.apache.org
>>>
>>>
>>>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>


-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: [rng] Travis ?

[Sergio Fernández]

Just add the build configuration (.travis.yml) to the repo and ask INFRA to
enable it.

On Aug 20, 2016 03:31, "Gilles"  wrote:

> On Fri, 19 Aug 2016 20:44:46 -0400, Rob Tompkins wrote:
>
>> I’m fairly familiar with build tools like travis, if you want me to
>> look into it I can.
>>
>
> Sure!
>
> Thanks,
> Gilles
>
> -Rob
>>
>> On Aug 19, 2016, at 8:06 PM, Gilles  wrote:
>>>
>>> Hi.
>>>
>>> Does someone know how this
>>>  https://travis-ci.org/apache/commons-rng
>>> appeared and how to make it reflect the reality?
>>>
>>>
>>> Thank you,
>>> Gilles
>>>
>>>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>

Re: [VOTE] Release Configuration 2.1 based on RC2

[Sergio Fernández]

+1 (non-binding)

So far I've checked: signatures and digests, source releases file layouts,
matched svn commit id, NOTICE
and LICENSE files, license headers, build sources in a clean environment
(Maven 3.3.9, OpenJDK 1.8.0_91 64-Bit, Debian amd64).


On Mon, Aug 1, 2016 at 11:04 AM, Dennis Kieselhorst <d...@apache.org> wrote:

> Hi Benedikt!
>
> > The build log is here [1]. It looks like some generated classes are
> checked
> > by checkstyle which causes the build to fail. The build works with Java 7
> > and Java 8. So my vote again is -1 because I think mvn clean install
> should
> > work with the minimum required JDK out of the box. Sorry.
> >
> That's strange, I don't see why it should behave differently. Anyway
> I've added an exclude for it (this was already done for rat and clirr).
> This time I installed the same versions you used to build it, so next
> time it should be successful. Sorry for being lazy last time...
>
> Regards
> Dennis
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>


-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: [VOTE][LAZY] Migrate Apache Commons CSV to git

[Sergio Fernández]

+1

On Mon, Jun 6, 2016 at 10:03 PM, Gary Gregory <garydgreg...@gmail.com>
wrote:

> +1
>
> Gary
>
> On Mon, Jun 6, 2016 at 12:17 PM, Benedikt Ritter <brit...@apache.org>
> wrote:
>
> > Hello,
> >
> > as done before for other components, I'd like to call a VOTE by LAZY
> > consensus for migrating the Apache Commons CSV component to git. Please
> > object to this vote if you see a problem with this. Otherwise this vote
> > will be considered as passed after 72 hours from now (9th June 2016,
> 21:30
> > CEST)
> >
> > Thank you,
> > Benedikt
> >
>
>
>
> --
> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
> Java Persistence with Hibernate, Second Edition
> <http://www.manning.com/bauer3/>
> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
> Spring Batch in Action <http://www.manning.com/templier/>
> Blog: http://garygregory.wordpress.com
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory
>



-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: [VOTE][LAZY] Migrate Apache Commons IO to git

[Sergio Fernández]

+1

On Tue, Jun 7, 2016 at 10:18 AM, Gary Gregory <garydgreg...@gmail.com>
wrote:

> +1
>
> Gary
>
> On Mon, Jun 6, 2016 at 11:37 PM, Kristian Rosenvold <krosenv...@apache.org
> >
> wrote:
>
> > Hello,
> >
> > I'd like to call a VOTE by LAZY
> > consensus for migrating the Apache Commons IO component to git. Please
> > object to this vote if you see a problem with this. Otherwise this vote
> > will be considered as passed after 72 hours from now (10th June 2016,
> 09:00
> > CET)
> >
> > Thank you,
> > Kristian
> >
>
>
>
> --
> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
> Java Persistence with Hibernate, Second Edition
> <http://www.manning.com/bauer3/>
> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
> Spring Batch in Action <http://www.manning.com/templier/>
> Blog: http://garygregory.wordpress.com
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory
>



-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

[IO] question: list files ordered natively from the fs?

[Sergio Fernández]

Hi,

I've just needed a simple feature, but it should not be that simple if
there is not helper available in Commons IO...

I'd like to get the list of files of a directory ordered from the
filesystem (data, name, etc). I think FileUtils does not provide such
feature, and all solutions I found are quite naive (order in memory the
name and order them).

So, I'd like to ask if there is a good reason for that, probably not enough
support from the IO/NIO stdlib. But I'd like to know the context before I
give it a try ;-)

Cheers,

-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: [ALL] ApacheCON EU 2016 - who is going?

[Sergio Fernández]

I also plan to attend. So let me know how I can help Commons.

On Fri, May 27, 2016 at 10:57 AM, Benedikt Ritter <brit...@apache.org>
wrote:

> Hi,
>
> I'm planning to submit an overview talk about the Apache Commons Project
> for ApacheCON EU 2016 [1]. Is someone else planning to go? I'd love to hear
> talks about VFS, Crypto, CSV and other cool stuff.
>
> Hope to meet you in Sevilla!
> Benedikt
>
> [1] http://events.linuxfoundation.org/events/apachecon-europe
>



-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

[ANNOUNCE] Apache CommonsRDF 0.2.0-incubating released

[Sergio Fernández]

The Apache CommonsRDF team is proud to announce the latest release of
Apache CommonsRDF 0.2.0.

Apache Commons RDF aims to provide a common library for RDF 1.1 that could
be implemented by systems on the Java Virtual Machine (e.g., Apache Jena or
Eclipse RDF4J). The main motivation behind this simple library is revise an
historical incompatibility issue. This library does not pretend to be a
generic API wrapping those libraries, but a set of interfaces for the RDF
1.1 concepts that can be used to expose common RDF 1.1 concepts using
common Java interfaces.

More details can be found at https://commonsrdf.incubator.apache.org/

Version 0.2.0 represent the evolution of the API towards providing a common
RDF library.

Further details can be found in the release notes:
https://s.apache.org/0.2.0-incubating

Binary and source archives are available from:
http://commonsrdf.incubator.apache.org/download.html

User guide:
http://commonsrdf.incubator.apache.org/userguide.html

Maven artifacts have also been made available on repository.apache.org and
Maven Central.

Thanks on behalf of the CommonsRDF PPMC.

Disclaimer: Apache Commons RDF is an effort undergoing incubation at The
Apache Software Foundation (ASF) sponsored by the Apache Incubator PMC.
Incubation is required of all newly accepted projects until a further
review indicates that the infrastructure, communications, and decision
making process have stabilized in a manner consistent with other successful
ASF projects. While incubation status is not necessarily a reflection of
the completeness or stability of the code, it does indicate that the
project has yet to be fully endorsed by the ASF.


-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: [ANNOUNCE] Apache CommonsRDF 0.2.0-incubating released

[Sergio Fernández]

OK, I'll re-issue the announcement.
Apologize for the deficiencies in the first one.

On Thu, May 26, 2016 at 6:54 PM, Gary Gregory <garydgreg...@gmail.com>
wrote:

> On Thu, May 26, 2016 at 7:42 AM, sebb <seb...@gmail.com> wrote:
>
>> There are quite a few typos in the e-mail below, and it does not make
>> it clear that the code is undergoing incubation.
>>
>> The e-mail should include the Incubation Disclaimer.
>> For example see the Mynewt announce message dated May 6th.
>>
>> I think the announce mail should be re-issued with the appropriate
>> corrections.
>>
>
> +1
>
> Gary
>
>
>>
>> On 25 May 2016 at 14:58, Sergio Fernández <wik...@apache.org> wrote:
>> > The Apache CommonsRDF team is proud to announce the latest release of
>> Apache
>> > CommonsRDF 0.2.0.
>> >
>> > Apache BroCommons RDF aims to provide a common library for RDF 1.1 that
>> > could be implemented by systems on the Java Virtual Machine. More
>> details
>> > can be found at https://commonsrdf.incubator.apache.org/
>> >
>> > Version 0.2.0 represent the evolution of the API towards providing a
>> common
>> > RDF library. Further details can be found in the release notes:
>> > https://s.apache.org/0.2.0-incubating
>> >
>> > Binary and source archives are available from:
>> > http://commonsrdf.incubator.apache.org/download.html
>> >
>> > User guide:
>> > http://commonsrdf.incubator.apache.org/userguide.html
>> >
>> > Maven artifacts have also been made available on repository.apache.org
>> and
>> > Maven Central.
>> >
>> > Thanks on behalf of the CmmonsRDF PPMC.
>> >
>> > --
>> > Sergio Fernández
>> > Partner Technology Manager
>> > Redlink GmbH
>> > m: +43 6602747925
>> > e: sergio.fernan...@redlink.co
>> > w: http://redlink.co
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>> For additional commands, e-mail: dev-h...@commons.apache.org
>>
>>
>
>
> --
> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
> Java Persistence with Hibernate, Second Edition
> <http://www.manning.com/bauer3/>
> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
> Spring Batch in Action <http://www.manning.com/templier/>
> Blog: http://garygregory.wordpress.com
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory
>



-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

[ANNOUNCE] Apache CommonsRDF 0.2.0-incubating released

[Sergio Fernández]

The Apache CommonsRDF team is proud to announce the latest release of Apache
CommonsRDF 0.2.0.

Apache BroCommons RDF aims to provide a common library for RDF 1.1 that
could be implemented by systems on the Java Virtual Machine. More details
can be found at https://commonsrdf.incubator.apache.org/

Version 0.2.0 represent the evolution of the API towards providing a common
RDF library. Further details can be found in the release notes:
https://s.apache.org/0.2.0-incubating

Binary and source archives are available from:
http://commonsrdf.incubator.apache.org/download.html

User guide:
http://commonsrdf.incubator.apache.org/userguide.html

Maven artifacts have also been made available on repository.apache.org and
Maven Central.

Thanks on behalf of the CmmonsRDF PPMC.

-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: [Rdf] Re: Nexus: Promotion Completed

[Sergio Fernández]

Hi Bernd,

On Tue, May 24, 2016 at 9:10 AM, <e...@zusammenkunft.net> wrote:
>
> It would be good if Incubator "releases" would be announced here on the
> development list. I havent been aware of all the (excellent) work going on
> in the commons-rdf sub project until I saw this release. The Incubator site
> and the maven artifacts are all fully commons branded already, so it is
> good to keep us in the loop.
>

I forwarded the result of the vote to dev@commons. On purpose our mentors
are also Commons PMC members. But you're absolutely right: in the
incubation process we internally started the vote, and then we continued it
into general@incubator. Maybe for a special "podling" like this we should
do it also here.

We'll try to improve the process for the next releases.

Thanks for such valuable feedback.

Cheers,

-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Fwd: [RESULT] [VOTE] Release Apache CommonsRDF 0.2.0-incubating based on RC3

[Sergio Fernández]

-- Forwarded message --
From: Sergio Fernández <wik...@apache.org>
Date: Tue, May 24, 2016 at 8:45 AM
Subject: [RESULT] [VOTE] Release Apache CommonsRDF 0.2.0-incubating based
on RC3
To: gene...@incubator.apache.org


Hi,

after being open for more than 72 hours, the vote for releasing RC3 as
Apache CommonsRDF 0.2.0-incubating
https://lists.apache.org/thread.html/Zgvi38zfo1yumzk has passed 5 +1s (4
binding) and 1 -0, detailed as follows:

+1s:
Stian Soiland-Reyes
Sergio Fernández
John D. Ament
Lewis John Mcgibbney
Justin Mclean

-0
Gary Gregory

I'll prepare the release and announce it when the sources and maven
binaries will be properly mirrored.

Thanks everybody who has helped in getting out this incubating release.

Cheers,

-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co



-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: [io] Make requirement Java 7?

[Sergio Fernández]

+1
On Apr 25, 2016 11:53 PM, "Gary Gregory"  wrote:

> Does anyone object updating [io] to Java 7?
>
> I have a coupe of utils that sit on top of Java 7 IO classes I'd like to
> include.
>
> Gary
>
> --
> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
> Java Persistence with Hibernate, Second Edition
> 
> JUnit in Action, Second Edition 
> Spring Batch in Action 
> Blog: http://garygregory.wordpress.com
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory
>

Re: [jira] [Apache Infrastructure] Grant write access to Apache Commons git repositories to all ASF committers

[Sergio Fernández]

Hi Benedikt,

On Sun, Apr 10, 2016 at 6:31 PM, Benedikt Ritter <brit...@apache.org> wrote:

> Hi,
>
> this issue has been fixed. All ASF committers should now be able to write
> to our git repositories. Sergio, can you give it a try and commit something
> to the commons-lang git repo?
>

Tested and working:

https://github.com/apache/commons-lang/commit/158373bb2154f188eb82f29d3e87916d147e61ca

:-)


-- Forwarded message -
> From: Mark Thomas <j...@apache.org>
> Date: Sa., 9. Apr. 2016 um 21:37 Uhr
> Subject: [jira] [Apache Infrastructure] Grant write access to Apache
> Commons git repositories to all ASF committers
> To: <brit...@apache.org>
>
>
> Request "Grant write access to Apache Commons git repositories to all ASF
> committers" with key INFRA-10636 has been resolved...
> *Apache Infrastructure* - Something else...
> <https://issues.apache.org/jira/servicedesk/customer/portal/1> Reference:
> *INFRA-10636*
> <https://issues.apache.org/jira/servicedesk/customer/portal/1/INFRA-10636>
> Grant write access to Apache Commons git repositories to all ASF committers
> <https://issues.apache.org/jira/servicedesk/customer/portal/1/INFRA-10636>
> Closed
>
> Mark Thomas Today 21:37
> Should be fixed now. Apologies for the delay.
> Status changed to *Closed* with resolution *Fixed*
> Today 21:37
> You can view the full request
> <https://issues.apache.org/jira/servicedesk/customer/portal/1/INFRA-10636>
> Previous activity
>
> Gary Gregory 14/Jan/16 22:43
> ping?
> Geoffrey Corey 18/Dec/15 20:01
> [~ipv6guru] any update on this?
> Pascal Schumacher 13/Nov/15 17:07
> Any updates on this?
>
> Thanks, Pascal
>
> 4 older messages
> <https://issues.apache.org/jira/servicedesk/customer/portal/1/INFRA-10636>
> Details
> Description Hello,
>
> a while back, the Apache Commons project decided to grant write access to
> it's source code repositories to all ASF committers [1]. We have managed to
> do that for our SVN repository at [2] ourself. However we are in the
> process of migrating our components to git and it looks like only Commons
> committers have write access to the git repositories [3].
>
> This ticket is about finding out what we have to do in order to
> automatically grant write access to all ASF committers to all writable git
> repositories owned by the Apache Commons project.
>
> Thank you!
>
> [1] https://github.com/apache/commons-lang/pull/112#issuecomment-149428870
> [2] https://svn.apache.org/repos/asf/commons/
> [3] https://git-wip-us.apache.org/repos/asf/commons-lang.git
> Component/s Git
>
> This message is automatically generated by JIRA Service Desk.
> If you think it was sent incorrectly, please contact your JIRA
> administrators.
> For more information on JIRA Service Desk, see:
> http://www.atlassian.com/software/jira/service-desk
>



-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: [VOTE] Accept Chimera as new Apache Commons Component

[Sergio Fernández]

+1 (non-binding)

On Mon, Mar 21, 2016 at 10:39 AM, Luc Maisonobe <l...@spaceroots.org> wrote:

> +1 for new component.
>
> Luc
>
> Le 21/03/2016 09:57, Bernd Eckenfels a écrit :
> > +1 Accept Chimera as new Apache Commons Component
> >
> >
> > Gruss
> > Bernd
> >
> > Von: Benedikt Ritter
> > Gesendet: Montag, 21. März 2016 09:45
> > An: Commons Developers List
> > Cc: Hadoop Common
> > Betreff: [VOTE] Accept Chimera as new Apache Commons Component
> >
> > Hi all,
> >
> > after long discussions I think we have gathered enough information to
> > decide whether we want to accept the Chimera project as a new Apache
> > Commons component.
> >
> > Proposed name: Apache Commons Crypto
> > Proposal text:
> > https://github.com/intel-hadoop/chimera/blob/master/PROPOSAL.html
> > Initial Code Base:  https://github.com/intel-hadoop/chimera/
> > Initial Committers (Names in alphabetical order):
> > - Aaron T. Myers (a...@apache.org, Apache Hadoop PMC, one of the original
> > Crypto dev team in Apache Hadoop)
> > - Andrew Wang (w...@apache.org, Apache Hadoop PMC, one of the original
> > Crypto dev team in Apache Hadoop)
> > - Chris Nauroth (cnaur...@apache.org, Apache Hadoop PMC and active
> > reviewer)
> > - Colin P. McCabe (cmcc...@apache.org, Apache Hadoop PMC, one of the
> > original Crypto dev team in Apache Hadoop)
> > - Dapeng Sun (s...@apache.org, Apache Sentry Committer, Chimera
> contributor)
> > - Dian Fu (dia...@apache.org, Apache Sqoop Committer, Chimera
> contributor)
> > - Dong Chen (do...@apache.org, Apache Hive Committer,interested on
> Chimera)
> > - Ferdinand Xu (x...@apache.org, Apache Hive Committer, Chimera
> contributor)
> > - Haifeng Chen (haifengc...@apache.org, Chimera lead and code
> contributor)
> > - Marcelo Vanzin (Apache Spark Committer, Chimera contributor)
> > - Uma Maheswara Rao G (umamah...@apache.org, Apache Hadoop PMC, One of
> the
> > original Crypto dev/review team in Apache Hadoop)
> > - Yi Liu (y...@apache.org, Apache Hadoop PMC, One of the original Crypto
> > dev/review team in Apache Hadoop)
> >
> > Please review the proposal and vote.
> > This vote will close no sooner than 72 hours from now, i.e. after 0900
> > GMT 24-Mar 2016
> >
> >   [ ] +1 Accept Chimera as new Apache Commons Component
> >   [ ] +0 OK, but...
> >   [ ] -0 OK, but really should fix...
> >   [ ] -1 I oppose this because...
> >
> > Thank you!
> > Benedikt
> >
> >
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>


-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: [jira] [Commented] (LANG-1175) Remove Ant-based build

[Sergio Fernández]

So I assume INFRA-10636 is still in the limbo...

Thanks Benedikt for taking care.


On Fri, Feb 26, 2016 at 6:01 AM, ASF GitHub Bot (JIRA) <j...@apache.org>
wrote:

>
> [
> https://issues.apache.org/jira/browse/LANG-1175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15168441#comment-15168441
> ]
>
> ASF GitHub Bot commented on LANG-1175:
> --
>
> Github user asfgit closed the pull request at:
>
> https://github.com/apache/commons-lang/pull/112
>
>
> > Remove Ant-based build
> > --
> >
> > Key: LANG-1175
> > URL: https://issues.apache.org/jira/browse/LANG-1175
> > Project: Commons Lang
> >  Issue Type: Task
> >  Components: lang.*
> >Affects Versions: 3.4
> >Reporter: Sergio Fernández
> >Priority: Trivial
> >  Labels: ant
> > Fix For: 3.5
> >
> >
> > We still have a {{build.xml}} file in our source code, and [~britter]
> asked if we could remove it. The single case could be for helping the
> Debian Java Packaging Team. We [asked|
> https://lists.debian.org/debian-java/2015/10/msg00082.html] and Debian
> has already moved to Maven for Commons Lang 3.x packaging, so it should be
> safe to get rid of it.
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v6.3.4#6332)
>



-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: Anyone for Apache Commons & Apache Con Core 2016 CFP?!

[Sergio Fernández]

I'll probably be there. I'm not the best person to speak for Commons. But
just in case you may need a backup.

On Fri, Jan 29, 2016 at 9:59 AM, Benedikt Ritter <brit...@apache.org> wrote:

> Hi Siegfried,
>
> I'd love to come! I just recentrly presented my talk "Beyond StringUtils"
> at JUG Karlsruhe, which could be expanded into a full fletched conference
> session. The thing is, I'm turning 30 the weekend of Apache Con NA, so I
> won't be able to make it. But I'm definitely planning to be at Apache Con
> EU this year.
>
> Regards,
> Benedikt
>
> 2016-01-28 22:24 GMT+01:00 Siegfried Goeschl <sgoes...@gmx.at>:
>
> > Hi folks,
> >
> > anyone out who would volunteer for a presentation at Apache Con Core - I
> > miss a little bit of enthusiasm :-)
> >
> > We have volunteers/proposals for
> >
> > * commons-exec
> > * commons-email
> > * commons-pool
> > * commons-dbcp
> >
> > For the less enthusiastic among us - don’t worry - we have done this
> > before - we assigned two presentation for a 45 slot to avoid boring the
> > audience to death.
> >
> > In other words
> >
> > * You could present your favourite Apache Commons project for 20 minutes
> > * You could participate as speaker which is a completely different
> > experience than being a visitor - I still have my very first speaker
> badge
> > at home :-)
> > * You could improve you CV (assuming that it is not already 10 pages
> long)
> > * You could give yourself a nice journey to lovely Vancouver
> >
> > Cheers,
> >
> > Siegfried Goeschl
> >
> > PS: Please keep in mind this is not a wildcard to present at ApacheCon -
> > each presentation needs still be accepted but chance are a lot better if
> we
> > team up :-)
> > ---------
> > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> > For additional commands, e-mail: dev-h...@commons.apache.org
> >
> >
>
>
> --
> http://home.apache.org/~britter/
> http://twitter.com/BenediktRitter
> http://github.com/britter
>



-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: Anyone for Apache Commons & Apache Con Core 2016 CFP?!

[Sergio Fernández]

On Fri, Jan 29, 2016 at 12:59 PM, Siegfried Göschl <
siegfried.goes...@it20one.com> wrote:
>
> there are no "best" persons to make a presentation :-)
>

Well, meritocracy does not say no... ;-)

Anyway, I understand your points, so keep me as backup just in case
(although by today I can't warranty 100% I'm attending).


-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: [Lang] Repository Write Access

[Sergio Fernández]

On Tue, Nov 3, 2015 at 8:54 AM, Jörg Schaible <joerg.schai...@swisspost.com>
wrote:
>
> GitHub is only a mirror and therefore read-only.
>
> http://wiki.apache.org/commons/UsingGIT


I know, I got the error trying to push to the actual repo:

$ git push
Counting objects: 5, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (5/5), done.
Writing objects: 100% (5/5), 592 bytes | 0 bytes/s, done.
Total 5 (delta 3), reused 0 (delta 0)
remote: You are not authorized to edit this repository.
remote:
To https://wik...@git-wip-us.apache.org/repos/asf/commons-lang.git
 ! [remote rejected] master -> master (pre-receive hook declined)
error: failed to push some refs to '
https://wik...@git-wip-us.apache.org/repos/asf/commons-lang.git'


-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: [Lang] Repository Write Access

[Sergio Fernández]

On Tue, Nov 3, 2015 at 8:23 AM, Benedikt Ritter <brit...@apache.org> wrote:
>
> I've already created a ticket für INFRA a while ago [1], but so far nothing
> has happend.
>

I guess we'd need to ping infra via the chat or somewhere else...

-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: libcommons-lang-java packaging?

[Sergio Fernández]

Thanks Emmanuel for such detailed introduction. Although not with the
official policies, I have quite some experience on Debian as user (~15
years) and packaging (~2 years). In my company all the internal deployment
process is fully based on Debian processes, including tools such
dch, dpkg-buildpackage, jdeb, reprepro, etc.

I've just submitted my request to Alioth. Assuming that Benedikt would pick
commons-math3 to start, what other package do you see as target for me to
be sponsored?

Thanks.



On Tue, Oct 27, 2015 at 2:08 PM, Emmanuel Bourg <ebo...@apache.org> wrote:

> Le 19/10/2015 21:36, Benedikt Ritter a écrit :
>
> > One thing I'd like to work on, is taking care that all Commons Components
> > can be build with Maven at the Debian project. So some pointers on how
> that
> > works would be really appreciated.
>
> Benedikt, Sergio,
>
> Thank you very much for offering your help. I've compiled a quick start
> guide to work on the Debian packages. Let me know if you have any
> question. You can also get some help on IRC (#debian-java on OFTC).
>
> For switching to Maven I recommend using the commons-math3 package as a
> reference (you can find more examples with "build-rdeps
> maven-debian-helper").
>
> Emmanuel Bourg
>
> 
>
> Part I - Install your development environment
>
> 1. Download the minimal ISO (netinst) for installing Debian:
>
> http://cdimage.debian.org/debian-cd/current/amd64/iso-cd/
>
> 2. Install it (on a spare box, or in a virtual machine)
>
> 3. Upgrade to the testing distribution
>
>Edit /etc/apt/sources.list and replace stable with testing
>Run:
>apt-get update
>apt-get dist-upgrade
>
> 4. Upgrade to the unstable distribution (same procedure)
>
> 5. Install the development tools:
>
> apt-get install build-essential svn-buildpackage git-buildpackage
> quilt default-jdk gnupg-agent topgit
>
> 6. Edit ~/.profile and add your name and your email:
>
> export MAIL=john...@example.org
> export DEBFULLNAME="John Doe"
>
> 7. Create or import a SSH key
>
> 8. Create the file ~/.quiltrc and add:
>
> QUILT_PATCHES=debian/patches
> QUILT_NO_DIFF_INDEX=1
> QUILT_NO_DIFF_TIMESTAMPS=1
> QUILT_REFRESH_ARGS="-p ab"
>
> 9. Create the file ~/.lintianrc and add:
>
> color = always
> pedantic = yes
> display-experimental = yes
> display-info = yes
>
> 10. Create the file ~/.devscripts and add:
>
> DEBCHECKOUT_SOURCE=always
>
> 11. Create an account on http://alioth.debian.org, and upload your SSH
> public key there.
>
> 12. Join the Java Team on alioth:
> https://alioth.debian.org/project/request.php?group_id=30085
>
>
>
> Part II - Update a package
>
> 1. Checkout the package:
>
>debcheckout --auth 
>
> 2. Install the build dependencies
>
>sudo apt-get build-deps 
>
> 3. Modify the package
>
> 4. Update the debian/changelog file with:
>
> dch --team
>
> 5. Rebuild the package:
>
> debuild
>
> 6. Commit your changes (with svn commit or git commit, git push), one
> commit per modification preferably, instead of a one big commit.
>
> 7. When the package is ready, notify the debian-java list about the
> changes you made. A Debian Developer will review them and upload the
> package.
>
> 8. Celebrate your first package update! :)
>
>
>
> Tips and tricks
>
> - Finding a package containing a specific file:
>
> apt-file find 
>
> - Finding a package containing a Maven artifact:
>
> apt-file find  | grep pom
>
> - Inspecting the content of a .deb file:
>
> dpkg -c foo.deb
>
> - Inspecting the metadata of a .deb file:
>
> dpkg -I foo.deb
>
> - Displaying the reverse dependencies of a package:
>
>build-rdeps 
>apt-cache showpkg 
>
>
> Ressources
>
>  Quilt for Debian Maintainers
>  http://pkg-perl.alioth.debian.org/howto/quilt.html
>
>  Using Quilt
>  http://wiki.debian.org/UsingQuilt
>
>  Maintainer Dashboard (pkg-java)
>
> http://udd.debian.org/dmd.cgi?email1=pkg-java-maintainers%40lists.alioth.debian.org
>
>  Guidelines for Packages Maintained on git.debian.org:/git/pkg-java
>  http://wiki.debian.org/Java/JavaGit
>
>
>


-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: Write access for ASF committers to our git repositories

[Sergio Fernández]

On Wed, Oct 21, 2015 at 9:11 AM, Benedikt Ritter <brit...@apache.org> wrote:

> 2015-10-21 9:06 GMT+02:00 Gary Gregory <garydgreg...@gmail.com>:
>
> > Git must be different from Svn WRT infra. I would log an INFRA ticket so
> we
> > can find out if this a one-off for Sergio's account or a problem for all
> > Commons git repos.
>
> Good idea, I'll do that. But I'd like to make sure Sergio really can't push
> to the repo. Maybe he just hasn't tried because he didn't know that it
> works. If there is a problem, I'll talk to infra.
>

No, I can't:

$ git push
Password for 'https://wik...@git-wip-us.apache.org':
Counting objects: 16, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (3/3), done.
Writing objects: 100% (3/3), 315 bytes | 0 bytes/s, done.
Total 3 (delta 2), reused 0 (delta 0)
remote: You are not authorized to edit this repository.
remote:
To https://wik...@git-wip-us.apache.org/repos/asf/commons-lang.git
 ! [remote rejected] master -> master (pre-receive hook declined)
error: failed to push some refs to '
https://wik...@git-wip-us.apache.org/repos/asf/commons-lang.git'




-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: Write access for ASF committers to our git repositories

[Sergio Fernández]

Perfect.

On Wed, Oct 21, 2015 at 9:52 AM, Benedikt Ritter <brit...@apache.org> wrote:

> 2015-10-21 9:42 GMT+02:00 Sergio Fernández <wik...@apache.org>:
>
> > On Wed, Oct 21, 2015 at 9:11 AM, Benedikt Ritter <brit...@apache.org>
> > wrote:
> >
> > > 2015-10-21 9:06 GMT+02:00 Gary Gregory <garydgreg...@gmail.com>:
> > >
> > > > Git must be different from Svn WRT infra. I would log an INFRA ticket
> > so
> > > we
> > > > can find out if this a one-off for Sergio's account or a problem for
> > all
> > > > Commons git repos.
> > >
> > > Good idea, I'll do that. But I'd like to make sure Sergio really can't
> > push
> > > to the repo. Maybe he just hasn't tried because he didn't know that it
> > > works. If there is a problem, I'll talk to infra.
> > >
> >
> > No, I can't:
> >
> > $ git push
> > Password for 'https://wik...@git-wip-us.apache.org':
> > Counting objects: 16, done.
> > Delta compression using up to 4 threads.
> > Compressing objects: 100% (3/3), done.
> > Writing objects: 100% (3/3), 315 bytes | 0 bytes/s, done.
> > Total 3 (delta 2), reused 0 (delta 0)
> > remote: You are not authorized to edit this repository.
> > remote:
> > To https://wik...@git-wip-us.apache.org/repos/asf/commons-lang.git
> >  ! [remote rejected] master -> master (pre-receive hook declined)
> > error: failed to push some refs to '
> > https://wik...@git-wip-us.apache.org/repos/asf/commons-lang.git'
> >
> >
> I've created INFRA-10636 [1].
>
> @Sergio: I won't merge LANG-1175 so that we can use it for testing.
>
> Thank you,
> Benedikt
>
> [1]
> https://issues.apache.org/jira/servicedesk/customer/portal/1/INFRA-10636
>
>
> >
> >
> >
> > --
> > Sergio Fernández
> > Partner Technology Manager
> > Redlink GmbH
> > m: +43 6602747925
> > e: sergio.fernan...@redlink.co
> > w: http://redlink.co
> >
>
>
>
> --
> http://people.apache.org/~britter/
> http://www.systemoutprintln.de/
> http://twitter.com/BenediktRitter
> http://github.com/britter
>



-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: [LANG] Drop Ant build?

[Sergio Fernández]

These are all packages in currently in Debian:

https://packages.debian.org/search?keywords=libcommons

Checking the unstable distribution (the most recently updated package),
these are the packages I saw still depending on ant to build
(Build-Depends):

* libcommons-cli-java 1.3.1-2:
https://sources.debian.net/src/libcommons-cli-java/1.3.1-2/debian/control/
* libcommons-codec-java 1.10-1:
https://sources.debian.net/src/libcommons-codec-java/1.10-1/debian/control/
* libcommons-collections-java 2.1.1-10:
https://sources.debian.net/src/libcommons-collections-java/2.1.1-10/debian/control/
* libcommons-collections3-java 3.2.1-8:
https://sources.debian.net/src/libcommons-collections3-java/3.2.1-8/debian/control/
* libcommons-compress-java 1.10-1:
https://sources.debian.net/src/libcommons-compress-java/1.10-1/debian/control/
* libcommons-digester-java 1.8.1-4:
https://sources.debian.net/src/libcommons-digester-java/1.8.1-4/debian/control/
* libcommons-el-java 1.0-8:
https://sources.debian.net/src/libcommons-el-java/1.0-8/debian/control/
* libcommons-lang-java 2.6-5:
https://sources.debian.net/src/libcommons-lang-java/2.6-5/debian/control/
* libcommons-launcher-java 1.1-8:
https://sources.debian.net/src/libcommons-launcher-java/1.1-8/debian/control/
* libcommons-modeler-java 2.0.1-7:
https://sources.debian.net/src/libcommons-modeler-java/2.0.1-7/debian/control/
* libcommons-net-java 3.3-2:
https://sources.debian.net/src/libcommons-net-java/3.3-2/debian/control/
* libcommons-net2-java 2.2-2:
https://sources.debian.net/src/libcommons-net2-java/2.2-2/debian/control/
* libcommons-validator-java 1:1.4.1-1:
https://sources.debian.net/src/libcommons-validator-java/1:1.4.1-1/debian/control/

Double check would be good, since I could missed any. I think most are old
versions, and given the package naming in Debian are still there. How many
components do actually still use Ant as build system?


On Mon, Oct 19, 2015 at 9:38 PM, Benedikt Ritter <brit...@apache.org> wrote:

> 2015-10-19 21:36 GMT+02:00 Oliver Heger <oliver.he...@oliver-heger.de>:
>
> > So is this a global decision, should we drop ant support for all Commons
> > components? I think there are only a few still maintaining an ant build,
> > and there is no guarantee that these build.xml files are up-to-date.
> >
>
> I think I've read, that some of the components are still build with ant at
> the Debian project. That's why I've offered to migrate all the Debian
> builds that are still using Ant to Maven. After that it's save for us to
> remove the Ant builds from our projects.
>
> Benedikt
>
>
> >
> > Oliver
> >
> > Am 19.10.2015 um 13:24 schrieb James Carman:
> > > +1
> > >
> > > On Mon, Oct 19, 2015 at 5:39 AM Benedikt Ritter <brit...@apache.org>
> > wrote:
> > >
> > >> 2015-10-19 10:50 GMT+02:00 Jan Matèrne (jhm) <apa...@materne.de>:
> > >>
> > >>>>> I thought it was being used to create Debian packages.
> > >>>>
> > >>>> If this turns out to be the case, then please add a note to the Ant
> > >>>> build file to explain this requirement.
> > >>>
> > >>>
> > >>> Haven't looked at the build script.
> > >>> But maybe you could keep only that part producing the Debian packages
> > and
> > >>> use Maven ant-run for including that.
> > >>>
> > >>
> > >> TBH I don't see why Apache Commons should do that. If the Debain
> Project
> > >> wishes to use a build system different from what Commons is using,
> they
> > >> should take care of maintaining it.
> > >>
> > >> Regards,
> > >> Benedikt
> > >>
> > >>
> > >>>
> > >>>
> > >>> Jan
> > >>>
> > >>>
> > >>> -
> > >>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> > >>> For additional commands, e-mail: dev-h...@commons.apache.org
> > >>>
> > >>>
> > >>
> > >>
> > >> --
> > >> http://people.apache.org/~britter/
> > >> http://www.systemoutprintln.de/
> > >> http://twitter.com/BenediktRitter
> > >> http://github.com/britter
> > >>
> > >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> > For additional commands, e-mail: dev-h...@commons.apache.org
> >
> >
>
>
> --
> http://people.apache.org/~britter/
> http://www.systemoutprintln.de/
> http://twitter.com/BenediktRitter
> http://github.com/britter
>



-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: [LANG] Drop Ant build?

[Sergio Fernández]

I have quite some experience building Debian packages with Maven (e.g., see
the jdeb build for Marmotta
https://github.com/apache/marmotta/blob/develop/launchers/marmotta-webapp/pom.xml#L124),
so I can help porting the ant task for commons-lang.

On Mon, Oct 19, 2015 at 10:50 AM, Jan Matèrne (jhm) <apa...@materne.de>
wrote:

> > > I thought it was being used to create Debian packages.
> >
> > If this turns out to be the case, then please add a note to the Ant
> > build file to explain this requirement.
>
>
> Haven't looked at the build script.
> But maybe you could keep only that part producing the Debian packages and
> use Maven ant-run for including that.
>
>
> Jan
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>


-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: [LANG] Drop Ant build?

[Sergio Fernández]

On Mon, Oct 19, 2015 at 3:25 PM, Benedikt Ritter <brit...@apache.org> wrote:

> 2015-10-19 15:11 GMT+02:00 Sergio Fernández <wik...@apache.org>:
>
> > Has anybody read my previous mail?
> >
> > Keep .deb support is straightforward in Maven too. For I have no idea
> what
> > the setup between the Commons project and the Java Packaging team at
> > Debian. Maybe I could ask at debian-j...@lists.debian.org...
> >
>
> Yes, I did :-) I was just trying to follow the "Debian requires the Ant
> build" trail to the end. If you're already subscribed and could take care
> of asking the debian guys, that'd be great!
>

OK, I'll do it.


-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: [LANG] Drop Ant build?

[Sergio Fernández]

Has anybody read my previous mail?

Keep .deb support is straightforward in Maven too. For I have no idea what
the setup between the Commons project and the Java Packaging team at
Debian. Maybe I could ask at debian-j...@lists.debian.org...

On Mon, Oct 19, 2015 at 1:24 PM, James Carman <ja...@carmanconsulting.com>
wrote:

> +1
>
> On Mon, Oct 19, 2015 at 5:39 AM Benedikt Ritter <brit...@apache.org>
> wrote:
>
> > 2015-10-19 10:50 GMT+02:00 Jan Matèrne (jhm) <apa...@materne.de>:
> >
> > > > > I thought it was being used to create Debian packages.
> > > >
> > > > If this turns out to be the case, then please add a note to the Ant
> > > > build file to explain this requirement.
> > >
> > >
> > > Haven't looked at the build script.
> > > But maybe you could keep only that part producing the Debian packages
> and
> > > use Maven ant-run for including that.
> > >
> >
> > TBH I don't see why Apache Commons should do that. If the Debain Project
> > wishes to use a build system different from what Commons is using, they
> > should take care of maintaining it.
> >
> > Regards,
> > Benedikt
> >
> >
> > >
> > >
> > > Jan
> > >
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> > > For additional commands, e-mail: dev-h...@commons.apache.org
> > >
> > >
> >
> >
> > --
> > http://people.apache.org/~britter/
> > http://www.systemoutprintln.de/
> > http://twitter.com/BenediktRitter
> > http://github.com/britter
> >
>



-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: libcommons-lang-java packaging?

[Sergio Fernández]

Hi Emmanuel,

On Mon, Oct 19, 2015 at 4:23 PM, Emmanuel Bourg <ebo...@apache.org> wrote:

> Hi Sergio,
>
> Le 19/10/2015 15:37, Sergio Fernández a écrit :
>
> > So, do you really need the build.xml for maintain
> > the libcommons-lang-java.deb package?
>
> libcommons-lang-java contains the old 2.x version, the new 3.x version
> is packaged in libcommons-lang3-java and already uses Maven. So removing
> the Ant build for Commons Lang will not affect Debian (this isn't true
> for all Commons components though).


OK, perfect, I've created https://issues.apache.org/jira/browse/LANG-1175
for tracking that.


> I've quite good experience with the jdeb plugin [2] for that, and
> > I coould volunteer for the task; but I saw you use another helper method
> > [3]. What would be the preferable setup?
>
> Some help for the maintenance of the Apache Commons components (or the
> other Apache Java projects) would be really welcome (we are ~10 active
> developers maintaining 900 packages spanning the whole Java ecosystem).
> If you are interested I can show you how updates are done and sponsor
> your changes. Commit access and upload rights can also be granted to
> those willing to publish directly the new releases to Debian/Ubuntu.
>

I can't promise that much time, but I'll do my best to help in the
maintenance of packages for the Commons components and other Apache
projects. Related, quite some time ago I opened a RFP for another project
I'm actively involved
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739957 So joining you,
and if someone could sponsor my contributions, I could understand better
how things work. So, tell me, how should we proceed next?

Thanks!


-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: [LANG] Drop Ant build?

[Sergio Fernández]

OK, got what they told me
https://lists.debian.org/debian-java/2015/10/msg00083.html

And is only used to package version 2.x as libcommons-lang-java,
and libcommons-lang3-java has already been moved to Maven. So Ant build
could be safely removed in 3.x, I think. I've created LANG-1175 to track
that, including a preliminary PR to review.

In addition, they look quite over flooded (10 people to maintain around 900
packages) so they asked for some help. I'll probably try to give some help
there, not that much, so anyfody else in the Commons PMC is also welcomed
to help there with the project components.

Cheers,


On Mon, Oct 19, 2015 at 3:26 PM, Sergio Fernández <wik...@apache.org> wrote:

>
>
> On Mon, Oct 19, 2015 at 3:25 PM, Benedikt Ritter <brit...@apache.org>
> wrote:
>
>> 2015-10-19 15:11 GMT+02:00 Sergio Fernández <wik...@apache.org>:
>>
>> > Has anybody read my previous mail?
>> >
>> > Keep .deb support is straightforward in Maven too. For I have no idea
>> what
>> > the setup between the Commons project and the Java Packaging team at
>> > Debian. Maybe I could ask at debian-j...@lists.debian.org...
>> >
>>
>> Yes, I did :-) I was just trying to follow the "Debian requires the Ant
>> build" trail to the end. If you're already subscribed and could take care
>> of asking the debian guys, that'd be great!
>>
>
> OK, I'll do it.
>
>
> --
> Sergio Fernández
> Partner Technology Manager
> Redlink GmbH
> m: +43 6602747925
> e: sergio.fernan...@redlink.co
> w: http://redlink.co
>



-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: [LANG] Drop Ant build?

[Sergio Fernández]

Me neither.

On Fri, Oct 16, 2015 at 6:26 PM, Matt Benson <gudnabr...@gmail.com> wrote:

> I don't see any point in keeping the Ant build, TBH.
>
> Matt
>
> On Fri, Oct 16, 2015 at 10:41 AM, Benedikt Ritter <brit...@apache.org>
> wrote:
> > Hi,
> >
> > Maven has been our leading build system for a long time now. Maintaining
> > the Ant build causes trouble. For example I often forget to synchronize
> > changes I make to the dependencies in pom.xml with the ant build.
> >
> > Are there any objections against removing the Ant build from the project?
> >
> > BR,
> > Benedikt
> >
> >
> > --
> > http://people.apache.org/~britter/
> > http://www.systemoutprintln.de/
> > http://twitter.com/BenediktRitter
> > http://github.com/britter
>
> -----
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>


-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

[ANN] Apache Commons RDF 0.1.0-incubating released

[Sergio Fernández]

The CommonsRDF team is pleased to announce the release of the Apache
Commons RDF, version 0.1.0-incubating.

Commons RDF aims to provide a common library for RDF 1.1 that could be
implemented by systems on the Java Virtual Machine.

The source release ca be downloaded from:

http://commonsrdf.incubator.apache.org/download.html

Maven artifact are available to download from Maven Central.

The changelog is available from the ASF Jira:

https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316620version=12332056

Check out our user guide for an introduction how to use the api:

http://commonsrdf.incubator.apache.org/userguide.html

Enjoy,

-The Apache Commons RDF team

-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

[RESULT] [VOTE] Release Apache Commons RDF 0.1.0-incubating RC2

[Sergio Fernández]

Hello,

the vote for releasing Apache Commons RDF 0.1.0-incubating RC2 passes with:

7 +1 votes (5 from IPMC):

* Olivier Lamy (IPMC)
* Enrico Daga (PPMC)
* Tommaso Teofili (IPMC)
* Lewis John Mcgibbney (IPMC)
* Stian Soiland-Reyes (PPMC)
* Andy Seaborne (IPMC and PPMC)
* Sergio Fernández (IPMC and PPMC)

and 1 +0 vote:

* Justin Mclean (IPMC)

Thanks everybody to have contributed to this release in any way. We'll work
to improve some details in the next release.

I'll promote the artifacts and send the announce once the release has been
synced to all mirrors.

Cheers,

-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: [RDF] grant Commons RDF (incubating) permission to deploy artifacts to org.apache.commons groupId

[Sergio Fernández]

Hi,

the CommonsRDF podling is preparing the fist incubating release, and the
PPMC members need to be granted with access to deploy maven artifacts
to org.apache.commons groupId in our nexus.

The Commons PMC is aware of such request, but if you have any question
please feel free to ask.

Thanks in advance.

Cheers,


On Tue, May 5, 2015 at 2:48 AM, Phil Steitz phil.ste...@gmail.com wrote:

 Try mailing repository@



  On May 4, 2015, at 12:32 PM, Benedikt Ritter brit...@apache.org wrote:
 
  2015-05-04 18:46 GMT+02:00 Gary Gregory garydgreg...@gmail.com:
 
  On Sun, May 3, 2015 at 12:03 PM, Phil Steitz phil.ste...@gmail.com
  wrote:
 
  On 5/3/15 11:56 AM, Jochen Wiedmann wrote:
  On Sun, May 3, 2015 at 4:44 PM, Sergio Fernández wik...@apache.org
  wrote:
  we're discussing our first incubating release, and we came to the
  issue
  that we are not grant with permissions to deploy maven artifacts to
  the
  org.apache.commons groupId [1].
  Why org.apache.commons, and not, say, org.apache.commons.rdf? The
  former seems overly broad to me.
 
  Could be we should have gone that way years ago when we moved to
  org.apache.commons:commons-foo; but that ship has sailed, so I think
  its best to stay consistent with the rest of the components and
  proceed as proposed.
 
  Some rambling thoughts (tm):
 
  I like to 'fix' things too but I was on the fence about this one until
 now.
  Yes, there is a redundancy because the substring 'commons' is in the
  AID/GID twice; but that is OK I claim. Why? The GID is the TLP ID, so of
  course we have o.a.commons, that's a must. The AID is the component,
 which
  I always call Commons Foo, and sometimes Apache Commons Foo when I want
 to
  make it clear to folks (at work for example) that I am talking about
  software hosted at Apache. If I were to talk within Apache about Foo, I
 bet
  some folks would not know what Foo is or where it lives. If I say
 'Commons
  Foo' then it's obvious (I hope). That is how I justify to myself the
  commons in the AID.
 
  FWIW: Over at Log4j, we have log4j- as the prefix for all module
 names,
  and no one seems to mind.
 
  I'm all for consistency. VFS does it this way, Weaver does it this way,
  Chain does it this way. And GID matching TLP ID makes sense as well.
 
  Who can grant the necessary permissions?
 
 
 
  Gary
 
 
 
  Phil
 
  Jochen
 
  -
  To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
  For additional commands, e-mail: dev-h...@commons.apache.org
 
 
  -
  To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
  For additional commands, e-mail: dev-h...@commons.apache.org
 
 
  --
  E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
  Java Persistence with Hibernate, Second Edition
  http://www.manning.com/bauer3/
  JUnit in Action, Second Edition http://www.manning.com/tahchiev/
  Spring Batch in Action http://www.manning.com/templier/
  Blog: http://garygregory.wordpress.com
  Home: http://garygregory.com/
  Tweet! http://twitter.com/GaryGregory
 
 
 
  --
  http://people.apache.org/~britter/
  http://www.systemoutprintln.de/
  http://twitter.com/BenediktRitter
  http://github.com/britter

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




-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: [RDF] grant Commons RDF (incubating) permission to deploy artifacts to org.apache.commons groupId

[Sergio Fernández]

Hi Brian,

On Tue, May 5, 2015 at 3:54 PM, Brian Fox bri...@sonatype.com wrote:

 As there is no ldap group for the podling, can you please file an infra
 jira with the user ids to be added?


The missing LDAP group is weird... anyway, all details at jira:
https://issues.apache.org/jira/browse/INFRA-9600
Thanks!





 On Tue, May 5, 2015 at 9:53 AM, Sergio Fernández wik...@apache.org
 wrote:

  Hi,
 
  the CommonsRDF podling is preparing the fist incubating release, and the
  PPMC members need to be granted with access to deploy maven artifacts
  to org.apache.commons groupId in our nexus.
 
  The Commons PMC is aware of such request, but if you have any question
  please feel free to ask.
 
  Thanks in advance.
 
  Cheers,
 
 
  On Tue, May 5, 2015 at 2:48 AM, Phil Steitz phil.ste...@gmail.com
 wrote:
 
  Try mailing repository@
 
 
 
   On May 4, 2015, at 12:32 PM, Benedikt Ritter brit...@apache.org
  wrote:
  
   2015-05-04 18:46 GMT+02:00 Gary Gregory garydgreg...@gmail.com:
  
   On Sun, May 3, 2015 at 12:03 PM, Phil Steitz phil.ste...@gmail.com
   wrote:
  
   On 5/3/15 11:56 AM, Jochen Wiedmann wrote:
   On Sun, May 3, 2015 at 4:44 PM, Sergio Fernández 
 wik...@apache.org
   wrote:
   we're discussing our first incubating release, and we came to the
   issue
   that we are not grant with permissions to deploy maven artifacts
 to
   the
   org.apache.commons groupId [1].
   Why org.apache.commons, and not, say, org.apache.commons.rdf? The
   former seems overly broad to me.
  
   Could be we should have gone that way years ago when we moved to
   org.apache.commons:commons-foo; but that ship has sailed, so I think
   its best to stay consistent with the rest of the components and
   proceed as proposed.
  
   Some rambling thoughts (tm):
  
   I like to 'fix' things too but I was on the fence about this one
 until
  now.
   Yes, there is a redundancy because the substring 'commons' is in the
   AID/GID twice; but that is OK I claim. Why? The GID is the TLP ID, so
  of
   course we have o.a.commons, that's a must. The AID is the component,
  which
   I always call Commons Foo, and sometimes Apache Commons Foo when I
  want to
   make it clear to folks (at work for example) that I am talking about
   software hosted at Apache. If I were to talk within Apache about Foo,
  I bet
   some folks would not know what Foo is or where it lives. If I say
  'Commons
   Foo' then it's obvious (I hope). That is how I justify to myself the
   commons in the AID.
  
   FWIW: Over at Log4j, we have log4j- as the prefix for all module
  names,
   and no one seems to mind.
  
   I'm all for consistency. VFS does it this way, Weaver does it this
 way,
   Chain does it this way. And GID matching TLP ID makes sense as well.
  
   Who can grant the necessary permissions?
  
  
  
   Gary
  
  
  
   Phil
  
   Jochen
  
  
 -
   To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
   For additional commands, e-mail: dev-h...@commons.apache.org
  
  
  
 -
   To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
   For additional commands, e-mail: dev-h...@commons.apache.org
  
  
   --
   E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
   Java Persistence with Hibernate, Second Edition
   http://www.manning.com/bauer3/
   JUnit in Action, Second Edition http://www.manning.com/tahchiev/
   Spring Batch in Action http://www.manning.com/templier/
   Blog: http://garygregory.wordpress.com
   Home: http://garygregory.com/
   Tweet! http://twitter.com/GaryGregory
  
  
  
   --
   http://people.apache.org/~britter/
   http://www.systemoutprintln.de/
   http://twitter.com/BenediktRitter
   http://github.com/britter
 
  -
  To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
  For additional commands, e-mail: dev-h...@commons.apache.org
 
 
 
 
  --
  Sergio Fernández
  Partner Technology Manager
  Redlink GmbH
  m: +43 6602747925
  e: sergio.fernan...@redlink.co
  w: http://redlink.co
 




-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: [RDF] grant Commons RDF (incubating) permission to deploy artifacts to org.apache.commons groupId

[Sergio Fernández]

Hi,

any consensus about this?

Please, take into account this issue is blocking the publication of our
first (incubating) release.

Thanks.

Cheers,


On Sun, May 3, 2015 at 10:53 PM, Sergio Fernández wik...@apache.org wrote:

 Well, we just followed Gary and Benedikt recommendation to adopt the
 current components' style. For us as podling is fine whatever you decide,
 we just need a decision (an permission to deploy over it).

 On Sun, May 3, 2015 at 9:33 PM, Phil Steitz phil.ste...@gmail.com wrote:

 On 5/3/15 12:26 PM, Jochen Wiedmann wrote:
  On Sun, May 3, 2015 at 9:03 PM, Phil Steitz phil.ste...@gmail.com
 wrote:
  On 5/3/15 11:56 AM, Jochen Wiedmann wrote:
  On Sun, May 3, 2015 at 4:44 PM, Sergio Fernández wik...@apache.org
 wrote:
  we're discussing our first incubating release, and we came to the
 issue
  that we are not grant with permissions to deploy maven artifacts to
 the
  org.apache.commons groupId [1].
  Why org.apache.commons, and not, say, org.apache.commons.rdf? The
  former seems overly broad to me.
  Could be we should have gone that way years ago when we moved to
  org.apache.commons:commons-foo; but that ship has sailed, so I think
  its best to stay consistent with the rest of the components and
  proceed as proposed.
 
  First release, and the ship has sailed? Sorry, but I don't think so.

 What I meant was the decision to standardize on

 GroupId: org.apache.commons
 ArtifactId: commons-foo[v]

 I am -1 for making new components different.

 Phil
 
  Jochen
 
 


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




 --
 Sergio Fernández
 Partner Technology Manager
 Redlink GmbH
 m: +43 6602747925
 e: sergio.fernan...@redlink.co
 w: http://redlink.co




-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: [RDF] grant Commons RDF (incubating) permission to deploy artifacts to org.apache.commons groupId

[Sergio Fernández]

Well, we just followed Gary and Benedikt recommendation to adopt the
current components' style. For us as podling is fine whatever you decide,
we just need a decision (an permission to deploy over it).

On Sun, May 3, 2015 at 9:33 PM, Phil Steitz phil.ste...@gmail.com wrote:

 On 5/3/15 12:26 PM, Jochen Wiedmann wrote:
  On Sun, May 3, 2015 at 9:03 PM, Phil Steitz phil.ste...@gmail.com
 wrote:
  On 5/3/15 11:56 AM, Jochen Wiedmann wrote:
  On Sun, May 3, 2015 at 4:44 PM, Sergio Fernández wik...@apache.org
 wrote:
  we're discussing our first incubating release, and we came to the
 issue
  that we are not grant with permissions to deploy maven artifacts to
 the
  org.apache.commons groupId [1].
  Why org.apache.commons, and not, say, org.apache.commons.rdf? The
  former seems overly broad to me.
  Could be we should have gone that way years ago when we moved to
  org.apache.commons:commons-foo; but that ship has sailed, so I think
  its best to stay consistent with the rest of the components and
  proceed as proposed.
 
  First release, and the ship has sailed? Sorry, but I don't think so.

 What I meant was the decision to standardize on

 GroupId: org.apache.commons
 ArtifactId: commons-foo[v]

 I am -1 for making new components different.

 Phil
 
  Jochen
 
 


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




-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: [VOTE][LAZY] Release commons-skin-4.1 based on RC1

[Sergio Fernández]

+1 (non-binding)

On Sun, May 3, 2015 at 11:43 AM, Benedikt Ritter brit...@apache.org wrote:

 Hi all,

 the Commons RDF project has discovered a problem with the Commons Skin when
 using it with a base url different from commons.apache.org (see
 COMMONSSITE-82 [1]). To fix this, I'd like to call a vote by lazy consensus
 to release commons-skin-4.1 based on RC1. The only change to commons-skin-4
 is the fix of COMMONSSITE-82.

 The files:
   https://repository.apache.org/content/repositories/orgapachecommons-1089

 The tag:


 https://svn.apache.org/repos/asf/commons/proper/commons-skin/tags/commons-skin-4.1-RC1

 The site:

 none.

 This VOTE by LAZY-CONSENSUS is open for at least 72 hours. It will finish
 no earlier than 06-May 2015 at 12:00 CEST.

 No need to vote unless you think there is a problem, in which case please
 vote -1 and explain what the issue is.

 Thanks!
 Benedikt


 [1] https://issues.apache.org/jira/browse/COMMONSSITE-82
 --
 http://people.apache.org/~britter/
 http://www.systemoutprintln.de/
 http://twitter.com/BenediktRitter
 http://github.com/britter




-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

[RDF] grant Commons RDF (incubating) permission to deploy artifacts to org.apache.commons groupId

[Sergio Fernández]

Hi,

we're discussing our first incubating release, and we came to the issue
that we are not grant with permissions to deploy maven artifacts to the
org.apache.commons groupId [1].

The path of the project of graduating as a Commons components has not
changed. So we have agreed to keep compatible with the current Commons
approach, naming our artifacts as org.apache.commons:commons-rdf-*

Therefore the PPMC would like to discuss that with you, asking for
permissions to deploy to the Commons groupId.

Thanks so much.

Cheers,

[1] http://markmail.org/message/uctgwzq2f7ueuwib
[2] http://markmail.org/message/jrle67wpuhenqhic

-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co