D
Dave
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
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