[ https://issues.jboss.org/browse/TOOLSDOC-445?page=com.atlassian.jira.plug... ] Michelle Murray commented on TOOLSDOC-445: ------------------------------------------ We can explain the project structure so that users can be more informed when making decisions about which files/dirs to place under version control. Since JBDS does not have it's own version controls actions we can't document exactly what to put under version control. As part of JBQA-8565, I stated: {quote} Gorkem Ercan, about "need to explain the different directories and what they do". This would be best included in the context of a description of standard Cordova projects and how JBDS produced Cordova projects vary. Standard/basis of Cordova projects are given in '8.2.1. About Apache Cordova'. If you think there should be more details please provide me with some pointers of what's missing. JBDS Cordova project distinctions can be given in '8.2.2. About Hybrid Mobile Tools', where the project wizard is detailed. Again, please provide any specifics of how JBDS Cordova projects differ. From the info above one distinction seems to be the absence of a platforms directory. {quote} Let's enact this for JBDS 8.0.0 (JBT 4.2.1). Information I have is as follows: 1. Cordova (CLI) project structure [1] = config.xml, hooks/, merges/, www/ with index.html, platforms/, plugins/ 2. Hybrid Mobile Tools Cordova project structure = .cordova/ with config.json, merges/, plugins/, .project, .settings/, www/ with config.xml and index.html *What info do I have wrong or am I missing?* [1] https://github.com/apache/cordova-cli#project-directory-structure -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira