Programmers are trained to organize related files in coordinated folders. Older people – or Linux people – might prefer “directory” to “folder.”<\/p>\n
However you see it, a way to organize related files in Java is to identify them as belonging to the same package. All the members of that package are stored in the same directory, which is named the same as the package.<\/p>\n
Each file in a package must declare, on its first line, <\/p>\n
package nameofpackage<\/i>;<\/span><\/p>\n Let’s imagine, for instance, a package called P1. Then each file in it contains the first line<\/p>\n package P1<\/i>;<\/span><\/p>\n Every file in that package is stored in the folder P1<\/span><\/p>\n A file in a package can be compiled from within the package directory, but running it might be easier to do from the directory above it. Let’s image that, in the package P1, the file containing the main()<\/span> method is called P1Driver. Furthermore, let’s imagine the full path to P1Driver is<\/p>\n \/javaprojects\/P1\/P1Driver.java (in Linux)<\/span><\/p>\n or<\/p>\n c:\/javaprojects\/P1\/P1Driver.java (Windows)<\/span><\/p>\n In either case, one way to run P1Driver, once compiled<\/u>, might be to back out to the directory above it:<\/p>\n \/javaprojects or c:\/javaprojects <\/p>\n then, from there, try the command<\/p>\n java P1.P1Driver<\/span> (Linux)<\/span><\/span><\/p>\n or, in Windows:<\/p>\n java -cp . P1.P1Driver<\/span><\/p>\n There are many fine points to discuss concerning Java. HTH:)<\/p>\n Source:<\/p>\n Schildt, Herbert. Java: the Complete Reference<\/u>. New York: McGraw Hill, 2011.<\/p>\n