Apache Maven Beginner to Guru - Maven Clean Plug-in

The video tutorial provides an in-depth look at the Maven clean plugin, explaining its role in the build lifecycle and how it helps manage the target directory. It highlights issues with old artifacts during refactoring and demonstrates how to clean the build directory. The tutorial also covers configuring Maven for automatic cleaning during the build process, testing the configuration, and the benefits of this setup.

What is the primary purpose of running the package goal in Maven?

• To install the project

• To deploy the project

• To generate a JAR file

• To clean the target directory

Why is it important to clean the target directory before building a project?

• To avoid unpredictable results from old artifacts

• To increase the size of the JAR file

• To ensure all classes are compiled twice

• To reduce build time

What phase should the clean goal be hooked into for automatic cleaning?

• Initialize phase

• Compile phase

• Deploy phase

• Package phase

What is the benefit of integrating the clean goal into the build lifecycle?

• It reduces the number of plugins needed

• It ensures a fresh start for each build

• It speeds up the build process

• It eliminates the need for a POM file

What happens to the target directory during the automatic cleaning process?

• It is archived

• It is ignored

• It is moved to a backup location

• It is deleted and recreated

How many phases are there in the default Maven build lifecycle?

• 10

• 15

• 27

• 5

What is a common command line practice when building with Maven?

• Running Maven compile

• Running Maven clean package

• Running only the package goal

• Running Maven deploy