Alexey,
Sorry, I forgot to update dependencies. Now it should be fine.
Roman


    On Wednesday, April 19, 2017 9:56 PM, Alexey Goncharuk 
<alexey.goncha...@gmail.com> wrote:
 

 Roman,
I see that you've changed the rocketmq version to 4.0.0-SNAPSHOT, but this does 
not work because it requires a local copy of rocketmq. If I revert it back to 
4.0.0-incubating, then the test does not compile for me.
2017-04-19 11:55 GMT+03:00 Roman Shtykh <rsht...@yahoo.com.invalid>:

Hi Alexey,
Fixed now. Thanks for checking!
Roman


    On Tuesday, April 18, 2017 10:17 PM, Alexey Goncharuk 
<alexey.goncha...@gmail.com> wrote:


 Hi Roman,

I tried to run tests for RocketMQ streamer, but they failed for me (I've
added a comment in the ticket). Can you please take a look?

2017-04-18 15:13 GMT+03:00 Vladimir Ozerov <voze...@gridgain.com>:

> Folks,
>
> I created branch for AI 2.0: ignite-2.0. Relevant PR #1819. Let's continue
> 2.0 finalization in this branch.
>
> On Wed, Apr 12, 2017 at 7:58 AM, Dmitriy Setrakyan <dsetrak...@apache.org>
> wrote:
>
> > Awesome! Great addition to the project.
> >
> > On Tue, Apr 11, 2017 at 8:27 PM, Denis Magda <dma...@apache.org> wrote:
> >
> > > Spring Data integration caught up the train and will be released in
> 2.0:
> > > https://issues.apache.org/ jira/browse/IGNITE-1192 <
> > > https://issues.apache.org/ jira/browse/IGNITE-1192>
> > >
> > > —
> > > Denis
> > >
> > > > On Apr 9, 2017, at 6:57 AM, Denis Magda <dma...@gridgain.com> wrote:
> > > >
> > > > Val, yes, as far as I know we still need to merge to the master. The
> > > branch should be ready later the next week.
> > > >
> > > > Denis
> > > >
> > > > On Sat, Apr 8, 2017 at 6:14 PM, Valentin Kulichenko <
> > > valentin.kuliche...@gmail.com <mailto:valentin.kulichenko@ gmail.com>>
> > > wrote:
> > > > Guys,
> > > >
> > > > There is no branch for 2.0 right now, correct? If I want to add
> > something
> > > > there, do I just merge to master?
> > > >
> > > > -Val
> > > >
> > > > On Sat, Apr 8, 2017 at 10:18 AM, Alexander Paschenko <
> > > > alexander.a.paschenko@gmail. com <mailto:alexander.a.paschenko@
> > gmail.com>>
> > > wrote:
> > > >
> > > > > I've fixed https://issues.apache.org/ jira/browse/IGNITE-4354 <
> > > https://issues.apache.org/ jira/browse/IGNITE-4354>, PR is
> > > > > https://github.com/apache/ ignite/pull/1759 <
> > https://github.com/apache/
> > > ignite/pull/1759>.
> > > > > Pavel, thank you very much for bringing that to my attention.
> > > > >
> > > > > - Alex
> > > > >
> > > > > 2017-04-07 20:28 GMT+03:00 Sergi Vladykin <
> sergi.vlady...@gmail.com
> > > <mailto:sergi.vladykin@gmail. com>>:
> > > > > > A bunch of SQL related tickets is delayed until H2 release on the
> > > next
> > > > > week.
> > > > > >
> > > > > > Sergi
> > > > > >
> > > > > > 2017-04-07 19:36 GMT+03:00 Alexey Goncharuk <
> > > alexey.goncha...@gmail.com <mailto:alexey.goncharuk@ gmail.com>
> > > > > >:
> > > > > >
> > > > > >> Folks,
> > > > > >>
> > > > > >> The status of ignite-3477 is as follows: we've fixed almost all
> > > tests
> > > > > and
> > > > > >> currently waiting for ignite-4535 and ignite-4534 to be merged,
> > > which
> > > > > will
> > > > > >> happen once TC for those branches is completed. This should
> happen
> > > over
> > > > > the
> > > > > >> weekend.
> > > > > >>
> > > > > >> 2017-04-06 19:12 GMT+03:00 Alexey Kuznetsov <
> > akuznet...@apache.org
> > > <mailto:akuznet...@apache.org> >:
> > > > > >>
> > > > > >> >  I've prepared
> > > > > >> >
> > > > > >> >  IGNITE-4349 <https://issues.apache.org/
> jira/browse/IGNITE-4349
> > <
> > > https://issues.apache.org/ jira/browse/IGNITE-4349>> -
> > > > > >> > Discontinue the schema-import utility
> > > > > >> >
> > > > > >> > Anton, could you review my changes related to Ignite *build*?
> > > > > >> > See: http://reviews.ignite.apache.
> org/ignite/review/IGNT-CR-163
> > <
> > > http://reviews.ignite.apache. org/ignite/review/IGNT-CR-163>
> > > > > >> >
> > > > > >> >
> > > > > >> > --
> > > > > >> > Alexey Kuznetsov
> > > > > >> >
> > > > > >>
> > > > >
> > > >
> > >
> > >
> >
>

   



   

Reply via email to