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

2017-11-01 Thread Aaron Coburn 
+1 (non-binding)

Checked signature, checksums
Built with JDK8 on OS X with no problems
Deployed all artifacts in Karaf 4.1 (OSGi)
License and Notice files are present

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.

Aaron Coburn
acob...@apache.org


On 11/1/17, 11:46 PM, "Sergio Fernández"  wrote:

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!

[VOTE] Release Apache Commons RDF 0.5.0 from RC1

2017-11-01 Thread 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?

2017-11-01 Thread 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  wrote:

> On 30 October 2017 at 03:26, Sergio Fernández  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 
> 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"  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 
> >>> >  To: Commons Developers List 
> >>> >  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 
> >>> 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"  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
>

[GitHub] commons-rdf pull request #42: COMMONSRDF-66: fixes RIOT exception in JenaDat...

2017-11-01 Thread asfgit 
Github user asfgit closed the pull request at:

https://github.com/apache/commons-rdf/pull/42


---

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

Re: [jelly] Site build and Jellydoc plugin

2017-11-01 Thread Bruno P. Kinoshita 
I think it may be worth to try to get in touch with Kohsuke. He became the CTO 
of CloudBees some time ago, but is still involved in the project (not writing 
as much code as before) mainly with decisions, and eventual pull request review.
You can find him sometimes on IRC / FreeNode, in the jenkins channel. But given 
how busy he might be, probably dropping him an e-mail and waiting a bit more 
might be a better idea.

Hope that helpsBruno

  From: Oliver Heger 
 To: Commons Developers List  
 Sent: Thursday, 2 November 2017 9:34 AM
 Subject: [jelly] Site build and Jellydoc plugin
   
Hi,

recently I did some work to get the Jelly site build with Maven running.
As this is experimental, I created my own fork of the project for this
purpose [1].

An important part of the documentation is the Jellydoc, an automatically
generated documentation for the standard tag libs shipped with Jelly.
This documentation is generated by the maven-jellydoc-plugin [2].
Unfortunately, the plugin has a few bugs which cause the site build to fail.

I therefore created a pull request [3] that fixes these problems. With
the patched version the build is now successful.

However, there has not yet been a reaction on this PR. Given the fact
that the plugin code had not been touched for more than 6 years, it may
well be possible that Kohsuke Kawaguchi, the author of the plugin, is no
longer interested in this code base.

Any thoughts how we could proceed here?

Oliver

[1] https://github.com/oheger/commons-jelly/tree/siteBuild
[2] https://github.com/kohsuke/maven-jellydoc-plugin
[3] https://github.com/kohsuke/maven-jellydoc-plugin/pull/1

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

Re: [pool] LinkedBlockingDeque

2017-11-01 Thread Bruno P. Kinoshita 
I think it sounds like a good idea. Probably worth creating a JIRA ticket for 
that and checking if anyone would volunteer to tackle it.
CheersBruno

  From: Gary Gregory 
 To: Commons Developers List  
 Sent: Thursday, 2 November 2017 8:39 AM
 Subject: [pool] LinkedBlockingDeque
   
Hi All,

Pool implements its own LinkedBlockingDeque which is almost like Java
7's LinkedBlockingDeque.

The JRE LinkedBlockingDeque is not a drop in replacement for
our LinkedBlockingDeque.

Any thoughts on migrating from our custom LinkedBlockingDeque to the JRE's
version?

Gary

[jelly] Site build and Jellydoc plugin

2017-11-01 Thread Oliver Heger 
Hi,

recently I did some work to get the Jelly site build with Maven running.
As this is experimental, I created my own fork of the project for this
purpose [1].

An important part of the documentation is the Jellydoc, an automatically
generated documentation for the standard tag libs shipped with Jelly.
This documentation is generated by the maven-jellydoc-plugin [2].
Unfortunately, the plugin has a few bugs which cause the site build to fail.

I therefore created a pull request [3] that fixes these problems. With
the patched version the build is now successful.

However, there has not yet been a reaction on this PR. Given the fact
that the plugin code had not been touched for more than 6 years, it may
well be possible that Kohsuke Kawaguchi, the author of the plugin, is no
longer interested in this code base.

Any thoughts how we could proceed here?

Oliver

[1] https://github.com/oheger/commons-jelly/tree/siteBuild
[2] https://github.com/kohsuke/maven-jellydoc-plugin
[3] https://github.com/kohsuke/maven-jellydoc-plugin/pull/1

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

[pool] LinkedBlockingDeque

2017-11-01 Thread Gary Gregory 
Hi All,

Pool implements its own LinkedBlockingDeque which is almost like Java
7's LinkedBlockingDeque.

The JRE LinkedBlockingDeque is not a drop in replacement for
our LinkedBlockingDeque.

Any thoughts on migrating from our custom LinkedBlockingDeque to the JRE's
version?

Gary