Skip to main content

Maven Repositories (local, central, global)

Maven relies on repositories to manage dependencies, plugins, and other artifacts required for a project. There are typically three types of repositories in Maven: local, central, and remote/global repositories.

Local Repository:

Location: The local repository is located on your local development machine. By default, it's in the .m2 directory within your user home directory (e.g., C:\Users\<username>\.m2\repository on Windows or /Users/<username>/.m2/repository on macOS and Linux).

Purpose: The local repository is used to store artifacts (JARs, POMs, and other files) that your machine has downloaded or built during previous Maven builds. These artifacts are specific to your local development environment.

Benefits: Using a local repository improves build performance since it caches dependencies locally, reducing the need to download them repeatedly. It also ensures reproducibility by maintaining a local copy of dependencies.


Central Repository:

Location: The central repository is a public repository maintained by the Apache Maven community. It's not on your local machine but is accessed over the internet.

Purpose: The central repository contains a vast collection of open-source libraries, plugins, and dependencies that are commonly used in Java development. When you specify dependencies in your project's POM, Maven checks the central repository to download these dependencies.

Benefits: Access to a central repository simplifies dependency management, as it contains a wide range of commonly used artifacts. It reduces the need to manually download and manage JAR files from different sources.


Remote or Global Repository:

Location: Remote repositories are repositories hosted externally, often within an organization, or on remote servers accessible over the internet.

Purpose: Remote repositories are used to store and share artifacts within a team or organization. They can include third-party dependencies, internal libraries, and proprietary artifacts.

Benefits: Setting up remote repositories allows teams to share and manage internal dependencies efficiently. Organizations can control and secure access to proprietary artifacts.


Configuring Repositories:

You can configure repositories in your project's pom.xml file within the <repositories> and <pluginRepositories> sections. Here's an example:


<repositories>

    <repository>

        <id>central</id>

        <url>https://repo.maven.apache.org/maven2</url>

    </repository>

    <repository>

        <id>my-internal-repo</id>

        <url>https://mycompany.com/maven-repo</url>

    </repository>

</repositories>


<pluginRepositories>

    <!-- Plugin repositories, if different from dependencies -->

</pluginRepositories>


In this example, two repositories are configured: the central repository for public dependencies and my-internal-repo for internal artifacts hosted within your organization.


By configuring repositories, you specify where Maven should look for dependencies and plugins during the build process. This allows Maven to resolve and download the required artifacts from the appropriate repositories.

Comments

Popular posts from this blog

Maven Create and Build Artifacts

In Maven, you can create and build artifacts using the package phase of the build lifecycle. The package phase is responsible for taking the compiled code and other project resources and packaging them into a distributable format, such as a JAR (Java Archive), WAR (Web Application Archive), or other custom formats. Here are the steps to create and build artifacts using Maven: Configure the Build Output: In your project's pom.xml file, you need to configure the output of the build. This includes specifying the type of artifact you want to create (e.g., JAR, WAR) and any additional resources to include. You do this in the <build> section of your pom.xml: <build>     <finalName>my-artifact</finalName> <!-- Name of the artifact without the extension -->     <plugins>         <!-- Plugin configurations for creating the artifact -->         <!-- For example, maven-jar-plugin or maven-war-plugin -->     </plugins> </build> Depend

Example of Maven project that interacts with a MySQL database and includes testing

Example Maven project that interacts with a MySQL database and includes testing To install Java, MySQL, Maven, and write a Java program to fetch table data, execute, and create a JAR file using Maven on Ubuntu, you can follow these steps: Step 1: Install Java You can install Java using the following commands: sudo apt update sudo apt install default-jre sudo apt install default-jdk Verify the installation by running: java -version Step 2: Install MySQL You can install MySQL using the following commands: sudo apt update sudo apt install mysql-server During the installation, you'll be prompted to set a root password for MySQL or you can set password at latter stage using following steps.  sudo mysql ALTER USER 'root'@'localhost' IDENTIFIED WITH mysql_native_password BY 'password'; exit Step 3: Install Maven You can install Maven using the following commands: sudo apt update sudo apt install maven Verify the installation by running: mvn -version Step 4: Create

Experiment No. 5 Title: Applying CI/CD Principles to Web Development Using Jenkins, Git, and Local HTTP Server

  Experiment No. 5 Title: Applying CI/CD Principles to Web Development Using Jenkins, Git, and Local HTTP Server  Objective: The objective of this experiment is to set up a CI/CD pipeline for a web development project using Jenkins, Git, and webhooks, without the need for a Jenkinsfile. You will learn how to automatically build and deploy a web application to a local HTTP server whenever changes are pushed to the Git repository, using Jenkins' "Execute Shell" build step. Introduction: Continuous Integration and Continuous Deployment (CI/CD) is a critical practice in modern software development, allowing teams to automate the building, testing, and deployment of applications. This process ensures that software updates are consistently and reliably delivered to end-users, leading to improved development efficiency and product quality. In this context, this introduction sets the stage for an exploration of how to apply CI/CD principles specifically to web development using J