Note that the creation of a Module Suite is only necessary if you want to upload your plugin to the contribution update center.

Using jMonkeyEngine SDK for development

  • Install the “Netbeans Plugin Development and “NetBeans API Documentation plugins via Tools→Plugins

  • Create a new “Module Suite project (can be any name, this will be your local “collection of plugins that you create)

  • If no platform is listed, add one by selecting the SDK application folder

    • Mac users have to right-click the jmonkeyplatform application and select “show contents and then select the jmonkeyplatform folder under Contents/Resources/

  • Open the suite, right-click the “Modules folder and select “Add new..

  • For “Project Name enter an all-lowercase name without spaces like my-library

  • Make sure the “Project Location is inside the module suite folder and press “Next

  • Enter the base java package for your plugin in “Code Name Base like com.mycompany.plugins.mylibrary

  • Enter a “Module Display Name for your plugin like “My Library

  • Press Finish

  • To use core SDK or jME3 functions, add “SDK Core and “SDK Engine via “Module Properties→Library→Add Dependency

  • Write your plugin (e.g. create a new editor or wrap a jar library)

jMonkeyEngine SDK Contributions Update Center

If you want your plugin to appear in the “jMonkeyEngine SDK Contributions Update Center so users can download, install and update it easily via the plugin manager, you can host your plugin in the contributions update center svn repository. The contributions update center is based on a googlecode project for contributed plugins which will be automatically compiled, version-labeled and added to the contributions update center like the core jMonkeyEngine SDK plugins.

Effectively its one large module suite with multiple modules which each represent one plugin, extension library.

Adding your plugin to the repository

To add your plugin to the repository, do the following:

  • Make sure the plugin is part of a “Module Suite and that its located in the folder of the suite (this saves you from problems with the svn and local version not being configured the same)

  • In “Module Properties→Sources

    • Set the “Source Level to 1.5 if possible (jMonkeyEngine SDK is compatible to Java 1.5)

  • In “Module Properties→API Versioning

    • Set a specification version for your plugin (like 0.8.1)

    • Set the “implementation version to “0 and select “append implementation versions automatically

  • In “Module Properties→Display

    • Enter a purposeful description of your plugin and one of the following categories:

      • For a library plugin: “jME3 - Library

      • For a SDK plugin: “jME3 - SDK Plugin

      • For a model loader plugin: “jME3 - Loader

  • In “Module Properties→Build→Packaging

    • Add your name

    • Add a link to your forum post / home page relating to the plugin

    • Add a license, you can use ../license-jme.txt to insert the default jME BSD license or use a text file you store in the project folder

  • Ask the managers or developers for access to the gc project

  • Commit only the module project to trunk:

    • Right click the Module Project and select “Versioning → Import into Subversion Repository

    • Enter https://jmonkeyplatform-contributions.googlecode.com/svn/trunk in the URL field

    • Enter your googlecode username and commit password (different than login pass, you can find your password here!) and press “Next

    • Check that the “Repository Folder is trunk/mypluginfolder and enter an import message

    • Press “Finish

And thats it, from now on each time you commit changes to your module it will be built and added to the contributions center automatically and the version number will be extended by the svn revision number (e.g. 0.8.1.1234)

Building wrapped library jar files on the server

You can just build your library locally and update and commit the jar file and javadoc/sources zip files to the release/libs folder of your plugin in the contrib repo. The users plugins will automatically be updated with the new jar files. You can however also build the library project on the server.

As normally only the module project is being built on the server, any projects that create the actual jar files for library plugins (“normal projects from the SDK/NetBeans) have to be built from the module build file. To do that simply add the following ant targets to the module build file (adapt to your project file and folder names):

<target name="init" depends="basic-init,files-init,build-init,-javac-init,-build-subproject"/>
<target name="-build-subproject">
    <ant dir="./AI" inheritall="false" inheritrefs="false" target="clean"/>
    <ant dir="./AI" inheritall="false" inheritrefs="false" target="jar"/>
    <ant dir="./AI" inheritall="false" inheritrefs="false" target="javadoc"/>
    <zip basedir="./AI/dist/javadoc" file="release/libs/jME3-ai-javadoc.zip"/>
    <zip basedir="./AI/src" file="release/libs/jME3-ai-sources.zip"/>
    <copy file="./AI/dist/jME3-ai.jar" todir="release/libs"/>
</target>

Note that for the module version number to increase automatically on a commit to the library project, the library project has to be a subfolder of the main module project.