[JBoss JIRA] (JBDS-3267) JSON Editor
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBDS-3267?page=com.atlassian.jira.plugin.... ]
Andre Dietisheim commented on JBDS-3267:
----------------------------------------
In an advanced scenarion we'll also need a json editor for OpenShift (kubernetes/json directives to build, deploy etc.). The json editor required here would ideally be based on the json schemes that exists for kubernetes/openshift.
> JSON Editor
> -----------
>
> Key: JBDS-3267
> URL: https://issues.jboss.org/browse/JBDS-3267
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Reporter: Burr Sutter
>
> As a Java or Java EE developer, who wishes to test my JAX-RS endpoints as well as edit various JSON files, I need an editor that formats the nested curly braces, helps me to insure that I am not missing (nor have extra) curly braces, missing quotes, helps me to know when to use square brackets, etc. Ideally, the Eclipse Outline view would also work if I am editing a .json file.
> Ideally, we would support both a full JSON editor as well as working within the Web Services Tester.
> http://screencast.com/t/hWAtlMytghV6
> http://screencast.com/t/h4VWGyAuqw
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 6 months
[JBoss JIRA] (JBDS-3278) OpenShift v3
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBDS-3278?page=com.atlassian.jira.plugin.... ]
Andre Dietisheim updated JBDS-3278:
-----------------------------------
Component/s: openshift
> OpenShift v3
> ------------
>
> Key: JBDS-3278
> URL: https://issues.jboss.org/browse/JBDS-3278
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: openshift
> Reporter: Burr Sutter
> Assignee: Andre Dietisheim
>
> As an OpenShift v3 end-user, I need to be deploy, undeploy, add, remove, view logs, etc. for applications targeting the v3 API.
> The UI for OpenShift Explorer will need to be expanded (or replaced) to handle v3's new terminology and architecture.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 6 months
[JBoss JIRA] (JBDS-3258) Docker Tooling (Advanced Integration)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBDS-3258?page=com.atlassian.jira.plugin.... ]
Andre Dietisheim updated JBDS-3258:
-----------------------------------
Assignee: Max Rydahl Andersen (was: Andre Dietisheim)
> Docker Tooling (Advanced Integration)
> -------------------------------------
>
> Key: JBDS-3258
> URL: https://issues.jboss.org/browse/JBDS-3258
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Reporter: Burr Sutter
> Assignee: Max Rydahl Andersen
>
> Once significant delta between the "basic" and advanced scenarios is that here I wish to custom craft my own docker images instead of using an existing one - where my custom crafted image includes my .war or .ear.
> In addition to the basic integrations of pull, run, stop, commit and push
> boot2docker init
> boot2docker up
> boot2docker down
> boot2docker ip
> docker run -d
> docker ps
> docker rm
> docker rmi
> docker build
> End-user steps:
> 0) assumes boot2docker has been dowloaded and installed
> 1) boot2docker init : required to to insure boot2docker-vm is properly initialized
> 2) boot2docker up : starts the VirtualBox boot2docker-vm
> 3) boot2docker ip : returns the IP address - this will be vital when it comes to testing - it would need to be integrated with our Run - As on Docker capability.
> 4) docker run -i -t -p 80:8080 jboss/wildfly -d : the -d means detached, I may need to run N containers simultaneously
> 5) docker ps : allows me to see all my currently running containers
> 6) docker rm : allows me to kill a currently running container
> 7) docker rmi : allows me to remove a local image
> 8) docker build : assumes that I have crafted a Dockerfile - this will create the local image - with my .war or .ear embedded
> 9) docker run : this new created image
> The docker build scenario can be triggered via a Maven plugin
> The docker build scenario can also be triggered via an Eclipse menu option (like a Maven install)
> We need to figure out the file-system layout so that the Dockerfile and the maven project are all nicely checked into git/svn. So that Jenkins can pick up this repository and perform an automated "docker build" (post Maven install) and then run all the appropriate unit, integration and functional tests.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 6 months
[JBoss JIRA] (JBDS-3258) Docker Tooling (Advanced Integration)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBDS-3258?page=com.atlassian.jira.plugin.... ]
Andre Dietisheim commented on JBDS-3258:
----------------------------------------
[~maxandersen]: are we having this in its own component or is this considered part of openshift (I assume there are integration parts and a standalone majority)?
> Docker Tooling (Advanced Integration)
> -------------------------------------
>
> Key: JBDS-3258
> URL: https://issues.jboss.org/browse/JBDS-3258
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Reporter: Burr Sutter
> Assignee: Andre Dietisheim
>
> Once significant delta between the "basic" and advanced scenarios is that here I wish to custom craft my own docker images instead of using an existing one - where my custom crafted image includes my .war or .ear.
> In addition to the basic integrations of pull, run, stop, commit and push
> boot2docker init
> boot2docker up
> boot2docker down
> boot2docker ip
> docker run -d
> docker ps
> docker rm
> docker rmi
> docker build
> End-user steps:
> 0) assumes boot2docker has been dowloaded and installed
> 1) boot2docker init : required to to insure boot2docker-vm is properly initialized
> 2) boot2docker up : starts the VirtualBox boot2docker-vm
> 3) boot2docker ip : returns the IP address - this will be vital when it comes to testing - it would need to be integrated with our Run - As on Docker capability.
> 4) docker run -i -t -p 80:8080 jboss/wildfly -d : the -d means detached, I may need to run N containers simultaneously
> 5) docker ps : allows me to see all my currently running containers
> 6) docker rm : allows me to kill a currently running container
> 7) docker rmi : allows me to remove a local image
> 8) docker build : assumes that I have crafted a Dockerfile - this will create the local image - with my .war or .ear embedded
> 9) docker run : this new created image
> The docker build scenario can be triggered via a Maven plugin
> The docker build scenario can also be triggered via an Eclipse menu option (like a Maven install)
> We need to figure out the file-system layout so that the Dockerfile and the maven project are all nicely checked into git/svn. So that Jenkins can pick up this repository and perform an automated "docker build" (post Maven install) and then run all the appropriate unit, integration and functional tests.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 6 months
[JBoss JIRA] (JBDS-3282) Screencasts: OpenShift v3
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBDS-3282?page=com.atlassian.jira.plugin.... ]
Andre Dietisheim reassigned JBDS-3282:
--------------------------------------
Assignee: Andre Dietisheim
> Screencasts: OpenShift v3
> -------------------------
>
> Key: JBDS-3282
> URL: https://issues.jboss.org/browse/JBDS-3282
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: openshift
> Reporter: Burr Sutter
> Assignee: Andre Dietisheim
>
> A series of short (5 minutes), educational videos to illustrate the new capabilities of JBDS associated with OpenShift.
> Including:
> - OpenShift's new web UI
> - OpenShift Explorer in the context of v3
> - perhaps an overview of Kubernetes, depends on how "pods" become visible to our end-user
> - an overview of Docker, depends on how 'containers" become visible to our end-user
> and all the typical start, stop, add, delete/remove, view logs, set env vars, etc.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 6 months
[JBoss JIRA] (JBIDE-18819) When discovery URL is not set, "Software/Updates" page is silently hidden
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18819?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-18819:
----------------------------------------
I think it's always a good idea to make error messages state the real error ;) Feel free to open a Jira on this topic. However, I'm not sure that the probablility of this issue to happen to end-users is high enough to make it reach the top of a priority list.
> When discovery URL is not set, "Software/Updates" page is silently hidden
> -------------------------------------------------------------------------
>
> Key: JBIDE-18819
> URL: https://issues.jboss.org/browse/JBIDE-18819
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: central
> Affects Versions: 4.2.0.Final
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Labels: respin-a
> Fix For: 4.2.1.CR1, 4.3.0.Alpha1
>
>
> With latest CI build (in http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio.product_8.... ), Central editor seems to miss the "Software/Updates" tab.
> Log mentions an error, which doesn't seem related at first sight:
> {code:none}
> !SESSION 2014-11-21 15:51:47.555 -----------------------------------------------
> eclipse.buildId=unknown
> java.version=1.8.0_11
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product com.jboss.devstudio.core.product
> Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> !ENTRY org.jboss.tools.project.examples 4 0 2014-11-21 15:53:24.762
> !MESSAGE All attempts to discover connectors have failed
> !SUBENTRY 1 org.eclipse.mylyn.discovery.core 4 0 2014-11-21 15:53:24.762
> !MESSAGE Failed to get connectors from RemoteProxyWizardDiscoveryStrategy
> !STACK 0
> java.lang.NullPointerException
> at java.net.URI$Parser.parse(URI.java:3042)
> at java.net.URI.<init>(URI.java:588)
> at org.jboss.tools.project.examples.internal.discovery.xpl.RemoteExternalBundleDiscoveryStrategy.loadRegistry(RemoteExternalBundleDiscoveryStrategy.java:90)
> at org.jboss.tools.project.examples.internal.discovery.xpl.ExternalBundleDiscoveryStrategy.performDiscovery(ExternalBundleDiscoveryStrategy.java:117)
> at org.jboss.tools.project.examples.internal.discovery.ChainedDiscoveryStrategy.performDiscovery(ChainedDiscoveryStrategy.java:62)
> at org.eclipse.mylyn.internal.discovery.core.model.ConnectorDiscovery.performDiscovery(ConnectorDiscovery.java:114)
> at org.jboss.tools.central.internal.discovery.wizards.ProxyWizardManager.loadWizards(ProxyWizardManager.java:107)
> at org.jboss.tools.central.internal.discovery.wizards.ProxyWizardUpdateJob.run(ProxyWizardUpdateJob.java:45)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 6 months
[JBoss JIRA] (JBDS-3282) Screencasts: OpenShift v3
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBDS-3282?page=com.atlassian.jira.plugin.... ]
Andre Dietisheim updated JBDS-3282:
-----------------------------------
Component/s: openshift
> Screencasts: OpenShift v3
> -------------------------
>
> Key: JBDS-3282
> URL: https://issues.jboss.org/browse/JBDS-3282
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: openshift
> Reporter: Burr Sutter
>
> A series of short (5 minutes), educational videos to illustrate the new capabilities of JBDS associated with OpenShift.
> Including:
> - OpenShift's new web UI
> - OpenShift Explorer in the context of v3
> - perhaps an overview of Kubernetes, depends on how "pods" become visible to our end-user
> - an overview of Docker, depends on how 'containers" become visible to our end-user
> and all the typical start, stop, add, delete/remove, view logs, set env vars, etc.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 6 months
[JBoss JIRA] (JBDS-3277) OpenShift v2
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBDS-3277?page=com.atlassian.jira.plugin.... ]
Andre Dietisheim edited comment on JBDS-3277 at 12/10/14 4:43 AM:
------------------------------------------------------------------
[~burrsutter]: I dont fully see the focus of this issue: isn't that what we already provide for OpenShift v2?
was (Author: adietish):
I dont fully see the focus of this issue: isn't that what we already provide for OpenShift v2?
> OpenShift v2
> ------------
>
> Key: JBDS-3277
> URL: https://issues.jboss.org/browse/JBDS-3277
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Reporter: Burr Sutter
>
> As a OpenShift v2 end-user, I need to deploy, undeploy, add, remove, view logs, etc apps running on OpenShift v2, so I can maintain my existing applications that were previously bound to OpenShift v2.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 6 months