Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!gegeweb.org!de-l.enfer-du-nord.net!feeder1.enfer-du-nord.net!newsfeed.CARNet.hr!newsfeed.t-com.hr!news3.t-com.hr!not-for-mail From: Pitch Newsgroups: comp.lang.java.programmer Subject: Re: Death To Sub-Sub-Sub-Directories! Date: Wed, 11 May 2011 10:53:08 +0200 Organization: T-Com Lines: 21 Message-ID: References: NNTP-Posting-Host: 93-141-54-3.adsl.net.t-com.hr Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: quoted-printable X-Trace: ss408.t-com.hr 1305103988 6864 93.141.54.3 (11 May 2011 08:53:08 GMT) X-Complaints-To: abuse@t-com.hr NNTP-Posting-Date: Wed, 11 May 2011 08:53:08 +0000 (UTC) User-Agent: MicroPlanet-Gravity/2.71.4 Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:3958 In article , "Lawrence D'Oliveiro" says... >=20 > Google?s tool for creating an Android project insists on creating a=20 > subdirectory hierarchy corresponding to the package naming hierarchy. Thu= s,=20 > if you name your class ?com.example.test_project.Main?, it will put=20 > Main.java inside the subdirectory src/com/example/test_project/. >=20 > But it turns out no part of the build process depends on this: you can pu= t=20 > all source files at the top level of your ?src? subdirectory, and the=20 > project still builds just fine. I hate subdirrs as well. All my java-projects often have only one package= =20 inside. I like the way .NET classes are configured.=20 --=20 CC BY-NC-SA 3.0