May 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3261) JSR-356: Websockets. Import, build, run on server

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3261?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3261: ------------------------------------------- [~mlabuda] what example are you using ? and is this not just the old issue of arunguptas repo currently require groovy (for no real good reason) ? These are bugs and issues but not related to websocket afaics.Should be opened as separate issue. Have you tried using http://www.jboss.org//quickstarts/eap/websocket-hello/index.html ? > JSR-356: Websockets. Import, build, run on server > ------------------------------------------------- > > Key: JBDS-3261 > URL: https://issues.jboss.org/browse/JBDS-3261 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: requirements, webservices > Reporter: Burr Sutter > Assignee: Xavier Coulon > Priority: Critical > Labels: websockets > Fix For: 9.0.0.Beta1 > > > Support for import (without error), build, Run on Server and Debug on Server. > https://github.com/javaee-samples/javaee7-samples/tree/master/websocket -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19875) server New and Noteworthy for 4.3.0.Beta1

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19875?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19875: --------------------------------------------- I've commented on the blog (good stuff), but please do also add basic screenshot to NN (can use the one from the blog) with a small description. > server New and Noteworthy for 4.3.0.Beta1 > ----------------------------------------- > > Key: JBIDE-19875 > URL: https://issues.jboss.org/browse/JBIDE-19875 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: archives, jmx, server > Reporter: Max Rydahl Andersen > Priority: Critical > Fix For: 4.3.0.Beta1 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If server is not listed here check if there are issues that should be added and add them. > Document the ones relevant for server by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19852) Set default path for runtimes downloaded and installed via java -jar

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19852?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-19852: --------------------------------------- [~rob.stryker], you may have missed the second part - if the user changes the installation path in the installer, it would be nice if the tooling noticed this and still added the right path. But this may be even harder than the first part. I think ideally the installation path selection should be skipped in the installer since you already chose your path in the tooling. > Set default path for runtimes downloaded and installed via java -jar > -------------------------------------------------------------------- > > Key: JBIDE-19852 > URL: https://issues.jboss.org/browse/JBIDE-19852 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: runtime-detection, server > Affects Versions: 4.3.0.Alpha2 > Reporter: Radim Hopp > > I'm not sure if this is possible, but it would be nice if the installer would fill the installation path from Download Runtime wizard. > The same for runtime detection after the download and installation is finished. > Example scenario: > 1. Select JBoss DV 6.1 for download&installation > 2. On "Download Runtime" page of wizard fill some install folder (for example /home/<user>/downloadedDV) > 3. Click Finish - DV is downloaded and it's installer executed > ASSERT: /home/<user>/downloadedDV is default installation path in installer > 4. In the installer select different installation folder (for example /home/<user>/DV) > 5. Finish installer > ASSERT: /home/<user>/DV is added to runtime-detection paths instead of /home/<user>/downloadedDV -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19787) As a user I want to import existing OpenShift projects into my Eclipse workspace

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19787?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19787: ------------------------------------- Fix Version/s: 4.3.0.Beta1 > As a user I want to import existing OpenShift projects into my Eclipse workspace > -------------------------------------------------------------------------------- > > Key: JBIDE-19787 > URL: https://issues.jboss.org/browse/JBIDE-19787 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.3.0.Beta1 > > > This is the case where a user has added resources via the CLI or console and wants to create an Eclipse project in order to start developing. > The Eclipse project nature will be of the appropriate type as inferred from the source. > Main focus is to correctly import java/maven projects or “General” project otherwise. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19787) As a user I want to import existing OpenShift projects into my Eclipse workspace

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19787?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19787: ------------------------------------- Sprint: Sprint #4 May 2015 > As a user I want to import existing OpenShift projects into my Eclipse workspace > -------------------------------------------------------------------------------- > > Key: JBIDE-19787 > URL: https://issues.jboss.org/browse/JBIDE-19787 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.3.0.Beta1 > > > This is the case where a user has added resources via the CLI or console and wants to create an Eclipse project in order to start developing. > The Eclipse project nature will be of the appropriate type as inferred from the source. > Main focus is to correctly import java/maven projects or “General” project otherwise. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19711) WTP servertools integration with CDT launchbar

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19711?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19711: --------------------------------------------- is it not in Eclipse Mars RC1 or RC2 ? if not then where is this targeted to be included ? SR1 ? Then we'll have to wait after Mars GA's to start using SR1 builds. > WTP servertools integration with CDT launchbar > ---------------------------------------------- > > Key: JBIDE-19711 > URL: https://issues.jboss.org/browse/JBIDE-19711 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server, upstream > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.3.0.Beta1 > > Attachments: JBIDE-19711.png > > > CDT has a new framework called Launchbar https://wiki.eclipse.org/CDT/LaunchBar > Integrating this with servertools, proof of concept, to see how feasible it is. > Relevant bugzillas upstream: > https://bugs.eclipse.org/bugs/show_bug.cgi?id=466786 > https://bugs.eclipse.org/bugs/show_bug.cgi?id=466660 > https://bugs.eclipse.org/bugs/show_bug.cgi?id=466658 > https://bugs.eclipse.org/bugs/show_bug.cgi?id=466490 > https://bugs.eclipse.org/bugs/show_bug.cgi?id=466489 > https://bugs.eclipse.org/bugs/show_bug.cgi?id=466488 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19804) Select folder dialog problem

by Lucia Jelinkova (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19804?page=com.atlassian.jira.plugi... ] Lucia Jelinkova commented on JBIDE-19804: ----------------------------------------- Well, at first I thought it might be connected to easyimport but then I saw the dialog also elsewhere so I am closing this issue since it is not connected to our component. > Select folder dialog problem > ---------------------------- > > Key: JBIDE-19804 > URL: https://issues.jboss.org/browse/JBIDE-19804 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: easymport > Affects Versions: 4.3.0.Beta1 > Reporter: Lucia Jelinkova > Attachments: dialog.png, video.avi > > > Sometimes (but not allways, maybe 1 out of 5 times) I got the problem that when I want to choose the folder to open, the dialog is open and after some time it is interrupted with some other dialog for really small time (you can only see it blink). After that you need to click OK several times to make the dialog response (maybe only wait would be OK). > I captured this on the video (attached) but due to the poor quality you cannot actually see the dialog (the blink is around second 10). However, I managed to make a screenshot from higher-quality video I have on my computer. > It seems it is an OOmph dialog so I am not sure it really relates to the easy import component at all. But maybe you do work with Preferences and could avoid the OOmph invokation. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19804) Select folder dialog problem

by Lucia Jelinkova (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19804?page=com.atlassian.jira.plugi... ] Lucia Jelinkova closed JBIDE-19804. ----------------------------------- Resolution: Rejected > Select folder dialog problem > ---------------------------- > > Key: JBIDE-19804 > URL: https://issues.jboss.org/browse/JBIDE-19804 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: easymport > Affects Versions: 4.3.0.Beta1 > Reporter: Lucia Jelinkova > Attachments: dialog.png, video.avi > > > Sometimes (but not allways, maybe 1 out of 5 times) I got the problem that when I want to choose the folder to open, the dialog is open and after some time it is interrupted with some other dialog for really small time (you can only see it blink). After that you need to click OK several times to make the dialog response (maybe only wait would be OK). > I captured this on the video (attached) but due to the poor quality you cannot actually see the dialog (the blink is around second 10). However, I managed to make a screenshot from higher-quality video I have on my computer. > It seems it is an OOmph dialog so I am not sure it really relates to the easy import component at all. But maybe you do work with Preferences and could avoid the OOmph invokation. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19851) Cannot refresh environment variable(s) for an OpenShift application

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19851?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19851: ------------------------------------- Fix Version/s: 4.3.0.Beta1 > Cannot refresh environment variable(s) for an OpenShift application > ------------------------------------------------------------------- > > Key: JBIDE-19851 > URL: https://issues.jboss.org/browse/JBIDE-19851 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Marián Labuda > Priority: Minor > Labels: environment_variables > Fix For: 4.3.0.Beta1 > > > In Manage Application Environment Variable shell opened either via servers adapter or OpenShift Explorer view are listed environment variables for a specific application. Refresh button should refresh state of variables according to state on a server, but click on Refresh button shows following error dialog with following stack in log: > {code} > com.openshift.client.OpenShiftSSHOperationException: Failed to execute remote ssh command "eapapp" > at com.openshift.internal.client.ApplicationResource.sshExecCmd(ApplicationResource.java:892) > at com.openshift.internal.client.ApplicationResource.loadPorts(ApplicationResource.java:860) > at com.openshift.internal.client.ApplicationResource.refresh(ApplicationResource.java:634) > at org.jboss.tools.openshift.express.internal.ui.wizard.environment.EditEnvironmentVariablesWizardModel.refreshEnvironmentVariables(EditEnvironmentVariablesWizardModel.java:35) > at org.jboss.tools.openshift.express.internal.ui.wizard.environment.EnvironmentVariablesWizardPage$RefreshEnvironmentVariablesJob.doRun(EnvironmentVariablesWizardPage.java:292) > at org.jboss.tools.openshift.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:36) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > Caused by: com.jcraft.jsch.JSchException: session is down > at com.jcraft.jsch.Session.openChannel(Session.java:844) > at com.openshift.internal.client.ApplicationResource.sshExecCmd(ApplicationResource.java:885) > ... 6 more > {code} > Otherwise adding, editing and removing environment variables work OK. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19845) Creating a new OpenShift application via Configure context menu of a project always use first connection from OpenShift Explorer view

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19845?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19845: ------------------------------------- Fix Version/s: 4.3.0.Beta1 > Creating a new OpenShift application via Configure context menu of a project always use first connection from OpenShift Explorer view > ------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19845 > URL: https://issues.jboss.org/browse/JBIDE-19845 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Priority: Critical > Labels: application_wizard > Fix For: 4.3.0.Beta1 > > > If user wants to create a new OpenShift application via context menu of a project, it is possible to do it via context menu "Configure - New/Import OpenShift application". Previously this selection prompted user to choose desired connection where to create a new application. Nowadays the first existing connection in OpenShift explorer view is selected and it is not possible to change connection. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 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 May 2015