You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@rya.apache.org by Jorge Machado <jo...@me.com.INVALID> on 2018/10/23 08:51:58 UTC

Upgrade of Rya to RDF4j

Hi guys, 

I saw on https://github.com/apache/incubator-rya/pull/291that we migrated from OpenRDF Sesame 2.7.6 to RDF4J 2.3.1 but I don’t see a release for it. 

Any tipps how should I do it ?

Regards

Jorge Machado
www.jmachado.me

Re: Upgrade of Rya to RDF4j

Posted by "Aaron D. Mihalik" <aa...@gmail.com>.
If the PR has been pulled in, you can use the Apache snapshot repo

https://repository.apache.org/content/repositories/snapshots/

—Aaron
On Tue, Oct 23, 2018 at 10:47 AM White, Eric <Er...@parsons.com> wrote:

> Jorge,
>
> This will be in the next published release of Rya (4.0.0). It is not
> available on any repo yet. Until then the source can be built locally from
> master.
>
> Thanks,
> -Eric White
>
> -----Original Message-----
> From: Jorge Machado <jo...@me.com.INVALID>
> Sent: Tuesday, October 23, 2018 4:52 AM
> To: dev@rya.incubator.apache.org
> Subject: Upgrade of Rya to RDF4j
>
> Hi guys,
>
> I saw on
> https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_apache_incubator-2Drya_pull_291that&d=DwIFaQ&c=Nwf-pp4xtYRe0sCRVM8_LWH54joYF7EKmrYIdfxIq10&r=RaJkRMooYbg4vmML14E10F9hYEBLOeOHS3mAimFNgqQ&m=6Ls2mnPq0HhW0f8lsmU95UMRVT1UeJsFvGh44BzTizU&s=uCP4uOYT1SN2qzsadi3iftt9KgUrud2CS95njv44Y8Y&e=
> we migrated from OpenRDF Sesame 2.7.6 to RDF4J 2.3.1 but I don’t see a
> release for it.
>
> Any tipps how should I do it ?
>
> Regards
>
> Jorge Machado
>
> https://urldefense.proofpoint.com/v2/url?u=http-3A__www.jmachado.me&d=DwIFaQ&c=Nwf-pp4xtYRe0sCRVM8_LWH54joYF7EKmrYIdfxIq10&r=RaJkRMooYbg4vmML14E10F9hYEBLOeOHS3mAimFNgqQ&m=6Ls2mnPq0HhW0f8lsmU95UMRVT1UeJsFvGh44BzTizU&s=eAzZPx3uWTUGtQ8iVYjpSbwy6F1rvolhmgtn70npjkA&e=
>
>
>
>
>
>
> NOTICE: This email message and all attachments transmitted with it may
> contain privileged and confidential information, and information that is
> protected by, and proprietary to, Parsons Corporation, and is intended
> solely for the use of the addressee for the specific purpose set forth in
> this communication. If the reader of this message is not the intended
> recipient, you are hereby notified that any reading, dissemination,
> distribution, copying, or other use of this message or its attachments is
> strictly prohibited, and you should delete this message and all copies and
> backups thereof. The recipient may not further distribute or use any of the
> information contained herein without the express written authorization of
> the sender. If you have received this message in error, or if you have any
> questions regarding the use of the proprietary information contained
> therein, please contact the sender of this message immediately, and the
> sender will provide you with further instructions.
>

RE: Upgrade of Rya to RDF4j

Posted by "White, Eric" <Er...@parsons.com>.
Jorge,

This will be in the next published release of Rya (4.0.0). It is not available on any repo yet. Until then the source can be built locally from master.

Thanks,
-Eric White

-----Original Message-----
From: Jorge Machado <jo...@me.com.INVALID>
Sent: Tuesday, October 23, 2018 4:52 AM
To: dev@rya.incubator.apache.org
Subject: Upgrade of Rya to RDF4j

Hi guys,

I saw on https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_apache_incubator-2Drya_pull_291that&d=DwIFaQ&c=Nwf-pp4xtYRe0sCRVM8_LWH54joYF7EKmrYIdfxIq10&r=RaJkRMooYbg4vmML14E10F9hYEBLOeOHS3mAimFNgqQ&m=6Ls2mnPq0HhW0f8lsmU95UMRVT1UeJsFvGh44BzTizU&s=uCP4uOYT1SN2qzsadi3iftt9KgUrud2CS95njv44Y8Y&e= we migrated from OpenRDF Sesame 2.7.6 to RDF4J 2.3.1 but I don’t see a release for it.

Any tipps how should I do it ?

Regards

Jorge Machado
https://urldefense.proofpoint.com/v2/url?u=http-3A__www.jmachado.me&d=DwIFaQ&c=Nwf-pp4xtYRe0sCRVM8_LWH54joYF7EKmrYIdfxIq10&r=RaJkRMooYbg4vmML14E10F9hYEBLOeOHS3mAimFNgqQ&m=6Ls2mnPq0HhW0f8lsmU95UMRVT1UeJsFvGh44BzTizU&s=eAzZPx3uWTUGtQ8iVYjpSbwy6F1rvolhmgtn70npjkA&e=






NOTICE: This email message and all attachments transmitted with it may contain privileged and confidential information, and information that is protected by, and proprietary to, Parsons Corporation, and is intended solely for the use of the addressee for the specific purpose set forth in this communication. If the reader of this message is not the intended recipient, you are hereby notified that any reading, dissemination, distribution, copying, or other use of this message or its attachments is strictly prohibited, and you should delete this message and all copies and backups thereof. The recipient may not further distribute or use any of the information contained herein without the express written authorization of the sender. If you have received this message in error, or if you have any questions regarding the use of the proprietary information contained therein, please contact the sender of this message immediately, and the sender will provide you with further instructions.