[build] Fixup maven publishing (#8753)

This primarily fixes up the bazel publishing to match the gradle
publishing again, as some new libraries were added but not hooked up to
the maven publishing.

During the process, I noticed that the 3rd party libraries (googletest,
catch2, and imgui_suite) were still getting published on the old
`edu.wpi` namespace. I tried to clean up all the other references to
that that I could. Note: opencv and libssh are handled outside
`allwpilib` so they need to be updated separately.
This commit is contained in:
PJ Reiniger
2026-04-11 16:52:43 -04:00
committed by GitHub
parent 9ea63c7fd6
commit c6f54e963c
21 changed files with 72 additions and 37 deletions

View File

@@ -28,7 +28,7 @@ To build an extension for use in a robot project, you'll need to build with Grad
# Using a custom extension
After setting up a build.gradle file for a custom extension, follow the guides to build and publish your own local build of allwpilib. Once you've published a local build, follow the instructions in [DevelopmentBuilds.md](/DevelopmentBuilds.md) to use the locally published build in a robot project. Then, place this line your robot project's build.gradle file:
```groovy
wpi.sim.addDep("Custom Sim Extension", "edu.wpi.first.halsim", "pluginName")
wpi.sim.addDep("Custom Sim Extension", "org.wpilib.halsim", "pluginName")
```
where `Custom Sim Extension` is the name of the extension shown by VS Code and `pluginName` is the same as `pluginName` declared in the build.gradle file for the simulation extension.