Maven Crash Course

Set up Java 18 and the JDK, install Eclipse with m2e for Maven, configure the JDK in Eclipse, then install Tomcat and Maven to build and deploy Maven projects.

Install the latest java by downloading the JDK from Oracle, run the appropriate OS installer (exe or dmg), and update the path variable to verify with java -version.

Install the latest eclipse, launch the installer, and complete setup. Configure eclipse preferences to select the correct java version and compiler version, ensuring the java path matches your system.

Configure your Eclipse web project facets to the correct Java version to avoid errors. Select Java 14 or the appropriate version in project facets for compatibility.

Download the latest apache maven binaries for linux tar.gz or windows/macos zip, extract them, and set the path to run maven commands from the command line.

Build the project using Maven install, which compiles, tests, and packages into a jar in the target directory. Run the jar with java -cp to print hello world.

Maven organizes work into lifecycle phases like process resources, compile, test, and package, each tied to plugin goals; depending on the project, packaging may map to jar or war.

Explore maven coordinates in pom.xml—groupId, artifactId, packaging, version—and how snapshots and releases influence naming and dependency retrieval from the central repository.

Explore how Maven downloads plugins and jars from the central repository at repo.apache.org/maven2, and how groupId, artifactId, and version organize artifacts in the local dot m2 repository and enterprise mirrors.

Build a Java Maven project in Eclipse, implementing data and business layers with in-memory collections. Learn to add dependencies to pom.xml, configure Java versions, build, run, and skip tests.

build a product web application using maven with web, business, and data access layers; implement a product dao and bo, wired by spring, using collections instead of a real database.

Create a product services maven project in Eclipse using the quickstart archetype. Build with Maven install to produce a jar and run the app.

Customize the default maven behavior by configuring the maven compiler plugin in pom.xml to compile with java 1.8, overriding the super pom settings, and update the project to apply changes.

Create the data access layer by defining a product pojo dto with id, name, description, and price, generate getters and setters, and establish a product dao interface and impl.

Implement the product dao impl using a hash map to create and read products by id with no database, preparing for unit tests; update and delete are optional.

Upgrade JUnit in the pom.xml from 3.8.1 to 4.4 by replacing the dependency with the copied maven snippet, then update the project to fetch latest dependencies.

Ensure your JUnit-Jupiter-Engine dependency and the latest version of the Surefire plugin, then download the updated build section from resources to make tests compile and run.

Write and run JUnit tests for the product DAO impl, creating a test class with a @Test method that calls create and read, then asserts not null and expected name.

Build a maven project from the command line by navigating to the Eclipse workspace and ensuring environment variables. Run mvn install to compile classes and tests and run the tests.

Skip unit tests in a maven build by running mvn install -D skipTests, see the build succeed while tests are skipped, and anticipate skipping from Eclipse in the next lecture.

Build the business object layer by implementing the product bo interface and its bo impl, using a static dao to create and find products by id in Maven.

Explore how maven dependency management uses pom.xml coordinates to download dependencies to the local repository, add them to the classpath, and resolve transitive dependencies and scopes for war packaging.

Clean the project with Maven clean to remove previous builds, then install with Maven install to build from scratch and produce a jar in the target directory.

Create a Maven web project in Eclipse using archetype webapp, set group id and artifact id, package as war, then run mvn install to produce product web.war in target folder.

Create two servlets to add and display products as an HTML table, set up the maven project structure and URL mappings, and implement doPost and doGet.

Tomcat 10+ uses the servlet 5.0 api, with packaging moved to jakarta.servlet; update imports to jakarta.servlet and add jakarta.servlet 5.0.2 as a provided dependency.

create a product.html form in the Maven crash course that submits via post to the Create Product servlet, collecting id, name, description, and price.

Create a maven web project in eclipse with source/main/java, add servlet classes and web.xml mappings, and include servlet dependencies in pom.xml; build product.html form for id, name, description, and price.

Learn to build a multi-module Maven project by creating a parent forum file, integrating it with a standalone and web application, and deploying on Apache Tomcat to display product details.

Create a multi-module project by defining a parent pom.xml in the parent folder, set packaging to pom, and declare modules for product services and product web.

Build a multi-module Maven project in one shot by running mvn clean install from the parent directory, revealing Maven's reactor build order and placing artifacts in the local repository.

Add the product services dependency to the product web pom.xml, using groupId com.bhrath.product, artifactId product services, version 1.0, ensuring the same coordinates as the product services pom.

Read request parameters in the create product servlet (id, name, description, price), parse them, and populate a product DTO for the upcoming spring API call to the business object.

Implement a display product details servlet that reads the product id from the request, retrieves the product via the BO, and outputs id, name, description, and price.

Build the web project using maven clean and maven install, then unzip the generated war to inspect index.jsp and web.xml, plus dependencies such as spring, servlet, and product services.

learn to build, run, and test a maven web app by cleaning, compiling to a war, deploying to tomcat, and validating product creation and retrieval through servlets.

Troubleshoot 404 errors by updating Maven projects with the latest Spring versions, deleting the dot m2 repository, and rebuilding to access product.html.

Create and test a multi-module maven project with a user services module implementing a dao backed by an in-memory hashmap and web module with servlets to create and display users.

Resolve the 'cannot access default fields for properties' error by downloading the maven war plugin xml, updating the build section with war plugin 3.3.2, and pasting it into your pom.xml.

Learn to import existing maven projects into the eclipse workspace using the import wizard, selecting existing maven projects, and finishing with pom files for product services and product web.

Import multi-module maven projects into Eclipse by selecting the parent folder; Eclipse detects the parent pom and imports all child projects, enabling you to build the application or individual projects.

Set up a parent POM with a dependency management section to enforce consistent dependency versions across a multi-module project, ensuring child modules inherit versions and avoid overrides.

Learn how to use Maven plugin management in the parent pom.xml to ensure consistent plugin versions and configurations across child projects, such as the Java compiler plugin.

Configure maven profiles to switch environment-specific settings using three configuration files and an application.properties with JDBC URL, username, and password, building the jar for the active profile.

Create a maven project using the archetype for a Java project, set a unique group id and artifact id, then outline dev, test, and production profiles with database settings.

Create three environment-specific configuration files in a new Profiles folder: dev, test, and prod, each with an application.properties containing URL, username, and password for their respective environments.