logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary Gregory <garydgreg...@gmail.com>
Subject Re: [proposal] import guidelines
Date Fri, 16 May 2014 21:53:25 GMT
I import most general (java, javax) to most specific (com) with org in between. I think this
is the eclipse default. 

I want guidelines that eclipse can sort automatically.  This way there is no time wasting
with manual fiddling. 


<div>-------- Original message --------</div><div>From: Paul Benedict <pbenedict@apache.org>
</div><div>Date:05/16/2014  15:12  (GMT-05:00) </div><div>To: Log4J
Developers List <log4j-dev@logging.apache.org> </div><div>Subject: Re: [proposal]
import guidelines </div><div>
</div>I'd like to throw out something I've grown fond of, which is making one's home
project the top import priority. For you guys, it would be "org.apache.logging.log4j". What
I like so much about this choice is that it makes eye-balling the use of your own classes
very apparent.



On Thu, May 15, 2014 at 12:44 PM, Gary Gregory <garydgregory@gmail.com> wrote:
I propose we use the following guidelines for import statements:


which in Eclipse looks like this:


Note that default settings are not reflected in the .importorder file.


E-Mail: garydgregory@gmail.com | ggregory@apache.org 
Java Persistence with Hibernate, Second Edition
JUnit in Action, Second Edition
Spring Batch in Action
Blog: http://garygregory.wordpress.com 
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

View raw message