Catch a Java mismatch before the restart
PluginGuardReleased- Starting problem
- A plugin update is now compiled for a newer Java than your server runs. The JVM would refuse to load it, and the cause is buried in a long startup log.
- What the plugin decides
- PluginGuard reads the class-file version inside every jar in plugins/ and compares it with the Java the server reports. It never executes or changes a jar.
- Result
- The scan reports a critical JAVA_VERSION_TOO_NEW finding for that plugin, and the fix list says to run a newer Java or use a build made for yours.
- Limits to keep in mind
- PluginGuard runs inside a server that is already up. Scan after copying the jar and before you restart; it cannot help a server that no longer boots.
Example flowIllustration, not live data
- Copy the new jar into plugins/
- Run /pluginguard scan
- Critical finding: Java version too new