Import statement usage in Java

Introduction

Import statements let you use code from other places easily. They save time and keep your code clean.

When you want to use a class from another package without writing its full name every time.

When you want to organize your code by using libraries or built-in Java classes.

When you want to avoid repeating long package names in your code.

When you want to use multiple classes from the same package.

When you want to make your code easier to read and maintain.

Syntax

Java

import packageName.ClassName;

// or to import all classes in a package
import packageName.*;

The import statement must be placed at the top of your Java file, before any class definitions.

Using * imports all classes in a package but does not import sub-packages.

Examples

This imports only the Scanner class from the java.util package.

Java

import java.util.Scanner;

This imports all classes from the java.util package, like Scanner, ArrayList, etc.

Java

import java.util.*;

This imports the static constant PI from the Math class, so you can use PI directly.

Java

import static java.lang.Math.PI;

Sample Program

This program uses the Scanner class to read user input. The import statement lets us use Scanner without writing java.util.Scanner every time.

Java

import java.util.Scanner;

public class ImportExample {
    public static void main(String[] args) {
        Scanner scanner = new Scanner(System.in);
        System.out.print("Enter your name: ");
        String name = scanner.nextLine();
        System.out.println("Hello, " + name + "!");
        scanner.close();
    }
}

Important Notes

Import statements do not import code automatically; they just let you use names without full paths.

If you forget to import a class, Java will show an error saying it cannot find the symbol.

You can also use fully qualified names without import, but it makes code longer and harder to read.

Summary

Import statements help you use classes from other packages easily.

Place import statements at the top of your Java file.

You can import single classes or all classes from a package using *.

Practice

1. What is the main purpose of an import statement in Java?

easy

A. To allow the use of classes from other packages without full package names

B. To declare a new package for the current class

C. To create a new class in the program

D. To start the main method of the program

Solution

1. Step 1: Understand the role of import statements

   Import statements let you use classes from other packages without writing their full package names every time.

2. Step 2: Differentiate from other Java keywords

   Import does not declare packages, create classes, or start methods; it only helps with class usage.

3. Final Answer:

   To allow the use of classes from other packages without full package names -> Option A

4. Quick Check:

   Import = Use classes easily [OK]

Hint: Import lets you use classes without full package names [OK]

Common Mistakes:

• Confusing import with package declaration
• Thinking import creates classes
• Assuming import runs code

2. Which of the following is the correct syntax to import all classes from the package java.util?

easy

A. import java.util.all;

B. import java.util;

C. import * from java.util;

D. import java.util.*;

Solution

1. Step 1: Recall the syntax for importing all classes

   To import all classes from a package, use the asterisk (*) after the package name with a semicolon.

2. Step 2: Check each option's syntax

   Only import java.util.*; is correct. Others miss the asterisk or use wrong keywords.

3. Final Answer:

   import java.util.*; -> Option D

4. Quick Check:

   Use * to import all classes [OK]

Hint: Use * after package name to import all classes [OK]

Common Mistakes:

• Omitting the asterisk (*) when importing all classes
• Missing semicolon at the end
• Using incorrect keywords like 'all' or 'from'

3. What will be the output of the following code?

import java.util.ArrayList;
public class Test {
  public static void main(String[] args) {
    ArrayList<String> list = new ArrayList<>();
    list.add("Hello");
    list.add("World");
    System.out.println(list.get(1));
  }
}

medium

A. ArrayList

B. Hello

C. World

D. Compilation error

Solution

1. Step 1: Understand the import and list usage

   The code imports ArrayList correctly and creates a list with "Hello" at index 0 and "World" at index 1.

2. Step 2: Check the printed element

   list.get(1) accesses the second element, which is "World".

3. Final Answer:

   World -> Option C

4. Quick Check:

   list.get(1) = World [OK]

Hint: Index 1 means second element in list [OK]

Common Mistakes:

• Confusing index 0 and 1
• Assuming import causes error
• Thinking output is class name

4. Identify the error in the following code snippet:

import java.util.List;
public class Demo {
  public static void main(String[] args) {
    List<String> items = new ArrayList<>();
  }
}

medium

A. Missing semicolon after import statement

B. ArrayList is not imported

C. List cannot be used without initialization

D. No error, code is correct

Solution

1. Step 1: Check import statements

   The code imports List but does not import ArrayList, which is used in the code.

2. Step 2: Identify missing import causing error

   ArrayList must be imported from java.util to be used; missing import causes compilation error.

3. Final Answer:

   ArrayList is not imported -> Option B

4. Quick Check:

   Missing import for ArrayList causes error [OK]

Hint: Import all classes you use explicitly [OK]

Common Mistakes:

• Forgetting semicolon after import
• Assuming List needs initialization differently
• Ignoring missing imports for used classes

5. You want to use both java.util.Date and java.sql.Date in the same Java file. How should you import them to avoid confusion?

hard

A. import java.util.Date;
// Use fully qualified name for java.sql.Date in code

B. import java.util.*;
import java.sql.*;

C. import java.util.Date;
import java.sql.Date;

D. import java.util.*;
import java.sql.Date;

Solution

1. Step 1: Understand class name conflict

   Both packages have a class named Date, so importing both directly causes ambiguity.

2. Step 2: Use import for one and full name for the other

   Import one Date class and use the full package name for the other to avoid confusion.

3. Final Answer:

   import java.util.Date; // Use fully qualified name for java.sql.Date in code -> Option A

4. Quick Check:

   Import one Date, fully qualify the other [OK]

Hint: Import one class, fully qualify the other to avoid name clash [OK]

Common Mistakes:

• Importing both classes directly causing ambiguity
• Using wildcard imports causing confusion
• Not using fully qualified names when needed