Ulises LicensesUlises Licenses
FeaturesPricingAPIChangelogs
Discord
Dashboard
  • Overview
  • Installation
  • Plugin Integration
  • Complete Example
  • API Methods
  • Connection Management
  • Auto-Update
  • Best Practices
  1. Docs
  2. /
  3. Installation
Section 01 / Build Configuration

Adding UlisesLib to Project Dependencies

UlisesLib.jar is distributed from your dashboard, not a public package registry. Once downloaded, add it as a local dependency and bundle it into your plugin's final jar so it's present at runtime on the server.

Gradle DSL (build.gradle)
build.gradle
Groovy
1plugins {2    id 'com.github.johnrengelman.shadow' version '8.1.1'3}4 5dependencies {6    implementation files('libs/UlisesLib.jar')7}
Maven POM (pom.xml)
pom.xml
XML
1<dependency>2    <groupId>pro.ulises.licenses</groupId>3    <artifactId>ulises-lib</artifactId>4    <version>2.0</version>5    <scope>system</scope>6    <systemPath>${project.basedir}/libs/UlisesLib.jar</systemPath>7</dependency>
NOTICE: Shade and Relocate Bytecode into Binary Artifact
Place the jar in your project's libs/ folder first. Bundling it with the Shadow plugin (Gradle) or maven-shade-plugin (Maven) packages UlisesLib into your compiled plugin jar, since PaperMC won't resolve it from the server's classpath otherwise.
PREVIOUS MODULE← OverviewNEXT MODULEPlugin Integration →

Built by Ulises - Citymoon Dynamics

Ulises LicensesUlises Licenses

© 2025-2030 Citymoon Dynamics (citymoon.org). All rights reserved.

TermsPrivacyDiscord