Re: PR-33: problems

is exposing. > > Nicolas > > > > > > > > > Jan > > > >> -Ursprüngliche Nachricht- > >> Von: J Pai [mailto:jai.forums2...@gmail.com] > >> Gesendet: Montag, 29. Mai 2017 10:26 > >> An: Ant Developers List > >

Re: PR-33: problems

Pai [mailto:jai.forums2...@gmail.com] >> Gesendet: Montag, 29. Mai 2017 10:26 >> An: Ant Developers List >> Betreff: Re: PR-33: problems >> >> IMO, for each of these public classes/methods/fields that we are fixing >> for typos, we should mark them @Deprecate

Re: AW: PR-33: problems

inary compatibility; however, it breaks contract compatibility (and source code compatibility)." What do we want? Jan > -Ursprüngliche Nachricht- > Von: J Pai [mailto:jai.forums2...@gmail.com] > Gesendet: Montag, 29. Mai 2017 10:26 > An: Ant Developers List > Betreff:

AW: PR-33: problems

ty)." What do we want? Jan > -Ursprüngliche Nachricht- > Von: J Pai [mailto:jai.forums2...@gmail.com] > Gesendet: Montag, 29. Mai 2017 10:26 > An: Ant Developers List > Betreff: Re: PR-33: problems > > IMO, for each of these public classes/methods/fi

Re: PR-33: problems

t;> Gesendet: Montag, 29. Mai 2017 11:00 >> An: Ant Developers List >> Betreff: Re: PR-33: problems >> >> If it's acceptable I'll complement the PR addressing all the points. >> >> Gintas >> >> Den 29 maj 2017 10:13 skrev "Jan Matèrne&

AW: PR-33: problems

lionis [mailto:g.grigelio...@gmail.com] > Gesendet: Montag, 29. Mai 2017 11:00 > An: Ant Developers List > Betreff: Re: PR-33: problems > > If it's acceptable I'll complement the PR addressing all the points. > > Gintas > > Den 29 maj 2017 10:13 skrev &qu

Re: PR-33: problems

If it's acceptable I'll complement the PR addressing all the points. Gintas Den 29 maj 2017 10:13 skrev "Jan Matèrne" : I did a review of https://github.com/apache/ant-ivy/pull/33 Here are the points I have problems with, so I want to discuss them he

Re: PR-33: problems

IMO, for each of these public classes/methods/fields that we are fixing for typos, we should mark them @Deprecated (and add a @deprecated javadoc too and point to the new field/method/class) and introduce the rightly named class/method/field. For methods it’s straightforward, the deprecated meth

PR-33: problems

I did a review of https://github.com/apache/ant-ivy/pull/33 Here are the points I have problems with, so I want to discuss them here. Basically it's about breaking BC. So how to deal with that? Jan Fixing the spell error in DelegateHandle