Path: csiph.com!newsfeed.hal-mli.net!feeder3.hal-mli.net!newsfeed.hal-mli.net!feeder1.hal-mli.net!feeder.erje.net!eu.feeder.erje.net!news.albasani.net!news.mixmin.net!aioe.org!.POSTED!not-for-mail From: Dave Newsgroups: comp.lang.java.programmer Subject: Package naming, disk organization Date: Mon, 01 Jul 2013 17:39:45 -0400 Organization: Aioe.org NNTP Server Lines: 27 Message-ID: NNTP-Posting-Host: 6Hsfpp6SxKsmazVIhouhmw.user.speranza.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@aioe.org User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130330 Thunderbird/17.0.5 X-Notice: Filtered by postfilter v. 0.8.2 Xref: csiph.com comp.lang.java.programmer:24557 I'm having fun with Java (really!), but the real-world use of packages is driving me crazy. If I were a corp. with a web site I might have a something like this: org.davesjava.firstlgproj for a package specification. I guess the disk drive files would be something like: home/org/davesjava/firstlgproj (I use Linux, so there are no '\'). However: * I don't have a commercial organization (yet), so I would need something else - but what? Would jsoft.davesjava.firstlgproj be ok? It seems to work for one trial, but down the road... * I read that Java programmers like to have a source path and a class path on the hard drive, which makes sense. So how does that work for package specifications? Would it be: src/jsoft/davesjava/firstlgproj and class/jsoft/davesjava/firstlgproj ? Assuming so, would a package specification of jsoft.davesjava.firstlgproj still be ok? * There is a conflict between a simple file structure and a conventional package specification. For example, I may like: home/jsoft/src/firstlgproj and home/jsoft/class/firstljproj , but that translates into jsoft.class.firstlgproj - not exactly to convention. So, I'm looking for some suggestions from people that have been there done that. Thanks, Dave