December 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-21303) Add tooltip to label in UI wizard in GUIs

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21303?page=com.atlassian.jira.plugi... ] George Gastaldi reassigned JBIDE-21303: --------------------------------------- Assignee: George Gastaldi > Add tooltip to label in UI wizard in GUIs > ----------------------------------------- > > Key: JBIDE-21303 > URL: https://issues.jboss.org/browse/JBIDE-21303 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: forge > Affects Versions: 4.3.0.Final > Reporter: Claus Ibsen > Assignee: George Gastaldi > Fix For: 4.3.1.Beta2, 4.4.0.Alpha1 > > Attachments: eclipse-tooltip.png, idea-tooltip.png > > > My camel addon builds some commands that has ui steps where the end user can enter some details. As we have documentation for each of those input fields what they mean, they are currently shows as tooltip. > The tooltip is only shows in the input field, eg see screenshot of eclipse. > In IDEA then the tooltip only works on some input fields like boolean types. But for the general text based inputs its not shown. > I wonder if we could add tooltip to the label also? so you can however over the label (eg Period:), then it would always work there. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21267) For JBIDE 4.3.1.Beta1: Code Freeze + Branch [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch]

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21267?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-21267: ---------------------------------------- I missed the part of your comment about build-ci, and only checked maven-plugins. Since build-ci aren't Maven artifacts AFAIK, there is nothing to "mvn release", just branching should be enough. WDYT? > For JBIDE 4.3.1.Beta1: Code Freeze + Branch [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch] > -------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21267 > URL: https://issues.jboss.org/browse/JBIDE-21267 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Blocker > Labels: task > Fix For: 4.3.1.Beta1 > > > For JBIDE 4.3.1.Beta1 [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch]: Please perform the following tasks: > 0. If nothing has changed in your component since the release of JBoss Tools 4.3.0.Final (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.1.Beta1 > [Unresolved JIRAs with fixVersion = 4.3.1.Beta1, 9.1.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 4.3.0 to 4.3.1, 1.2.3 to 1.2.100, or 2.3.100 to 2.3.101 > *NOTE:* If you already did this earlier when we were preparing for Beta1 (after 4.3.0.Final was released), 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.3.x branch. > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.24.0:set-version -DnewVersion=4.3.1-SNAPSHOT > {code} > 2. Update your root pom to use parent pom version 4.3.1.Beta1-SNAPSHOT. > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.1.Beta1-SNAPSHOT</version> > </parent> > {code} > 3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.2.Beta1 (or 4.50.2.Beta1-SNAPSHOT). > {code} > mvn clean verify -Dtpc.version=4.50.2.Beta1-SNAPSHOT # (if the TP is still a SNAPSHOT) > or > mvn clean verify -Dtpc.version=4.50.2.Beta1 # (if the TP is already released) > {code} > 4. Branch from your existing jbosstools-4.3.x branch into a new *{color:blue}jbosstools-4.3.1.Beta1x{color}* branch; > {code} > git checkout jbosstools-4.3.x > git pull origin jbosstools-4.3.x > git checkout -b jbosstools-4.3.1.Beta1x > git push origin jbosstools-4.3.1.Beta1x > {code} > 5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}jbosstools-4.3.x branch{color}*. > {code} > git checkout jbosstools-4.3.x > git pull origin jbosstools-4.3.x > {code} > 6. Update your *{color:orange}jbosstools-4.3.x branch{color}* parent pom to use the latest version, *{color:orange}4.3.1.Beta2-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.1.Beta2-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.3.1.Beta1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.1.Beta1x{color}* branch, and > * *{color:orange}4.3.1.Beta2-SNAPSHOT{color}* in your *{color:orange}jbosstools-4.3.x{color}* branch. > 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 build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21303) Add tooltip to label in UI wizard in GUIs

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21303?page=com.atlassian.jira.plugi... ] George Gastaldi updated JBIDE-21303: ------------------------------------ Project: Tools (JBoss Tools) (was: Forge) Key: JBIDE-21303 (was: FORGE-2556) Workflow: GIT Pull Request workflow (was: GIT Pull Request workflow with automatic PR triggers) Component/s: forge (was: UI - Eclipse) (was: UI - IntelliJ IDEA) (was: UI - NetBeans) Affects Version/s: 4.3.0.Final (was: 2.19.2.Final) (was: 3.0.0.Alpha3) Fix Version/s: 4.3.1.Beta2 4.4.0.Alpha1 (was: 3.x Future) > Add tooltip to label in UI wizard in GUIs > ----------------------------------------- > > Key: JBIDE-21303 > URL: https://issues.jboss.org/browse/JBIDE-21303 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: forge > Affects Versions: 4.3.0.Final > Reporter: Claus Ibsen > Fix For: 4.3.1.Beta2, 4.4.0.Alpha1 > > Attachments: eclipse-tooltip.png, idea-tooltip.png > > > My camel addon builds some commands that has ui steps where the end user can enter some details. As we have documentation for each of those input fields what they mean, they are currently shows as tooltip. > The tooltip is only shows in the input field, eg see screenshot of eclipse. > In IDEA then the tooltip only works on some input fields like boolean types. But for the general text based inputs its not shown. > I wonder if we could add tooltip to the label also? so you can however over the label (eg Period:), then it would always work there. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21150) SSL certificate dialog: Provide a way to change one's mind about accepting an SSL certificate

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21150?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21150: ------------------------------------- Summary: SSL certificate dialog: Provide a way to change one's mind about accepting an SSL certificate (was: Provide a way to change one's mind about accepting an SSL certificate) > SSL certificate dialog: Provide a way to change one's mind about accepting an SSL certificate > --------------------------------------------------------------------------------------------- > > Key: JBIDE-21150 > URL: https://issues.jboss.org/browse/JBIDE-21150 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Jan Richter > Labels: openshift_v2, openshift_v3 > Fix For: 4.3.1.Beta2 > > > The tooling will only give the user one chance to accept/deny the SSL certificate, which happens on start of the session. This is particularly annoying when for some reason the user denies the certificate (or just cancels the dialog) because the only way to reset it is to restart the IDE. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21150) SSL certificate dialog: Provide a way to change one's mind about accepting an SSL certificate

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21150?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21150: ------------------------------------- Labels: openshift_v2 openshift_v3 (was: ) > SSL certificate dialog: Provide a way to change one's mind about accepting an SSL certificate > --------------------------------------------------------------------------------------------- > > Key: JBIDE-21150 > URL: https://issues.jboss.org/browse/JBIDE-21150 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Jan Richter > Labels: openshift_v2, openshift_v3 > Fix For: 4.3.1.Beta2 > > > The tooling will only give the user one chance to accept/deny the SSL certificate, which happens on start of the session. This is particularly annoying when for some reason the user denies the certificate (or just cancels the dialog) because the only way to reset it is to restart the IDE. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21301) Preferences: path to OC binary is not shown on OpenShift 3 page if binary is on $PATH

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21301?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21301: ------------------------------------- Summary: Preferences: path to OC binary is not shown on OpenShift 3 page if binary is on $PATH (was: Path to OC binary is not shown on OpenShift 3 preference page if binary is on $PATH) > Preferences: path to OC binary is not shown on OpenShift 3 page if binary is on $PATH > ------------------------------------------------------------------------------------- > > Key: JBIDE-21301 > URL: https://issues.jboss.org/browse/JBIDE-21301 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Marián Labuda > Labels: openshift_v3, preferences > Fix For: 4.3.1.Beta2 > > > In JBIDE-21183 was implemented auto-lookup of 'oc' binary on $PATH. This works ok, but in Workbench Preference dialog on OpenShift 3 preference page where location to oc is shown and stored is not this path displayed in this case. If 'oc' binary is located on $PATH it should be also visible on OpenShift 3 preference page. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21301) Preferences: path to OC binary is not shown on OpenShift 3 page if binary is on $PATH

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21301?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21301: ------------------------------------- Priority: Minor (was: Major) > Preferences: path to OC binary is not shown on OpenShift 3 page if binary is on $PATH > ------------------------------------------------------------------------------------- > > Key: JBIDE-21301 > URL: https://issues.jboss.org/browse/JBIDE-21301 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Marián Labuda > Priority: Minor > Labels: openshift_v3, preferences > Fix For: 4.3.1.Beta2 > > > In JBIDE-21183 was implemented auto-lookup of 'oc' binary on $PATH. This works ok, but in Workbench Preference dialog on OpenShift 3 preference page where location to oc is shown and stored is not this path displayed in this case. If 'oc' binary is located on $PATH it should be also visible on OpenShift 3 preference page. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21301) Path to OC binary is not shown on OpenShift 3 preference page if binary is on $PATH

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21301?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21301: ------------------------------------- Labels: openshift_v3 preferences (was: preferences) > Path to OC binary is not shown on OpenShift 3 preference page if binary is on $PATH > ----------------------------------------------------------------------------------- > > Key: JBIDE-21301 > URL: https://issues.jboss.org/browse/JBIDE-21301 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Marián Labuda > Labels: openshift_v3, preferences > Fix For: 4.3.1.Beta2 > > > In JBIDE-21183 was implemented auto-lookup of 'oc' binary on $PATH. This works ok, but in Workbench Preference dialog on OpenShift 3 preference page where location to oc is shown and stored is not this path displayed in this case. If 'oc' binary is located on $PATH it should be also visible on OpenShift 3 preference page. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21301) Path to OC binary is not shown on OpenShift 3 preference page if binary is on $PATH

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21301?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21301: ------------------------------------- Fix Version/s: 4.3.1.Beta2 > Path to OC binary is not shown on OpenShift 3 preference page if binary is on $PATH > ----------------------------------------------------------------------------------- > > Key: JBIDE-21301 > URL: https://issues.jboss.org/browse/JBIDE-21301 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Marián Labuda > Labels: preferences > Fix For: 4.3.1.Beta2 > > > In JBIDE-21183 was implemented auto-lookup of 'oc' binary on $PATH. This works ok, but in Workbench Preference dialog on OpenShift 3 preference page where location to oc is shown and stored is not this path displayed in this case. If 'oc' binary is located on $PATH it should be also visible on OpenShift 3 preference page. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21150) Provide a way to change one's mind about accepting an SSL certificate

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21150?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21150: ------------------------------------- Fix Version/s: 4.3.1.Beta2 > Provide a way to change one's mind about accepting an SSL certificate > --------------------------------------------------------------------- > > Key: JBIDE-21150 > URL: https://issues.jboss.org/browse/JBIDE-21150 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Jan Richter > Fix For: 4.3.1.Beta2 > > > The tooling will only give the user one chance to accept/deny the SSL certificate, which happens on start of the session. This is particularly annoying when for some reason the user denies the certificate (or just cancels the dialog) because the only way to reset it is to restart the IDE. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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