Yes. Good idea. Anyway the dependency should be optional (build in a dedicated profile or not).
Regards JB On Oct 29, 2016, 08:22, at 08:22, Aljoscha Krettek <aljos...@apache.org> wrote: >For the future, we should maybe only build the Kinesis Connector in a >profile. Then it would truly not be build. pushed to maven central, >etc. >For a normal build. > >On Sat, 29 Oct 2016 at 08:20 Jean-Baptiste Onofré <j...@nanthrax.net> >wrote: > >> Thanks Justin. >> >> Anyway I will double check the Kinesis client dependency definition. >> >> Thanks again >> Regards >> JB >> >> >> >> On Oct 29, 2016, 08:18, at 08:18, Justin Mclean ><jus...@classsoftware.com> >> wrote: >> >Hi, >> > >> >Changing my vote to +1 (binding). >> > >> >> Not sure I understand. If the dependency is optional and scope >> >provided, I don't think it's an issue. >> > >> >In the legal JIRA and the discussion on the dev list there's no >nothing >> >about if the dependancy is considered optional or not that I could >> >find. >> > >> >This of course may be obvious to people working on the project but >not >> >to people outside the project - so sorry about that. :-) >> > >> >> Kinesis IO will be used by a very small part of users imho (only >the >> >ones who needs pipelines connected with Kinesis). >> > >> >If that’s the case then IMO there no issue with the dependancy. >> > >> >Thanks, >> >Justin >> >>--------------------------------------------------------------------- >> >To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> >For additional commands, e-mail: general-h...@incubator.apache.org >>
