- Make sure your local version of baritone works with altoclef (check here for a brief guide on how to do this)
- Clone this repo
- Build the baritone jars
- Grab every jar from the build folder (
...-dev.jar,...-api.jar, etc.) and copy it to themaven-scriptsfolder - Run
maven-unix.shormaven-windows.batin the folder. Version is the same as what you see on the jar file (ex.baritone-1.18.2is version1.18.2), Head Version is the version of the baritone update (ex. baritone for 1.18.2 is version 1.8.4 - Some new folders should be generated in the
maven-scriptsfolder. Copy these folders into thecabalettafolder (make sure they match the folder structure. For example, the newbaritone-api-fabricfolder should be copied to the exact same location of the oldbaritone-api-fabricfolder so their contents get merged.) - You should now have an updated version of the repo that needs to be pushed. To confirm, do a
git diff cabaletta/baritone/maven-metadata-local.xmland confirm that the version number has been updated to your new version. - Delete the old baritone jar files from the
maven-scriptsfolder - Push the
cabalettafolder - You're done!
- Check the github pages setting to verify that the site is updated
- After the new github page is live, you can update your
altoclefbuild.gradleto use the new baritone from maven (check this line)
-
Notifications
You must be signed in to change notification settings - Fork 6
gaucho-matrero/maven
Folders and files
| Name | Name | Last commit message | Last commit date | |
|---|---|---|---|---|
Repository files navigation
About
Maven access point for our custom baritone
Resources
Stars
Watchers
Forks
Releases
No releases published
Packages 0
No packages published