June 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19583) Explorer: exception for v3 connection is not fully shown

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19583?page=com.atlassian.jira.plugi... ] Andre Dietisheim resolved JBIDE-19583. -------------------------------------- Resolution: Done > Explorer: exception for v3 connection is not fully shown > -------------------------------------------------------- > > Key: JBIDE-19583 > URL: https://issues.jboss.org/browse/JBIDE-19583 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: explorer > Fix For: 4.3.0.Beta1 > > Attachments: connection-refused.png, missing-exception-details.png > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19100) On RHEL7 (JBT and JBDS) tooltips appear as dark text on a dark background

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19100?page=com.atlassian.jira.plugi... ] Snjezana Peco updated JBIDE-19100: ---------------------------------- Fix Version/s: 4.3.x (was: 4.3.0.Beta1) > On RHEL7 (JBT and JBDS) tooltips appear as dark text on a dark background > ------------------------------------------------------------------------- > > Key: JBIDE-19100 > URL: https://issues.jboss.org/browse/JBIDE-19100 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cleanup > Affects Versions: 4.2.2.Final > Environment: RHEL7 > Reporter: Len DiMaggio > Assignee: Snjezana Peco > Fix For: 4.3.x > > Attachments: JBDS8_RHEL7_vnc.png, RHEL7_devtoolset3_JBT422_QS_Tooltip.png > > > On RHEL7, some tooltips - for example - the notice displayed when updates to Tools/JBDS are available and the information relating to quickstarts as displayed in Central are shown as dark text on a dark background. See attached screenshots. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19583) Explorer: exception for v3 connection is not fully shown

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19583?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-19583: ---------------------------------------- Assignee: Andre Dietisheim > Explorer: exception for v3 connection is not fully shown > -------------------------------------------------------- > > Key: JBIDE-19583 > URL: https://issues.jboss.org/browse/JBIDE-19583 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: explorer > Fix For: 4.3.0.Beta1 > > Attachments: missing-exception-details.png > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19583) Explorer: exception for v3 connection is not fully shown

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19583?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-19583: ------------------------------------------ this was fixed with some change I cannot identify: !connection-refused.png! > Explorer: exception for v3 connection is not fully shown > -------------------------------------------------------- > > Key: JBIDE-19583 > URL: https://issues.jboss.org/browse/JBIDE-19583 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: explorer > Fix For: 4.3.0.Beta1 > > Attachments: missing-exception-details.png > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19362) Garbled text in forge list when SWT_GTK3 is true

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19362?page=com.atlassian.jira.plugi... ] Snjezana Peco resolved JBIDE-19362. ----------------------------------- Resolution: Done > Garbled text in forge list when SWT_GTK3 is true > ------------------------------------------------ > > Key: JBIDE-19362 > URL: https://issues.jboss.org/browse/JBIDE-19362 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge, upstream > Affects Versions: 4.3.0.Alpha1 > Reporter: Pavol Srna > Assignee: Snjezana Peco > Fix For: 4.3.0.Beta1 > > Attachments: garbled-text.png > > > This is probably an older eclipse issue with GTK3 [1]. But if we can find some workaround for forge it would be nice. > [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=446075 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16071) Duplicate cheat sheet options in Project Examples Preferences

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16071?page=com.atlassian.jira.plugi... ] Snjezana Peco updated JBIDE-16071: ---------------------------------- Fix Version/s: 4.3.0.Beta2 (was: 4.3.0.Beta1) > Duplicate cheat sheet options in Project Examples Preferences > ------------------------------------------------------------- > > Key: JBIDE-16071 > URL: https://issues.jboss.org/browse/JBIDE-16071 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.1.1.CR1 > Reporter: Michelle Murray > Assignee: Snjezana Peco > Fix For: 4.3.0.Beta2 > > Attachments: Central_cheatsheet.png > > > Click Window > Preferences > JBoss Tools > Project Examples. > The check box options include 'show readme/cheatsheet file' and then further down specifically for cheat sheets radio buttons for cheat sheet behavior. > !Central_cheatsheet.png! > I think the labelling of 'show readme/cheatsheet file' is left over from earlier. With the new cheat sheet functionality, I think that option should just read 'show readme file'. And then the radio button 'Always show' etc. deal with cheat sheets. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19604) Save Password in New Openshift Application Wizard is annoying

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19604?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19604: ------------------------------------- Sprint: Sprint #2 April 2015, Sprint #3 May 2015 (was: Sprint #2 April 2015, Sprint #3 May 2015, Sprint #4 May 2015) > Save Password in New Openshift Application Wizard is annoying > ------------------------------------------------------------- > > Key: JBIDE-19604 > URL: https://issues.jboss.org/browse/JBIDE-19604 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Environment: Linux, x86_64, Open JDK 7 > Reporter: Denis Golovin > Assignee: Andre Dietisheim > Fix For: 4.3.0.Beta2 > > Attachments: openshif-save-password.mp4 > > > Selected "Save Password" option in wizard triggers secure storage login that cannot be canceled in on click. This dialog keeps coming back after Cancel is pressed (three or more times). After reopening wizard first Security Storage Login pops up that I have to Cancel it several times (see attached video). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19146) Make sure new tooling can restore a workspace that was created with JBT 4.2.0.Final

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19146?page=com.atlassian.jira.plugi... ] Andre Dietisheim resolved JBIDE-19146. -------------------------------------- Resolution: Done tested with JBDS8 workspace, had the v2 connection in the new tooling. > Make sure new tooling can restore a workspace that was created with JBT 4.2.0.Final > ----------------------------------------------------------------------------------- > > Key: JBIDE-19146 > URL: https://issues.jboss.org/browse/JBIDE-19146 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.3.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.3.0.Beta1 > > > We have to make sure that the new tooling (with the new plugins and the code reorg in JBIDE-19048) can restore a workspace that was created with JBT 4.2.0.Final / JBDS 8.0.0: > - restore opened views (explorer) > - restore connections > - restore server editor(s) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19924) For JBIDE 4.3.0.Beta1: Code Freeze + Branch [Birt]

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19924?page=com.atlassian.jira.plugi... ] Snjezana Peco reassigned JBIDE-19924: ------------------------------------- Assignee: Snjezana Peco > For JBIDE 4.3.0.Beta1: Code Freeze + Branch [Birt] > -------------------------------------------------- > > Key: JBIDE-19924 > URL: https://issues.jboss.org/browse/JBIDE-19924 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: birt > Reporter: Nick Boldt > Assignee: Snjezana Peco > Priority: Blocker > Labels: task > Fix For: 4.3.0.Beta1 > > > For JBIDE 4.3.0.Beta1 [Birt]: Please perform the following tasks: > 0. If nothing has changed in your component since the creation of the 4.2.x branch (eg., Portal, Freemarker), *{color:red}Reject this JIRA{color}*. > Otherwise: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Beta1 > [Unresolved JIRAs with fixVersion = 4.3.0.Beta1, 9.0.0.Beta1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...] > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0, or from 1.2.2 to 1.2.100. > *NOTE:* If you already did this for your master branch, you do *not* need to do so again. Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.2.x branch. > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT > {code} > 2. Update your root pom to use parent pom version 4.3.0.Beta1-SNAPSHOT; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.0.Beta1-SNAPSHOT</version> > </parent> > {code} > 3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Beta1; > {code} > mvn clean verify -Dtpc.version=4.50.0.Beta1-SNAPSHOT # (if the TP is still a SNAPSHOT) > or > mvn clean verify -Dtpc.version=4.50.0.Beta1 # (if the TP is already released) > {code} > 4. Branch from your existing master branch into a new *{color:blue}jbosstools-4.3.0.Beta1x{color}* branch; > {code} > git checkout master > git pull origin master > git checkout -b jbosstools-4.3.0.Beta1x > git push origin jbosstools-4.3.0.Beta1x > {code} > 5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*. > {code} > git checkout master > git pull origin master > {code} > 6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.3.0.Beta2-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.0.Beta2-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.3.0.Beta1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.0.Beta1x{color}* branch, and > * *{color:orange}4.3.0.Beta2-SNAPSHOT{color}* in your *{color:orange}master{color}* bran > 7. Close (do not resolve) this JIRA when done. > 8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Birt task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19927) For JBIDE 4.3.0.Beta1: Code Freeze + Branch [Arquillian]

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19927?page=com.atlassian.jira.plugi... ] Snjezana Peco reassigned JBIDE-19927: ------------------------------------- Assignee: Snjezana Peco > For JBIDE 4.3.0.Beta1: Code Freeze + Branch [Arquillian] > -------------------------------------------------------- > > Key: JBIDE-19927 > URL: https://issues.jboss.org/browse/JBIDE-19927 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: arquillian > Reporter: Nick Boldt > Assignee: Snjezana Peco > Priority: Blocker > Labels: task > Fix For: 4.3.0.Beta1 > > > For JBIDE 4.3.0.Beta1 [Arquillian]: Please perform the following tasks: > 0. If nothing has changed in your component since the creation of the 4.2.x branch (eg., Portal, Freemarker), *{color:red}Reject this JIRA{color}*. > Otherwise: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Beta1 > [Unresolved JIRAs with fixVersion = 4.3.0.Beta1, 9.0.0.Beta1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...] > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0, or from 1.2.2 to 1.2.100. > *NOTE:* If you already did this for your master branch, you do *not* need to do so again. Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.2.x branch. > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT > {code} > 2. Update your root pom to use parent pom version 4.3.0.Beta1-SNAPSHOT; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.0.Beta1-SNAPSHOT</version> > </parent> > {code} > 3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Beta1; > {code} > mvn clean verify -Dtpc.version=4.50.0.Beta1-SNAPSHOT # (if the TP is still a SNAPSHOT) > or > mvn clean verify -Dtpc.version=4.50.0.Beta1 # (if the TP is already released) > {code} > 4. Branch from your existing master branch into a new *{color:blue}jbosstools-4.3.0.Beta1x{color}* branch; > {code} > git checkout master > git pull origin master > git checkout -b jbosstools-4.3.0.Beta1x > git push origin jbosstools-4.3.0.Beta1x > {code} > 5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*. > {code} > git checkout master > git pull origin master > {code} > 6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.3.0.Beta2-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.0.Beta2-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.3.0.Beta1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.0.Beta1x{color}* branch, and > * *{color:orange}4.3.0.Beta2-SNAPSHOT{color}* in your *{color:orange}master{color}* bran > 7. Close (do not resolve) this JIRA when done. > 8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Arquillian task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- 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 June 2015