Files and history
Manage plugin dependencies
Some Paper plugins depend on other plugins or Java libraries. Name the dependencies during planning, then check that the code, build configuration, metadata, and deployment use compatible versions.
Identify the kind of dependency
Section titled “Identify the kind of dependency”| Kind | How it is represented | What to check |
|---|---|---|
| Another Paper plugin | An uploaded dependency JAR and appropriate plugin metadata declarations. | Compatible version, required/optional status, and runtime presence. |
| A Java runtime library | Project build configuration and, where used, the libraries declaration in plugin.yml. |
Correct package coordinates and compatible library version. |
The dependency list can display uploaded plugins and Runtime libraries separately. A declared library is not the same as an uploaded plugin JAR.
Tell Buildryn about the integration
Section titled “Tell Buildryn about the integration”Include the dependency’s name, version, purpose, and required behavior when it is absent:
Integrate this feature with <plugin name and version>.The integration is <required / optional>.When unavailable, <disable this feature / report a clear startup error>.Explain the metadata declarations and test setup.Upload the required plugin artifact and inspect the generated configuration. Mentioning the dependency in chat leaves that upload step to you.
Upload a dependency JAR
Section titled “Upload a dependency JAR”- Open Dependencies in the Paper project.
- Choose Add dependency.
- Select the compatible
.jarfile. - Choose Upload.
- Check the detected plugin name and version in the dependency list.
- Build and deploy again so the changed dependency setup is included in testing.
The application validates JAR content and plugin metadata. Upload a valid supported plugin archive; renaming a file to .jar does not convert its contents.
Dependency storage is limited according to the owner’s artifact-size allowance. If an upload is rejected for capacity, remove unnecessary dependencies or choose a suitable plan.
Replace a dependency
Section titled “Replace a dependency”- Open the dependency’s actions and choose Replace.
- Select the new JAR for the same plugin.
- Confirm replacement.
- Check the detected version.
- Build and test the integration again.
Replacement requires matching plugin identity. To switch to a different dependency, remove the old one and add the new one, then update the code and metadata to use it.
Download or remove
Section titled “Download or remove”Use Download to retrieve a stored dependency JAR. Use Delete to remove one that is no longer required.
Before deletion, check whether source or metadata still requires it. Ask Buildryn to remove or adapt the integration, review the change, then rebuild. Removing the stored JAR alone does not rewrite your code or plugin.yml.
Deployment checks
Section titled “Deployment checks”Before launching a Paper deployment, Buildryn checks required dependencies and can warn about missing optional ones. Resolve a missing required dependency before deployment. An optional warning still deserves checking if the feature you want to test depends on that integration.
On the running server, inspect startup logs for dependency loading and integration errors. Test both the ordinary feature and the integration-specific behavior.
Common problems
Section titled “Common problems”| Problem | Next step |
|---|---|
| Invalid JAR or missing metadata | Obtain the actual plugin artifact rather than a source archive or unrelated Java library. |
| Replacement name mismatch | Replace with the same plugin identity, or add a different dependency separately. |
| Required dependency missing | Upload it and check the generated dependency declaration. |
| Integration compiles but fails at startup | Check the runtime version and full startup error. |
| Storage limit exceeded | Remove unused JARs and review the owner’s plan limit. |
Use security reports for known vulnerabilities in scanned Java components. A dependency report does not replace compatibility testing.