When creating a multi-module project, a parent project must be created. Maven uses that parent POM as a starting point before it reads the child project’s POM. The ‘child’ module inherits everything, including the groupId and version number. One of the nice things about using an IDE is that it reduces the time it takes to create all the necessary files and folders for a Maven project. Remember, a parent project only has a POM file when you first create it.
- [Instructor] When creating a multi-module project…using Maven, a parent project must first be created.…Let's take a look at creating a parent project,…and let's look specifically at the POM file,…which is the Project Object Model.…Maven uses this parent POM as a starting point…before it reads the child project's POM file.…The child module inherits everything,…including the group ID and version number,…and it uses those two values as part of its coordinates.…One of the nice things about using an IDE,…or an integrated development environment,…is that it reduces the time it takes…to create all the necessary files and folders…for a Maven project.…
Remember, a parent project only has a POM file…when you first create it.…It'll be an XML file, and it'll be called POM dot XML.…Once that file is created,…then we can add modules to this project…and the parent POM file is updated automatically.…Now I'd like to switch to NetBeans…so we can create a parent project…that will have two modules.…Just a quick reminder:…If you're using NetBeans IDE 6.7 and newer,…
Released
9/22/2016- Creating parent project
- Creating submodules
- Building a multi-module project
- Working with different IDEs
- Understanding Maven build lifecycles and build profiles
- Writing plugins
Share this video
Embed this video
Video: Create a parent project