Yeah, my idea is that I'll be lowering the build time quite a bit. :)
On Fri, Oct 4, 2013 at 3:44 PM, Christian Müller <christian.muel...@gmail.com> wrote: > Cool. > We have to have an eye on the build time, because we add new components and > tests in each release which is increasing it... > > Best, > > Christian > ----------------- > > Software Integration Specialist > > Apache Camel committer: https://camel.apache.org/team > V.P. Apache Camel: https://www.apache.org/foundation/ > Apache Member: https://www.apache.org/foundation/members.html > > https://www.linkedin.com/pub/christian-mueller/11/551/642 > > > On Fri, Oct 4, 2013 at 9:07 PM, James Carman > <ja...@carmanconsulting.com>wrote: > >> Agreed, Christian. There are more references to Mockito in the >> codebase than there are EasyMock. Given that trend, I'm thinking I'll >> write up a patch with Mockito. >> >> On Fri, Oct 4, 2013 at 3:03 PM, Christian Müller >> <christian.muel...@gmail.com> wrote: >> > Hy guys, I'm a bit late... >> > >> > I'm also fine with both, Mockito and EasyMock, but would also prefer if >> we >> > only use one of both in intermediate-term. I think it's easier to >> maintain >> > only one over the time... >> > >> > Best, >> > >> > Christian >> > ----------------- >> > >> > Software Integration Specialist >> > >> > Apache Camel committer: https://camel.apache.org/team >> > V.P. Apache Camel: https://www.apache.org/foundation/ >> > Apache Member: https://www.apache.org/foundation/members.html >> > >> > https://www.linkedin.com/pub/christian-mueller/11/551/642 >> > >> > >> > On Fri, Oct 4, 2013 at 3:54 PM, Jean-Baptiste Onofré <j...@nanthrax.net >> >wrote: >> > >> >> Thanks to you ! >> >> >> >> I will take a look to "replace" Easymock by Mockito in other tests. >> >> >> >> Regards >> >> JB >> >> >> >> >> >> On 10/04/2013 03:52 PM, James Carman wrote: >> >> >> >>> JIRA created: >> >>> >> >>> https://issues.apache.org/**jira/browse/CAMEL-6826< >> https://issues.apache.org/jira/browse/CAMEL-6826> >> >>> >> >>> I'll work on a patch this evening and attach it. Thanks for the input, >> >>> JB! >> >>> >> >>> >> >>> On Fri, Oct 4, 2013 at 9:47 AM, Jean-Baptiste Onofré <j...@nanthrax.net> >> >>> wrote: >> >>> >> >>>> Fair enough, yes. >> >>>> >> >>>> Regards >> >>>> JB >> >>>> >> >>>> >> >>>> On 10/04/2013 03:44 PM, James Carman wrote: >> >>>> >> >>>>> >> >>>>> By the way, I just did a quick search and mockito is found all over >> >>>>> the place in the codebase, so I would guess it's okay. >> >>>>> >> >>>>> >> >>>>> On Fri, Oct 4, 2013 at 9:41 AM, James Carman < >> >>>>> ja...@carmanconsulting.com> >> >>>>> wrote: >> >>>>> >> >>>>>> >> >>>>>> I agree that we should try to standardize, but it is only a >> >>>>>> test-scoped dependency, so it's not like you'll put a burden on user >> >>>>>> code. Do we really think that in order for one component to use >> >>>>>> Mockito that we have to change everyone else? If it's not that >> >>>>>> pervasive, it's not a big deal, but could be a nightmare if it is. >> >>>>>> >> >>>>> >> >>>> >> >>>> -- >> >>>> Jean-Baptiste Onofré >> >>>> jbono...@apache.org >> >>>> http://blog.nanthrax.net >> >>>> Talend - http://www.talend.com >> >>>> >> >>> >> >> -- >> >> Jean-Baptiste Onofré >> >> jbono...@apache.org >> >> http://blog.nanthrax.net >> >> Talend - http://www.talend.com >> >> >>
