Re: git commit: Deprecate unused version of the project dependencies resovler in the core

2014-07-05 Thread Hervé BOUTEMY
thank you Jason Regards, Hervé Le samedi 5 juillet 2014 15:59:31 Jason van Zyl a écrit : > On Jul 5, 2014, at 3:16 PM, Jeff Jensen wrote: > > Jason, for: > >> 1) Include a "since" statement indicating at point the API was deprecated > > > > You didn't mention if you are against doing so or no

Re: git commit: Deprecate unused version of the project dependencies resovler in the core

2014-07-05 Thread Jason van Zyl
On Jul 5, 2014, at 3:16 PM, Jeff Jensen wrote: > Jason, for: > >> 1) Include a "since" statement indicating at point the API was deprecated > > You didn't mention if you are against doing so or not. Do you find it of > value for yourself and others? > Certainly can't hurt, so I added a com

Re: git commit: Deprecate unused version of the project dependencies resovler in the core

2014-07-05 Thread Jeff Jensen
Jason, for: > 1) Include a "since" statement indicating at point the API was deprecated You didn't mention if you are against doing so or not. Do you find it of value for yourself and others? > 2) include a statement pointing to the replacement API (or non-replacement > and reason for same).

Re: git commit: Deprecate unused version of the project dependencies resovler in the core

2014-07-05 Thread Jason van Zyl
Generally when I use @Deprecate alone it means there is no replacement. But I marked this change with that sentiment. Right now I consider Maven to be and end user tool. The jumble of components we have let leak to confuse most integrators I would not consider much of an API or SPI. With 4.0.0

Re: git commit: Deprecate unused version of the project dependencies resovler in the core

2014-07-05 Thread William Ferguson
The original Java deprecation guidelines were to 1) Include a "since" statement indicating at point the API was deprecated 2) include a statement pointing to the replacement API (or non-replacement and reason for same). On Sat, Jul 5, 2014 at 10:34 PM, Robert Scholte wrote: > +1, I often hit de

Re: git commit: Deprecate unused version of the project dependencies resovler in the core

2014-07-05 Thread Robert Scholte
+1, I often hit deprecated code without knowing what to use instead. A hint would certainly help. Robert Op Sat, 05 Jul 2014 14:32:14 +0200 schreef Hervé BOUTEMY : when we deprecate somthing like this, we should add a hint on what to do instead: we have a bunch of deprecated things withou

Re: git commit: Deprecate unused version of the project dependencies resovler in the core

2014-07-05 Thread Hervé BOUTEMY
when we deprecate somthing like this, we should add a hint on what to do instead: we have a bunch of deprecated things without any idea on what to do I don't know how we can fix the existing deprecations, but at least I'd like to avoid adding more such "dead-end" deprecations Regards, Hervé Le