What is Maven?

• 2002 – The beginning of the Maven project
• 2004 – Release of Maven 1.0
• 2005 – Release of Maven 2.0, which introduced significant changes to the architecture
• 2010 – Maven 3.0 release, focusing on performance and extensibility
• Subsequent versions (3.1, 3.2, 3.3, etc.) introduced further improvements and new features

1. Convention over configuration – Maven uses standard conventions for project structure and naming, which reduces the need for configuration.
2. Declarative dependency management – Allows you to easily define and manage project dependencies.
3. Repositories – Central and local repositories facilitate the management of libraries and dependencies.
4. Project lifecycle – Maven defines a standard project lifecycle, including phases such as compilation, testing, packaging and deployment.
5. Plug-ins – Extensible architecture allows you to add new functionality through plug-ins.
6. Integration with IDEs – Maven is well integrated with popular development environments.

projekt-maven/ 
│ 
├── src/ 
│   ├── main/ 
│   │   ├── java/        # Kod źródłowy Java 
│   │   └── resources/   # Zasoby aplikacji 
│   └── test/ 
│       ├── java/        # Kod testów jednostkowych 
│       └── resources/   # Zasoby testowe 
│ 
├── target/              # Skompilowane pliki i artefakty 
│ 
└── pom.xml              # Plik konfiguracyjny projektu 

1. validate – Validate the design
2. compile – Compilation of source code
3. test – Running the tests
4. package – Packaging of compiled code
5. verify – Verification of the package
6. install – Installing a package in the local repository
7. deploy – Copying a package to a remote repository

Each of these phases is executed sequentially and can be run with the appropriate Maven commands.

<dependencies> 
  <dependency> 
    <groupId>junit</groupId> 
    <artifactId>junit</artifactId> 
    <version>4.11</version> 
    <scope>test</scope> 
  </dependency> 
</dependencies> 

• maven-compiler-plugin – to compile Java code
• maven-surefire-plugin – to run unit tests
• maven-jar-plugin – to create JAR files
• maven-war-plugin – to create WAR files for web applications
• maven-deploy-plugin – to deploy artifacts

These plug-ins can be configured in the pom.xml file, adapting the build process to the specific needs of the project.

• Ant: Maven offers a more structured approach and better dependency management than Ant.
• Gradle: Gradle is a newer tool that offers more flexibility and performance, but Maven remains popular for its simplicity and broad support.

1. Keep an up-to-date version of Maven and its plug-ins.
2. Use Maven’s naming conventions and directory structure.
3. Regularly update dependencies to the latest stable versions.
4. Use Maven profiles to manage different configurations (e.g. for dev, test, prod environments).
5. Optimize build time by using parallel execution of tasks.
6. Document your pom.xml file, especially for custom configurations.

Maven, with its simplicity, powerful dependency management features and standardization of the build process, remains one of the most popular tools in the Java ecosystem. Its familiarity is a valuable skill for any Java developer, especially in the context of developing large, complex projects.