Added Jenkins Build on Incoming Pull Requests

All, I added a Jenkins job to build PRs as they come in. The Jenkins job is here [1] and you can see an example of a failing PR build here [2]. I'll close the failing PR in the next couple of days. Right now, Jenkins builds the optional profile and runs the junit tests (but skips the

Re: findbugs-annotations?

I meant "fluo has a transitive dependency on findbugs:jsr305". I agree that findbugs-annotations is good and jsr305 is bad. On Mon, Oct 17, 2016 at 2:51 PM Puja Valiyil wrote: > Yea findbugs-annotations is not LGPL: > https://github.com/stephenc/findbugs-annotations > It

Re: findbugs-annotations?

Yea findbugs-annotations is not LGPL: https://github.com/stephenc/findbugs-annotations It appears to be apache 2, though aaron you should verify. On Mon, Oct 17, 2016 at 11:19 AM, Aaron D. Mihalik wrote: > fluo has a transitive dependency on findbugs-annotations, not

RE: [VOTE] Release Rya (Incubating) version 3.2.10 RC2

-1 because of the findbugs issue. Also, Rat failed on Mongo, animal sniffer failed on Tinkerpop.Rya, And there was a test failure (CopyToolTest.testImportDirectoryTool) for the merge tool. Stopped building when I encountered the test failure. -Original Message- From: Aaron D. Mihalik

Re: checklist for release

Some additional detail: Here's a checklist for things to consider when evaluating the release > candidate: > > 1. Download the sources and verify they compile cleanly. > > 2. Validate the hashes match. > > 3. Validate that the sources contain no unexpected binaries. > Run the find/grep command:

Re: [VOTE] Release Rya (Incubating) version 3.2.10 RC2

Sorry! I should have been more clear and used fewer emoticons. I'll try to take a look at rc2 today for some feedback before rc3. Aaron D. Mihalik wrote: -1 We're still including findbugs. I'm sorry everyone. I misread Josh's earlier email [1] and thought it was okay to continue to include

Re: SCM tagging conventions

Precisely. Some sort of v3.2.10-rcX during voting with the creation of rel/v3.2.10 after the ppmc and ipmc votes pass. Meier, Caleb wrote: Given that you cannot delete the tag "rel/", what are the tagging conventions that people use throughout the release process? Obviously you don't want the

checklist for release

Hello Everyone, Here's a checklist for things to consider when evaluating the release candidate: 1. Download the sources and verify they compile cleanly. 2. Validate the hashes match. 3. Validate that the sources contain no unexpected binaries. Run the find/grep command: find . -type f |

Re: findbugs-annotations?

fluo has a transitive dependency on findbugs-annotations, not direct. My issue is that com.github.stephenc.findbugs:findbugs-annotations:3.0.1-1 isn't in maven central. I think it would be straightforward for us to exclude and replace with c.g.s.f:findbugs-annotations:3.0.1-1, but it's going to

Re: [VOTE] Release Rya (Incubating) version 3.2.10 RC2

-1 We're still including findbugs. I'm sorry everyone. I misread Josh's earlier email [1] and thought it was okay to continue to include findbugs for our first release, I'll take a look at upgrading/changing findbugs and make an RC3 very soon. If anyone has feedback for RC2, I'd appreciate

RE: SCM tagging conventions

Given that you cannot delete the tag "rel/", what are the tagging conventions that people use throughout the release process? Obviously you don't want the tag for an RC to be rel in the event that you have to create a new RC and delete the old tag. Is the convention to just create an RC tag,

regarding the ingestion of ttl files

Hi everyone i am getting an exception while ingesting infobox properties turtle file from dbpedia dataset into rya . The file size is 9.8 gb. Here is the exception :- Caused by: org.openrdf.repository.RepositoryException: org.openrdf.sail.SailException: mvm.rya.api.persist.RyaDAOException: