Package not found

[Maria Isabel]

Why is it not recognizing the package?

p.s ClassA:

package packagea;
public class ClassA{}

[Campbell Ritchie]

Welcome to the Ranch

Please navigate to the root folder where both packages would appear if you use ls. [edit]That means the OCP folder.

[Norm Radder]

If you are in the packageb folder,  the javac command needs a way to find the packagea folder.  I believe the -cp option can do that. For example:
javac -cp <path-to-folder-holding-packagea> ClassB.java

[Roland Mueller]

Using plain javac the default classpath contains the work directory where javac is executed.

For production you should look into some build tool like Maven.

Example:

In directory java_packs you have the two source files located
$ tree java_packs/ java_packs/ ├── packagea │   └── A.java └── packageb    └── B.java

Compile the packageb/B.java
$ cd java_packs $ javac packageb/B.java

After that javac create both class files since its able to resolve the dependency inside packageb.B
$ tree java_packs/ java_packs/ ├── packagea │   ├── A.class │   └── A.java └── packageb    ├── B.class    └── B.java

Execute the code inside java_packs
$ cd java_packs $ java packageb.B

... or provide java with an explicit class path that contains java_packs:
$ java -cp /tmp/java_packs packageb.B

[Campbell Ritchie]

Norm Radder wrote:. . . I believe the -cp option can do that. . . .

Yes, it can.

[Maria Isabel]

Thank you guys!

The solution from Norm Radder using cp from packageb folder worked:

javac -cp ../ ClassB.java 

And the one suggested by Roland Mueller worked as well:
in OCP folder I've run:

javac packageb/ClassB.java 

[Campbell Ritchie]

Maria Isabel wrote:Thank you guys!  . . .

That's a pleasure