Re: Apache Bahir release for the Flink runtime

2019-09-27 Thread Gustavo Momenté
> > I don't think it's easy to get multiple snapshots for same artifact > name/version. I agree with you, I think right now the best solution for my use case (I can't upgrade to Flink 1.9.0 yet) is to release the old versions in an internal maven repository. I'm not having issues build locally,

Re: Apache Bahir release for the Flink runtime

2019-09-27 Thread Gustavo Momenté
Thanks a lot, that will be really helpful. Do think it would be possible to also publish older versions for flink 1.8.x? On Fri, Sep 27, 2019, 13:03 Luciano Resende wrote: > I just started publishing a snapshot based on latest master. > > It will be available shortly from : >

Re: Apache Bahir release for the Flink runtime

2019-09-27 Thread Luciano Resende
I just started publishing a snapshot based on latest master. It will be available shortly from : https://repository.apache.org/content/groups/snapshots/ On Fri, Sep 27, 2019 at 8:51 AM Gustavo Momenté wrote: > > Any update on this? Are snapshot published anywhere? I'm interested in > using

Re: Apache Bahir release for the Flink runtime

2019-09-27 Thread Gustavo Momenté
Any update on this? Are snapshot published anywhere? I'm interested in using Apache Bahir right now, but can't figure where snapshots are published. On 2019/05/20 07:41:24, Luciano Resende wrote: > Ok, if everybody agrees, we can go with 1.8.0 and try to keep it synchronized.> > > As for

Re: Apache Bahir release for the Flink runtime

2019-05-20 Thread Luciano Resende
Ok, if everybody agrees, we can go with 1.8.0 and try to keep it synchronized. As for remaining items, any must-have items before we try a release candidate? On Mon, May 20, 2019 at 12:30 AM Joao Boto wrote: > > if we re going to try to be syncronized with flink version and this could be >

Re: Apache Bahir release for the Flink runtime

2019-05-19 Thread Joao Boto
if we re going to try to be syncronized with flink version and this could be important because of Blink (Alibaba fork) integration to Flink i think that the next release should be 1.8.0 El lun., 20 may. 2019 a las 0:21, Luciano Resende () escribió: > What should we call the next release then?

Re: Apache Bahir release for the Flink runtime

2019-05-19 Thread Luciano Resende
What should we call the next release then? Just 1.1? 1.5? 2.0? On Mon, May 20, 2019 at 00:13 Joao Boto wrote: > There are a new connectors and some actualizations on previous connectors > Because of that I think so. > > Relatively to synchronization to Flink version, could be interesting but >

Re: Apache Bahir release for the Flink runtime

2019-05-19 Thread Joao Boto
There are a new connectors and some actualizations on previous connectors Because of that I think so. Relatively to synchronization to Flink version, could be interesting but we have to do release more often Joao Boto El dom., 19 may. 2019 a las 23:05, Luciano Resende () escribió: > It has