bergerkiller/NoLagg — Issue #14: Packaging issues and version detection.
Author: Diskmaster
Created: 2012-02-13 22:11:55+00:00
State: open

Okay, two issues. One, why is BKCommonLib.jar being named by version in the zip. If people are gonna update, that's gonna cause headaches as then there's multiple copies of the same library in the plugins folder.

Additionally:
15:54:52 [INFO] This server is running CraftBukkit version git-Bukkit-1.1-R4-1-g9228e37 (MC: 1.1) (Implementing API version 1.1-R5-SNAPSHOT)
That's an example of a version string built from the git repo via maven directly (not a jenkins built build).
23:10:20 [INFORMATION] This server is running CraftBukkit version git-Bukkit-1.1-R4-b1938jnks (MC: 1.1) (Implementing API version 1.1-R4)
That's an example of a jenkins build. All jenkins builds have the bnum tag in them.

As a result, both the supporting library and nolagg give:
15:54:53 [WARNING] Plugin 'BKCommonLib' v1.06 is too old to run on CraftBukkit build 9228
15:54:53 [WARNING] Update BKCommonLib to a newer version or look for an older build of CraftBukkit
15:54:53 [WARNING] Plugin 'NoLagg' v1.64 is too old to run on CraftBukkit build 9228
15:54:53 [WARNING] Update NoLagg to a newer version or look for an older build of CraftBukkit

So, add a configurable to the plugins to shut up the warnings?