[JBoss JIRA] (ERT-315) Changes in config.xml are not correctly propagated to project [EBZ#496329]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/ERT-315?page=com.atlassian.jira.plugin.sy... ]
Nick Boldt updated ERT-315:
---------------------------
Fix Version/s: Oxygen.3 (4.7)
(was: Neon (4.6))
> Changes in config.xml are not correctly propagated to project [EBZ#496329]
> --------------------------------------------------------------------------
>
> Key: ERT-315
> URL: https://issues.jboss.org/browse/ERT-315
> Project: Eclipse Release Train
> Issue Type: Task
> Components: Thym
> Reporter: Nick Boldt
> Priority: Minor
> Labels: 2.0.0, General, bzira
> Fix For: Oxygen.3 (4.7)
>
>
> Thym relies on config.xml for information about the current Cordova project. While changes to config.xml made through Thym functionality correctly update the project and config.xml, changes made directly to config.xml cause the actual project and WidgetModel to be inconsistent.
> Example: Deleting a plugin tag from config.xml makes it appear as though that plugin was removed from the project, even though the folders for that plugin are still attached to the project, and running `cordova plugin list` from the commandline will list that plugin as still installed.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (ERT-313) Fatal error invoking cordova CLI [EBZ#491764]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/ERT-313?page=com.atlassian.jira.plugin.sy... ]
Nick Boldt updated ERT-313:
---------------------------
Fix Version/s: Oxygen.3 (4.7)
(was: Neon (4.6))
> Fatal error invoking cordova CLI [EBZ#491764]
> ---------------------------------------------
>
> Key: ERT-313
> URL: https://issues.jboss.org/browse/ERT-313
> Project: Eclipse Release Train
> Issue Type: Task
> Components: Thym
> Reporter: Nick Boldt
> Priority: Critical
> Labels: 2.0.0, General, bzira
> Fix For: Oxygen.3 (4.7)
>
>
> Steps to reproduce:
> 1) Open THYM new project wizard
> 2) Select android engine only
> 3) install cordova-plugin-device
> 4) finish
> Stacktrace:
> -------------------
> java.io.IOException
> at org.eclipse.debug.internal.core.StreamsProxy.write(StreamsProxy.java:132)
> at org.eclipse.thym.core.internal.cordova.CordovaCLI.sendCordovaCommand(CordovaCLI.java:153)
> at org.eclipse.thym.core.internal.cordova.CordovaCLI.prepare(CordovaCLI.java:103)
> at org.eclipse.thym.ui.internal.project.RestoreProjectListener$RestoreProjectJob.run(RestoreProjectListener.java:54)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (ERT-160) Provide guidance when setting up Data Volumes in Run a Docker Image dialog [EBZ#491029]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/ERT-160?page=com.atlassian.jira.plugin.sy... ]
Nick Boldt updated ERT-160:
---------------------------
Fix Version/s: Oxygen.3 (4.7)
(was: Neon (4.6))
> Provide guidance when setting up Data Volumes in Run a Docker Image dialog [EBZ#491029]
> ---------------------------------------------------------------------------------------
>
> Key: ERT-160
> URL: https://issues.jboss.org/browse/ERT-160
> Project: Eclipse Release Train
> Issue Type: Task
> Components: Linux Tools
> Reporter: Friendly Jira Robot
> Labels: Docker, bzira
> Fix For: Oxygen.3 (4.7)
>
>
> When you set up a volume mount when running an image on Docker Machine or other non-native docker daemon, you have to make sure to use the right directory for this to work.
> From https://docs.docker.com/engine/userguide/containers/dockervolumes/#mount-... :
> If you are using Docker Machine on Mac or Windows, your Docker daemon has only limited access to your OS X or Windows filesystem. Docker Machine tries to auto-share your /Users (OS X) or C:\Users (Windows) directory.
> This means that unless you choose a mount inside your home directory, it will not work for you - the docker container will have a directory that is mounted inside docker machine, but not on your machine.
> It would be good if we could make this clear to the user somehow - perhaps provide a tooltip or something.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (ERT-524) org.w3c.dom.DOMException when changing engines [EBZ#520669]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/ERT-524?page=com.atlassian.jira.plugin.sy... ]
Nick Boldt updated ERT-524:
---------------------------
Fix Version/s: Oxygen.3 (4.7)
(was: Neon.1 (4.6))
> org.w3c.dom.DOMException when changing engines [EBZ#520669]
> -----------------------------------------------------------
>
> Key: ERT-524
> URL: https://issues.jboss.org/browse/ERT-524
> Project: Eclipse Release Train
> Issue Type: Task
> Components: Thym
> Reporter: Friendly Jira Robot
> Labels: 2.1.0, General, bzira
> Fix For: Oxygen.3 (4.7)
>
>
> Steps to reproduce:
> =========================================
> 1) create hybrid mobile application
> 2) have config.xml opened
> 3) right click on the app, select Properties -> Hybrid Mobile Engines
> 4) change engine (android or cordova)
> 5) Apply and close
> Stacktrace:
> =========================================
> org.w3c.dom.DOMException: Not Found
> at org.eclipse.wst.xml.core.internal.document.NodeContainer.removeChild(NodeContainer.java:375)
> at org.eclipse.thym.core.config.Widget.removeItem(Widget.java:345)
> at org.eclipse.thym.core.config.Widget.removeEngine(Widget.java:333)
> at org.eclipse.thym.core.engine.HybridMobileEngineManager$1.runInWorkspace(HybridMobileEngineManager.java:295)
> at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:39)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years