April 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-16874) OpenShift Explorer: Domain URL has last letter in different color

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16874?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-16874: ------------------------------------------ corrected the decoration: !Corrected-domain-decoration.png! > OpenShift Explorer: Domain URL has last letter in different color > ----------------------------------------------------------------- > > Key: JBIDE-16874 > URL: https://issues.jboss.org/browse/JBIDE-16874 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Beta1 > Environment: Fedora 19, 64-bit, java version "1.7.0_51", OpenJDK Runtime Environment (fedora-2.4.5.0.fc19-x86_64 u51-b31) > Reporter: Michelle Murray > Priority: Minor > Labels: explorer > Fix For: 4.2.0.Beta2 > > Attachments: Corrected-domain-decoration.png, OpenShift_boldcom.png > > > Final letter of .com for domain URLs is a different colour. > !OpenShift_boldcom.png! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16874) OpenShift Explorer: Domain URL has last letter in different color

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16874?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-16874: ------------------------------------- Attachment: Corrected-domain-decoration.png > OpenShift Explorer: Domain URL has last letter in different color > ----------------------------------------------------------------- > > Key: JBIDE-16874 > URL: https://issues.jboss.org/browse/JBIDE-16874 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Beta1 > Environment: Fedora 19, 64-bit, java version "1.7.0_51", OpenJDK Runtime Environment (fedora-2.4.5.0.fc19-x86_64 u51-b31) > Reporter: Michelle Murray > Priority: Minor > Labels: explorer > Fix For: 4.2.0.Beta2 > > Attachments: Corrected-domain-decoration.png, OpenShift_boldcom.png > > > Final letter of .com for domain URLs is a different colour. > !OpenShift_boldcom.png! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17210) where is our nightly site OR why is nightly site not actually built regularly?

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17210?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-17210: --------------------------------------------- Yes [~mickael_istria] it is uptodate because I did what I wrote: "p.s. i'm going to kick of a build so we get some fixes into the nightly." Look at the build history - https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossTools/view/JBo... last build before one I kicked of was 6 days ago. build 8748 was back in March 31 and build is now at build 8754 - there have only been 6 builds for close to a month. I'm not saying this aggregate needs to run faster - but i'm asking how we get a nightly site again. > where is our nightly site OR why is nightly site not actually built regularly? > ------------------------------------------------------------------------------ > > Key: JBIDE-17210 > URL: https://issues.jboss.org/browse/JBIDE-17210 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Max Rydahl Andersen > > http://download.jboss.org/jbosstools/updates/nightly/core/master > our official "nightly" updatesite has not been rebuilt for ~6 days at the time of writing. > see https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossTools/view/JBo... > Why is this ? > Is there another site that can be used as "nightly" ? i.e. one that just composites instead of aggregates ? > p.s. i'm going to kick of a build so we get some fixes into the nightly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-273) Fix blog link for JBTIS 4.1.4.Final in jbosstools-website

by Paul Leacu (JIRA)

Paul Leacu created JBTIS-273: -------------------------------- Summary: Fix blog link for JBTIS 4.1.4.Final in jbosstools-website Key: JBTIS-273 URL: https://issues.jboss.org/browse/JBTIS-273 Project: JBoss Tools Integration Stack Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.1.4.Final Reporter: Paul Leacu Assignee: Paul Leacu Fix blog link for JBTIS 4.1.4.Final in jbosstools-website -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16883) Broken UI logic in Hybrid Mobile/ Engine properties

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16883?page=com.atlassian.jira.plugi... ] Vlado Pakan edited comment on JBIDE-16883 at 4/29/14 8:42 AM: -------------------------------------------------------------- Case 1: I agree with you it works the same way as Installed JREs properties Case 2: I will verify with 4.2.0.Beta2 build when available. Regarding Progress Bar if it has just 2 values it's actually not Progress Bar we should use another kind of animation because it's confusing for user to see nothing happening in progress bar even there is ongoing download. Case 3: It's OK to remove downloaded engine from UI but not ok to remove it from hard drive. JRE dialog is not removing JRE from hard drive. And in case user remove JRE and then close dialog via Cancel button JRE is not removed. When JRE dialog is reopen user can see there were no JRE removed otherwise buttons OK and Cancel have no sense. Case 4: I will verify with 4.2.0.Beta2 build when available. Case 5: created issue JBIDE-17214 was (Author: vpakan): Case 1: I agree with you it works the same way as Installed JREs properties Case 2: I will verify with 4.2.0.Beta2 build when available. Regarding Progress Bar if it has just 2 values it's actually not Progress Bar we should use another kind of animation because it's confusing for user to see nothing happening in progress bar even there is ongoing download. Case 3: It's OK to remove downloaded engine from UI but not ok to remove it from hard drive. JRE dialog is not removing JRE from hard drive. And in case user remove JRE and then close dialog via Cancel button JRE is not removed. When JRE dialog is reopen user can see there were no JRE removed Case 4: I will verify with 4.2.0.Beta2 build when available. Case 5: created issue JBIDE-17214 > Broken UI logic in Hybrid Mobile/ Engine properties > --------------------------------------------------- > > Key: JBIDE-16883 > URL: https://issues.jboss.org/browse/JBIDE-16883 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.2.0.Beta1 > Environment: JBDS 8.0.0.Beta1-v20140323-1410-B78, Linux > Reporter: Vlado Pakan > Assignee: Gorkem Ercan > Priority: Critical > Fix For: 4.2.0.Beta2 > > Attachments: enginesearch.png > > > Case 0: > 1. Open Window > Preferences > Hybrid Mobile > Engines with no engines defined > 2. Resize Preferences window > ERROR: Engine table is not resized > Case 1: > 1. Open Window > Preferences > Hybrid Mobile > Engines with no engines defined > 2. Click on another Preferences tree item > ERROR: It's not possible to select another preferences. Error dialog is displayed saying: "The currently displayed page contains invalid values" > Case 2: > 1. Use this preferences dialog to download Hybrid Mobile engine > ERROR: Displayed Progress Bar has only two values 0% and 100% there is no progress change during downloading > ERROR: OK button within Download Hybrid Mobile Engine dialog should be enabled only when version and at least one platform is selected > ERROR: When first engine is downloaded it should be marked as default automatically > ERROR: While downloading OK button, Version Combo and Platform Table are is still enabled > Case 3: > 1. Remove all downloaded engines by clicking on button Remove > ERROR: Engines are removed immediately after Remove button is clicked. They should be really removed when button OK is pushed > ERROR: Once there is no engine in dialog error from Case 1 happens > Case 4: > 1. Remove all downloaded engines > 2. Reopen preferences dialog > 3. Download engine > 4. Check downloaded engine as default > ERROR: Button OK is still disabled. > 5. Uncheck default button > 6. Check default button > 7. OK button is enabled and it's possible to click on it > Case 5: > 1. Download at least 1 engine > 2. Search for engine on local file system more times using the same directory > ERROR: Platform in table is "Android Android ..." > 3. Click on i image in third column > ERROR: It shows more than one line with engine location and shows incorrect location for files found on local file system not downloaded from repo > !enginesearch.png! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17214) Wrong tooltip on info column of Engines table in Hybrid Mobile preferences

by Vlado Pakan (JIRA)

Vlado Pakan created JBIDE-17214: ----------------------------------- Summary: Wrong tooltip on info column of Engines table in Hybrid Mobile preferences Key: JBIDE-17214 URL: https://issues.jboss.org/browse/JBIDE-17214 Project: Tools (JBoss Tools) Issue Type: Bug Components: aerogear-hybrid Affects Versions: 4.2.0.Beta1 Reporter: Vlado Pakan Fix For: 4.2.0.Beta2 See Case 5: within linked issue JBIDE-16883 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16883) Broken UI logic in Hybrid Mobile/ Engine properties

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16883?page=com.atlassian.jira.plugi... ] Vlado Pakan commented on JBIDE-16883: ------------------------------------- Case 1: I agree with you it works the same way as Installed JREs properties Case 2: I will verify with 4.2.0.Beta2 build when available. Regarding Progress Bar if it has just 2 values it's actually not Progress Bar we should use another kind of animation because it's confusing for user to see nothing happening in progress bar even there is ongoing download. Case 3: It's OK to remove downloaded engine from UI but not ok to remove it from hard drive. JRE dialog is not removing JRE from hard drive. And in case user remove JRE and then close dialog via Cancel button JRE is not removed. When JRE dialog is reopen user can see there were no JRE removed Case 4: I will verify with 4.2.0.Beta2 build when available. Case 5: created issue JBIDE-17214 > Broken UI logic in Hybrid Mobile/ Engine properties > --------------------------------------------------- > > Key: JBIDE-16883 > URL: https://issues.jboss.org/browse/JBIDE-16883 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.2.0.Beta1 > Environment: JBDS 8.0.0.Beta1-v20140323-1410-B78, Linux > Reporter: Vlado Pakan > Assignee: Gorkem Ercan > Priority: Critical > Fix For: 4.2.0.Beta2 > > Attachments: enginesearch.png > > > Case 0: > 1. Open Window > Preferences > Hybrid Mobile > Engines with no engines defined > 2. Resize Preferences window > ERROR: Engine table is not resized > Case 1: > 1. Open Window > Preferences > Hybrid Mobile > Engines with no engines defined > 2. Click on another Preferences tree item > ERROR: It's not possible to select another preferences. Error dialog is displayed saying: "The currently displayed page contains invalid values" > Case 2: > 1. Use this preferences dialog to download Hybrid Mobile engine > ERROR: Displayed Progress Bar has only two values 0% and 100% there is no progress change during downloading > ERROR: OK button within Download Hybrid Mobile Engine dialog should be enabled only when version and at least one platform is selected > ERROR: When first engine is downloaded it should be marked as default automatically > ERROR: While downloading OK button, Version Combo and Platform Table are is still enabled > Case 3: > 1. Remove all downloaded engines by clicking on button Remove > ERROR: Engines are removed immediately after Remove button is clicked. They should be really removed when button OK is pushed > ERROR: Once there is no engine in dialog error from Case 1 happens > Case 4: > 1. Remove all downloaded engines > 2. Reopen preferences dialog > 3. Download engine > 4. Check downloaded engine as default > ERROR: Button OK is still disabled. > 5. Uncheck default button > 6. Check default button > 7. OK button is enabled and it's possible to click on it > Case 5: > 1. Download at least 1 engine > 2. Search for engine on local file system more times using the same directory > ERROR: Platform in table is "Android Android ..." > 3. Click on i image in third column > ERROR: It shows more than one line with engine location and shows incorrect location for files found on local file system not downloaded from repo > !enginesearch.png! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17213) Improve the default value of Download folder in the download runtimes wizard

by Lars Heinemann (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17213?page=com.atlassian.jira.plugi... ] Lars Heinemann commented on JBIDE-17213: ---------------------------------------- On Kubuntu the value of java.io.tmpdir is "/tmp" which makes not big sense. So we should somehow test for that and use a fallback folder if its not writable. Updated the issue text. > Improve the default value of Download folder in the download runtimes wizard > ---------------------------------------------------------------------------- > > Key: JBIDE-17213 > URL: https://issues.jboss.org/browse/JBIDE-17213 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: runtime-detection > Affects Versions: 4.2.0.Beta1 > Environment: Kubuntu 13.10 > Reporter: Lars Heinemann > Attachments: jbt_downloadruntime.png > > > The download folder defaults to /tmp folder. That is on Kubuntu and maybe Ubuntu as well a bad choice as only root can write to that folder. The folder /var/tmp/ is the better choice on this OS. > I would propose to use java.io.tmpdir for the default value if possible and check if that is writable for the user. If thats not the case we should have some fallback folder. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17213) Improve the default value of Download folder in the download runtimes wizard

by Lars Heinemann (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17213?page=com.atlassian.jira.plugi... ] Lars Heinemann updated JBIDE-17213: ----------------------------------- Description: The download folder defaults to /tmp folder. That is on Kubuntu and maybe Ubuntu as well a bad choice as only root can write to that folder. The folder /var/tmp/ is the better choice on this OS. I would propose to use java.io.tmpdir for the default value if possible and check if that is writable for the user. If thats not the case we should have some fallback folder. was: The download folder defaults to /tmp folder. That is on Kubuntu and maybe Ubuntu as well a bad choice as only root can write to that folder. The folder /var/tmp/ is the better choice on this OS. I would propose to use java.io.tmpdir for the default value if possible. > Improve the default value of Download folder in the download runtimes wizard > ---------------------------------------------------------------------------- > > Key: JBIDE-17213 > URL: https://issues.jboss.org/browse/JBIDE-17213 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: runtime-detection > Affects Versions: 4.2.0.Beta1 > Environment: Kubuntu 13.10 > Reporter: Lars Heinemann > Attachments: jbt_downloadruntime.png > > > The download folder defaults to /tmp folder. That is on Kubuntu and maybe Ubuntu as well a bad choice as only root can write to that folder. The folder /var/tmp/ is the better choice on this OS. > I would propose to use java.io.tmpdir for the default value if possible and check if that is writable for the user. If thats not the case we should have some fallback folder. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17213) Improve the default value of Download folder in the download runtimes wizard

by Lars Heinemann (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17213?page=com.atlassian.jira.plugi... ] Lars Heinemann updated JBIDE-17213: ----------------------------------- Attachment: jbt_downloadruntime.png The text area below also look a bit weird. > Improve the default value of Download folder in the download runtimes wizard > ---------------------------------------------------------------------------- > > Key: JBIDE-17213 > URL: https://issues.jboss.org/browse/JBIDE-17213 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: runtime-detection > Affects Versions: 4.2.0.Beta1 > Environment: Kubuntu 13.10 > Reporter: Lars Heinemann > Attachments: jbt_downloadruntime.png > > > The download folder defaults to /tmp folder. That is on Kubuntu and maybe Ubuntu as well a bad choice as only root can write to that folder. The folder /var/tmp/ is the better choice on this OS. > I would propose to use java.io.tmpdir for the default value if possible. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 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 April 2014