If you cut your java packages along the business logic but need one class in two packages, what do you do? Replicate or a 'commons' package?
4
@owehrens Two systems? Copy. One system? Share.
1
@stilkov So that's an almost to easy answer, so I just name it util package right? ;-)
1
Replying to @owehrens
@owehrens The risk of "util" is that you'll start grouping stuff together that has nothing to do with each other

Jul 27, 2013 路 9:37 PM UTC

1
Replying to @stilkov
@stilkov Jup, so sharing from one package to another ? without the 'in-between-util' ?
1
@owehrens What's wrong with having many properly named utility packed, each containing just a few (related) classes?
2
more replies