C
cppaddict
When I organize new Java projects I like to put
all the files in a new folder. To avoid class
not found errors at runtime, I've been putting
the new folder in my CLASSPATH. This method is
obviously a hack, and it results in an
ever-growing CLASSPATH.
What can I do to avoid this?
My goals are:
1. Be able to put new projects in new directories
(prefereably anywhere on my computer, but I'll
settle for below my CLASSPATH).
2. Be able to reference reusable library packages
that reside in my CLASSPATH using import
statements.
As a related aside, how does java find things in
the java package even though the path to it isn't
in my CLASSPATH? Is the path to these files
somehow built-in during installation?
Thanks for any advice,
cpp
all the files in a new folder. To avoid class
not found errors at runtime, I've been putting
the new folder in my CLASSPATH. This method is
obviously a hack, and it results in an
ever-growing CLASSPATH.
What can I do to avoid this?
My goals are:
1. Be able to put new projects in new directories
(prefereably anywhere on my computer, but I'll
settle for below my CLASSPATH).
2. Be able to reference reusable library packages
that reside in my CLASSPATH using import
statements.
As a related aside, how does java find things in
the java package even though the path to it isn't
in my CLASSPATH? Is the path to these files
somehow built-in during installation?
Thanks for any advice,
cpp