Re: [VOTE] Release Rya (Incubating) version 4.0.0 RC1

[Jeff Dasch]

+1 (non-binding)
Verified checksums match for source release.  I found a couple issues with
flaky integration tests, but they can probably just be logged in JIRA.

I had no issues when I used docker to verify the build with this command:
docker run -it --rm
  -v /path/to/blank-m2-cache:/root/.m2 \
  -v "$(pwd)":/usr/src/rya \
  -w /usr/src/rya \
  maven:3.6.1-jdk-8 \
  mvn clean install -P geoindexing,benchmark,giraph

I did run into some issues when I tried running a complete build with all
profiles enabled:
mvn clean install -P geoindexing,benchmark,giraph,enable-it

I had to -rf from rya.pcj.fluo.integration, rya.streams.client, and
rya.streams.integration as there were some timeout issues that caused the
builds to fail.  I suppose it could be docker related, or some IT
dependencies aren't getting cleaned up properly during teardown.
Ultimately, I was not able to get rya.streams.client to build with all of
those profiles in docker.

I also ran it against an internal build server and it logged 3 IT failures:
org.apache.rya.streams.client.command.AddQueryCommandIT.longParams
org.apache.rya.streams.client.command.RunQueryCommandIT.runQueryFromFile
org.apache.rya.streams.client.command.RunQueryCommandIT.runQuery

I exercised those IT's individually and found that RunQueryCommandIT seemed
to hang forever, but AddQueryComandIT passed.  RunQueryCommandIT has some
threading and joins, so we might want to put an additional timeout in so it
fails faster instead of failing with the maven-failsafe-plugin's timeout.

Finally, the kafka and zookeeper loggers are configured to log at the debug
level during the build which dumps out a lot of unnecessary logging
statements.  We might want to turn that off or down as it will help
speed-up builds.



On Thu, Jul 18, 2019 at 11:04 AM Aaron D. Mihalik 
wrote:

> All,
>
> The vote will close in less than 24 hours at 11:00 AM Friday, July 19, 2019
> (EDT).
>
> Please download the release candidate and evaluate the necessary items
> including checking hashes, signatures, build from source, and test.  Then
> please vote:
>
> [ ] +1 Release this package as rya-project-4.0.0
> [ ] +0 no opinion
> [ ] -1 Do not release this package because because...
>
> On Wed, Jul 17, 2019 at 3:05 PM Aaron D. Mihalik 
> wrote:
>
> > Adina,
> >
> > Thanks for taking the time to build and verify the release.
> >
> > - Notice Issue:
> >
> > I'll commit a change to master, but I don't think this should hold up the
> > release.  If you (or others) think it's an issue, toss a '-1' vote on
> this
> > thread and that'll force em to fix it in the release :)
> >
> > - Release Notes:
> >
> > I'll double check all of the release notes and fix them.  I don't think
> > this an issue to hold up the release (the notes aren't actually part of
> the
> > release, and 'll probably have them fixed before the end of the vote).
> >
> > - Build issues:
> >
> > Try using the flag -DskipTests (I don't think -Dskip-tests is valid).
> >
> > The build issue is related to a test and it appears that the mongo client
> > (Rya) cannot connect to the temporary mongo server that the plug-in sets
> > up.  The server seems to start up and binds to localhost.  This could be
> a
> > firewall issue or an ip address issue (127.0.1.1 seems like a strange ip
> in
> > the connection string: WRK1065646GOVTu/127.0.1.1:27017).
> >
> > I built Rya and ran all of the tests on both my personal macOS machine
> (in
> > order to sign the code and artifacts) and on AWS Linux on EC2 (for
> > validation).  I've included my build notes below.
> >
> > --Aaron
> >
> > AMI: Amazon Linux AMI 2018.03.0 (HVM), SSD Volume Type
> > Instance Type: t3a.xlarge
> >
> > # configure repo to get maven
> > sudo wget
> >
> http://repos.fedorapeople.org/repos/dchen/apache-maven/epel-apache-maven.repo
> > -O /etc/yum.repos.d/epel-apache-maven.repo
> > sudo sed -i s/\$releasever/6/g /etc/yum.repos.d/epel-apache-maven.repo
> >
> > # install maven, java 8 and git
> > sudo yum install -y java-1.8.0-openjdk-devel git apache-maven
> >
> > # change to java 8
> > sudo update-alternatives --set java
> > /usr/lib/jvm/jre-1.8.0-openjdk.x86_64/bin/java
> > sudo update-alternatives --set javac
> > /usr/lib/jvm/java-1.8.0-openjdk.x86_64/bin/javac
> >
> > # This should fail
> > ping $(hostname)
> >
> > # add hostname in /etc/hosts
> > hostname
> > sudo vi /etc/hosts
> >
> > # now this should work
> > ping $(hostname)
> >
> > git clone https://github.com/apache/incubator-rya.git
> > cd incubator-rya
> > mvn clean install
> >
> >
> > On Wed, Jul 17, 2019 at 7:16 AM Adina Crainiceanu 
> wrote:
> >
> >> Hi,
> >>
> >> I'm leaving on vacation today with no computer access, so I will not be
> >> able to finish testing the release before Monday. This is what I have so
> >> far:
> >>
> >> -name includes incubating
> >> -checksums correct (md5,sha1, sha512) (I did sha1sum filename and md5sum
> >> filename)
> >> -DISCLAIMER exists and has the correct content
> >> -LICENSE exist and has the 

Re: 4.x branch for RDF4j updates.

[Jeff Dasch]

I just wanted to clarify what is meant by support.  I see a couple
different ways this could be done.  I'm pretty sure we're all talking about
Process 1 below, but wanted to get a discussion going on what we're
proposing.  If we're considering Process 2 or 3, I think we need to be more
explicit about the circumstances where pull requests will be backported.

So for the scenario of a PR of some feature/bugfix/improvement into master
(aka 4.x):

Process 1)
- It is only pulled into Master.  A separate PR can be made for the 3.x
branch if desired, but likely won't.

Process 2)
- It is pulled into Master and also backported into branch 3.x if trivial
(easy, no conflicts, or minimal re-write effort).

Process 3)
- It is pulled into Master and also backported into branch 3.x provided it
is applicable and below some maximum effort threshold.







On Tue, Apr 17, 2018 at 10:17 AM, Adina Crainiceanu  wrote:

> I agree with supporting two branches of development for now: 3.x and 4.x.
>
> In the 4.x branch we should update all dependencies, as Jurgen suggested. I
> think it is OK to update the master to be the 4.x development line.
>
> Thanks,
> Adina
>
> On Tue, Apr 17, 2018 at 10:04 AM, Brown, Jennifer <
> jennifer.br...@parsons.com> wrote:
>
> > I agree that it is time to upgrade to the latest version of RDF4J and
> that
> > this should involve a major version increment.
> >
> > To provide time for Rya users to upgrade, I think that we should support
> a
> > 3.x branch and a 4.x branch for the near future (minimally the end of the
> > calendar year) and then reevaluate continuing to maintain 3.x.
> >
> > Best Regards,
> >
> > Jen
> >
> > Jennifer Brown
> > Project Manager, Semantic Technologies
> > PARSONS
> > 1911 N. Fort Myer Dr. Ste 800
> > Arlington, VA 22209
> > Phone: (703) 797-3136
> > Fax: (703) 522-6310
> > jennifer.br...@parsons.com
> > www.parsons.com
> >
> > On Apr 9, 2018, at 12:30 PM, Chilton, Kevin  > mailto:kevin.chil...@parsons.com>> wrote:
> >
> > Hey Rya devs,
> >
> > I'd like to get PR #245 (RYA-405) pulled in.  This is a pretty big
> > dependency change, and should probably involve a major version increment
> to
> > 4.0.0.  Could we get a discussion going on the devlist about if we want
> to
> > support a 3.x branch and a 4.x branch going forward, or just update
> master
> > to 4.x.
> >
> > Thanks,
> > Kevin
> >
> > 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.
> >
> >
>
>
> --
> Dr. Adina Crainiceanu
> Associate Professor
> Computer Science Department
> United States Naval Academy
> 410-293-6822
> ad...@usna.edu
> http://www.usna.edu/Users/cs/adina/
>

Re: Failed build from master

[Jeff Dasch]

Jorge,

Master looks to be ok right now.  There are a number of reasons why RAT
might complain.  Files generated by your IDE might be the culprit, or
builds using different combinations of profiles might also be the culprit.
You'd have to send out the rat.txt file to know for sure.

For a fix, the command "git clean -fdx" will be more thorough than "mvn
clean", but it might clobber something your IDE depends on.  The command
"mvn clean install -Drat.skip" is the more lightweight workaround.

-Jeff

On Tue, Apr 10, 2018 at 10:05 AM, Jorge Machado  wrote:

> Hi Guys,
>
> I was trying to compile Rya from master and I always get :
>
> Failed to execute goal org.apache.rat:apache-rat-plugin:0.11:check
> (check-licenses) on project rya.extras: Too many files with unapproved
> license: 6 See RAT report in: /Users/jorge/Documents/
> BigData/experiments/incubator-rya/extras/target/rat.txt
>
> Is the repo broken on master ? I’m using the command: mvn clean install
>
> Thanks
>
>
> Jorge Machado
> www.jmachado.me
>
>
>
>
>
>

Re: 4.x branch for RDF4j updates.

[Jeff Dasch]

The simplest thing for the community is to have a single branch of
development that is being supported/maintained.  Otherwise we're always
forward/backporting new features that apply to both versions which is a
pain.  I do think we should push a 3.x branch so we can always do a future
3.2.13 release if requested by the community.  Then someone should bump
master to 4.0.0-SNAPSHOT, and then we should pull in PR 245.

There have been a couple commits on master since the 3.2.12 release.  Do we
want to cut a 3.2.13 release with just those remaining commits, or should
they all get rolled into the 4.0.0 release?



On Mon, Apr 9, 2018 at 12:30 PM, Chilton, Kevin 
wrote:

> Hey Rya devs,
>
> I'd like to get PR #245 (RYA-405) pulled in.  This is a pretty big
> dependency change, and should probably involve a major version increment to
> 4.0.0.  Could we get a discussion going on the devlist about if we want to
> support a 3.x branch and a 4.x branch going forward, or just update master
> to 4.x.
>
> Thanks,
> Kevin
>
> 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: Loading Rya via Map/Reduce is this the best I can do?

[Jeff Dasch]

Geoffry,

Take a look at the RdfFileInputTool [1] in the rya.mapreduce module.  It
doesn't look like the shaded jar was uploaded to maven, so you will likely
need to build that artifact yourself by including the "-P mr" profile when
building Rya.

There are instructions for loading data with the RdfFileInputTool here [2],
but they appear to be out of date.  I haven't tried it recently, but this
command, based on the unit test [3] should work:

hadoop jar target/rya.mapreduce-3.2.12-shaded.jar
org.apache.rya.accumulo.mr.tools.RdfFileInputTool
-Dac.zk=zoo1,zoo2,zoo3 -Dac.instance=accumulo -Dac.username=root
-Dac.pwd=password -Dac.auth=auths -Dac.cv=auths -Drdf.tablePrefix=rya_
-Drdf.format=N-Triples /hdfs/path/to/triplefiles


[1]
https://github.com/apache/incubator-rya/blob/master/mapreduce/src/main/java/org/apache/rya/accumulo/mr/tools/RdfFileInputTool.java
[2]
https://github.com/apache/incubator-rya/blob/master/extras/rya.manual/src/site/markdown/loaddata.md
[3]
https://github.com/apache/incubator-rya/blob/master/mapreduce/src/test/java/org/apache/rya/accumulo/mr/tools/RdfFileInputToolTest.java



On Wed, Mar 14, 2018 at 5:28 PM, Geoffry Roberts 
wrote:

> All,
>
> Am I doing things the best way?
>
> I have a pile of data that I need to load into Rya.  I must first convert
> it into RDF, then do the load.  I am using map/reduce because I have a lot
> of data.
>
> I have an hdfs directory full of RDF in NTRIPLE format.
>
> I have a mapper like this:
>
> protected void map(LongWritable key, RyaStatementWritable value, Context
> ctx)
> {
>
> // RyaStatementWritable gives me a RyaStatement like this:
>
>
> RyaStatement ryaStatement = value.getRyaStatement();
>
>
> // At this point I find myself having to convert the
>
> // RyaStatement into an OpenRDF Statement like this:
>
>
> Sail ryaSail = RyaSailFactory.getInstance(conf);
>
> ValueFactory vf = ryaSail.getValueFactory();
>
> Statement stmt = vf.createStatement(vf.createURI(sS), vf.createURI(sP), vf
> .createURI(sO));
>
> ctx.write(null, stmt);
>
> }
>
> In my reducer, I use AccumuloLoadStatements to lood Rya like this:
>
> protected void reduce(NullWritable key, Iterable stmts,
> Reducer.Context ctx)
> throws IOException, InterruptedException {
>
> super.reduce(key, stmts, ctx);
>
>
> AccumuloLoadStatements load = ...omitted for brevity...
>
>
> try {
>
> load.loadStatements(instance, stmts);
>
> } catch (RyaClientException e) {
>
> log.error("", e);
>
> }
>
> }
>
>
> Thanks
>
> --
> There are ways and there are ways,
>
> Geoffry Roberts
>

Re: [VOTE] Release Apache Rya (incubating) 3.2.12 RC2

[Jeff Dasch]

+1 (non-binding)

Verified sigs/checksums match for source release and maven artifacts.
Built on CentOS 7.3.1611 with Maven 3.3.9 and Oracle JDK 1.8.0_144 on a
fresh repo.  Also built with -P geoindexing,benchmark,giraph

The only potential blocker I see is the Windows issues, but I'm fine
marking that as a known issue in the release notes and fixing it for our
next release.  I created RYA-470 to track this issue -- it includes adding
a Windows CI build to help prevent regression.

I also added RYA-471 to track Dave's feedback on a JDK9 build.  I don't
think the lack of Java 9 build support is a blocker for this release but
should be documented in the release notes and fixed for the next release.


On Tue, Feb 20, 2018 at 11:26 AM, Adina Crainiceanu  wrote:

> Rya community,
>
> I am pleased to be calling this vote for the source release of Apache Rya
> (Incubating), version 3.2.12.
>
> The source zip, including signatures, digests, etc. can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/rya/rya-inc
> ubating-3.2.12-rc2/
>
> Ancillary artifacts such as poms, jars, wars, etc. can be found here:
> https://repository.apache.org/content/repositories/orgapache
> rya-1010/org/apache/rya/
>
> The Git tag is rya-incubating-3.2.12-rc2
> The Git commit ID is edb9aa6f9d3479f22a8d17dae928d2ca19e5de37
> https://git-wip-us.apache.org/repos/asf?p=incubator-rya.git;
> a=commit;h=edb9aa6f9d3479f22a8d17dae928d2ca19e5de37
>
>
> Checksums of rya-project-3.2.12-source-release.zip:
> SHA512:
> a0e87e1b3813e1425bf58e5e66e8cf8f948a1157f6905a55c913d4169dfb
> 8cfa05fa7c77514c2f75e414654198f9674533227a15ceee2fb6835e15777a0c48d8
> SHA1: 58128bf6cc5c8d92e429bd3a26aa1c104c757097
> MD5: 6e70b0d5aa54a4f018d5c12464e774e3
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/adina.asc
>
> KEYS file available here:
> https://dist.apache.org/repos/dist/release/incubator/rya/KEYS
>
> Issues that were closed/resolved for this release are here:
> *https://issues.apache.org/jira/secure/ReleaseNote.jspa?proj
> ectId=12319020=12341570
>  ectId=12319020=12341570>*
>
> Issues closed/resolved between RC1 and RC2
> https://issues.apache.org/jira/browse/RYA-468
>
>
> The vote will be open for at least 72 hours (until Friday, February 23,
> 2018 1200 ET).
> Please download the release candidate and evaluate the necessary items
> including checking hashes, signatures, build from source, and test.  Then
> please vote:
>
> [ ] +1 Release this package as rya-project-3.2.12
> [ ] +0 no opinion
> [ ] -1 Do not release this package because because...
>
>
> Thank you,
> Adina
>
> --
> Dr. Adina Crainiceanu
> Associate Professor
> Computer Science Department
> United States Naval Academy
> 410-293-6822
> ad...@usna.edu
> http://www.usna.edu/Users/cs/adina/
>

Re: [VOTE] Release Apache Rya (incubating) 3.2.12 RC1

[Jeff Dasch]

+1 (non-binding)

Verified sigs/checksums match for source release and maven artifacts.
Built with maven clean install on MacOS X 10.11.6 with Maven 3.2.5 and
Oracle JDK 1.8.0_72 against a blank repo.  Also built with -P
geoindexing,benchmark.

I have concerns about the Apache Giraph license issue(?), but I see no
reason to hold up this release since we are still incubating and can fix it
for our next release.

The shell test failing on a Windows build is concerning, however since
there isn't even a rya.shell-${version}/bin/rya.bat batch file in that
assembly, we can just say we don't support Windows on the rya shell for
this release.  It looks like apache does have four idle windows build
slaves (https://builds.apache.org/computer).  Might be worth tying a build
to one of them.


On Mon, Feb 12, 2018 at 8:51 PM, Adina Crainiceanu  wrote:

> Rya community,
>
> I am pleased to be calling this vote for the source release of Apache Rya
> (Incubating), version 3.2.12.
>
> The source zip, including signatures, digests, etc. can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/rya/rya-
> incubating-3.2.12-rc1/
>
> Ancillary artifacts such as poms, jars, wars, etc. can be found here:
> https://repository.apache.org/content/repositories/
> orgapacherya-1009/org/apache/rya/
>
> The Git tag is rya-incubating-3.2.12-rc1
> The Git commit ID is e9ecf7fae76e308cfc0d90684ce684493482266c
> https://git-wip-us.apache.org/repos/asf?p=incubator-rya.git;a=commit;h=
> e9ecf7fae76e308cfc0d90684ce684493482266c
>
>
> Checksums of rya-project-3.2.12-source-release.zip:
> SHA512:8059adff3a264cdcc85edb8ab1c820d87d4e2adbdfd4eebfcd7d2
> 7b9a3c8c2af8cd09cb39b91ccb5170fe37159b1360078ef8e61321e7f6ca
> e6141442bbf8dda
> SHA1: 64296d86923dae11294dcff0719cfcb9522a744d
> MD5: 9c55ae7f811afaa147ebb7f652543620
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/adina.asc
>
> KEYS file available here:
> https://dist.apache.org/repos/dist/release/incubator/rya/KEYS
>
> Issues that were closed/resolved for this release are here:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12319020=12341570
>
>
> The vote will be open for at least 72 hours until end of Thursday, February
> 15, 2018 ET.
> Please download the release candidate and evaluate the necessary items
> including checking hashes, signatures, build from source, and test.  Then
> please vote:
>
> [ ] +1 Release this package as rya-project-3.2.12
> [ ] +0 no opinion
> [ ] -1 Do not release this package because because...
>
>
> Thank you,
> Adina
>
> --
> Dr. Adina Crainiceanu
> Associate Professor
> Computer Science Department
> United States Naval Academy
> 410-293-6822 <(410)%20293-6822>
> ad...@usna.edu
> http://www.usna.edu/Users/cs/adina/
>

Re: [VOTE] Release Apache Rya (incubating) 3.2.12 RC1

[Jeff Dasch]

I'm not voting yet, but I did run a license check and got a hit on this:
(GNU Lesser Public License) FindBugs-Annotations
(com.google.code.findbugs:annotations:2.0.2
- http://findbugs.sourceforge.net/)

which comes from Apache Giraph
[INFO] org.apache.rya:rya.giraph:jar:3.2.12-incubating
[INFO] +- org.apache.giraph:giraph-core:jar:1.2.0:compile
[INFO] |  +- com.google.code.findbugs:annotations:jar:2.0.2:compile

I'm pretty sure we ran into this during the last release.  Are we still
good to go on this RC, or do we need to cut a new one that has a giraph
profile?



On Mon, Feb 12, 2018 at 8:51 PM, Adina Crainiceanu  wrote:

> Rya community,
>
> I am pleased to be calling this vote for the source release of Apache Rya
> (Incubating), version 3.2.12.
>
> The source zip, including signatures, digests, etc. can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/rya/rya-
> incubating-3.2.12-rc1/
>
> Ancillary artifacts such as poms, jars, wars, etc. can be found here:
> https://repository.apache.org/content/repositories/
> orgapacherya-1009/org/apache/rya/
>
> The Git tag is rya-incubating-3.2.12-rc1
> The Git commit ID is e9ecf7fae76e308cfc0d90684ce684493482266c
> https://git-wip-us.apache.org/repos/asf?p=incubator-rya.git;a=commit;h=
> e9ecf7fae76e308cfc0d90684ce684493482266c
>
>
> Checksums of rya-project-3.2.12-source-release.zip:
> SHA512:8059adff3a264cdcc85edb8ab1c820d87d4e2adbdfd4eebfcd7d2
> 7b9a3c8c2af8cd09cb39b91ccb5170fe37159b1360078ef8e61321e7f6ca
> e6141442bbf8dda
> SHA1: 64296d86923dae11294dcff0719cfcb9522a744d
> MD5: 9c55ae7f811afaa147ebb7f652543620
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/adina.asc
>
> KEYS file available here:
> https://dist.apache.org/repos/dist/release/incubator/rya/KEYS
>
> Issues that were closed/resolved for this release are here:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12319020=12341570
>
>
> The vote will be open for at least 72 hours until end of Thursday, February
> 15, 2018 ET.
> Please download the release candidate and evaluate the necessary items
> including checking hashes, signatures, build from source, and test.  Then
> please vote:
>
> [ ] +1 Release this package as rya-project-3.2.12
> [ ] +0 no opinion
> [ ] -1 Do not release this package because because...
>
>
> Thank you,
> Adina
>
> --
> Dr. Adina Crainiceanu
> Associate Professor
> Computer Science Department
> United States Naval Academy
> 410-293-6822 <(410)%20293-6822>
> ad...@usna.edu
> http://www.usna.edu/Users/cs/adina/
>

Re: [VOTE] Release Rya (Incubating) version 3.2.11 RC3

[Jeff Dasch]

+1 (non-binding)

Verified sigs/checksums match for source release and maven artifacts.
Built with all tests on CentOS 7.3.1611 with Maven 3.3.9 and Oracle JDK
1.8.0_144 on a fresh repo.  Also built with -P geoindexing,benchmark.

On Tue, Sep 26, 2017 at 1:27 PM, David Lotts  wrote:

> I am pleased to be calling this vote for the source release of Apache Rya
> (Incubating), version 3.2.11.
>
> The source zip, including signatures, digests, etc. can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/rya/rya-
> incubating-3.2.11-rc3/
>
>
> Ancillary artifacts such as poms, jars, wars. can be found here:
> https://repository.apache.org/content/repositories/
> orgapacherya-1008/org/apache/rya/rya-project/3.2.11-incubating/
>
> The Git tag is rya-incubating-3.2.11-rc3
> The Git commit ID is afe522412fb74cbb4ab97e1b7a8d1c112be33773
> https://git-wip-us.apache.org/repos/asf?p=incubator-rya.git;a=commit;h=
> afe522412fb74cbb4ab97e1b7a8d1c112be33773
>
>
> Checksums of rya-project-3.2.11-source-release.zip:
> MD5: 3968cfb695a5740cac6acb3c33b702ca
> SHA1: d601431c06d9adb3336c2913cc544bd9b43c0d7a
> SHA512: b6ae761aa42f80e1cb84bb645184e29e4436eaaaf66aa7249aa65b6adb38
> f3dfdd9a6f8b536eb0e2de88ac75cc2a0c8d97d85b4dd0ffef7f9407e05642110b3f
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/dlotts.asc
>
> KEYS file available here:
> https://dist.apache.org/repos/dist/release/incubator/rya/KEYS
>
> Issues that were closed/resolved for this release are here:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?proje
> ctId=12319020=12341279
>
>
> The vote will be open for at least 72 hours starting Tuesday 2pm 9/26/2017
> and close at Friday 9/29/2017 2pm Eastern Time USA.
> Please download the release candidate and evaluate the necessary items
> including checking hashes, signatures, build from source, and test.  Then
> please vote:
>
> [ ] +1 Release this package as rya-project-3.2.11
> [ ] +0 no opinion
> [ ] -1 Do not release this package because because...
>

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

[Jeff Dasch]

Created RYA-370 to track the geoindexing profile bug and the renaming
recommendation.

My finding wrt the sesame-runtime-osgi pom is covered by RYA-8.  Ignoring
that for now.

Here's the current license check.  Are there any issues with the GNU
licenses here?
Apache Giraph seems to be providing the
com.google.code.findbugs:annotations:2.0.2
dependency.
Do we need to profile away the rya.benchmark project which provides the JMH
dependency?

$ mvn license:aggregate-add-third-party
$ egrep -iv "BSD|ASF|MIT|CDDL|EPL|Apache|ASL|Eclipse|Public Domain"
target/generated-sources/license/THIRD-PARTY.txt

Lists of 538 third-party dependencies.
 (Unknown license) ASM Core (asm:asm:3.1 - http://asm.objectweb.org/asm/
)
 (GNU Lesser Public License) FindBugs-Annotations
(com.google.code.findbugs:annotations:2.0.2 - http://findbugs.sourceforge.
net/)
 (Unknown license) commons-beanutils
(commons-beanutils:commons-beanutils:1.7.0
- no url defined)
 (HSQLDB License) HSQLDB (hsqldb:hsqldb:1.8.0.10 - http://hsqldb.org/)
 (Unknown license) servlet-api (javax.servlet:servlet-api:2.5 - no url
defined)
 (Unknown license) jsp-api (javax.servlet.jsp:jsp-api:2.1 - no url
defined)
 (Common Public License Version 1.0) JUnit (junit:junit:4.8.2 -
http://junit.org)
 (Unknown license) Antlr 3.4 Runtime (org.antlr:antlr-runtime:3.4 -
http://www.antlr.org)
 (Unknown license) Jettison (org.codehaus.jettison:jettison:1.1 - no
url defined)
 (provided without support or warranty) JSON (JavaScript Object
Notation) (org.json:json:20090211 - http://www.json.org/java/index.html)
 (GNU General Public License (GPL), version 2, with the Classpath
exception) JMH Core (org.openjdk.jmh:jmh-core:1.13 -
http://openjdk.java.net/projects/code-tools/jmh/jmh-core/)
 (GNU General Public License (GPL), version 2, with the Classpath
exception) JMH Generators: Annotation Processors
(org.openjdk.jmh:jmh-generator-annprocess:1.13
- http://openjdk.java.net/projects/code-tools/jmh/jmh-generator-annprocess/)
 (Unknown license) org.osgi.compendium (org.osgi:org.osgi.compendium:4.2.0
- no url defined)
 (Unknown license) org.osgi.core (org.osgi:org.osgi.core:4.2.0 - no url
defined)
 (Jython Software License) Jython (org.python:jython:2.5.3 -
http://www.jython.org/)
 (Unknown license) spring-aop (org.springframework:spring-aop:3.0.5.RELEASE
- no url defined)
 (Unknown license) spring-asm (org.springframework:spring-asm:3.0.5.RELEASE
- no url defined)
 (Unknown license) spring-beans
(org.springframework:spring-beans:3.0.5.RELEASE
- no url defined)
 (Unknown license) spring-context
(org.springframework:spring-context:3.0.5.RELEASE
- no url defined)
 (Unknown license) spring-context-support
(org.springframework:spring-context-support:3.0.7.RELEASE
- no url defined)
 (Unknown license) spring-core
(org.springframework:spring-core:3.0.5.RELEASE
- no url defined)
 (Unknown license) spring-expression
(org.springframework:spring-expression:3.0.5.RELEASE
- no url defined)
 (Unknown license) spring-tx (org.springframework:spring-tx:3.0.5.RELEASE
- no url defined)
 (Unknown license) oro (oro:oro:2.0.8 - no url defined)
 (Unknown license) regexp (regexp:regexp:1.3 - no url defined)

On Wed, Sep 13, 2017 at 10:45 AM, David Lotts <dlo...@gmail.com> wrote:

> > , nexus seems to have a lot of geoindexing
> > artifacts in it.  Probably need to revist the extras/pom.xml as it
> > looks like there's a regression in there.
>
> The last release 3.2.10 has no geoindexing jars in Nexus.  I see what you
> are saying.  This release candidate has folders for each.
> https://repository.apache.org/content/repositories/releases/
> org/apache/rya/
>
>  I unfortunately missed your renaming recommendation from your review.
>
>  david.
>
> On Wed, Sep 13, 2017 at 9:25 AM, Jeff Dasch <hcs...@gmail.com> wrote:
>
> > Also, it appears that there is an issue with this project as well:
> >
> > grep -r 3.2.10-incubating-SNAPSHOT rya-project-3.2.11-incubating
> > rya-project-3.2.11-incubating/osgi/sesame-runtime-osgi/pom.xml:
> > *3.2.10-incubating-SNAPSHOT*
> >
> > On Wed, Sep 13, 2017 at 12:05 AM, Jeff Dasch <hcs...@gmail.com> wrote:
> >
> > > It is fine to not to release the geoindexing artifacts, but we need all
> > of
> > > the pom version strings to be consistent (and correct) so that if one
> did
> > > want to build them with the geoindexing profile, they can.
> > >
> > > Speaking of artifacts, nexus seems to have a lot of geoindexing
> artifacts
> > > in it.  Probably need to revist the extras/pom.xml as it looks like
> > there's
> > > a regression in there.
> > >
> > >
> > >
> > > On Tue, Sep 12, 2017 at 10:22 PM, Puja Valiyil <puja...@gmail.com>
> &

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

[Jeff Dasch]

Also, it appears that there is an issue with this project as well:

grep -r 3.2.10-incubating-SNAPSHOT rya-project-3.2.11-incubating
rya-project-3.2.11-incubating/osgi/sesame-runtime-osgi/pom.xml:
*3.2.10-incubating-SNAPSHOT*

On Wed, Sep 13, 2017 at 12:05 AM, Jeff Dasch <hcs...@gmail.com> wrote:

> It is fine to not to release the geoindexing artifacts, but we need all of
> the pom version strings to be consistent (and correct) so that if one did
> want to build them with the geoindexing profile, they can.
>
> Speaking of artifacts, nexus seems to have a lot of geoindexing artifacts
> in it.  Probably need to revist the extras/pom.xml as it looks like there's
> a regression in there.
>
>
>
> On Tue, Sep 12, 2017 at 10:22 PM, Puja Valiyil <puja...@gmail.com> wrote:
>
>> Don't we not release the geoindexing artifacts? Sorry if I'm being slow
>> here
>>
>> Sent from my iPhone
>>
>> > On Sep 12, 2017, at 5:23 PM, Jeff Dasch <hcs...@gmail.com> wrote:
>> >
>> > -1 (non-binding)
>> >
>> > The pom for rya.pcj.functions.geo references a parent artifact with a
>> > 3.2.11-incubating-SNAPSHOT version:
>> > grep -r 3.2.11-incubating-SNAPSHOT rya-project-3.2.11-incubating
>> > rya-project-3.2.11-incubating/extras/rya.pcj.fluo/rya.pcj.fu
>> nctions.geo/pom.xml:
>> > 3.2.11-incubating-SNAPSHOT
>> >
>> > Need to clean your maven repo and build with the geoindexing profile to
>> see
>> > this issue.  RC1 was also affected.
>> >
>> >
>> >> On Mon, Sep 11, 2017 at 5:44 PM, David Lotts <dlo...@gmail.com> wrote:
>> >>
>> >> I am pleased to be calling this vote for the source release of Apache
>> Rya
>> >> (Incubating), version 3.2.11.
>> >>
>> >> The source zip, including signatures, digests, etc. can be found at:
>> >> https://dist.apache.org/repos/dist/dev/incubator/rya/rya-
>> >> incubating-3.2.11-rc2/
>> >>
>> >>
>> >> Ancillary artifacts such as poms, jars, wars. can be found here:
>> >> https://repository.apache.org/content/repositories/
>> >> orgapacherya-1006/org/apache/rya/rya-project/3.2.11-incubating/
>> >>
>> >> The Git tag is rya-incubating-3.2.11-rc2
>> >> The Git commit ID is f9e5787a4057d8fbaacc8d22e4de5d86fcb45ba8
>> >> https://git-wip-us.apache.org/repos/asf?p=incubator-rya.git;
>> a=commit;h=
>> >> f9e5787a4057d8fbaacc8d22e4de5d86fcb45ba8
>> >>
>> >> Checksums of rya-project-3.2.11-source-release.zip:
>> >> MD5: aa4dff6ed9664fb1e06752389bebcea9
>> >> SHA1: a801e7814bdd09f603256858e4511db4b59605b2
>> >> SHA512:
>> >> 66ad82cf9f6c04e5ab230b609fb902f071fd77ff63989f3fa2e331ddcc34
>> >> 3b1ad7ee7d3ae3bbd138b399e59c565a57457060c357c01a805c0b4bbe2cd0c34dd9
>> >>
>> >> Release artifacts are signed with the following key:
>> >> https://people.apache.org/keys/committer/dlotts.asc
>> >>
>> >> KEYS file available here:
>> >> https://dist.apache.org/repos/dist/release/incubator/rya/KEYS
>> >>
>> >> Issues that were closed/resolved for this release are here:
>> >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
>> >> projectId=12319020=12341279
>> >> (Should be complete now.)
>> >>
>> >> The vote will be open for at least 72 hours starting Monday 9/11/2017
>> and
>> >> close at Friday 9/15/2017 10am Eastern Time USA.
>> >> Please download the release candidate and evaluate the necessary items
>> >> including checking hashes, signatures, build from source, and test.
>> Then
>> >> please vote:
>> >>
>> >> [ ] +1 Release this package as rya-project-3.2.11
>> >> [ ] +0 no opinion
>> >> [ ] -1 Do not release this package because because...
>> >>
>>
>
>

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

[Jeff Dasch]

It is fine to not to release the geoindexing artifacts, but we need all of
the pom version strings to be consistent (and correct) so that if one did
want to build them with the geoindexing profile, they can.

Speaking of artifacts, nexus seems to have a lot of geoindexing artifacts
in it.  Probably need to revist the extras/pom.xml as it looks like there's
a regression in there.



On Tue, Sep 12, 2017 at 10:22 PM, Puja Valiyil <puja...@gmail.com> wrote:

> Don't we not release the geoindexing artifacts? Sorry if I'm being slow
> here
>
> Sent from my iPhone
>
> > On Sep 12, 2017, at 5:23 PM, Jeff Dasch <hcs...@gmail.com> wrote:
> >
> > -1 (non-binding)
> >
> > The pom for rya.pcj.functions.geo references a parent artifact with a
> > 3.2.11-incubating-SNAPSHOT version:
> > grep -r 3.2.11-incubating-SNAPSHOT rya-project-3.2.11-incubating
> > rya-project-3.2.11-incubating/extras/rya.pcj.fluo/rya.pcj.
> functions.geo/pom.xml:
> > 3.2.11-incubating-SNAPSHOT
> >
> > Need to clean your maven repo and build with the geoindexing profile to
> see
> > this issue.  RC1 was also affected.
> >
> >
> >> On Mon, Sep 11, 2017 at 5:44 PM, David Lotts <dlo...@gmail.com> wrote:
> >>
> >> I am pleased to be calling this vote for the source release of Apache
> Rya
> >> (Incubating), version 3.2.11.
> >>
> >> The source zip, including signatures, digests, etc. can be found at:
> >> https://dist.apache.org/repos/dist/dev/incubator/rya/rya-
> >> incubating-3.2.11-rc2/
> >>
> >>
> >> Ancillary artifacts such as poms, jars, wars. can be found here:
> >> https://repository.apache.org/content/repositories/
> >> orgapacherya-1006/org/apache/rya/rya-project/3.2.11-incubating/
> >>
> >> The Git tag is rya-incubating-3.2.11-rc2
> >> The Git commit ID is f9e5787a4057d8fbaacc8d22e4de5d86fcb45ba8
> >> https://git-wip-us.apache.org/repos/asf?p=incubator-rya.git;a=commit;h=
> >> f9e5787a4057d8fbaacc8d22e4de5d86fcb45ba8
> >>
> >> Checksums of rya-project-3.2.11-source-release.zip:
> >> MD5: aa4dff6ed9664fb1e06752389bebcea9
> >> SHA1: a801e7814bdd09f603256858e4511db4b59605b2
> >> SHA512:
> >> 66ad82cf9f6c04e5ab230b609fb902f071fd77ff63989f3fa2e331ddcc34
> >> 3b1ad7ee7d3ae3bbd138b399e59c565a57457060c357c01a805c0b4bbe2cd0c34dd9
> >>
> >> Release artifacts are signed with the following key:
> >> https://people.apache.org/keys/committer/dlotts.asc
> >>
> >> KEYS file available here:
> >> https://dist.apache.org/repos/dist/release/incubator/rya/KEYS
> >>
> >> Issues that were closed/resolved for this release are here:
> >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> >> projectId=12319020=12341279
> >> (Should be complete now.)
> >>
> >> The vote will be open for at least 72 hours starting Monday 9/11/2017
> and
> >> close at Friday 9/15/2017 10am Eastern Time USA.
> >> Please download the release candidate and evaluate the necessary items
> >> including checking hashes, signatures, build from source, and test.
> Then
> >> please vote:
> >>
> >> [ ] +1 Release this package as rya-project-3.2.11
> >> [ ] +0 no opinion
> >> [ ] -1 Do not release this package because because...
> >>
>

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

[Jeff Dasch]

-1 (non-binding)

The pom for rya.pcj.functions.geo references a parent artifact with a
3.2.11-incubating-SNAPSHOT version:
grep -r 3.2.11-incubating-SNAPSHOT rya-project-3.2.11-incubating
rya-project-3.2.11-incubating/extras/rya.pcj.fluo/rya.pcj.functions.geo/pom.xml:
3.2.11-incubating-SNAPSHOT

Need to clean your maven repo and build with the geoindexing profile to see
this issue.  RC1 was also affected.


On Mon, Sep 11, 2017 at 5:44 PM, David Lotts  wrote:

> I am pleased to be calling this vote for the source release of Apache Rya
> (Incubating), version 3.2.11.
>
> The source zip, including signatures, digests, etc. can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/rya/rya-
> incubating-3.2.11-rc2/
>
>
> Ancillary artifacts such as poms, jars, wars. can be found here:
> https://repository.apache.org/content/repositories/
> orgapacherya-1006/org/apache/rya/rya-project/3.2.11-incubating/
>
> The Git tag is rya-incubating-3.2.11-rc2
> The Git commit ID is f9e5787a4057d8fbaacc8d22e4de5d86fcb45ba8
> https://git-wip-us.apache.org/repos/asf?p=incubator-rya.git;a=commit;h=
> f9e5787a4057d8fbaacc8d22e4de5d86fcb45ba8
>
> Checksums of rya-project-3.2.11-source-release.zip:
> MD5: aa4dff6ed9664fb1e06752389bebcea9
> SHA1: a801e7814bdd09f603256858e4511db4b59605b2
> SHA512:
> 66ad82cf9f6c04e5ab230b609fb902f071fd77ff63989f3fa2e331ddcc34
> 3b1ad7ee7d3ae3bbd138b399e59c565a57457060c357c01a805c0b4bbe2cd0c34dd9
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/dlotts.asc
>
> KEYS file available here:
> https://dist.apache.org/repos/dist/release/incubator/rya/KEYS
>
> Issues that were closed/resolved for this release are here:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12319020=12341279
> (Should be complete now.)
>
> The vote will be open for at least 72 hours starting Monday 9/11/2017 and
> close at Friday 9/15/2017 10am Eastern Time USA.
> Please download the release candidate and evaluate the necessary items
> including checking hashes, signatures, build from source, and test.  Then
> please vote:
>
> [ ] +1 Release this package as rya-project-3.2.11
> [ ] +0 no opinion
> [ ] -1 Do not release this package because because...
>

Re: [VOTE] Release Rya (Incubating) version 3.2.11 RC1

[Jeff Dasch]

+0 (non binding)

Sorry for the tardy vote.
Found a UX nit on the rya.shell during verification testing.  Filed and
fixed under RYA-362.



> On 9/2/17 1:08 AM, David Lotts wrote:
>
>> I am pleased to be calling this vote for the source release of Apache Rya
>> (Incubating), version 3.2.11.
>> Since I am sending this on the eve of a holiday weekend in the USA, we'll
>> start the vote on Tuesday, although voting early is fine.
>>
>> The source zip, including signatures, digests, etc. can be found at:
>> https://dist.apache.org/repos/dist/dev/incubator/rya/rya-incubating-3
>> .2.11-rc1/
>>
>> Ancillary artifacts such as poms, jars, wars, ect. can be found here:
>> https://repository.apache.org
>> /content/repositories/orgapacherya-1005/org/apache/rya/rya-project/3
>> .2.11-incubating/
>>
>> The Git tag is rya-incubating-3.2.11-rc1
>> The Git commit ID is 2588d189d483698c0d2cd30e1e7c28f18c3d6871
>> https://git-wip-us.apache.org/repos/asf
>> ?p=incubator-rya.git;a=commit;h=2588d189d483698c0d2cd30e1e7c28f18c3d6871
>>
>> Checksums of rya-project-3.2.10-source-release.zip:
>> SHA1: f40fe200b6768076d28ccd7b3d613ff6
>> MD5: f40fe200b6768076d28ccd7b3d613ff6
>>
>> Release artifacts are signed with the following key:
>> https://people.apache.org/keys/committer/dlotts.asc
>>
>> KEYS file available here:
>> https://dist.apache.org/repos/dist/release/incubator/rya/KEYS
>>
>> Issues that were closed/resolved for this release are here:
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?proje
>> ctId=12319020=12341279
>> (This is very incomplete as many items are yet to be tagged for the
>> release.  I'll take care of that after the Labor day Monday along with
>> release notes for the website.)
>>
>> The vote will be open for at least 72 hours starting Tuesday 9/12/2017 and
>> close at 9/15/2017 Noon Eastern Time USA.
>> Please download the release candidate and evaluate the necessary items
>> including checking hashes, signatures, build from source, and test.  Then
>> please vote:
>>
>> [ ] +1 Release this package as rya-project-3.2.11
>> [ ] +0 no opinion
>> [ ] -1 Do not release this package because because...
>>
>>

Re: [VOTE] Release Rya (Incubating) version 3.2.11 RC1

[Jeff Dasch]

One example is in rya.export.accumulo, but there are couple other source
jars affected.  These files are generated from an XML Schema file which has
the correct header.

https://repository.apache.org/content/groups/staging/org/apache/rya/rya.export.accumulo/3.2.11-incubating/rya.export.accumulo-3.2.11-incubating-sources.jar
rya.export.accumulo-3.2.11-incubating-sources.jar:/org/apache/rya/export/ObjectFactory.java
rya.export.accumulo-3.2.11-incubating-sources.jar:/org/apache/rya/export/MergeToolConfiguration.java
rya.export.accumulo-3.2.11-incubating-sources.jar:/org/apache/rya/export/MergePolicy.java
rya.export.accumulo-3.2.11-incubating-sources.jar:/org/apache/rya/export/InstanceType.java
rya.export.accumulo-3.2.11-incubating-sources.jar:/org/apache/rya/export/DBType.java
rya.export.accumulo-3.2.11-incubating-sources.jar:/org/apache/rya/export/AccumuloMergeToolConfiguration.java

The header currently looks like this:

/*-
 * LICENSE_START=
 * Apache Rya Export Accumulo
 * %%
 * Copyright (C) 2015 - 2017 The Apache Software Foundation
 * %%
 * Licensed under the Apache License, Version 2.0 (the "License");
 * you may not use this file except in compliance with the License.
 * You may obtain a copy of the License at
 *
 *  http://www.apache.org/licenses/LICENSE-2.0
 *
 * Unless required by applicable law or agreed to in writing, software
 * distributed under the License is distributed on an "AS IS" BASIS,
 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 * See the License for the specific language governing permissions and
 * limitations under the License.
 * =LICENSE_END==
 */
//
// This file was generated by the JavaTM Architecture for XML Binding(JAXB)
Reference Implementation, v2.2.11
// See http://java.sun.com/xml/jaxb;>http://java.sun.com/xml/jaxb

// Any modifications to this file will be lost upon recompilation of the
source schema.
// Generated on: 2017.09.01 at 09:18:38 PM EDT
//

On Wed, Sep 6, 2017 at 1:16 PM, Billie Rinaldi <bil...@apache.org> wrote:

> On Wed, Sep 6, 2017 at 10:12 AM, Jeff Dasch <hcs...@gmail.com> wrote:
>
> > Billie,
> >
> > We also have some generated source (jaxb related) that is getting an
> Apache
> > License header with a copyright line to The Apache Software Foundation
> from
> > the org.codehaus.mojo:license-maven-plugin.
>
>
> Which files are you referring to?
>
>
> > Does generated source fall
> > under the category of "A file without any degree of creativity" [1] that
> > does not require a license header?
> >
> > [1] https://www.apache.org/legal/src-headers.html
> >
> >
> >
> >
> >
> > On Wed, Sep 6, 2017 at 11:44 AM, Billie Rinaldi <
> billie.rina...@gmail.com>
> > wrote:
> >
> > > On Tue, Sep 5, 2017 at 6:29 PM, Puja Valiyil <puja...@gmail.com>
> wrote:
> > >
> > > > Hey Billie,
> > > > Are we using the rat plugin properly?  I would have thought that
> would
> > > have
> > > > caught the bad header.
> > > >
> > >
> > > The file has an Apache license header, but it's not the ASF license
> > header,
> > > which is why it wouldn't be flagged. Also, rat does not check for
> > copyright
> > > lines.
> > >
> > >
> > > >
> > > > On Tue, Sep 5, 2017 at 7:40 PM, Billie Rinaldi <bil...@apache.org>
> > > wrote:
> > > >
> > > > > This file has the wrong license header (including a copyright line
> > > which
> > > > > should not be present):
> > > > > extras/rya.export/export.client/src/main/java/org/apache/rya
> > > > > /export/client/conf/TimeUtils.java
> > > > >
> > > > > Signature, checksums, disclaimer look good, and the source zip
> > matches
> > > > the
> > > > > tag. I was able to build from source and the unit tests passed. I
> > > haven't
> > > > > done a full dependency analysis yet.
> > > > >
> > > > > On Fri, Sep 1, 2017 at 10:08 PM, David Lotts <dlo...@gmail.com>
> > wrote:
> > > > >
> > > > > > I am pleased to be calling this vote for the source release of
> > Apache
> > > > Rya
> > > > > > (Incubating), version 3.2.11.
> > > > > > Since I am sending this on the eve of a holiday weekend in the
> USA,
> > > > we'll
> > > > > > start the vote on Tuesday, although voting early is fine.
> > > > > >
> >

Re: [VOTE] Release Rya (Incubating) version 3.2.11 RC1

[Jeff Dasch]

Billie,

We also have some generated source (jaxb related) that is getting an Apache
License header with a copyright line to The Apache Software Foundation from
the org.codehaus.mojo:license-maven-plugin.  Does generated source fall
under the category of "A file without any degree of creativity" [1] that
does not require a license header?

[1] https://www.apache.org/legal/src-headers.html





On Wed, Sep 6, 2017 at 11:44 AM, Billie Rinaldi 
wrote:

> On Tue, Sep 5, 2017 at 6:29 PM, Puja Valiyil  wrote:
>
> > Hey Billie,
> > Are we using the rat plugin properly?  I would have thought that would
> have
> > caught the bad header.
> >
>
> The file has an Apache license header, but it's not the ASF license header,
> which is why it wouldn't be flagged. Also, rat does not check for copyright
> lines.
>
>
> >
> > On Tue, Sep 5, 2017 at 7:40 PM, Billie Rinaldi 
> wrote:
> >
> > > This file has the wrong license header (including a copyright line
> which
> > > should not be present):
> > > extras/rya.export/export.client/src/main/java/org/apache/rya
> > > /export/client/conf/TimeUtils.java
> > >
> > > Signature, checksums, disclaimer look good, and the source zip matches
> > the
> > > tag. I was able to build from source and the unit tests passed. I
> haven't
> > > done a full dependency analysis yet.
> > >
> > > On Fri, Sep 1, 2017 at 10:08 PM, David Lotts  wrote:
> > >
> > > > I am pleased to be calling this vote for the source release of Apache
> > Rya
> > > > (Incubating), version 3.2.11.
> > > > Since I am sending this on the eve of a holiday weekend in the USA,
> > we'll
> > > > start the vote on Tuesday, although voting early is fine.
> > > >
> > > > The source zip, including signatures, digests, etc. can be found at:
> > > > https://dist.apache.org/repos/dist/dev/incubator/rya/rya-
> incubating-3
> > > > .2.11-rc1/
> > > >
> > > > Ancillary artifacts such as poms, jars, wars, ect. can be found here:
> > > > https://repository.apache.org
> > > > /content/repositories/orgapacherya-1005/org/apache/rya/rya-project/3
> > > > .2.11-incubating/
> > > >
> > > > The Git tag is rya-incubating-3.2.11-rc1
> > > > The Git commit ID is 2588d189d483698c0d2cd30e1e7c28f18c3d6871
> > > > https://git-wip-us.apache.org/repos/asf
> > > > ?p=incubator-rya.git;a=commit;h=2588d189d483698c0d2cd30e1e7c28
> > f18c3d6871
> > > >
> > > > Checksums of rya-project-3.2.10-source-release.zip:
> > > > SHA1: f40fe200b6768076d28ccd7b3d613ff6
> > > > MD5: f40fe200b6768076d28ccd7b3d613ff6
> > > >
> > > > Release artifacts are signed with the following key:
> > > > https://people.apache.org/keys/committer/dlotts.asc
> > > >
> > > > KEYS file available here:
> > > > https://dist.apache.org/repos/dist/release/incubator/rya/KEYS
> > > >
> > > > Issues that were closed/resolved for this release are here:
> > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > > > projectId=12319020=12341279
> > > > (This is very incomplete as many items are yet to be tagged for the
> > > > release.  I'll take care of that after the Labor day Monday along
> with
> > > > release notes for the website.)
> > > >
> > > > The vote will be open for at least 72 hours starting Tuesday
> 9/12/2017
> > > and
> > > > close at 9/15/2017 Noon Eastern Time USA.
> > > > Please download the release candidate and evaluate the necessary
> items
> > > > including checking hashes, signatures, build from source, and test.
> > Then
> > > > please vote:
> > > >
> > > > [ ] +1 Release this package as rya-project-3.2.11
> > > > [ ] +0 no opinion
> > > > [ ] -1 Do not release this package because because...
> > > >
> > >
> >
>

[jira] [Created] (RYA-19) Type-o in MongoDBRyaDAO

[Jeff Dasch (JIRA)]

Jeff Dasch created RYA-19:
-

 Summary: Type-o in MongoDBRyaDAO
 Key: RYA-19
 URL: https://issues.apache.org/jira/browse/RYA-19
 Project: Rya
  Issue Type: Bug
  Components: dao
Affects Versions: 3.2.10
Reporter: Jeff Dasch


Prevents a user from authenticating unless their password and db_name are the 
same.

At MongoDBRyaDAO.java:95

Bug:
MongoCredential cred = MongoCredential.createCredential(
conf.get(MongoDBRdfConfiguration.MONGO_USER),
conf.get(MongoDBRdfConfiguration.MONGO_USER_PASSWORD),
conf.get(MongoDBRdfConfiguration.MONGO_DB_NAME).toCharArray());

Fix:
MongoCredential cred = MongoCredential.createCredential(
conf.get(MongoDBRdfConfiguration.MONGO_USER),
conf.get(MongoDBRdfConfiguration.MONGO_DB_NAME),
conf.get(MongoDBRdfConfiguration.MONGO_USER_PASSWORD).toCharArray());




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)