Skip to content

Maven access point for our custom baritone

Notifications You must be signed in to change notification settings

MarvionKirito/maven

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

37 Commits
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Maven Repo

How to update to new version

  1. Make sure your local version of baritone works with altoclef (check here for a brief guide on how to do this)
  2. Clone this repo
  3. Build the baritone jars
  4. Grab every jar from the build folder (...-dev.jar, ...-api.jar, etc.) and copy it to the maven-scripts folder
  5. Run maven-unix.sh or maven-windows.bat in the folder. Version is the same as what you see on the jar file (ex. baritone-1.18.2 is version 1.18.2), Head Version is the version of the baritone update (ex. baritone for 1.18.2 is version 1.8.4
  6. Some new folders should be generated in the maven-scripts folder. Copy these folders into the cabaletta folder (make sure they match the folder structure. For example, the new baritone-api-fabric folder should be copied to the exact same location of the old baritone-api-fabric folder so their contents get merged.)
  7. 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.xml and confirm that the version number has been updated to your new version.
  8. Delete the old baritone jar files from the maven-scripts folder
  9. Push the cabaletta folder
  10. You're done!
  11. Check the github pages setting to verify that the site is updated image
  12. After the new github page is live, you can update your altoclef build.gradle to use the new baritone from maven (check this line)

About

Maven access point for our custom baritone

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

  • Batchfile 50.1%
  • Shell 49.9%