Not sure I understand. If the dependency is optional and scope provided, I don't think it's an issue.
If it's not the case (I gonna check) and the resulting jar embeds the dependency it's an issue. Kinesis IO will be used by a very small part of users imho (only the ones who needs pipelines connected with Kinesis). So they can add the Kinesis client by hand. Regards JB On Oct 29, 2016, 07:37, at 07:37, Justin Mclean <jus...@classsoftware.com> wrote: >Hi, > >> We discussed about this dependency on the dev mailing list. > >Yep I read that discussion and it seems to me to be missing the main >point. Yes you can’t have Category X software in a release but you >can’t have it as a dependancy either unless it’s optional. > >> The dependency is not embedded in any Beam distribution or jar file. >The users have to explicitly define the dependency to be able to use >the Kinesis IO. > >Which may not be enough IMO. The question to ask is “Will most users >want to use Kinesis IO or not?" > >Thanks, >Justin >--------------------------------------------------------------------- >To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >For additional commands, e-mail: general-h...@incubator.apache.org
