February 2018 - jbosstools-issues

[JBoss JIRA] (ERT-502) Cannot run hybrid app on ios simulator when eclipse runs in osx sandbox [EBZ#514543]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/ERT-502?page=com.atlassian.jira.plugin.sy... ] Nick Boldt updated ERT-502: --------------------------- Fix Version/s: Oxygen.3 (4.7) (was: Neon (4.6)) > Cannot run hybrid app on ios simulator when eclipse runs in osx sandbox [EBZ#514543] > ------------------------------------------------------------------------------------ > > Key: ERT-502 > URL: https://issues.jboss.org/browse/ERT-502 > Project: Eclipse Release Train > Issue Type: Task > Components: Thym > Reporter: Friendly Jira Robot > Priority: Critical > Labels: 2.0.0, bzira, iOS > Fix For: Oxygen.3 (4.7) > > > stack tracke: > -------------- > Instruments Error: Could not create output document '/private/var/folders/40/nmzqdw3n2f50bt94vlp0rq440000gn/T/AppTranslocation/FBD47789-8BCA-44F6-80C3-EC62388C5339/d/Eclipse-neon3.app/Contents/MacOS/instrumentscli0.trace': The volume “FBD47789-8BCA-44F6-80C3-EC62388C5339” is read only -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ERT-441) Cannot export native app [EBZ#506551]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/ERT-441?page=com.atlassian.jira.plugin.sy... ] Nick Boldt updated ERT-441: --------------------------- Fix Version/s: Oxygen.3 (4.7) (was: Neon (4.6)) > Cannot export native app [EBZ#506551] > ------------------------------------- > > Key: ERT-441 > URL: https://issues.jboss.org/browse/ERT-441 > Project: Eclipse Release Train > Issue Type: Task > Components: Thym > Reporter: Friendly Jira Robot > Labels: 2.0.0, General, bzira > Fix For: Oxygen.3 (4.7) > > > Created attachment 265051 > screen.png > Error code 65 for command: xcodebuild with args: -xcconfig,/Users/psrna/data/workspaces/10_2-am3_01/test.hyb.app/platforms/ios/cordova/build-debug.xcconfig,-project,test hyb app.xcodeproj,-target,test hyb app,-configuration,Debug,-destination,platform=iOS,build,CONFIGURATION_BUILD_DIR=/Users/psrna/data/workspaces/10_2-am3_01/test.hyb.app/platforms/ios/build/device,SHARED_PRECOMPS_DIR=/Users/psrna/data/workspaces/10_2-am3_01/test.hyb.app/platforms/ios/build/sharedpch -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ERT-440) Too many XML problems in platforms folder shown [EBZ#506517]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/ERT-440?page=com.atlassian.jira.plugin.sy... ] Nick Boldt updated ERT-440: --------------------------- Fix Version/s: Oxygen.3 (4.7) (was: Neon (4.6)) > Too many XML problems in platforms folder shown [EBZ#506517] > ------------------------------------------------------------ > > Key: ERT-440 > URL: https://issues.jboss.org/browse/ERT-440 > Project: Eclipse Release Train > Issue Type: Task > Components: Thym > Reporter: Friendly Jira Robot > Labels: 2.0.0, General, bzira > Fix For: Oxygen.3 (4.7) > > > Created attachment 265043 > screen.png -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ERT-437) Config.xml is not saved after "Create Hybrid Mobile Application" wizard finished [EBZ#506123]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/ERT-437?page=com.atlassian.jira.plugin.sy... ] Nick Boldt updated ERT-437: --------------------------- Fix Version/s: Oxygen.3 (4.7) (was: Neon (4.6)) > Config.xml is not saved after "Create Hybrid Mobile Application" wizard finished [EBZ#506123] > --------------------------------------------------------------------------------------------- > > Key: ERT-437 > URL: https://issues.jboss.org/browse/ERT-437 > Project: Eclipse Release Train > Issue Type: Task > Components: Thym > Reporter: Friendly Jira Robot > Labels: 2.0.0, General, bzira > Fix For: Oxygen.3 (4.7) > > > Created attachment 264908 > screenshot.png -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ERT-423) Errors updating engines from config.xml [EBZ#502146]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/ERT-423?page=com.atlassian.jira.plugin.sy... ] Nick Boldt updated ERT-423: --------------------------- Fix Version/s: Oxygen.3 (4.7) (was: Neon (4.6)) > Errors updating engines from config.xml [EBZ#502146] > ---------------------------------------------------- > > Key: ERT-423 > URL: https://issues.jboss.org/browse/ERT-423 > Project: Eclipse Release Train > Issue Type: Task > Components: Thym > Reporter: Friendly Jira Robot > Labels: 2.0.0, General, bzira > Fix For: Oxygen.3 (4.7) > > > Steps to reproduce: > 1) Run Thym new project wizard, pick some project name, finish > 2) Errors are shown. > screenshots attached. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ERT-316) Plugin folder decorators do not appear on Linux. [EBZ#496330]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/ERT-316?page=com.atlassian.jira.plugin.sy... ] Nick Boldt updated ERT-316: --------------------------- Fix Version/s: Oxygen.3 (4.7) (was: Neon (4.6)) > Plugin folder decorators do not appear on Linux. [EBZ#496330] > ------------------------------------------------------------- > > Key: ERT-316 > URL: https://issues.jboss.org/browse/ERT-316 > Project: Eclipse Release Train > Issue Type: Task > Components: Thym > Reporter: Nick Boldt > Priority: Trivial > Labels: 2.0.0, General, bzira > Fix For: Oxygen.3 (4.7) > > > Decorators on plugin folders in the plugins subdirectory do not appear when running on Linux (Fedora 23). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[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, 3 months

1
0
0 / 0

[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, 3 months

1
0
0 / 0

[JBoss JIRA] (ERT-204) Docker Machine lookup does not work on Windows machines [EBZ#494305]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/ERT-204?page=com.atlassian.jira.plugin.sy... ] Nick Boldt updated ERT-204: --------------------------- Fix Version/s: Oxygen.3 (4.7) (was: Neon (4.6)) > Docker Machine lookup does not work on Windows machines [EBZ#494305] > -------------------------------------------------------------------- > > Key: ERT-204 > URL: https://issues.jboss.org/browse/ERT-204 > Project: Eclipse Release Train > Issue Type: Bug > Components: Linux Tools > Reporter: Friendly Jira Robot > Assignee: Xavier Coulon > Labels: 5.0.0, Docker, bzira > Fix For: Oxygen.3 (4.7) > > > When creating Docker connection, the docker-machine mechanism does not work on Window as it seems to find docker-machine and not docker-machine.exe -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[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, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues February 2018