IBM Worklight v5.0.5 > Develop IBM Worklight applications > Development guidelines for mobile environments

Integrate with source control systems

There are two types of files and folders in a standard IBM Worklight project hierarchy:

• Custom source code files and some source code files provided in the device runtime libraries.

  You should commit these files to a version control system.

• Files generated from your web source code and some JavaScript files provided with the IBM Worklight platform (such as wlclient.js). These files are added to the file system every build. These files are bolded in the list below.

  These files should not be committed to a version control system.

IBM Worklight project hierarchy...

MyProject
adapters
apps
    myApp
        android
            css
            images
            js
            native
                assets
                www
                wlclient.properties
                other user files
            bin
            gen
            nativeResources
                res
            libs
            res
            src
            AndroidManifest.xml
            default.properties
        blackberry
            css
            images
            js
            native
            ext
            www
            config.xml
            icon.png
            splash.png
            common
        ipad / iphone
            css
            images
            js
            native
                build
                Classes
                Cordova.framework
                <application-name>.xcodeproj
                Plugins
                Resources
                WorklightSDK
                www
                Entitlements.plist
                main.m
                Cordova.plist
                <application-name>_Prefix.pch
                <application-name>-Info.plist
                README.txt
                worklight.plist
            nativeResources
                Resources
            package
dojo
server
    conf
    java
    lib

Add the bold files and folders to the ignore list in your source control system.

For example, for Subversion...

1. Using the Tortoise extension for Subversion, right-click each file or folder that is to be ignored and add it to the ignore list.

2. Go up one level in the file system and commit the change to the SVN repository. The changes take effect from now on for every developer who updates the code.

Parent Development guidelines for mobile environments

---

+

Search Tips   |   Advanced Search