• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Reading Chapter 10 to Grasp Chapter 1 public, protected, private mechanisms

 
Ranch Hand
Posts: 434
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hello,

I'm reading Sierra/Bates and to understand the public, protected, private mechanisms used across multiple files in multiple packages, I am interested in understanding how to compile multiple files. Since I am unable to grasp this concept at Chapter 10, I studied several links, one of which is:

http://javaworkshop.sourceforge.net/chapter3.html

I followed the directions for creating and compiling the file, even using the same directory structure. When I type in the following command to compile:



I get this:



What does this error mean?
 
Sheriff
Posts: 9707
43
Android Google Web Toolkit Hibernate IntelliJ IDE Spring Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
This error means that the directory path you gave doesn't exists. Are you executing this command from the parent directory of src directory i.e. test directory?? And did you properly place the java files in the test/src/com/mycompany/myproject/ directory??
 
Sandra Bachan
Ranch Hand
Posts: 434
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Gosh, that was pretty obvious

I guess I was confusing this with setting up packages, i.e. I was under the impression that I had to create a path test/src/com/example/graphic, but no, the class files will go into test/classes/com/example/graphic, while the source files go under test/src/com/mycompany/myproject

When the .java files get compiled using the command in the common test directory, the class files go under /classes/.../graphic.


Wow, I've been ruminating over this all week!

Thanks!
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic