December 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-20935) Central doesn't scale back after being enlarged on Windows

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20935?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-20935: ------------------------------- Fix Version/s: 4.4.3.AM1 (was: 4.3.x) (was: 4.4.x) > Central doesn't scale back after being enlarged on Windows > ---------------------------------------------------------- > > Key: JBIDE-20935 > URL: https://issues.jboss.org/browse/JBIDE-20935 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.3.0.Final > Environment: Windows 10 > 250% UI scale > Reporter: Jan Richter > Assignee: Ilya Buziuk > Labels: ui-scaling > Fix For: 4.4.3.AM1 > > Attachments: JBossCentral_not-rescaling_2015-10-14_14-39-28.mp4, central.png, screenshot-1.png > > > When I maximize the central tab in eclipse and then restore it, instead of it scaling back to its confined space it stays expanded and adds scrollbars. > Like so: > !central.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21019) Implement cancelling in Knowledge Base Builder

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21019?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-21019: ------------------------------- Fix Version/s: 4.5.0.AM1 (was: 4.3.x) > Implement cancelling in Knowledge Base Builder > ---------------------------------------------- > > Key: JBIDE-21019 > URL: https://issues.jboss.org/browse/JBIDE-21019 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: common > Affects Versions: 4.3.0.Final > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Fix For: 4.5.0.AM1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20972) As a user I want to see relevant but simple info about my OpenShift v3 server adapter in the servers view

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20972?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-20972: ------------------------------- Fix Version/s: 4.5.0.AM1 (was: 4.4.x) > As a user I want to see relevant but simple info about my OpenShift v3 server adapter in the servers view > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20972 > URL: https://issues.jboss.org/browse/JBIDE-20972 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Alpha1 > Reporter: Jeff Cantrill > Labels: openshift_v3, server_adapter > Fix For: 4.5.0.AM1 > > Attachments: 2015-10-13 19.03.bmml, 2015-10-13 19.03.png, Console of 'App' with the pieces wired.png, Pipeline view mockup.bmml > > > Add an alternate view in the openshift v3 explorer to try to 'link' resources in a similiar fashion to the web console -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20911) open local terminal with oc already logged in

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20911?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-20911: ------------------------------- Fix Version/s: 4.5.0.AM1 (was: 4.4.x) > open local terminal with oc already logged in > --------------------------------------------- > > Key: JBIDE-20911 > URL: https://issues.jboss.org/browse/JBIDE-20911 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Max Rydahl Andersen > Fix For: 4.5.0.AM1 > > > it would be great to have a "Show in > OpenShift CLI" in openshift explorer and on projects that are known to be on openshift that would use local terminal (like: https://v.usetapes.com/ISfR95tJK8) but have `oc login --token=<tokenforlogin> --server=<serverurl>` executed at start. > This would allow users to work with CLI whenever the UI does not have exactly the command needed by user. > * This assumes users have oc in their path > * might need different commands based on what OS (windows vs *nix) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20771) Livereload not working with projects hosted on local Server with Content Security Policy (CSP) enabled

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20771?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-20771: ------------------------------- Fix Version/s: 4.5.0.AM1 (was: 4.4.x) > Livereload not working with projects hosted on local Server with Content Security Policy (CSP) enabled > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-20771 > URL: https://issues.jboss.org/browse/JBIDE-20771 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: livereload > Affects Versions: 4.3.0.CR1 > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Fix For: 4.5.0.AM1 > > Attachments: csp.png > > > This problem might be treated as an edge case from the first glance, but actually it might have a sufficient impact on Livereload in the short run. *CSP* is sort of security policy which complements *CORS*. However, Content Security Policy and CORS are two separate things. CORS is the web service declaring which apps are authorized to call the service. > Content Security Policy is kind of the opposite: it's the app that declares which services can be called. > Basically, [Content Security Policy|http://www.html5rocks.com/en/tutorials/security/content-security-p...] is supported by new versions on major browsers in order to prevent Cross-site scripting (XSS) attacks. However, this policy restricts the usage of LiveReload to the certain extend. > Steps to reproduce: > 1) Create default *jboss-as-kitchensink-html5-mobile* > 2) Add CSP meta tag > {code} > <meta http-equiv="Content-Security-Policy" content="default-src *; style-src 'self' 'unsafe-inline'; script-src 'self' 'unsafe-inline' 'unsafe-eval' ajax.googleapis.com/ajax/libs/jquery/1.9.1/jquery.js"> > {code} > ^ allow to use jquery (other stuff is hosted locally) > 3) In Preferences (General -> Web Browser) add newest version of chrome and set as default > 4) Run the project on the Local Server (Tomcat) > 5) In the Server View right-click on the hosted project -> Show In -> Web Browser via LiveReload > 6) Edit and save index.html > 7) ERROR: Livereload is broken - CSP has prevented *livereload.js* injection > !csp.png! > N.B. LiveReload will work with the file protocol (right click on index.html -> *Open With* -> *Web Browser with LiveReload*) even with CSP enabled, cause in this case livereload.js is hosted on the same port (35729 by default) as the whole project > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20838) Misleading dialog displayed to user when installing example and dependent packages

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20838?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-20838: ------------------------------- Fix Version/s: 4.5.0.AM1 (was: 4.4.x) > Misleading dialog displayed to user when installing example and dependent packages > ---------------------------------------------------------------------------------- > > Key: JBIDE-20838 > URL: https://issues.jboss.org/browse/JBIDE-20838 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.3.0.CR2 > Reporter: Len DiMaggio > Priority: Minor > Fix For: 4.5.0.AM1 > > Attachments: Screenshot.png > > > Steps to recreate: > * After a clean install, from Central install create a project such as a Java EE project > * Observe the dialog in the attached screenshot - after the required packages are installed the user is returned to Central - as a user I would have expected to have had the project created automatically after the required packages were installed -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20765) The JBoss Central connectorDescriptor description field text should be displayed with some type of auto-formatting if it's too large for the label space.

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20765?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-20765: ------------------------------- Fix Version/s: 4.5.0.AM1 (was: 4.4.x) > The JBoss Central connectorDescriptor description field text should be displayed with some type of auto-formatting if it's too large for the label space. > --------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20765 > URL: https://issues.jboss.org/browse/JBIDE-20765 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: central, central-update > Affects Versions: 4.3.0.CR1 > Reporter: Paul Leacu > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.5.0.AM1 > > > The JBoss Central connectorDescriptor description field should be displayed with some type of auto-formatting if it's too large for the label space. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22290) Open via livereload quick access errors when no livereload server is present

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22290?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-22290: ------------------------------- Fix Version/s: 4.4.3.AM1 (was: 4.4.x) > Open via livereload quick access errors when no livereload server is present > ---------------------------------------------------------------------------- > > Key: JBIDE-22290 > URL: https://issues.jboss.org/browse/JBIDE-22290 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: livereload > Affects Versions: 4.4.0.Alpha1 > Reporter: Jan Richter > Assignee: Xavier Coulon > Fix For: 4.4.3.AM1 > > > The following error is produced while the livereload server is starting: > {noformat} > Problems occurred when invoking code from plug-in: "org.jboss.tools.livereload.ui". > org.eclipse.swt.SWTException: Invalid thread access > at org.eclipse.swt.SWT.error(SWT.java:4522) > at org.eclipse.swt.SWT.error(SWT.java:4437) > at org.eclipse.swt.SWT.error(SWT.java:4408) > at org.eclipse.swt.widgets.Display.error(Display.java:1186) > at org.eclipse.swt.widgets.Display.checkDevice(Display.java:765) > at org.eclipse.swt.widgets.Display.getActiveShell(Display.java:1400) > at org.jboss.tools.livereload.ui.internal.command.OpenInWebBrowserViaLiveReloadUtils.openInWebBrowser(OpenInWebBrowserViaLiveReloadUtils.java:189) > at org.jboss.tools.livereload.ui.internal.command.LaunchLiveReloadServerCommandHandler.openInWebBrowser(LaunchLiveReloadServerCommandHandler.java:114) > at org.jboss.tools.livereload.ui.internal.command.LaunchLiveReloadServerCommandHandler.access$0(LaunchLiveReloadServerCommandHandler.java:112) > at org.jboss.tools.livereload.ui.internal.command.LaunchLiveReloadServerCommandHandler$2.done(LaunchLiveReloadServerCommandHandler.java:67) > at org.eclipse.core.internal.jobs.JobListeners$3.notify(JobListeners.java:42) > at org.eclipse.core.internal.jobs.JobListeners.doNotify(JobListeners.java:106) > at org.eclipse.core.internal.jobs.JobListeners.done(JobListeners.java:144) > at org.eclipse.core.internal.jobs.JobManager.endJob(JobManager.java:694) > at org.eclipse.core.internal.jobs.WorkerPool.endJob(WorkerPool.java:105) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:72) > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20730) Displaying of a project in OpenShift Explorer view is not consistent

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20730?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-20730: ------------------------------- Fix Version/s: 4.5.0.AM1 (was: 4.4.x) > Displaying of a project in OpenShift Explorer view is not consistent > -------------------------------------------------------------------- > > Key: JBIDE-20730 > URL: https://issues.jboss.org/browse/JBIDE-20730 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Marián Labuda > Fix For: 4.5.0.AM1 > > > OpenShift 3 project is displayed a bit tricky in OpenShift Explorer view. If project has only project name, then project name is shown as normal text in OpenShift Explorer view under an OpenShift 3 connection. But if a project has set also an optional attribute displayName, then this name is used as a normal text under an OpenShift 3 connection and it's name is used only as a decorated text in parenthesis. Example: > Project 01 has name: project01 > Project 02 has name: project02 and displayName: projectName02 > In OpenShift Explorer view are those projects shown as > project01 > projectName02 (project02) > One could think that project01 and projectName02 are the same attribute of a project, but it's not. I think we could and should show projects like this: > project01 (project01) > projectName02 (project02) > because default value for a displayName is attribute name. In that case it would be consistent and user would not be confused. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20763) Provide 'oc' binaries per platform

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20763?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-20763: ------------------------------- Fix Version/s: 4.5.0.AM1 (was: 4.4.x) > Provide 'oc' binaries per platform > ---------------------------------- > > Key: JBIDE-20763 > URL: https://issues.jboss.org/browse/JBIDE-20763 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Fix For: 4.5.0.AM1 > > > Instead of forcing the user to search, download and install the 'oc' library manually before being able to use port forwarding or log streaming, the platform-related binary could be installed automatically. > Possible implementation: > - define the oc binary URLs in stacks.yaml > - on openshift 3 plugin startup, check if oc binary is set in preferences > - if not set trigger background job to d/l oc binary matching current platform, and update preferences, else, do nothing. > [~maxandersen] does it correspond to what you had in mind? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 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 December 2016