The jMonkeyEngine3 SDK based on netbeans
Clone or download
Latest commit 3feca90 Dec 1, 2018
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
BasicGameTemplate Fix source version Sep 21, 2016
JME3TestsTemplate Add proper `assets` folder for the tests because the build fails othe… Mar 20, 2017
JME3TestsTemplateAndroid Proguard Exception for NativeVorbisFile (https://hub.jmonkeyengine.or… Jan 8, 2018
ant-jme sdk: change javac source / target to 1.6 Aug 9, 2015
ant-lib - fix wiki download ant scripts Jan 28, 2015
branding GLSL Support Round 1: Syntax Highlighting (#156) Jan 29, 2018
debscripts move sdk to trunk Mar 14, 2011
docs Small Documentation Addition: Corelibs vs Optlibs Mar 20, 2017
gradle Upgrade Gradle Version from 2.11 to 4.1, so it's newer and consistent… Jan 13, 2018
harness-override Minor spelling/explaining and formatting fixes Mar 12, 2016
jdks Upgraded Download JDKs so it works again (had to upgrade the jdk vers… Mar 5, 2018
jme3-android Update all project properties to 3.2.0 (so they don't show as changed… Jan 29, 2018
jme3-angelfont Update the genfiles Jan 29, 2018
jme3-assetpack-support Update the genfiles Jan 29, 2018
jme3-blender Update the genfiles Jan 29, 2018
jme3-cinematics Update all project properties to 3.2.0 (so they don't show as changed… Jan 29, 2018
jme3-code-check Update all project properties to 3.2.0 (so they don't show as changed… Jan 29, 2018
jme3-codepalette Update all project properties to 3.2.0 (so they don't show as changed… Jan 29, 2018
jme3-core-baselibs Update all project properties to 3.2.0 (so they don't show as changed… Jan 29, 2018
jme3-core-libraries Update all project properties to 3.2.0 (so they don't show as changed… Jan 29, 2018
jme3-core-updatecenters Update all project properties to 3.2.0 (so they don't show as changed… Jan 29, 2018
jme3-core Improved Error Reporting (it was broken probably since I missed commi… Nov 27, 2018
jme3-dark-laf Update all project properties to 3.2.0 (so they don't show as changed… Jan 29, 2018
jme3-desktop-executables Update all project properties to 3.2.0 (so they don't show as changed… Jan 29, 2018
jme3-documentation Update all project properties to 3.2.0 (so they don't show as changed… Jan 29, 2018
jme3-glsl-highlighter GLSL Support Round 1: Syntax Highlighting (#156) Jan 29, 2018
jme3-gui Update the genfiles Jan 29, 2018
jme3-ios Update all project properties to 3.2.0 (so they don't show as changed… Jan 29, 2018
jme3-lwjgl-applet Update all project properties to 3.2.0 (so they don't show as changed… Jan 29, 2018
jme3-materialeditor Fixes #2 - Errors in EditableMatDef now spawn ErrorDialogs and the Fo… Nov 27, 2018
jme3-model-importer Update all project properties to 3.2.0 (so they don't show as changed… Jan 29, 2018
jme3-navmesh-gen Update all project properties to 3.2.0 (so they don't show as changed… Jan 29, 2018
jme3-obfuscate Update all project properties to 3.2.0 (so they don't show as changed… Jan 29, 2018
jme3-ogretools Update all project properties to 3.2.0 (so they don't show as changed… Jan 29, 2018
jme3-ogrexml Update all project properties to 3.2.0 (so they don't show as changed… Jan 29, 2018
jme3-project-baselibs Update all project properties to 3.2.0 (so they don't show as changed… Jan 29, 2018
jme3-project-libraries Update all project properties to 3.2.0 (so they don't show as changed… Jan 29, 2018
jme3-project-testdata Update all project properties to 3.2.0 (so they don't show as changed… Jan 29, 2018
jme3-scenecomposer Fix LightProbe scaling by pressing S not working Nov 27, 2018
jme3-templates Update all project properties to 3.2.0 (so they don't show as changed… Jan 29, 2018
jme3-terrain-editor Actually fix #162 (#168) Aug 9, 2018
jme3-tests-template Update all project properties to 3.2.0 (so they don't show as changed… Jan 29, 2018
jme3-texture-editor Update all project properties to 3.2.0 (so they don't show as changed… Jan 29, 2018
jme3-vehicle-creator Update all project properties to 3.2.0 (so they don't show as changed… Jan 29, 2018
jme3-wavefront Update all project properties to 3.2.0 (so they don't show as changed… Jan 29, 2018
jme3-welcome-screen Update all project properties to 3.2.0 (so they don't show as changed… Jan 29, 2018
lib Fixes #61, Maybe Fixes #53 and others: Re-Added Missing JBullet Runti… Apr 24, 2016
nbi Fixed a regression with a installer fix: Use Java 7 in the Installer … Dec 1, 2018
nbproject Update the genfiles Jan 29, 2018
patches Fixes only work when you don't forget to commit half of them Dec 25, 2017
resources Changed the About Screen to use less Scrollbars and added change inst… Mar 21, 2016
.gitignore iOS: Added a way to simplify the depedency-download in order to build… Aug 22, 2016
.travis.yml Move the JDK Building into the pre-deployment so it's only done for r… Aug 9, 2018
build.gradle Fix the Gradle Build (HTTP 301 Redirects weren't supported) Nov 27, 2018
build.xml Build: Separated Mac OSX and Platform Independant into a third build … Feb 19, 2017
build_engine.sh Fix build_engine.sh: The Engine GIT Tags are "v3.2.0-stable", whereas… Jan 11, 2018
fix_engine.sh Fixes only work when you don't forget to commit half of them Dec 25, 2017
gradle.properties Upgrade official SDK Version to 3.2. (should've happend much earlier) Jan 15, 2018
gradlew Upgrading from Gradle 2.2-1 to 2.11 Mar 9, 2016
gradlew.bat Upgrading from Gradle 2.2-1 to 2.11 Mar 9, 2016
jmonkeyplatform.icns - update SDK OSX icon Jan 21, 2015
jmonkeyplatform.png sdk: use a high resolution icon Aug 9, 2015
license-jme.txt Updating License File Mar 27, 2016
licenses-sdk.txt Fixes #55 Old Installer License Year. Apr 14, 2016
readme.md Initial step towards Engine Version 3.2 Mar 21, 2017
version.gradle Try to fix stable builds: They also carry the nbmVersion as opposed t… May 8, 2016

readme.md

jMonkeyEngine Software Development Kit (SDK) Build Status

Welcome to the repository of the jMonkeyEngine Software Development Kit (SDK). This SDK simplifies developing 3D Applications with the jMonkeyEngine. It contains everything ever needed to develop a full application.

Our SDK (or jmonkeyplatform) is based on the Netbeans IDE but includes additional features like:

  • A Scene Editor (SceneExplorer: Preview your scene, adjust all positions, add Controls and AppStates (WYSIWYG) and then just save the scene)
  • A Material Editor
  • A Filter Editor (combine multiple filters and just load them in-game)
  • Bundled JDK for each platform (so you don't need to install java first)
  • Bundled Blender (so you can start 3d modelling and also use it's import capabilities) and many more!

It is important to know that the SDK is not coupled with the engine itself, so if you have issues which are unrelated to the IDE, report them here. This however also means, that the SDK can have a different pace than the engine (at the time of writing, the SDK is on 3.1.0-stable whereas the engine team is already working on 3.2) but you can nonetheless work on a different engine version than the one which is bundled.

!!! Note: You are currently watching the master branch which is the active development for JMonkeyEngine 3.2. For the current release candidate, see the v3.1 branch! !!!

Getting Started / Downloading the SDK

Just have a look at our releases section. There you can download the version you desire. The SDK will generally follow the convention that it's version number is lined up with the matching engine version plus some suffixes for different SDK releases on the same engine version.

There are multiple files from which you can choose:
You can take the platform agnostic jmonkeyplatform.zip which contains the full SDK able to be run on "any" (X86/x86_64) platform (Windows, Mac OS, Linux) however it lacks the jdk as well as blender.
Thus the prefered download is jmonkeyplatform-windows-x64.exe which essentially is jmonkeyplatform.zip and the correct version of the JDK and Blender (hence the ~250MiB size increase).
If you don't know whether your system is 64 bits (x64) or 32 bits (x86), you can type uname -i on Linux or look into the system informations (right click on Computer->Properties) on Windows.

Note: The Tag stable is refering to 3.0-stable, which is an ancient version. You should not start any new projects based of 3.0 but use 3.1 instead. Also the tag is pointing to the wrong commit since we had to re-upload those files but the repo doesn't really contain any 3.0 commits anymore.

Building the SDK

Building the SDK is an easy process basically, but it depends on what kind of distribution you want to build. You also have to know that the build process changes from time to time, so have a look at the .travis.yml file, or related, you will see how we build our releases then.

Note: Currently, the SDK has to build the engine on it's own, because not all needed dependencies are in mavenCentral/jCenter. Thus you have to call build_engine.sh first on a Linux System, Inside your Windows-Git-Shell or you can manually checkout the jMonkeyEngine repository and then invoke gradlew.bat -PbuildJavaDoc=true install. This will add all jMonkeyEngine Libraries into your local maven "server".

Technically the gradle task buildSdk is the main task which builds the sdk (Invoking ./gradlew buildSdk or gradlew.bat buildSdk on Windows).

If you just want to run the SDK on your machine:
call ./gradlew run (gradlew.bat run), which internally calls buildSdk and then uses ant to run the SDK.

If you want to build the platform agnostic zip:
call ./gradlew buildSdk and then you have the file in dist/jmonkeyplatform.zip

If you want to build the platform installers (like we do):
call ./download-jdks.sh, ./gradlew buildSdk and then ant build-installers You have to install ant for this to work (for linux consult the internet, for mac os look into homebrew). Note that this takes a long time (more than one hour), because a huge amount of data is compressed and such.

If you want to build the platform installers (On Windows -> without having ant):
See above. You can bypass ant by declaring a gradle task, just like it has been done for run. There, the gradle included ant will be used). Alternatively you can launch netbeans in netbeans/, open the SDK as Netbeans Project Collection and select package as: Package as.... Note that you still have to download and unpack the jdks somehow, which is a cumbersome process, which is why it is discouraged to build the installers on Windows (Linux and Mac OS are supported).

If you want to debug the SDK inside an IDE:
See above. You want to open the SDK as Netbeans Project from within Netbeans (you can use the nb in netbeans/) and you can then treat it as regular project with the difference that there are several subproject.

A note about the netbeans/ folder: To save bandwidth buildSdk downloads netbeans once to said folder and uses it over and over again. Even when the download URL is changed (i.e. when you update the netbeans version), you have to delete the netbeans folder and remove it from any cache (Travis!), so it can be reloaded.

Developing/Contributing

First of all, I suggest you to take a look at docs/. Those docs are a loose collection of things I came across during development, but they prevent you from re-doing the same experiences. Other than that, Netbeans Platform is your google keyword for any NB related issues. Basically the only tricky thing is how we handle custom entries in the SceneExplorer. This is called the Netbeans Nodes API and is somewhat unintuitive. Just take a look at the Motion Event Pull Request, which should've been added around March 2016, there you can see what was needed to add MotionEvents to the SDK.

Other than that, we are more than happy to help, even if your addition is incomplete. Make sure you use the Netbeans formatting, obvious variable naming and commented and especially documented code, though. Before you open an issue, make sure that it is not an engine bug, but a real sdk bug. If you are uncertain whether it is a real bug or misuse, you can either open an issue or ask on the hub using the Troubleshooting | jmonkeyplatform category.

Issues when building

Could not find jme3.1.0-stable :
When you occur this issue, you have to go back to the engine build step and see how the engine is called. Technically the engine version is collected out from git tags, or called SNAPSHOT. Then there are cases where this recognition fails. For example when the SDK has a tag but the engine is snapshot. Then take a look at build.gradle in the sdk repo. It contains a field called ext.jmeVersion or something, where you can specify the version.

Could not find jme3-jbullet :
jBullet is not part of jCenter, which means you forgot to build the engine first. See above.