RE: Merging to trunk?

2018-01-30 Thread Wahrmann, Helmut
Mike Percy [mailto:mpe...@apache.org] Sent: Dienstag, 30. Jänner 2018 04:57 To: dev@flume.apache.org Subject: Re: Merging to trunk? On Mon, Jan 29, 2018 at 10:48 AM, Wahrmann, Helmut <helmut.wahrm...@rsa.com > wrote: > > I think it is not a problem to distribute the modules together if we >

Re: Merging to trunk?

2018-01-29 Thread Mike Percy
On Mon, Jan 29, 2018 at 10:48 AM, Wahrmann, Helmut wrote: > > I think it is not a problem to distribute the modules together if we have > maintainers for them. > It doesn't make sense to release Flume 1.9 in 2018 with support for module > versions which were current in

Re: Merging to trunk?

2018-01-29 Thread Ferenc Szabo
o > their latest version. > If we can't find someone, we should distribute it separately. > > best regards, > > Helmut > > > -Original Message- > From: Mike Percy [mailto:mpe...@apache.org] > Sent: Montag, 29. Jänner 2018 09:12 > To: dev@flume.apache.o

RE: Merging to trunk?

2018-01-29 Thread Wahrmann, Helmut
version. If we can't find someone, we should distribute it separately. best regards, Helmut -Original Message- From: Mike Percy [mailto:mpe...@apache.org] Sent: Montag, 29. Jänner 2018 09:12 To: dev@flume.apache.org Subject: Re: Merging to trunk? Interesting proposal Yonghao. I think

Re: Merging to trunk?

2018-01-29 Thread Mike Percy
It is ridiculous to release flume 1.9 with elasticsearch 0.90.1 support, > > when 6.x is the current version. > > > > > > > > Best regards, > > > > Helmut Wahrmann > > > > > > Ursprüngliche Nachricht ---- > >

Re: Merging to trunk?

2018-01-27 Thread Yonghao Zou
oers <ralph.go...@dslextreme.com> > Datum: 26.01.18 22:12 (GMT+01:00) > An: dev@flume.apache.org > Betreff: Re: Merging to trunk? > > The “right” way to deal with this from a Maven perspective is to declare > the version you want in the dependencyManagement section of the par

Re: Merging to trunk?

2018-01-26 Thread Wahrmann, Helmut
Nachricht Von: Ralph Goers <ralph.go...@dslextreme.com> Datum: 26.01.18 22:12 (GMT+01:00) An: dev@flume.apache.org Betreff: Re: Merging to trunk? The “right” way to deal with this from a Maven perspective is to declare the version you want in the dependencyManagement section of the pare

Re: Merging to trunk?

2018-01-26 Thread Ralph Goers
inal Message- > From: Mike Percy [mailto:mpe...@apache.org] > Sent: Donnerstag, 25. Jänner 2018 23:01 > To: dev@flume.apache.org > Subject: Re: Merging to trunk? > > Hi Helmut, > I wrote a small Perl script to identify dependency conflicts based on output > from mvn dependenc

RE: Merging to trunk?

2018-01-26 Thread Wahrmann, Helmut
st regards, Helmut -Original Message- From: Mike Percy [mailto:mpe...@apache.org] Sent: Donnerstag, 25. Jänner 2018 23:01 To: dev@flume.apache.org Subject: Re: Merging to trunk? Hi Helmut, I wrote a small Perl script to identify dependency conflicts based on output from mvn dependency:tree

Re: Merging to trunk?

2018-01-25 Thread Mike Percy
, which might cause problems to > other projects. > So I think it can be safely merged into trunk. > > best regards, > > Helmut > > > -Original Message- > From: Mike Percy [mailto:mpe...@apache.org] > Sent: Dienstag, 23. Jänner 2018 20:39 > To: dev@flume.a

RE: Merging to trunk?

2018-01-24 Thread Wahrmann, Helmut
problems to other projects. So I think it can be safely merged into trunk. best regards, Helmut -Original Message- From: Mike Percy [mailto:mpe...@apache.org] Sent: Dienstag, 23. Jänner 2018 20:39 To: dev@flume.apache.org Subject: Re: Merging to trunk? Hi Helmut, Thank you

Re: Merging to trunk?

2018-01-23 Thread Mike Percy
Hi Helmut, Thank you for bringing this up on dev@ and thank you for the patch. I see there are other people people interested in this component upgrade as well. As you are probably aware, a Flume committer will need to approve the change before I gets merged to trunk. My primary concern w/