May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21068) Project wizard: Set maximum length for display name

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21068?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21068: ------------------------------------- Fix Version/s: 4.4.0.Alpha3 (was: 4.4.0.Alpha2) > Project wizard: Set maximum length for display name > --------------------------------------------------- > > Key: JBIDE-21068 > URL: https://issues.jboss.org/browse/JBIDE-21068 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Jan Richter > Priority: Minor > Labels: openshift_v3, project_wizard > Fix For: 4.4.0.Alpha3 > > > Currently the 'Display Name' text field has no length limit. OpenShift on the other hand will only allow fields of length up to 65536 characters. Would be nice to let the user only input a valid length string. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22378) Server editor: cannot edit the route

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22378?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22378: ------------------------------------- Fix Version/s: 4.4.0.Alpha3 (was: 4.4.0.Alpha2) > Server editor: cannot edit the route > ------------------------------------ > > Key: JBIDE-22378 > URL: https://issues.jboss.org/browse/JBIDE-22378 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Andre Dietisheim > Labels: openshift_v3, server_adapter_editor > Fix For: 4.4.0.Alpha3 > > Attachments: server-editor.png > > > The server editor wont allow the user to edit the route: > !server-editor.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21121) Port Forwarding: Warning/error dialog should pop up if there is no oc binary when opening Port forwarding dialog

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21121?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21121: ------------------------------------- Fix Version/s: 4.4.0.Alpha3 (was: 4.4.0.Alpha2) > Port Forwarding: Warning/error dialog should pop up if there is no oc binary when opening Port forwarding dialog > ---------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21121 > URL: https://issues.jboss.org/browse/JBIDE-21121 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Marián Labuda > Labels: openshift_v3, port_forwarding_wizard > Fix For: 4.4.0.Alpha3 > > > OpenShift 3 port forwarding features requires 'oc' binary to be set up in tooling. It's done in Workbench preference dialog on page OpenShift 3. If there is no 'oc' binary set and user invokes a port forwarding dialog, it is opened and even Start All button is enabled. User finds out that it is not possible to perform only when he gets an error message upon clicking on Start All button describing the problem. There could be some warning/error dialog popped up before opening a port forwarding dialog if there is no 'oc' location set in preferences. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22287) Test: Provide ability to run integration tests

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22287?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22287: ------------------------------------- Fix Version/s: 4.4.0.Alpha3 (was: 4.4.0.Alpha2) > Test: Provide ability to run integration tests > ---------------------------------------------- > > Key: JBIDE-22287 > URL: https://issues.jboss.org/browse/JBIDE-22287 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Andre Dietisheim > Fix For: 4.4.0.Alpha3 > > > We should provide the ability to run integration tests in a way that's separate from running pure unit tests. There already is at least 1 integration test that's run with the unit tests currently: [DockerHubRegistryTest|https://github.com/adietish/jbosstools-openshift/bl...]. We shoud separate this integration test (and the other ones that there might be?) and provide > * a specific maven profile for integration tests only > * a separate test suite -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22187) Connection wizard: Should not be able to create duplicate Openshift connections

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22187?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22187: ------------------------------------- Fix Version/s: 4.4.0.Alpha3 (was: 4.4.0.Alpha2) > Connection wizard: Should not be able to create duplicate Openshift connections > ------------------------------------------------------------------------------- > > Key: JBIDE-22187 > URL: https://issues.jboss.org/browse/JBIDE-22187 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Jeff MAURY > Assignee: Viacheslav Kabanovich > Priority: Minor > Labels: connection_wizard, openshift_v3 > Fix For: 4.4.0.Alpha3 > > > It is possible to create 2 identical Openshift connections (same url and credentials). They will appear as 2 tree items in the Openshift explorer but when you use various wizards, only a single items is show. I think we should not allow the creation of such identical connections as the name is composed of those elements. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22079) Import wizard: Error when import a project already existing in workspace

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22079?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22079: ------------------------------------- Fix Version/s: 4.4.0.Alpha3 (was: 4.4.0.Alpha2) > Import wizard: Error when import a project already existing in workspace > ------------------------------------------------------------------------ > > Key: JBIDE-22079 > URL: https://issues.jboss.org/browse/JBIDE-22079 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Labels: import_wizard, openshift_v3 > Fix For: 4.4.0.Alpha3 > > Attachments: import-error.png > > > When I am creating a new OpenShift application using an existing repo, or at least project in workspace, it throws an error upon application creation completion. This is a bit of pain, because even I have an existing git repo and checked the checkbox in Import Wizard to reuse it, it tries to import project then, but it fails. But the existing project is still usable to use it for a new OpenShift 3 server adapter and upon start of the adapter, local changes are published to OpenShift. This issue is just about error. Maybe we could display a dialog that such a project already exists in workspace and let user to choose to replace it by the one being imported or keep it as it is (if user know that the project in workspace is the correct one and he/she does not want to overwrite it and let local changes disappear). > Error: > {code}Could not import project from org.jboss.tools.openshift.internal.common.ui.application.importoperation.ImportFailedException: There was a maven related error that prevented us from importing the project. We encourage you to look into the pom in the cloned repository at /home/mlabuda/git/jboss-eap-quickstarts. > One of the possible reasons is that there is already a project in your workspace that matches the maven name of the OpenShift application. You can then rename your workspace project and start over again. > An exception stack trace is not available. > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3727) Installer fails with not normalized paths

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3727?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3727: --------------------------------- Component/s: installer (was: platform-installer) > Installer fails with not normalized paths > ----------------------------------------- > > Key: JBDS-3727 > URL: https://issues.jboss.org/browse/JBDS-3727 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Jan Richter > Assignee: Denis Golovin > Fix For: 10.0.0.Alpha3 > > > The installer accepts installation paths with the following format: > {noformat}/home/jrichter/Downloads/xyz/../abdc/../temp/../temp{noformat} > With such a path it fails immediately after the installation starts with the following exception: > {noformat}java.io.FileNotFoundException: /home/jrichter/Downloads/xyz/../abdc/../temp/../temp/JBoss-EULA.html (No such file or directory) > at java.io.FileOutputStream.open0(Native Method) > at java.io.FileOutputStream.open(FileOutputStream.java:270) > at java.io.FileOutputStream.<init>(FileOutputStream.java:213) > at java.io.FileOutputStream.<init>(FileOutputStream.java:162) > at com.izforge.izpack.installer.Unpacker.run(Unpacker.java:448) > at java.lang.Thread.run(Thread.java:745){noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22392) Aerogear New and Noteworthy for 4.4.0.Alpha2

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22392?page=com.atlassian.jira.plugi... ] Alexey Kazakov closed JBIDE-22392. ---------------------------------- Resolution: Rejected No N&N in that release. > Aerogear New and Noteworthy for 4.4.0.Alpha2 > -------------------------------------------- > > Key: JBIDE-22392 > URL: https://issues.jboss.org/browse/JBIDE-22392 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: aerogear-hybrid > Reporter: Alexey Kazakov > Assignee: Gorkem Ercan > Priority: Critical > Fix For: 4.4.0.Alpha2 > > > 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 Aerogear is not listed here check if there are issues that should be added and add them. > Document the ones relevant for Aerogear by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pull request. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22401) javascript New and Noteworthy for 4.4.0.Alpha2

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22401?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-22401: ---------------------------------------- cc: [~ibuziuk] > javascript New and Noteworthy for 4.4.0.Alpha2 > ---------------------------------------------- > > Key: JBIDE-22401 > URL: https://issues.jboss.org/browse/JBIDE-22401 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: javascript, nodejs > Reporter: Alexey Kazakov > Assignee: Victor Rubezhny > Priority: Critical > Fix For: 4.4.0.Alpha2 > > > 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 javascript is not listed here check if there are issues that should be added and add them. > Document the ones relevant for javascript by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pull request. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22411) update TPs to latest Docker/Vagrant tooling

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22411?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22411: ------------------------------- Summary: update TPs to latest Docker/Vagrant tooling (was: update to latest Docker/Vagrant tooling) > update TPs to latest Docker/Vagrant tooling > ------------------------------------------- > > Key: JBIDE-22411 > URL: https://issues.jboss.org/browse/JBIDE-22411 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: docker > Affects Versions: 4.4.0.Alpha2 > Reporter: Nick Boldt > Fix For: 4.4.0.Alpha3 > > > Latest Docker tooling from Linux Tools can be found at: http://download.eclipse.org/linuxtools/update-neon-docker-rc1 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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