- mvn install failed on the integration tests on streams-examples because of java.lang.NoClassDefFoundError: org/apache/commons/io/FileUtils eminating from de.flapdoodle.embed.process
I seem to recall the mongo embed plugin acting up on certain (older) versions of maven/java. It works on the newest maven 3.3.x and either java 1.7.0_x or 1.8.0_x The package name was wrong in the twitter-userstream-elasticsearch example docs/the package naming is inconsistent in the various examples Created STREAMS-408 The docker instructions probably need a note on how to provide application.conf to the container without using HTTP There are a lot of ways to pass type safe configs into streams. The examples only use two (file and http) - file when calling java (easiest) and http with calling docker (also easiest b/c that way no shared file system is required). Maybe we add a more detailed guide on using typesafe within streams-config and link to above the footer on each example page? The Elasticsearch examples are broken on ES 2.x Yes. STREAMS-400 would address this. ES 2.0 works with very minor changes under src/main/java, the changes to integration testing are more significant because the harness currently used no longer exposes the transport client port in 2.0+. I’ve found integration testing with docker containers to be superior to maven plugins and suggest getting started in that direction in STREAMS-404. Links in the READMEs are broken on GitHub Mentioned this also in STREAMS-408 Since these are in the examples project and none of them are, functionally, blockers I think it'd be fine to go ahead and fix them in the next release. I think so too. Steve On September 24, 2016 at 4:00:58 PM, Joey Frazee (joey.fra...@icloud.com) wrote: +1 (non-binding) - Verified checksums and signatures. - Ran mvn clean install test verify on OS X with Java 1.8.0_71 on streams-project. - Ran mvn clean install test verify -DskipITs on OS X with Java 1.8.0_71 on streams-examples. - Ran mvn clean install test verify on OS X with Java 1.8.0_71 on streams-master. - Built and ran both twitter-userstream-elasticsearch and twitter-history-elasticsearch with and without Docker on Elasticsearch 1.7.5. There's been a lot of functionality added, bugfixes, (support for graphs, improvements to HDFS, addition of Kinesis, improvements to configuration) and a lot of good documentation written so it seems time for a release. I did notice some minor problems with the streams-examples project FWIW: - mvn install failed on the integration tests on streams-examples because of java.lang.NoClassDefFoundError: org/apache/commons/io/FileUtils eminating from de.flapdoodle.embed.process - The package name was wrong in the twitter-userstream-elasticsearch example docs/the package naming is inconsistent in the various examples - The docker instructions probably need a note on how to provide application.conf to the container without using HTTP - The Elasticsearch examples are broken on ES 2.x - Links in the READMEs are broken on GitHub Since these are in the examples project and none of them are, functionally, blockers I think it'd be fine to go ahead and fix them in the next release. -joey On Sep 21, 2016, at 07:13 PM, Steve Blackmon <sblack...@apache.org> wrote: I neglected to supply the hashes of each release candidates. They are: incubator-streams-master source tag (r0.3-incubating): https://git-wip-us.apache.org/repos/asf?p=incubator-streams-master.git;a=commit;h=4a148fc84ce688165f85f9813ebd46ceda73b5e4 incubator-streams source tag (r0.3-incubating): https://git-wip-us.apache.org/repos/asf?p=incubator-streams.git;a=commit;h=bf17cfcba3a4f22a40592d9fbe0ecb47d6cfd58e incubator-streams-examples source tag (r0.3-incubating): https://git-wip-us.apache.org/repos/asf?p=incubator-streams-examples.git;a=commit;h=3e91ab1da036f6e6b3e0ea2fd38519770018198f Steve Blackmon sblack...@apache.org On Wed, Sep 21, 2016 at 7:03 PM, apache <sblack...@apache.org> wrote: I've created a combined 0.3-incubating release candidate, with the following artifacts up for a vote: incubator-streams-master source tag (r0.3-incubating): https://git-wip-us.apache.org/repos/asf?p=incubator-streams- master.git;a=commit;h=... incubator-streams source tag (r0.3-incubating): https://git-wip-us.apache.org/repos/asf?p=incubator-streams. git;a=commit;h=... incubator-streams-examples source tag (r0.3-incubating): https://git-wip-us.apache.org/repos/asf?p=incubator-streams- examples.git;a=commit;h=... This is the third release for streams-project, the second release for streams-master, and the first release for streams-examples. Maven staging repo: https://repository.apache.org/content/repositories/ orgapachestreams-1014 Source releases: https://repository.apache.org/content/repositories/${ release.master.repository}/org/apache/streams/streams- master/0.3-incubating/streams-master-0.3-incubating-source-release.zip https://repository.apache.org/content/repositories/${ release.project.repository}/org/apache/streams/streams- project/0.3-incubating/streams-project-0.3-incubating-source-release.zip https://repository.apache.org/content/repositories/${ release.project.repository}/org/apache/streams/streams- examples/0.3-incubating/streams-examples-0.3-incubating-source-release.zip Checksums of streams-master-0.3-incubating-source-release.zip: MD5: 28b5f6b973195b93b8728d2e1734e25a SHA1: 89c24bdaae4d4f0ad699d9fe5f4749bde1eae953 Checksums of streams-project-0.3-incubating-source-release.zip: MD5: 066031e9d68d00b271ed4085f5203976 SHA1: 046a46bab61f995a88ff138dc182099c6d9a14f1 Checksums of streams-examples-0.3-incubating-source-release.zip: MD5: 1a67d67fa1548ffb614bd1ad93141f96 SHA1: 7e059149915c648033514eb981137fa35e8a645d Release artifacts are signed with the following key: https://people.apache.org/keys/committer/sblackmon.asc These repositories must be built in the right order: first streams-master, then streams-project, finally streams-examples, all using: mvn clean install test verify Note that MAVEN_OPTS should set the java heap to at least 2G for best results. Please take the time to verify the artifacts before casting your vote. Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why)
