BiteSizedChunks.comLearn one small thing at a time.

Course contentsShow

658What Are Packages and Why They Matter
659Package Declaration Syntax
660Mapping Packages to Directory Structure
661The Default Package and Why to Avoid It
662Source File Organization Rules
663Compiling Packaged Classes
664Running Packaged Classes
665Package Hierarchies Are Not Inheritance
666Best Practices for Package Structure
667The import Statement: Simplifying Fully Qualified Names
668Single-Type Import Declarations
669Type-Import-on-Demand Declarations: The Wildcard Import
670Import Precedence and Handling Name Conflicts
671The java.lang Package: Automatically Imported
672Static Import: Importing Static Members
673Single Static Import vs Static Import on Demand
674Static Import Use Cases: Math and Constants
675Static Import Anti-Patterns and Best Practices
676What Is a Fully Qualified Name (FQN)?
677Using FQNs to Resolve Name Conflicts
678When to Use FQNs vs Import Statements
679Package Naming Convention: Reverse Domain Names
680Package Name Case Conventions: All Lowercase
681Multi-Level Package Hierarchies
682Avoiding Reserved Keywords in Package Names
683Best Practices: Meaningful Package Names
684What Is a JAR File?
685Creating a JAR File with the jar Command
686The JAR Manifest File
687Executable JARs and the Main-Class Attribute
688Extracting and Viewing JAR Contents
689The Classpath: Finding Classes at Runtime
690Setting the Classpath with -cp and -classpath
691The CLASSPATH Environment Variable
692Classpath Order and Class Loading Precedence
693Common Classpath Issues and ClassNotFoundException

658What Are Packages and Why They Matter
659Package Declaration Syntax
660Mapping Packages to Directory Structure
661The Default Package and Why to Avoid It
662Source File Organization Rules
663Compiling Packaged Classes
664Running Packaged Classes
665Package Hierarchies Are Not Inheritance
666Best Practices for Package Structure
667The import Statement: Simplifying Fully Qualified Names
668Single-Type Import Declarations
669Type-Import-on-Demand Declarations: The Wildcard Import
670Import Precedence and Handling Name Conflicts
671The java.lang Package: Automatically Imported
672Static Import: Importing Static Members
673Single Static Import vs Static Import on Demand
674Static Import Use Cases: Math and Constants
675Static Import Anti-Patterns and Best Practices
676What Is a Fully Qualified Name (FQN)?
677Using FQNs to Resolve Name Conflicts
678When to Use FQNs vs Import Statements
679Package Naming Convention: Reverse Domain Names
680Package Name Case Conventions: All Lowercase
681Multi-Level Package Hierarchies
682Avoiding Reserved Keywords in Package Names
683Best Practices: Meaningful Package Names
684What Is a JAR File?
685Creating a JAR File with the jar Command
686The JAR Manifest File
687Executable JARs and the Main-Class Attribute
688Extracting and Viewing JAR Contents
689The Classpath: Finding Classes at Runtime
690Setting the Classpath with -cp and -classpath
691The CLASSPATH Environment Variable
692Classpath Order and Class Loading Precedence
693Common Classpath Issues and ClassNotFoundException

Lesson 665 of 2,870·16. Packages, Imports, and JAR FilesPro lesson

Package Hierarchies Are Not Inheritance

com.example.util and com.example.util.math are separate packages with no special relationship or visibility.

This lesson is for subscribers

You've completed the free preview. Subscribe to unlock every lesson in every course.

See pricing Back to course