Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!goblin3!goblin.stu.neva.ru!odin.sdf-eu.org!.POSTED!not-for-mail From: dagon@dagon.net (Dagon) Newsgroups: comp.lang.java.programmer Subject: Re: Death To Sub-Sub-Sub-Directories! Date: Thu, 5 May 2011 09:16:35 -0700 Organization: Dagon.net Lines: 23 Message-ID: <34va98-dgm.ln1@dagon.net> References: NNTP-Posting-Host: sverige.freeshell.org X-Trace: odin.sdf-eu.org 1304625333 23021 192.94.73.4 (5 May 2011 19:55:33 GMT) X-Complaints-To: usenet@odin.sdf-eu.org NNTP-Posting-Date: Thu, 5 May 2011 19:55:33 +0000 (UTC) mail-copies-to: never x-fastest-land-animal: cheetah disclaimer: bears author this post for full responsibility X-Newsreader: trn 4.0-test77 (Sep 1, 2010) Originator: dagon@dagon.net (Dagon) Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:3583 Lawrence D'Oliveiro wrote: >Google’s tool for creating an Android project insists on creating a >subdirectory hierarchy corresponding to the package naming hierarchy. So does everyone else's java tools, including eclipse, netbeans, javac. And by "insist", you mean "does this by default" - it's optional but highly recommended. >Thus, if you name your class com.example.test_project.Main, it will put >Main.java inside the subdirectory src/com/example/test_project/. Right. That's sensible for any non-tiny codebase. >But it turns out no part of the build process depends on this: you can put >all source files at the top level of your “src” subdirectory, and the >project still builds just fine. Yup. You'll hate yourself when you try to manage a nontrivial project that's set up wrong, but it's allowed by almost all java tools. -- Mark Rafn dagon@dagon.net