Packaging Java libraries to be "IDE friendly"

I have been working on packaging some of my (mostly) research code into four libraries (a picture), three that depend on a forth.

My concern is mostly "Java IDE kung-fu": users of these libraries (mostly just me :-) only want the highest level APIs to show in popup completion lists and the entire set of implementation classes remain invisible. The solution is easy: a public API class with implementation classes in the same package with package-ony (i.e., neither public or private) visibility.

Comments

Popular posts from this blog

My Dad's work with Robert Oppenheimer and Edward Teller

Ruby Sinatra web apps with background work threads

Time and Attention Fragmentation in Our Digital Lives