Azhrei wrote:This can be done without too much trouble. If Rumble right-clicks on the build.xml and builds the project, the output will be a JAR file with the version number embedded in it. He'll have to edit the file containing that number (I think it's build.number?) prior to the build so that it won't get incremented to b57.
Also, I put some code in a few releases back that allowed a command line option to force a particular version, but it hasn't been merged. It was a semi-complicated scheme that allowed the deployed JAR to accept a version number from the command line and turn on additional debugging output. So a developer could make 1.3.b57 look like 1.3.b56, for example, for the purpose of testing data passing over the network or loading/saving of campaign data. But as I said, it's not there in b56.
Ah, okay, I'll give that a shot.