How to connect your library to another project?

There are several main methods depending on the build system:

Using a dependency management system (Maven, Gradle): Creating the library as a separate artifact (JAR, AAR) and publishing it to a repository (local, corporate, public). Then, in the target project, a dependency is added pointing to this artifact.

Example for Maven pom.xml:
```
<dependency>
    <groupId>com.your.library</groupId>
    <artifactId>your-library-name</artifactId>
    <version>1.0.0</version>
</dependency>
```
Example for Gradle build.gradle:
```
implementation 'com.your.library:your-library-name:1.0.0'
```
Including source files of the library directly: Copying or symlinking the source files (.java) of the library into the source directory of the target project. This method is not recommended for complex projects and libraries.
Adding the compiled JAR file to the classpath: Adding the compiled JAR file of the library to the classpath of the target project. This can be done manually during compilation and execution or through IDE settings.

Example of adding a JAR to the classpath when running from the command line:
```
java -cp your-library.jar:your-app.jar com.your.app.Main
```
Example of adding a JAR to the classpath in IntelliJ IDEA (Module Settings -> Dependencies -> + -> JARs or directories).

The most commonly used and recommended method for modern Java projects is using dependency management systems (Maven or Gradle). This ensures automatic resolution of transitive dependencies and simplifies library version updates.