August 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22624) Explorer: connection stays "Loading" after I provided the authentication info

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22624?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-22624: ----------------------------------- Assignee: Dmitry Bocharov > Explorer: connection stays "Loading" after I provided the authentication info > ----------------------------------------------------------------------------- > > Key: JBIDE-22624 > URL: https://issues.jboss.org/browse/JBIDE-22624 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Jeff MAURY > Assignee: Dmitry Bocharov > Labels: explorer, openshift_v3 > Fix For: 4.4.1.AM3 > > Attachments: 2016-06-21 at 10-23-04.mp4 > > > EXEC: create a new v3 connection to CDK, don't store the password > EXEC: restart Eclipse > EXEC: in OpenShift Explorer: unfold the connection > ASSERT: connection dialog appears, prompting you to provide the password. > EXEC: provide the password, finish > ASSERT: explorer still displays "Loading..." > EXEC: refresh the connection > ASSERT: explorer now displays the resources -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15189) Check compatible JRE/JDK when adding server via runtime detection

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15189?page=com.atlassian.jira.plugi... ] Rob Stryker edited comment on JBIDE-15189 at 8/11/16 8:41 PM: -------------------------------------------------------------- In general, you have a new column in the dialog. If you click on this column, the problems will be listed below, and if you double-click the problem, it will attempt to resolve it for you (or ask you to help it resolve it). At this time, my roll-your-own quickfix only allows one possible resolution per error. This isn't a problem with the API but rather me not knowing how to properly display multiple possible solutions to a problem. Also, since we currently only really have one example, it's not necessary at the moment, since there's only one solution to adding a missing JRE. Things to test: 1) The popup dialog behaves as you'd expect. It disappears when you'd expect, and stays visible when you'd expect. This includes clicking around, pressing escape, using arrow keys and the enter key, etc. 2) The popup quickfix menu is resizable and appears in the exact position you'd expect. 3) The dialog that pops up to fix the issue has descriptive instructions 4) The error disappears once you've fixed it 5) The error disappears for other runtimes, as well, if the solution should have fixed both. Please only re-open this issue if a critical issue is found. If a small issue is found or a small improvement is suggested, please open a new issue. Workflow to test: 1) Open new workspace, remove your j8 jre, add a j6 or j5 jre instead. 2) Go to runtime detection, add two paths pointing to an eap6.4 and wf 10 3) Perform a runtime detection, note that both found runtimes have problems 4) Click a problem / quickfix, to expand the quickfix menu 5) Resize the item, click around, etc 6) Eventually, double-click the 'problem' 7) Note that a add-jre wizard comes up with proper description and instructions. 8) Add a java8 jre 9) Watch as both runtimes no longer have errors. was (Author: rob.stryker): In general, you have a new column in the dialog. If you click on this column, the problems will be listed below, and if you double-click the problem, it will attempt to resolve it for you (or ask you to help it resolve it). At this time, my roll-your-own quickfix only allows one possible resolution per error. This isn't a problem with the API but rather me not knowing how to properly display multiple possible solutions to a problem. Also, since we currently only really have one example, it's not necessary at the moment, since there's only one solution to adding a missing JRE. Things to test: 1) The popup dialog behaves as you'd expect. It disappears when you'd expect, and stays visible when you'd expect. This includes clicking around, pressing escape, using arrow keys and the enter key, etc. 2) The popup quickfix menu is resizable and appears in the exact position you'd expect. 3) The dialog that pops up to fix the issue has descriptive instructions Please only re-open this issue if a critical issue is found. If a small issue is found or a small improvement is suggested, please open a new issue. > Check compatible JRE/JDK when adding server via runtime detection > ----------------------------------------------------------------- > > Key: JBIDE-15189 > URL: https://issues.jboss.org/browse/JBIDE-15189 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: runtime-detection > Affects Versions: 4.1.0.CR1 > Reporter: Radim Hopp > Assignee: Rob Stryker > Fix For: 4.4.1.AM3 > > > Now, people are not allowed to create runtime when no compatible java is configured in eclipse (JBIDE-14858). > But when adding server and runtime via runtime detection, server and runtime are added even though no compatible java is configured. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15189) Check compatible JRE/JDK when adding server via runtime detection

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15189?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-15189: ------------------------------------- In general, you have a new column in the dialog. If you click on this column, the problems will be listed below, and if you double-click the problem, it will attempt to resolve it for you (or ask you to help it resolve it). At this time, my roll-your-own quickfix only allows one possible resolution per error. This isn't a problem with the API but rather me not knowing how to properly display multiple possible solutions to a problem. Also, since we currently only really have one example, it's not necessary at the moment, since there's only one solution to adding a missing JRE. Things to test: 1) The popup dialog behaves as you'd expect. It disappears when you'd expect, and stays visible when you'd expect. This includes clicking around, pressing escape, using arrow keys and the enter key, etc. 2) The popup quickfix menu is resizable and appears in the exact position you'd expect. 3) The dialog that pops up to fix the issue has descriptive instructions Please only re-open this issue if a critical issue is found. If a small issue is found or a small improvement is suggested, please open a new issue. > Check compatible JRE/JDK when adding server via runtime detection > ----------------------------------------------------------------- > > Key: JBIDE-15189 > URL: https://issues.jboss.org/browse/JBIDE-15189 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: runtime-detection > Affects Versions: 4.1.0.CR1 > Reporter: Radim Hopp > Assignee: Rob Stryker > Fix For: 4.4.1.AM3 > > > Now, people are not allowed to create runtime when no compatible java is configured in eclipse (JBIDE-14858). > But when adding server and runtime via runtime detection, server and runtime are added even though no compatible java is configured. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15189) Check compatible JRE/JDK when adding server via runtime detection

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15189?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-15189. --------------------------------- Resolution: Done This is fixed (I think) ;) > Check compatible JRE/JDK when adding server via runtime detection > ----------------------------------------------------------------- > > Key: JBIDE-15189 > URL: https://issues.jboss.org/browse/JBIDE-15189 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: runtime-detection > Affects Versions: 4.1.0.CR1 > Reporter: Radim Hopp > Assignee: Rob Stryker > Fix For: 4.4.1.AM3 > > > Now, people are not allowed to create runtime when no compatible java is configured in eclipse (JBIDE-14858). > But when adding server and runtime via runtime detection, server and runtime are added even though no compatible java is configured. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22909) JavaModelException below FileSet.checkType (thrown in JavaElement.newNotPresentException)

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22909?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-22909: ----------------------------------------------- The problem most probably happens when build is on while the project is removed from the workspace (e.g. during Eclipse closing). Let us ignore exceptions caught in builder if the project for which the build goes is not accessible. > JavaModelException below FileSet.checkType (thrown in JavaElement.newNotPresentException) > ----------------------------------------------------------------------------------------- > > Key: JBIDE-22909 > URL: https://issues.jboss.org/browse/JBIDE-22909 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsf > Affects Versions: 4.3.1.Final > Reporter: Automated Error Reporting Bot > Assignee: Viacheslav Kabanovich > Fix For: 4.4.x > > > The following problem was reported via the automated error reporting: > Message: IntermediateMessageHandler [in WsRemoteEndpointImplBase$IntermediateMessageHandler.class [in org.apache.tomcat.websocket [in D:\sts-bundle\apache-tomcat-8.0.30\lib\tomcat-websocket.jar]]] does not exist > {noformat} > org.eclipse.jdt.core.JavaModelException: IntermediateMessageHandler [in WsRemoteEndpointImplBase$IntermediateMessageHandler.class [in org.apache.tomcat.websocket [in D:\sts-bundle\apache-tomcat-8.0.30\lib\tomcat-websocket.jar]]] does not exist > at org.eclipse.jdt.internal.core.JavaElement.newNotPresentException(JavaElement.java:556) > at org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(JavaElement.java:590) > at org.eclipse.jdt.internal.core.BinaryType.getElementInfo(BinaryType.java:287) > at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:302) > at org.eclipse.jdt.internal.core.BinaryType.isAnnotation(BinaryType.java:738) > at org.jboss.tools.jsf.jsf2.bean.scanner.FileSet.checkType(FileSet.java:80) > at org.jboss.tools.jsf.jsf2.bean.scanner.FileSet.add(FileSet.java:50) > at org.jboss.tools.jsf.jsf2.bean.build.JSF2ProjectBuilder.buildJars(JSF2ProjectBuilder.java:242) > at org.jboss.tools.jsf.jsf2.bean.build.JSF2ProjectBuilder.build(JSF2ProjectBuilder.java:143) > at org.jboss.tools.jst.web.kb.internal.KbBuilder.buildExtensionModels(KbBuilder.java:216) > at org.jboss.tools.jst.web.kb.internal.KbBuilder.build(KbBuilder.java:134) > at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:735) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:206) > at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:246) > at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:301) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:304) > at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:360) > at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:383) > at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:144) > at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:235) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {noformat} > Bundles: > | org.eclipse.core.jobs | 3.7.0.v20150330-2103 | 3.8.0.v20160509-0411 | > | org.eclipse.core.resources | 3.10.1.v20150725-1910 | 3.11.0.v20160503-1608 | > | org.eclipse.core.runtime | 3.11.1.v20150903-1804 | 3.12.0.v20160606-1342 | > | org.eclipse.jdt.core | 3.11.0.xx-201604081629-e45 | 3.12.0.v20160516-2131 | > | org.eclipse.jdt.ui | 3.11.2.v20151123-1510 | 3.11.2.v20151123-1510 | > | org.eclipse.jface.text | 3.10.0.v20150603-1752 | 3.11.0.v20160505-1301 | > | org.eclipse.wst.sse.ui | 1.3.401.v201510130005 | 1.3.500.v201605120129 | > | org.jboss.tools.common.el.core | 3.7.1.Final-v20160408-2358-B112 | 3.8.0.Final-v20160610-1533-B7 | > | org.jboss.tools.common.model | 3.7.1.Final-v20160408-2358-B112 | 3.8.0.Final-v20160610-1533-B7 | > | org.jboss.tools.common.validation | 3.7.1.Final-v20160408-2358-B112 | 3.8.0.Final-v20160610-1533-B7 | > | org.jboss.tools.jsf | 3.7.1.Final-v20160330-2256-B84 | 3.8.1.v20160607-2131 | > | org.jboss.tools.jst.web.kb | 3.7.1.Final-v20160331-0256-B96 | 3.8.1.v20160607-2115 | > Operating Systems: > | Linux | 3.2.0 | 4.6.4.fc23 | > | MacOSX | 10.10.5 | 10.11.6 | > | Windows | 6.1.0 | 10.0.0 | > The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/56fa9212e4b08ccb7b...] for the latest data. > Thank you for your assistance. > Your friendly error-reports-inbox. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3997) Upgrade to vagrant 1.8.1 and compatible virtual box 5.0.26

by Denis Golovin (JIRA)

Denis Golovin created JBDS-3997: ----------------------------------- Summary: Upgrade to vagrant 1.8.1 and compatible virtual box 5.0.26 Key: JBDS-3997 URL: https://issues.jboss.org/browse/JBDS-3997 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Task Components: platform-installer Affects Versions: 10.1.0.AM3 Reporter: Denis Golovin Assignee: Denis Golovin Fix For: 10.1.0.AM3 Originally we wanted to use Virtualbox 5.1.x, but vagrant 1.8.1 does not recognize Virtualbox 5.1.x and downloads 5.0.10 during vagrant up. This is the reason to change to 5.0.26 which works fine with recommended vagrant, -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22773) Openshift server adapter can't start with eap64-basic-s2i template on Windows: can't copy MANIFEST.MF reported

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22773?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22773: ----------------------------------- Sprint: devex #117 July 2016, devex #119 August 2016 (was: devex #117 July 2016, devex #118 July 2016) > Openshift server adapter can't start with eap64-basic-s2i template on Windows: can't copy MANIFEST.MF reported > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22773 > URL: https://issues.jboss.org/browse/JBIDE-22773 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, upstream > Affects Versions: 4.4.1.AM2 > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Critical > Labels: server > Fix For: 4.4.1.AM3 > > Attachments: screenshot-1.png > > > When starting the Openshift server adapter created from the eap64-basic-s2i template, the rsync phase reports the following error: > [^screenshot-1.png] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ERT-378) [JS Debugger] Need to prevent "Choose Tab for Debugging" dialog appearing [EBZ#499579]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-378: --------------------------------------- Summary: [JS Debugger] Need to prevent "Choose Tab for Debugging" dialog appearing [EBZ#499579] Key: ERT-378 URL: https://issues.jboss.org/browse/ERT-378 Project: Eclipse Release Train Issue Type: Task Components: JSDT Reporter: Friendly Jira Robot -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22966) create bzira fork that supports scraping RH bugzilla

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22966?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-22966: --------------------------------------------- btw. why is this jira suggesting a fork ? shouldn't the current bzira be fine for the new one as long as the config gets to be different ? > create bzira fork that supports scraping RH bugzilla > ---------------------------------------------------- > > Key: JBIDE-22966 > URL: https://issues.jboss.org/browse/JBIDE-22966 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.4.1.AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.1.Final > > > Sample issue to scrape: > https://bugzilla.redhat.com/show_bug.cgi?id=1363849 > More issues: > https://bugzilla.redhat.com/buglist.cgi?component=rh-eclipse46&list_id=56... > Target method: > * look for whiteboard = RHT (then filter by date since last change, as current bzira.py [1] does) > Mappings: > * BZ Product = Red Hat Software Collections --> RHECLIPSE jira > * BZ component = rh-eclipse46 (maybe others in future, eg., eclipse-cdt, eclipse-docker) --> same component in jira (python script will generate new components automatically) > * Version = rh-eclipse46 --> "rh-eclipse46" version in JIRA > * Target Milestone --> label in JIRA > * Target Release -> label in JIRA > [1] https://github.com/maxandersen/jiralint/blob/master/bzira.py -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22382) Use different icons for EAP server and Red Hat Central

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22382?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-22382: --------------------------------------------- the suggestion here brings us back to the "old" look that was overly colorful IMO - this would personally make me close it sooner, especially if it causes central to load slower :) in current form it is clean and non-invasive and fits with rest of the IDE. Can't we get some compromise that make it feel less like a big ad ? > Use different icons for EAP server and Red Hat Central > ------------------------------------------------------ > > Key: JBIDE-22382 > URL: https://issues.jboss.org/browse/JBIDE-22382 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: central, server > Affects Versions: 4.4.0.Alpha2 > Reporter: Marián Labuda > Assignee: Fred Bricon > Priority: Minor > Labels: respin-a > Fix For: 4.4.1.Final > > Attachments: central-rhd-icon.png, fullIDE.png, tools_rebrand.png > > > If there is an EAP server present in Servers view, workbench tool bar contains 2 same icons - Select a default server icon is same as Red Hat Central icon. We should make this explicitly different. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 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 August 2016