[
https://issues.jboss.org/browse/JBIDE-16312?page=com.atlassian.jira.plugi...
]
Vineet Reynolds commented on JBIDE-16312:
-----------------------------------------
The intention was to allow import of HMT projects that were once created in JBDS. Right
now, I need to store the .project file in SCM (to retain the HMT nature), and {{import as
an existing project}} (supplying the root directory). From the point of view of an
end-user it would be great to find an "Import as HMT project" in the Eclipse
Import dialog.
It does look similar to importing projects with the structure generated by Cordova-CLI.
You could mark this as a duplicate of JBIDE-13649 if both of these issues would be served
by the same feature.
Support importing of Hybrid Mobile projects into workspace
----------------------------------------------------------
Key: JBIDE-16312
URL:
https://issues.jboss.org/browse/JBIDE-16312
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: aerogear-hybrid
Affects Versions: 4.1.1.Final
Reporter: Vineet Reynolds
Fix For: LATER
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
Currently, to import a Hybrid Mobile project, I need to import it as a plain Eclipse
project, while ensuring that the original Eclipse project file (.project) is present that
contains the desired project natures.
If the .project file is disallowed in version control, then this becomes a bit tricky
since the .project file needs to be recreated.
It would be better to allow support for importing an existing directory into the
workspace as a Hybrid Mobile project (like importing existing android project, existing
maven projects etc.) via the Eclipse Import menu.
--
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