I contacted the guy who did a pull request and he will re-do the request as
I committed the commons-lan 3.1 changes and did not want to merge his code.


On 25 January 2012 19:12, Dmitry Buzdin <
reply@reply.github.com
> wrote:

> Hi Alan,
>
> Yes, 5.4.0 would be more suitable for the next release.
>
> I would like to apply submitted patches and one pull request before
> releasing.
>
> http://sourceforge.net/tracker/?func=detail&aid=3414674&group_id=133517&atid=727370
>
> http://sourceforge.net/tracker/?func=detail&aid=3415759&group_id=133517&atid=727370
>
> Regards,
> Dmitry
>
> On Wed, Jan 25, 2012 at 2:13 AM, Alan Stewart
> <reply@reply.github.com>
> wrote:
> > Hi Dimitry,
> >
> > I updated Dozer to use comons-lang to 3.1.
> >
> > Following the version convention of major.minor.patch, I believe with the
> > changes I have made over the past few days and the move to GitHub as
> well,
> > the next release of Dozer should be 5.4.0, as we have changed
> dependencies
> > and added at at least one new mapping feature (non void setters).
> >
> > I think a new release soon would be good, as 5.3.2 was almost a year ago.
> >
> > Cheers
> >
> > Alan
> >
> >
> > On 24 January 2012 21:29, Dmitry Buzdin <
> > reply@reply.github.com
> >> wrote:
> >
> >> yes, I have renamed the repository to dozer as it is github best
> practice.
> >>
> >> Dmitry
> >>
> >> On Tue, Jan 24, 2012 at 11:39 AM, Alan Stewart
> >> <reply@reply.github.com>
> >> wrote:
> >> > Actually push just worked after I changed the DozerMapper/Dozer.git to
> >> > DozerMapper/dozer.git. Did you change this?
> >> >
> >> >
> >> > On 24 January 2012 20:36, Alan Stewart <alankstewart@gmail.com>
> wrote:
> >> >
> >> >> Hi,
> >> >>
> >> >> I added a new new unit test to ReflectionUtilsTest and also cleaned
> up
> >> all
> >> >> the calls in GranularDozerBeanMapperTest to getMapper so that just a
> >> string
> >> >> is passed as suggested.
> >> >>
> >> >> Having trouble pushing at the moment. Getting
> >> >> ERROR: DozerMapper/Dozer.git doesn't exist. Did you enter it
> correctly?
> >> >> fatal: The remote end hung up unexpectedly
> >> >>
> >> >> Another advantage of commons-lang is that the Validate class can be
> used
> >> >> to enforce the contract of the public api by calls from users.
> >> >> Anyway, I have time tonight and tomorrow morning to do the
> commons-lang
> >> >> 3.1 upgrade, but since this will affect a lot of classes, do you want
> >> me to
> >> >> wait until the morning for you to apply any other patches?  I don't
> >> need to
> >> >> do any more tonight.
> >> >>
> >> >> Let me know
> >> >> Alan
> >> >>
> >> >>
> >> >> On 24 January 2012 19:48, Alan Stewart <alankstewart@gmail.com>
> wrote:
> >> >>
> >> >>> Will have at look at it again soon - just out at the moment. Will
> also
> >> >>> add a unit test for the the new ReflectionUtils method.
> >> >>>
> >> >>>
> >> >>> On 24 January 2012 19:20, Dmitry Buzdin <
> >> >>> reply@reply.github.com
> >> >>> > wrote:
> >> >>>
> >> >>>> I would add a separate unit test on this one in ReflectionUtilsTest
> >> >>>>
> >> >>>> ---
> >> >>>> Reply to this email directly or view it on GitHub:
> >> >>>>
> >> >>>>
> >>
> https://github.com/DozerMapper/Dozer/commit/59513a3e91791671b2475a46655ee81fcc038c5b#commitcomment-895341
> >> >>>>
> >> >>>
> >> >>>
> >> >>
> >> >
> >> > ---
> >> > Reply to this email directly or view it on GitHub:
> >> >
> >>
> https://github.com/DozerMapper/dozer/commit/59513a3e91791671b2475a46655ee81fcc038c5b#commitcomment-895503
> >>
> >> ---
> >> Reply to this email directly or view it on GitHub:
> >>
> >>
> https://github.com/DozerMapper/dozer/commit/59513a3e91791671b2475a46655ee81fcc038c5b#commitcomment-895662
> >>
> >
> > ---
> > Reply to this email directly or view it on GitHub:
> >
> https://github.com/DozerMapper/dozer/commit/59513a3e91791671b2475a46655ee81fcc038c5b#commitcomment-898526
>
> ---
> Reply to this email directly or view it on GitHub:
>
> https://github.com/DozerMapper/dozer/commit/59513a3e91791671b2475a46655ee81fcc038c5b#commitcomment-899356
>