I believe using wildcards for imports can, in some cases, cause issues.
http://www.coderanch.com/how-to/java/WildCardVsSpecificImports
http://stackoverflow.com/questions/147454/why-is-using-a-wild-card-with-a-java-import-statement-bad/147461#147461
This question should not apply to CDT in general if we we use Ctrl-Shift-O to manage our imports since Eclipse won't use wildcards unless you have more than 99 similar imports. I think there is only one file were that happens, which triggered Elena's question.
I agree not to ask people to change their settings. For that one file, I'll probably change it back myself when I notice it, but I won't ask others to do it.
Now, to my surprise, I do see that wildcards are used once in a while in CDT for imports. Those are imports that were included by hand. I think we should avoid those as a general rule.
I'd would suggest CDT not uses wilcards for imports unless Eclipse does it itself using Ctrl-Shift-O. This addresses Elena's concern, and makes the code more robust.
Opinions?
Marc
From: cdt-dev-bounces@xxxxxxxxxxx [cdt-dev-bounces@xxxxxxxxxxx] on behalf of Alena Laskavaia [elaskavaia.cdt@xxxxxxxxx]
Sent: January 19, 2015 10:24 AM
To: Doug Schaefer
Cc: CDT General developers list.
Subject: Re: [cdt-dev] Using '*' for java imports
Marc are you ok with that?