ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jaikiran Pai <>
Subject Re: Coding style: import of nested classes
Date Thu, 20 Jul 2017 13:13:56 GMT
I have no personal preference for this specific kind of usages. Although 
I almost always use Map.Entry in the statements, I don't mind seeing 
code which uses just plain Entry. Having said that, for this specific 
kind of cases, I personally would just let the developer decide which 
form of it to use instead of trying to make it consistent via checkstyle 
or refactoring.


On 18/07/17 5:09 PM, Gintautas Grigelionis wrote:
> In my last PR I tried to address inconsistencies with import of nested
> classes, such as Map.Entry; some classes, e.g. IvySettings ended up with
> foreach loops over both Entry and Map.Entry. So: should qualified names be
> encouraged or avoided?
> Gintas

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message