Please use this thread for discussion regarding the vote.
I'll start by noting that streams now generates maven site documentation.
http://streams.incubator.apache.org/site/0.2-incubating/streams-project/index.html
The site generated from the last commit to streams-examples 0,2-incubating-rc1:
I've created a streams-examples 0.2-incubating release candidate, with
the following artifacts up for a vote:
Git tag streams-examples-0.2-incubating-rc1 (commit 54f25ab)
https://git-wip-us.apache.org/repos/asf?p=incubator-streams-examples.git;a=commit;h=54f25ab25fc66cf882364dbf5f80c4dc0788db1d
M
After many hours trying to suppress the shade plugin during the
release, I've come up with a workaround:
Shaded artifacts are now placed in /dist rather than /target when
apache-release profile is activated.
This allows mvn verify to create and integration test shaded jars, but
ensures they are n
