[ https://issues.jboss.org/browse/JBDS-2839?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-2839: ------------------------------------------- About the Epic - the main "complaint" about HMT for now is that the user experience is a bit hard thus this Epic is intended to illustrate that is the focus for JBDS 8 foremost. For now I just added what looked like usability issues from the existing aerogear component as I found them (I haven't looked at all yet). Intent is to order the issues in priority and choose which can be done. If issues are found to be something we can't do then put it in the backlog, similar if issues relates to something more specific and is better grouped in another epic we can split it out. About the specific issues: 5) We discussed this in past - current ticketmonster is structured based on how WFK/JDF could get something running with cordova back then. It is not a typical project structure. I believe the only sensible thing to support is to support importing Cordova projects created with the cordova cli (on a best effort basis since I know some of its project structures changes over time - but at least being able to import a cordova cli project will make the tools have much broader use than "just" to work with eclipse). The "next level" of this is that the cordova eclipse project will coexist with cordova cli as suggested in JBIDE-16659 to allow the HMT projects to be used in cli and continous integraiton builds too. 6 & 7) is related to #3 imo. having some central examples or project wizard templates (up to us to decide the approach) that allows users to get started with cordova using some of these techs and jquery mobile being the one that has the best support so far it seem to make sense to have that as the first priority and then everything else lower priority. -- 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