[JBoss JIRA] (JBIDE-18900) CordovaSim: Can't run default FeedHenry app locally
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18900?page=com.atlassian.jira.plugi... ]
Ilya Buziuk reassigned JBIDE-18900:
-----------------------------------
Assignee: Ilya Buziuk (was: Burr Sutter)
> CordovaSim: Can't run default FeedHenry app locally
> ---------------------------------------------------
>
> Key: JBIDE-18900
> URL: https://issues.jboss.org/browse/JBIDE-18900
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cordovasim
> Affects Versions: 4.2.1.Final
> Reporter: Ilya Buziuk
> Assignee: Ilya Buziuk
> Fix For: 4.3.0.Alpha1
>
> Attachments: configuration.png, cordovasimFH.png, hello_tom.png, preferences.png, ToolsProject-Cloud-App.zip, ToolsProject-Cordova-App.zip
>
>
> Basically, the situation is the following:
> 1. *ToolsProject-Cordova-App.zip* - is a basic FH hybrid app (all the app does is saying Hello + 'username' from the input field )
> 2. To run this app one simply needs to unpack the archive and import it as a cordova project to the studio
> 3. The application will work with a *remote* server like a charm !hello_tom.png|thumbnail!
> 4. However, there is an option to use *local* server instead of *remote* one
> 5. *ToolsProject-Cloud-App.zip* - is a app for running local server via grunt task runner
> 6. In order to run local server one needs:
> - unpack the app
> - run *npm install .*
> - run *grunt serve*
> Need to find the way to made CordovaSim use this *local* server
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 11 months
[JBoss JIRA] (TOOLSDOC-569) OpenShift How To: Add trouble shooting error info to Upload SSH Keys article
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-569?page=com.atlassian.jira.plug... ]
Michelle Murray commented on TOOLSDOC-569:
------------------------------------------
With regards troubleshooting for OpenShift SSH keys, test the following scenarios and make a note of 1) the error message (inc. SS), 2) cause and 3) solution/how to fix:
a) No SSH keys assigned to the OpenShift Online account
b) Public key assigned to OpenShift account but IDE doesn't know about private key
> OpenShift How To: Add trouble shooting error info to Upload SSH Keys article
> ----------------------------------------------------------------------------
>
> Key: TOOLSDOC-569
> URL: https://issues.jboss.org/browse/TOOLSDOC-569
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Enhancement
> Affects Versions: 4.2.0.Final
> Reporter: Michelle Murray
> Assignee: Supriya Bharadwaj
> Fix For: 4.2.0.Final
>
>
> Add a trouble shooting section to the article with info on common error messages relating to SSH keys and how to resolve.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 11 months
[JBoss JIRA] (TOOLSDOC-494) Add info on BrowserSim web engines + options
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-494?page=com.atlassian.jira.plug... ]
Michelle Murray commented on TOOLSDOC-494:
------------------------------------------
See TOOLSDOC-576: "Btw I'd rather add info that livereload will not work with java 7 if web engine is javaFx. Why - see FAQ"
> Add info on BrowserSim web engines + options
> --------------------------------------------
>
> Key: TOOLSDOC-494
> URL: https://issues.jboss.org/browse/TOOLSDOC-494
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Feature Request
> Components: User Guide - BrowserSim
> Affects Versions: 4.2.0.Beta1
> Reporter: Michelle Murray
> Assignee: Michelle Murray
> Fix For: 4.2.0.Beta2
>
>
> Alternative web engine available for BrowserSim/CordovaSim.
> This lifts previous Windows restrictions (need for Safari 32-bit).
> Both web engines are available for Mac OS X.
> Only JavaFX is available for Windows (unless install Safari and go down 32-bit route).
> Both web engines are available for RHEL, providing Oracle JDK installed and happy to use GTK2 or GTK3.
> Only SWT WebKit is available for Fedora/Ubuntu, as Oracle JDK not supported by RH for use with IDE.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 11 months
[JBoss JIRA] (JBDS-3256) JBoss specific Docker Tooling (Basic Integration)
by Arun Gupta (JIRA)
[ https://issues.jboss.org/browse/JBDS-3256?page=com.atlassian.jira.plugin.... ]
Arun Gupta commented on JBDS-3256:
----------------------------------
Would also like to take an existing Maven or Eclipse project, figure out the dependencies, and create a Dockerfile
> JBoss specific Docker Tooling (Basic Integration)
> -------------------------------------------------
>
> Key: JBDS-3256
> URL: https://issues.jboss.org/browse/JBDS-3256
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: openshift
> Reporter: Burr Sutter
> Assignee: Andre Dietisheim
>
> Goal: to allow the Eclipse user to easily discover, pull, run, deploy my .war or .ear to it, stop, commit, push for docker images/containers.
> Expected end-user flow 1:
> 0) Installation - assumes boot2docker pre-installed on the end-user's machine
> 1) I, the Java developer, need to browse a docker registry (either DockerHub or private registry), identify the image that I wish to have local and download (docker pull) for that image+tag.
> 2) Assumption: the docker image includes not only the operating system + JVM but also the EAP, Wildfly or Tomcat installed in a 'known' location.
> 3) I start (docker run) the image which auto-starts the embedded app server
> 4) I can then deploy my .war or .ear to the running app server
> 5) I can restart the running app server in debug mode and run the debugger
> 6) I can undeploy and redeploy my .war or .ear
> 7) I can stop/restart the running, embedded app server
> 8) I can then commit (docker commit)
> 9) then I can publish my changes (docker push)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 11 months
[JBoss JIRA] (JBDS-3256) JBoss specific Docker Tooling (Basic Integration)
by Arun Gupta (JIRA)
[ https://issues.jboss.org/browse/JBDS-3256?page=com.atlassian.jira.plugin.... ]
Arun Gupta commented on JBDS-3256:
----------------------------------
Here is some basic Docker tooling that would be helpful:
- Configure Docker Registries (public or private)
- Search images that on the configured registry
- Specify the name of an image that need to run the container. The image is downloaded, and possibly cached, if does not already exist.
- Like Servers tab at the bottom, it would be useful to have a Docker tab or provide a single UI to interact with everything Docker
- Orchestration of multiple Docker containers. For example, WildFly running in one container and MySQL in another one. Tooling can provide plumbing to make that happen.
[~maxandersen] Docker images already exist and defined at: http://www.jboss.org/docker/. As [~burrsutter] explained, app server-specific integration would be very useful, and much desirable by JBoss Tools.
> JBoss specific Docker Tooling (Basic Integration)
> -------------------------------------------------
>
> Key: JBDS-3256
> URL: https://issues.jboss.org/browse/JBDS-3256
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: openshift
> Reporter: Burr Sutter
> Assignee: Andre Dietisheim
>
> Goal: to allow the Eclipse user to easily discover, pull, run, deploy my .war or .ear to it, stop, commit, push for docker images/containers.
> Expected end-user flow 1:
> 0) Installation - assumes boot2docker pre-installed on the end-user's machine
> 1) I, the Java developer, need to browse a docker registry (either DockerHub or private registry), identify the image that I wish to have local and download (docker pull) for that image+tag.
> 2) Assumption: the docker image includes not only the operating system + JVM but also the EAP, Wildfly or Tomcat installed in a 'known' location.
> 3) I start (docker run) the image which auto-starts the embedded app server
> 4) I can then deploy my .war or .ear to the running app server
> 5) I can restart the running app server in debug mode and run the debugger
> 6) I can undeploy and redeploy my .war or .ear
> 7) I can stop/restart the running, embedded app server
> 8) I can then commit (docker commit)
> 9) then I can publish my changes (docker push)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 11 months