SDK Maintenance Plan

Darkchaos · April 28, 2016, 9:04pm

The gradle.properties specify these:

# Version number used for plugins, only 3 numbers (e.g. 3.1.3)
jmeVersion = 3.1.0
# Version used for application and settings folder, no spaces!
jmeMainVersion = 3.1
# Version addition pre-alpha-svn, Stable, Beta
jmeVersionTag = SNAPSHOT
# Increment this each time jmeVersionTag changes but jmeVersion stays the same
jmeVersionTagID = 0

whereas the said nbm_revision is specifed in build.gradle like this:

ext.jmeFullVersion = "3.1.0-beta1" //3.1.0-SNAPSHOT
ext.jmeNbmRevision = 0

So I’m somewhat under the impression that VersionTagID and nbmRevision should roughly be the same?
Or maybe changing the VersionTag?

It seems that the WindowTitle etc only care fore jmeFullVersion

Edit: Also I hope it’s possible to use the ant script to create nbm’s?

normen · April 29, 2016, 8:16am

The build script can create NBMs, yeah. Theres the old hudsonXXX targets which were used for creating release versions to upload to the update server.

Momoko_Fan · April 29, 2016, 2:55pm

These are the ant targets:

github.com

jMonkeyEngine/sdk/blob/master/build.xml#L123-L129


<!--creates update center version via hudson build server (update-help-sets, )-->
<target name="hudson-nightly" depends="suite.clean, set-impl-version, suite.nbms, unset-impl-version">
</target>
<!--to be used after release, sets version number sans svn revision-->
<target name="hudson-stable" depends="suite.clean, set-spec-version, suite.nbms, unset-spec-version">
</target>

One creates updates for nightly and another for stable. They are identical except for the version number.
All the versioning stuff is handled here: jmonkeyengine/version.gradle at master · jMonkeyEngine/jmonkeyengine · GitHub
Unfortunately, when taking the SDK out of the engine repo, the SDK parts of version.gradle file were not moved over.

Two things are handled by it:

Generating the Update Center URL to use for the SDK release, e.g.: https://updates.jmonkeyengine.org/stable/3.1/plugins. This depends on whether or not the release is tagged or not.
Generating the NBM Revision which is the third part of the NBM version - it is based on the GIT revision for snapshot releases and its 0 for tagged releases. E.g. 3.1.5123.0 would be a snapshot NBM version, whereas 3.1.0.2 would be an alpha / beta / RC / stable release because the fourth part of the NBM version is used.