Hi
On 30/08/2013 09:23, Aleksandar Kurtakov wrote:
--- If this things has been developed in separate branch I would dare to say
that noone would have looked at it and we would have been having same
discussion at the time of branch merge, way later in the release cycle and with
way more changes done in not the best way.
This comment has been made before and is just not true.
If it was in a branch it might perhaps only be used by real enthusiasts.
But if that branch was built so that there was an update available (as
there was with JDT @NonNull Annotations) then it really could be used.
JDT @NonNull Annotations is perhaps an interesting comparison. I started
off very enthisiatic about it but have got somewhat disillusioned
because of the large number of legacy calls that would provoke too many
warnings if checked. So sadly the Annotations are only 50% Bye-Bye-NPE
deceiving me into thinking my code is now good.
The JDT @NonNull Annotations are also interesting in regard to the
amount of discussion provoked. Again sadly limited resources mean that
few of the suggestions have actually progressed.
But yes a branch and a build will provoke relevant uptake. I see no
reason why an optional JFace update shouldn't be made available, apart
from the problem that every downstream project might be broken.
Regards
Ed Willink
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
