May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22386) Server Editor: Select different service takes too long

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22386?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-22386: ---------------------------------- Issue Type: Bug (was: Enhancement) > Server Editor: Select different service takes too long > ------------------------------------------------------ > > Key: JBIDE-22386 > URL: https://issues.jboss.org/browse/JBIDE-22386 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Labels: openshift_v3, server_editor > > Trying to select a different service for an OpenShift 3 Server Adapter in Server Editor takes too long. After click on the Select... button it takes ~2-3 seconds to open dialog to select a different service. It would be ok to take it that time if there would be some indication that something is happening, but there is no job while "something" is happening. > Also clicking on the button multiple times (if it is not responsible, I clicked again and again and again), it takes a bit longer and open multiple dialogs. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21848) NPE when extracting a zip using UnzipUtility

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21848?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-21848: --------------------------------------- [~rob.stryker], was there a way to reproduce this? I'm not sure when would you use unzip anywhere. > NPE when extracting a zip using UnzipUtility > -------------------------------------------- > > Key: JBIDE-21848 > URL: https://issues.jboss.org/browse/JBIDE-21848 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: common/jst/core > Affects Versions: 4.3.1.CR1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.3.1.CR1 > > > Error discovered when max attempted incremental publish preparing for demo. > Test case added. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21848) NPE when extracting a zip using UnzipUtility

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21848?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-21848: ---------------------------------- Summary: NPE when extracting a zip using UnzipUtility (was: NPE when extracgint a zip using UnzipUtility) > NPE when extracting a zip using UnzipUtility > -------------------------------------------- > > Key: JBIDE-21848 > URL: https://issues.jboss.org/browse/JBIDE-21848 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: common/jst/core > Affects Versions: 4.3.1.CR1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.3.1.CR1 > > > Error discovered when max attempted incremental publish preparing for demo. > Test case added. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21803) Dialog Add a Credential Domain allows create domain with empty name

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21803?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-21803. --------------------------------- I tried this in JBDS 9.1.0.GA and 10.0.0.Alpha1 nightly (jboss-devstudio-10.0.0.Alpha1-v20160518-1105-B5380-installer-standalone.jar) and I cannot create a domain with empty name, so closing. > Dialog Add a Credential Domain allows create domain with empty name > ------------------------------------------------------------------- > > Key: JBIDE-21803 > URL: https://issues.jboss.org/browse/JBIDE-21803 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.3.1.Beta2 > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Fix For: 4.3.1.CR1, 4.4.0.Alpha1 > > Attachments: AddDomainPromtsToSetName.png > > > Created domain object has null for name which later causes different NPE's (e.g. JBIDE-21795) and may make Credentials preference page unusable. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18951) jboss-web_8_0.xsd in AS XML catalog reported as "containing errors" by Luna

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18951?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-18951: ---------------------------------- Fix Version/s: (was: 4.3.1.CR1) > jboss-web_8_0.xsd in AS XML catalog reported as "containing errors" by Luna > --------------------------------------------------------------------------- > > Key: JBIDE-18951 > URL: https://issues.jboss.org/browse/JBIDE-18951 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server, upstream > Affects Versions: 4.2.0.Final > Environment: W7 Pro SP1 > eclipse.buildId=4.4.1.M20140925-0400 > org.jboss.tools.as.catalog (3.0.0.Final-v20141016-1911-B95) "JBoss AS XML Catalog Entries" > Reporter: Jordan Glassman > Assignee: Rob Stryker > Attachments: Capture4.PNG > > > In a jboss-web.xml file, a namespace declaration like: > {code} <jboss-web xmlns="http://www.jboss.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-web_8_0.xsd" version="8.0" > >{code} > Gives eclipse error: > {quote}Referenced file contains errors (jar:file:/C:/eclipse/plugins/org.jboss.tools.as.catalog_3.0.0.Final-v20141016-1911-B95.jar!/schema/xsd/jboss-web_8_0.xsd). > For more information, right click on the message in the Problems View and select "Show Details..."{quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22385) Show Console Output When Standard Out Changes toggle item is always triggered

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-22385: ------------------------------------- Summary: Show Console Output When Standard Out Changes toggle item is always triggered Key: JBIDE-22385 URL: https://issues.jboss.org/browse/JBIDE-22385 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 4.4.0.Alpha2 Reporter: Marián Labuda Tool item Show Console Output When Standard Out Changes placed in console view of rsync output is triggerable. If it is not triggered, console view should not be shown forcefully if different console view is opened. At the moment when I am having opened 2 console views, first one with log of an application pod and another one with rsync output for a server adapter, the pod log console view is forced to display rsync output even if the tool item is in the other console view (for rsync) not triggered. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22385) Show Console Output When Standard Out Changes toggle item is always triggered

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22385?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-22385: ---------------------------------- Labels: openshift_v3 (was: ) > Show Console Output When Standard Out Changes toggle item is always triggered > ----------------------------------------------------------------------------- > > Key: JBIDE-22385 > URL: https://issues.jboss.org/browse/JBIDE-22385 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Marián Labuda > Labels: openshift_v3 > > Tool item Show Console Output When Standard Out Changes placed in console view of rsync output is triggerable. If it is not triggered, console view should not be shown forcefully if different console view is opened. At the moment when I am having opened 2 console views, first one with log of an application pod and another one with rsync output for a server adapter, the pod log console view is forced to display rsync output even if the tool item is in the other console view (for rsync) not triggered. -- 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 Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3727?page=com.atlassian.jira.plugin.... ] Jan Richter commented on JBDS-3727: ----------------------------------- Why is this marked as platform-installer issue? It's an issue in the izpack 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: platform-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] (JBDS-3835) Installer: click on Download & install button doesn't do anything when recursively installation folder creation needed

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3835?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-3835. ----------------------------- Verified with B157. > Installer: click on Download & install button doesn't do anything when recursively installation folder creation needed > ---------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3835 > URL: https://issues.jboss.org/browse/JBDS-3835 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 9.1.0.CR1 > Reporter: Pavol Pitonak > Assignee: Denis Golovin > Priority: Critical > Labels: havoc > Fix For: 10.0.0.Alpha2 > > > # start the installer > # login > # set this path as installation folder: _c:\DeveloperPlatform\Platform01\Platform02\Platform03_ > # click _Continue_ > # click _Download & Install_ > result: > * nothing happens > * when you go back and change the path tho _c:\DeveloperPlatform_, it works fine > * might be related to JBDS-3816 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22384) Application Wizard: Skip revalidating of a connection if it is already established

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22384?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-22384: ---------------------------------- Labels: application_wizard openshift_v3 (was: ) > Application Wizard: Skip revalidating of a connection if it is already established > ---------------------------------------------------------------------------------- > > Key: JBIDE-22384 > URL: https://issues.jboss.org/browse/JBIDE-22384 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Marián Labuda > Labels: application_wizard, openshift_v3 > > When launching a New OpenShift Application wizard via shell menu File - New - OpenShift Application or via Red Hat Central, at first I am obliged to select an existing connection (or create a new one) and then proceed to New OpenShift Application wizard. At the moment, if I select an existing, already established connection (it is possible to work with it in OpenShift Explorer view, password/token has been filled in and is valid), it is still revalidated, what take some time (not too much but seems to be annoying for me every time opening the wizard). Also the connection is every time refreshed in OpenShift Explorer view once revalidation is finished. It would be nice if already established connections would not be revalidated again. -- 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