Code versioning - Visualizer 7.3

HCL Volt MX Volt MX Forum
1
This thread was migrated from an old forum. It may contain information that are no longer valid. For further assistance, please post a new question or open a support ticket from the Customer Support portal.

Hi Everyone?

Which folders of a Visualizer 7.3 workspace I don't need to add to my Git repository?

For example: do I need to control these folders?

$/jssrc/android/generated/*

Workspace/webapps/*

Workspace/.emulators

Workspace/.cordova/cordova

Can you guys share a gitIgnore that works well?

Thanks in advance!

2

Mine is just jssrc/* for every project.

I put versioning on every project instead of the entire workspace

Regards,

3

Hi,

Thank you for contacting Kony.

All the above files which you have mentioned are generated files and you can ignore those files. When you create a new project in the Visualizer, the files which are there in the new project are the original files to commit into the Git repository. You can ignore the remaining files.

Please check and let us know if you need any further support.

Thank You,

4

Thank you. did these answers help you resolve your issue? If yes, please click [Select as Best] under the answer that helped you the most. Thanks!

5

Hi Everyone.

Thanks for your help!

6

WorkSpace7/.backup/**

WorkSpace7/.cloud/**

WorkSpace7/.cordova/**

WorkSpace7/.eventshistory/**

WorkSpace7/.exports/**

WorkSpace7/.imports/**

WorkSpace7/.metadata/**

WorkSpace7/.nativebindings/**

WorkSpace7/.userlibs/**

WorkSpace7/.webapps/**

WorkSpace7/HeadlessBuild-Global.properties

WorkSpace7/konyplugins.xml

WorkSpace7/konypluginstate.xml

WorkSpace7/DigiINK7/jssrc/**

WorkSpace7/DigiINK7/services/**

WorkSpace7/.emulators/**

WorkSpace7/webapps/**

WorkSpace7/temp/**

7

Hi,

Please ignore the above files before committing to the version control.

Thank You,

8

Yah thats the reason we have them in git ignore.

9

Visualizer Team has compiled this list for your convenience. Append it to your existing ignore list.

In the workspace directory the follow paths can be added to .gitignore list

  1. .backup
  2. .cloud
  3. .exports
  4. .fp
  5. .imports
  6. .webapps
  7. Project/.webmeta/localfiles.meta-info
  8. .nativebindings
  9. .eventshistory
  10. .metadata ->This metdata folder is maintained by eclipse, which stores projects info and workspace last state etc..
  11. _ios -> This contains, iOS Xcode and simulator details which are fetched during configuration of iOS emualtors/devices.
  12. webapps -> This contains some intermediate files related to build/fp.
  13. temp -> This contains all temp files that are created during build/fp.

10

Thanks Everyone! It helped a lot!

11

Versioning an entire workspace is NOT a reasonable solution if you have more than one project. You could of course have multiple workspaces and only one project per workspace, but then switching projects will require restarting Visualizer. The sensible thing is to ignore anything that can can cause merging conflicts BUT but is not a source file -such as temporary files- AND can also be auto-generated by the build, so that a newly cloned project won't break. If you'd like a comprehensive answer plus the tips and tricks I use on a daily basis, and regular updates on how this evolves with newer versions of Visualizer please go here:

https://goo.gl/jhGBTy

If you're just looking for a quick .gitignore, here it is:

/jssrc/* !/resources/customlibs/jsSrc

Starting with Visualizer 8.0 the Ant Contrib Jar used for the build process will

be regenerated when the build is fired. If you’re using Visualizer 7.x then comment out

this line. Vis 7.x will not regenerate this jar and ignoring it will break your project.

ant-contrib-0.6.jar

Binaries.

/binaries
*.apk
*.KAR

Starting with Vis 7.3 the /sdkplugin.properties file has been moved to

/resources/customlibs/sdkplugin.properties and can be automatically re-created by Vis

during the build.

resources/customlibs/sdkplugin.properties

The jar’s and zip’s under these directories can be ignored so long as

sdkplugin.properties (See above) is also ignored. The missing sdkplugin.properties will

trigger the regeneration of these jar’s and zip’s during the build.

resources/customlibs/lib/android/
resources/customlibs/lib/tabrcandroid/
resources/customlibs/lib/iphone/
resources/customlibs/lib/ipad/
resources/customlibs/lib/windows10/
resources/customlibs/lib/winphone10/

Other Visualizer auto-generated files.

/.webmeta
middleware.properties
splashscreenproperties.json

Visualizer headless build configuration files

HeadlessBuild.properties
HeadlessBuild-Global.properties

Visualizer modules which are automatically re-created when missing

modules/mbaasconfig.js

Auxiliary files generated during a build to expose the widget ID’s for testing.

resources/mobile/native/android/values/widgetids.xml
resources/tablet/native/androidtab/values/widgetids.xml

NPM dependencies folder which gets created for apps using the “Nitro” Cordova integration

when you choose NOT to use a globally installed Cordova SDK by unchecking

Project Settings>Application>Cordova Settings>Use globally installed Cordova version.

node_modules

When using the “Nitro” Cordova integration, the Cordova plugins and platforms

directories can be ignored as with any Cordova project.

cordovatemp
web/cordova/plugins
web/cordova/platforms

Auto-generated temporary internationalization files.

resources/i18n/

Logs created by building from the command line.

velocity.log

A Logger FFI that gets bundled with each project and is auto-generated by Visualizer with each build.

resources/customlibs/jsSrc/android/com/konylabs/ffi/N_KonyLogger.java
resources/customlibs/jsSrc/tabrcandroid/com/konylabs/ffi/N_KonyLogger.java
resources/customlibs/jsSrc/kiosk/KonyLogger.js
resources/customlibs/jsSrc/kiosk/KonyLogger.xml
resources/customlibs/jsSrc/windows8/KonyLogger.js
resources/customlibs/jsSrc/windows8/KonyLogger.xml
resources/customlibs/jsSrc/winmobile/KonyLogger.js
resources/customlibs/jsSrc/winmobile/KonyLogger.xml
resources/customlibs/jsSrc/winphone8/KonyLogger.js
resources/customlibs/jsSrc/winphone8/KonyLogger.xml
resources/customlibs/jsSrc/winphone81s/KonyLogger.js
resources/customlibs/jsSrc/winphone81s/KonyLogger.xml
resources/customlibs/jsXml/KonyLogger.js
resources/customlibs/jsXml/KonyLogger.xml

A Single Sign-On FFI that gets bundled with each project and is auto-generated by Visualizer with each build.

resources/customlibs/jsSrc/kiosk/SSOFFI.js
resources/customlibs/jsSrc/kiosk/SSOFFI.xml
resources/customlibs/jsSrc/windows8/SSOFFI.js
resources/customlibs/jsSrc/windows8/SSOFFI.xml
resources/customlibs/jsSrc/winmobile/SSOFFI.js
resources/customlibs/jsSrc/winmobile/SSOFFI.xml
resources/customlibs/jsSrc/winphone8/SSOFFI.js
resources/customlibs/jsSrc/winphone8/SSOFFI.xml
resources/customlibs/jsSrc/winphone81s/SSOFFI.js
resources/customlibs/jsSrc/winphone81s/SSOFFI.xml
resources/customlibs/jsXml/SSOFFI.js
resources/customlibs/jsXml/SSOFFI.xml

A utility FFI that gets bundled with each project and is auto-generated by Visualizer with each build.

resources/customlibs/jsSrc/android/com/konylabs/ffi/ND_binary_util.java
resources/customlibs/jsSrc/android/com/konylabs/ffi/N_binarydata.java
resources/customlibs/jsSrc/tabrcandroid/com/konylabs/ffi/ND_binary_util.java
resources/customlibs/jsSrc/tabrcandroid/com/konylabs/ffi/N_binarydata.java
resources/customlibs/jsXml/binary.util.js
resources/customlibs/jsXml/binary.util.xml
resources/customlibs/jsXml/binarydata.js
resources/customlibs/jsXml/binarydata.xml

12

Thanks @Jvmes Hill​!

13

For a comprehensive answer to this question and more on using Git on Visualizer projects you can go to: https://basecamp.kony.com/s/article-detail/a046A00000AT2AlQAL/git-for-visualizer-projects