Skip to content
Sign in
Failed

Changes

Summary

  1. Upgrade Proguard to a version that supports Java 18. (details)
  2. Fix Javadoc error. (details)
  3. Update nexus-staging-maven-plugin to 1.6.13. (details)
  4. [maven-release-plugin] prepare release getdown-1.8.7 (details)
  5. [maven-release-plugin] prepare for next development iteration (details)
  6. Update the CHANGELOG with the shipped changes. (details)
Commit 26d559e5c25dc21736b7df6b345eaec7ed04604d by mdb
Upgrade Proguard to a version that supports Java 18.
For unfortunate reasons, we have to add a separate (build-time)
dependency on proguard-core, code from which proguard-base relies on but
neither includes directly nor expresses as a dependency.
How is it in the year of our lord two thousand and twenty two, we are
still making such basic build errors in our Maven plugins and POM files?
The file was modifiedlauncher/pom.xml (diff)
Commit fda9590d21469d294dd4cd7ff0ead7e3e8e8cbff by mdb
Fix Javadoc error.
The file was modifiedcore/src/main/java/com/threerings/getdown/data/ClassPath.java (diff)
Commit 089761da24eb0d4ba0c8e80f4354fb853a55c02e by mdb
Update nexus-staging-maven-plugin to 1.6.13.
In hopes that it works properly with Java 18. Let's find out!
The file was modifiedpom.xml (diff)
Commit 425e0d0c87c78d122d84ffbc1aa1531f974f8452 by mdb
[maven-release-plugin] prepare release getdown-1.8.7
The file was modifiedpom.xml (diff)
The file was modifiedant/pom.xml (diff)
The file was modifiedlauncher/pom.xml (diff)
The file was modifiedcore/pom.xml (diff)
Commit d41a817b55b77feca824e9776032328e3bfc14d8 by mdb
[maven-release-plugin] prepare for next development iteration
The file was modifiedant/pom.xml (diff)
The file was modifiedlauncher/pom.xml (diff)
The file was modifiedpom.xml (diff)
The file was modifiedcore/pom.xml (diff)
Commit 29437aa993b1f9307347c4e5c985c114a937b00a by mdb
Update the CHANGELOG with the shipped changes.
The file was modifiedCHANGELOG.md (diff)