Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.java.programmer > #24557 > unrolled thread

Package naming, disk organization

Back to article view | Back to comp.lang.java.programmer

Contents

  Package naming, disk organization Dave <dboland9@fastmail.fm> - 2013-07-01 17:39 -0400
    Re: Package naming, disk organization markspace <markspace@nospam.nospam> - 2013-07-01 15:22 -0700
      Re: Package naming, disk organization Martin Gregorie <martin@address-in-sig.invalid> - 2013-07-01 23:56 +0000
    Re: Package naming, disk organization Roedy Green <see_website@mindprod.com.invalid> - 2013-07-01 15:35 -0700
    Re: Package naming, disk organization Roedy Green <see_website@mindprod.com.invalid> - 2013-07-01 15:36 -0700
    Re: Package naming, disk organization Lew <lewbloch@gmail.com> - 2013-07-01 17:22 -0700
      Re: Package naming, disk organization Jukka Lahtinen <jtfjdehf@hotmail.com.invalid> - 2013-07-02 18:51 +0300
      Re: Package naming, disk organization Arved Sandstrom <asandstrom2@eastlink.ca> - 2013-07-18 23:50 -0300
    Re: Package naming, disk organization Eric Sosman <esosman@comcast-dot-net.invalid> - 2013-07-01 21:30 -0400
      Re: Package naming, disk organization markspace <markspace@nospam.nospam> - 2013-07-01 18:43 -0700
    Re: Package naming, disk organization Dave <dboland9@fastmail.fm> - 2013-07-02 11:09 -0400
      Re: Package naming, disk organization Arne Vajhøj <arne@vajhoej.dk> - 2013-07-03 22:53 -0400
      Re: Package naming, disk organization markspace <markspace@nospam.nospam> - 2013-07-03 20:35 -0700
        Re: Package naming, disk organization Dave <dboland9@fastmail.fm> - 2013-07-04 12:34 -0400
          Re: Package naming, disk organization Jukka Lahtinen <jtfjdehf@hotmail.com.invalid> - 2013-07-04 20:08 +0300
          Re: Package naming, disk organization lipska the kat <"nospam at neversurrender dot co dot uk"> - 2013-07-04 18:24 +0100
          Re: Package naming, disk organization Lew <lewbloch@gmail.com> - 2013-07-04 11:26 -0700
          Re: Package naming, disk organization Arne Vajhøj <arne@vajhoej.dk> - 2013-07-04 15:42 -0400
          Re: Package naming, disk organization Martin Gregorie <martin@address-in-sig.invalid> - 2013-07-04 20:40 +0000
            Re: Package naming, disk organization Lew <lewbloch@gmail.com> - 2013-07-04 14:01 -0700
            Re: Package naming, disk organization Arne Vajhøj <arne@vajhoej.dk> - 2013-07-04 17:06 -0400
      Re: Package naming, disk organization Arne Vajhøj <arne@vajhoej.dk> - 2013-07-04 15:39 -0400

Page 2 of 2 — ← Prev page 1 [2]

#24631

On 7/4/2013 4:40 PM, Martin Gregorie wrote:
> On Thu, 04 Jul 2013 12:34:57 -0400, Dave wrote:
>> On 07/03/2013 11:35 PM, markspace wrote:
>>> I still don't like the split between src and class at the top level.
>>> It's weird, and as others have pointed out you'll fight most tools
>>> (IDEs, etc.) to do it this way.  Easier is project_name/src and
>>> project_name/build/classes.
>>>
> Same here - and I've never bothered with any attempt to separate .java
> files from the rest of the compiler output. All the tools (javac, ant,
> javadocs etc.) can work very nicely with this mix. I know some C
> programmers like to separate source from object, but in Java its really
> just as easy to leave them in the same place. ant, in particular, is even
> has a notation, "org/**/*.class", which means "walk the directory tree
> whose root is 'org' and apply this operation to every class file in the
> tree. IOW, if it was building a jarfile, it would include all the
> directories and class files while omitting any other files in the tree.

The same tools also work with the source and output files
separated.

And it is easier to just view the source files instead of all
files.

And if you start to run tools that generate Java source code
(like WSDL2Java), then having everything in one dir just doesn't
cut it anymore.

Arne

[toc] | [prev] | [next] | [standalone]

#24624

On 7/2/2013 11:09 AM, Dave wrote:
> On 07/01/2013 05:39 PM, Dave wrote:
>> 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.

> Fist, thanks for all of the insight!  Based on what everyone has said,
> and what I have read (Oracle, other online info), the plan is to:
>
> 1. Eventually get URL, but that will have to wait until a few other
> shoes have dropped so I don't have to keep changing it (as was mentioned
> by a few of you).  Something I did not consider, but with the wave of
> mergers of companies, I can see that this could be a real headache to
> down-stream developers using my packages.
>
> 2. For now, use foo.dboland.<proj_name> as the URL.

I will say as many other - why not do it right from start
and follow the domain convention.

>                                                      The disk
> organization would then be (Linux):
>      home/user/javadev/src/foo/dboland/<proj_name>
>      home/user/javadev/class/foo/dboland/<proj_name>
> The class path will be: home/user/javadev/class
> And the package specification will be: foo.dboland.<proj_name>

You will find that:

home/user/javadev/<proj_name>/src/foo/dboland/<proj_name>
home/user/javadev/<proj_name>/bin/foo/dboland/<proj_name>

work better with both the common IDE's and some command
line tools.

Arne

[toc] | [prev] | [standalone]

Page 2 of 2 — ← Prev page 1 [2]

Back to top | Article view | comp.lang.java.programmer

csiph-web