[JBoss JIRA] (JBIDE-22274) Show In->System Explorer on docker volume is not working when the volume is just a file (not a directory)
by Jeff Johnston (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22274?page=com.atlassian.jira.plugi... ]
Jeff Johnston updated JBIDE-22274:
----------------------------------
Fix Version/s: (was: 4.4.x)
> Show In->System Explorer on docker volume is not working when the volume is just a file (not a directory)
> ---------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-22274
> URL: https://issues.jboss.org/browse/JBIDE-22274
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: docker, upstream
> Affects Versions: 4.4.0.Alpha1
> Environment: JBDS 10.0.0.Alpha1-v20160428-0509-B5247
> Reporter: Radim Hopp
> Assignee: Jeff Johnston
> Fix For: 4.4.1.AM1
>
>
> Start docker container with -v parameter pointing to some file. For example: "docker run -d -p 5000:5000 -v /home/rhopp/temp/config.yml_new:/etc/docker/registry/config.yml --name registry1 registry:2"
> Go to Docker Explorer, expand running container->right click on the only volume in there->Show In->System Explorer-> Error is logged:
> {noformat:title=Failed to open in Web Browser}
> java.io.IOException: Cannot run program "/bin/sh" (in directory "/home/rhopp/temp/config.yml_new"): error=20, Not a directory
> at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048)
> at java.lang.Runtime.exec(Runtime.java:620)
> at org.eclipse.linuxtools.internal.docker.ui.commands.ShowInSystemExplorerCommandHandler.getLaunchProcess(ShowInSystemExplorerCommandHandler.java:99)
> at org.eclipse.linuxtools.internal.docker.ui.commands.ShowInSystemExplorerCommandHandler.access$0(ShowInSystemExplorerCommandHandler.java:96)
> at org.eclipse.linuxtools.internal.docker.ui.commands.ShowInSystemExplorerCommandHandler$1.run(ShowInSystemExplorerCommandHandler.java:65)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: java.io.IOException: error=20, Not a directory
> at java.lang.UNIXProcess.forkAndExec(Native Method)
> at java.lang.UNIXProcess.<init>(UNIXProcess.java:248)
> at java.lang.ProcessImpl.start(ProcessImpl.java:134)
> at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029)
> ... 5 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (ERT-329) Use Closure compiler [EBZ#497249]
by Friendly Jira Robot (JIRA)
Friendly Jira Robot created ERT-329:
---------------------------------------
Summary: Use Closure compiler [EBZ#497249]
Key: ERT-329
URL: https://issues.jboss.org/browse/ERT-329
Project: Eclipse Release Train
Issue Type: Task
Components: JSDT
Reporter: Friendly Jira Robot
Fix For: Oxygen (4.7)
Take closure compiler into use instead of the Esprima Parser to creates ASTs.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22593) New application wizard: preselect v3 connection that I most recently used
by Dmitry Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22593?page=com.atlassian.jira.plugi... ]
Dmitry Bocharov reassigned JBIDE-22593:
---------------------------------------
Assignee: (was: Dmitry Bocharov)
> New application wizard: preselect v3 connection that I most recently used
> -------------------------------------------------------------------------
>
> Key: JBIDE-22593
> URL: https://issues.jboss.org/browse/JBIDE-22593
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.0.Final
> Reporter: Andre Dietisheim
> Labels: application_wizard, connection_wizard, openshift_v2, openshift_v3
> Fix For: 4.4.1.AM1
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> # ASSERT: make sure that you have used a v3 connection (ex. import an application from your OpenShift server to your workspace)
> # EXEC: launch openshift wizard via File->New->OpenShift Application
> # ASSERT: connection dialog shows up
> Result:
> Connection dialog shows up with <New Connection> and connection type "OpenShift 2" pre-selected.
> Expected result:
> Connection dialog has my v3 connection preselected, that I recently used.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22593) New application wizard: preselect v3 connection that I most recently used
by Dmitry Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22593?page=com.atlassian.jira.plugi... ]
Dmitry Bocharov updated JBIDE-22593:
------------------------------------
Sprint: (was: devex #116 June 2016)
> New application wizard: preselect v3 connection that I most recently used
> -------------------------------------------------------------------------
>
> Key: JBIDE-22593
> URL: https://issues.jboss.org/browse/JBIDE-22593
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.0.Final
> Reporter: Andre Dietisheim
> Assignee: Dmitry Bocharov
> Labels: application_wizard, connection_wizard, openshift_v2, openshift_v3
> Fix For: 4.4.1.AM1
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> # ASSERT: make sure that you have used a v3 connection (ex. import an application from your OpenShift server to your workspace)
> # EXEC: launch openshift wizard via File->New->OpenShift Application
> # ASSERT: connection dialog shows up
> Result:
> Connection dialog shows up with <New Connection> and connection type "OpenShift 2" pre-selected.
> Expected result:
> Connection dialog has my v3 connection preselected, that I recently used.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22433) Properties: Add Storage tab
by Dmitry Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22433?page=com.atlassian.jira.plugi... ]
Dmitry Bocharov updated JBIDE-22433:
------------------------------------
Sprint: devex #117 July 2016
> Properties: Add Storage tab
> ---------------------------
>
> Key: JBIDE-22433
> URL: https://issues.jboss.org/browse/JBIDE-22433
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Reporter: Fred Bricon
> Assignee: Dmitry Bocharov
> Labels: openshift_v3, properties
> Fix For: 4.4.x
>
> Attachments: storage from web console.png
>
>
> We should be able to display Persistent Volume (aka Storage) informations in the OpenShift properties.
> Need to define the extent of the informations to display. At the very least, it should be the same as what the OpenShift Console provides.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months