January 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21528) Properties view: Show pod status in column for tabbed pod property

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21528?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-21528: ---------------------------------- Labels: properties (was: ) > Properties view: Show pod status in column for tabbed pod property > ------------------------------------------------------------------ > > Key: JBIDE-21528 > URL: https://issues.jboss.org/browse/JBIDE-21528 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Marián Labuda > Labels: properties > > In new deployment view, more precisely in Properties view and tabbed property Pods, there is a table with pods under a selected project. It would be nice if there would be a column with pod status. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21402) 'Untrusted SSL Certificate' shell keeps extending when help is turned on and off again

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21402?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21402. --------------------------------- Verified in nigthly build of JBT with OpenShift tools plugin of version 3.1.0.Beta2-v20160121-0335-B154. > 'Untrusted SSL Certificate' shell keeps extending when help is turned on and off again > -------------------------------------------------------------------------------------- > > Key: JBIDE-21402 > URL: https://issues.jboss.org/browse/JBIDE-21402 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Jan Richter > Assignee: Viacheslav Kabanovich > Labels: openshift_v2, openshift_v3 > Fix For: 4.3.1.Beta2 > > Attachments: ssl-certificate-dialog-expanding.ogv > > > Clicking the 'Help' button in 'Untrusted SSL Certificate' shell opens the help menu on the right. When I click it again, instead of just closing the help menu, it extends the shell to the size it would take with the help open. This can be repeated as long as there is enough space on the screen. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21377) Include Yaml editor in JBoss Tools (& JBDS) via feature dep from o.j.t.central & add to CoreTools category, too

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21377?page=com.atlassian.jira.plugi... ] Fred Bricon edited comment on JBIDE-21377 at 1/21/16 9:45 AM: -------------------------------------------------------------- I don't see why the YAML editor should be force-fed to Central users, given that no feature from Central actually requires it or remotely has anything to do with YAML. The JSON editor is 1000x more relevant was (Author: fbricon): I don't see why the YAML editor should be force-fed to Central users, given that no feature from Central actually requires it or remotely has anything to do with YAML. > Include Yaml editor in JBoss Tools (& JBDS) via feature dep from o.j.t.central & add to CoreTools category, too > --------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21377 > URL: https://issues.jboss.org/browse/JBIDE-21377 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: updatesite > Affects Versions: 4.3.1.Beta1 > Reporter: Mickael Istria > Assignee: Nick Boldt > Fix For: 4.3.1.Beta2, 4.4.0.Alpha1 > > Attachments: jbtcentral-p2diff-summary.txt, jbtcentral-p2diff.txt, jbtcentral-p2diff_460.txt > > > There is a decent Yaml editor existing for Eclipse IDE: https://github.com/oyse/yedit . It has 21 stars and is included in STS ( JBDS-3465 ). Similarly to JSon Editor, we should provide it to JBoss Tools users by default. > This would require adding it to the TP and adding a dependency from a JBT feature to it. > On longer-term, we should get it touch with the author to get this plugin migrated to Eclipse.org world, most likely under the WTP/SSE project (cc [~vrubezhny]) > -- > Story points - 8 (fibonacci): > * update Central TP, > * update JBT/JBDS TPs, > * update JBT/JBDS category.xml files, > * update JBDS feature.xml, > * send announcement email re: TP changes -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21377) Include Yaml editor in JBoss Tools (& JBDS) via feature dep from o.j.t.central & add to CoreTools category, too

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21377?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-21377: ------------------------------------- I don't see why the YAML editor should be force-fed to Central users, given that no feature from Central actually requires it or remotely has anything to do with YAML. > Include Yaml editor in JBoss Tools (& JBDS) via feature dep from o.j.t.central & add to CoreTools category, too > --------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21377 > URL: https://issues.jboss.org/browse/JBIDE-21377 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: updatesite > Affects Versions: 4.3.1.Beta1 > Reporter: Mickael Istria > Assignee: Nick Boldt > Fix For: 4.3.1.Beta2, 4.4.0.Alpha1 > > Attachments: jbtcentral-p2diff-summary.txt, jbtcentral-p2diff.txt, jbtcentral-p2diff_460.txt > > > There is a decent Yaml editor existing for Eclipse IDE: https://github.com/oyse/yedit . It has 21 stars and is included in STS ( JBDS-3465 ). Similarly to JSon Editor, we should provide it to JBoss Tools users by default. > This would require adding it to the TP and adding a dependency from a JBT feature to it. > On longer-term, we should get it touch with the author to get this plugin migrated to Eclipse.org world, most likely under the WTP/SSE project (cc [~vrubezhny]) > -- > Story points - 8 (fibonacci): > * update Central TP, > * update JBT/JBDS TPs, > * update JBT/JBDS category.xml files, > * update JBDS feature.xml, > * send announcement email re: TP changes -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21123) Port forwarding: Free ports for port forwarding are cached even though dialog was canceled

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21123?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21123. --------------------------------- Verified in nigthly build of JBT with OpenShift tools plugin of version 3.1.0.Beta2-v20160121-0335-B154. > Port forwarding: Free ports for port forwarding are cached even though dialog was canceled > ------------------------------------------------------------------------------------------ > > Key: JBIDE-21123 > URL: https://issues.jboss.org/browse/JBIDE-21123 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Labels: openshift_v3, port_forwarding_wizard > Fix For: 4.3.1.Beta2 > > > In Port forwarding dialog there is a checkbox to use free ports for port forwading. Upon checking this checkbox, free port are used in a table showing services. If user check the checkbox, free ports are used but then cancel the dialog either by pressing Esc or close the dialog, the state of checkbox is cached. If then user opens a dialog again checkbox is not checked but dialog is behaving like it is, because there are used free ports for port forwading. It forces user to check checkbox again, it finds another free ports and then uncheck it to get to default state. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21506) For JBIDE 4.3.1.Beta2: Code Freeze + Branch [BrowserSim]

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21506?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov closed JBIDE-21506. ------------------------------------------ Resolution: Done > For JBIDE 4.3.1.Beta2: Code Freeze + Branch [BrowserSim] > -------------------------------------------------------- > > Key: JBIDE-21506 > URL: https://issues.jboss.org/browse/JBIDE-21506 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: browsersim > Reporter: Nick Boldt > Assignee: Konstantin Marmalyukov > Priority: Blocker > Labels: task > Fix For: 4.3.1.Beta2 > > > For JBIDE 4.3.1.Beta2 [BrowserSim]: 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.Beta2 > [Unresolved JIRAs with fixVersion = 4.3.1.Beta2, 9.1.0.Beta2|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 Beta2 (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.Beta2-SNAPSHOT. > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.1.Beta2-SNAPSHOT</version> > </parent> > {code} > 3a. Ensure you've *built your code* using the latest *minimum* target platform version 4.50.2.Beta2-SNAPSHOT (4.50 = Eclipse Mars.0) > {code} > mvn clean verify -Dtpc.version=4.50.2.Beta2-SNAPSHOT > {code} > 3b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.52.0.Beta2-SNAPSHOT (4.52 = Eclipse Mars.2) > {code} > mvn clean verify -Dtpc.version=4.52.0.Beta2-SNAPSHOT > {code} > 4. Branch from your existing jbosstools-4.3.x branch into a new *{color:blue}jbosstools-4.3.1.Beta2x{color}* branch; > {code} > git checkout jbosstools-4.3.x > git pull origin jbosstools-4.3.x > git checkout -b jbosstools-4.3.1.Beta2x > git push origin jbosstools-4.3.1.Beta2x > {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.CR1-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.1.CR1-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.3.1.Beta2-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.1.Beta2x{color}* branch, and > * *{color:orange}4.3.1.CR1-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 BrowserSim 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, 5 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 Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21150?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21150. --------------------------------- Verified in nigthly build of JBT with OpenShift tools plugin of version 3.1.0.Beta2-v20160121-0335-B154. > 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 > Assignee: Viacheslav Kabanovich > 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21457) Explorer: Show build in explorer deployment view if it any state other then complete

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21457?page=com.atlassian.jira.plugi... ] Fred Bricon resolved JBIDE-21457. --------------------------------- Resolution: Done > Explorer: Show build in explorer deployment view if it any state other then complete > ------------------------------------------------------------------------------------ > > Key: JBIDE-21457 > URL: https://issues.jboss.org/browse/JBIDE-21457 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Labels: openshift_deployment_view > Fix For: 4.3.1.Beta2 > > > Display the build in the tree view when it is any non-terminated state ("Complete", "Failed", "Error", "Cancelled"). Expectation is builds should be visible in the tree for a short period of time and then disappear. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21372) Server Adapter: automatically create a server for new apps

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21372?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21372: ------------------------------------- Fix Version/s: 4.3.1.CR1 (was: 4.3.1.Beta2) > Server Adapter: automatically create a server for new apps > ---------------------------------------------------------- > > Key: JBIDE-21372 > URL: https://issues.jboss.org/browse/JBIDE-21372 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter > Fix For: 4.3.1.CR1 > > > Currently one has to create the OpenShift 3 server adapter manually by using the menu File > New > Server > OpenShift 3 (or context menu in the Server view). We should now also create the server adapter when one successfully finishes the new/import application wizard. To achieve this we'll have to include a page in the new/import-application wizard for the required server settings. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21514) Old webpages are displayed

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21514?page=com.atlassian.jira.plugi... ] Martin Malina edited comment on JBIDE-21514 at 1/21/16 9:28 AM: ---------------------------------------------------------------- It seems to be resolved. There were duplicate records for tools.jboss.org: {code} $ dig tools.jboss.org ; <<>> DiG 9.9.4-RedHat-9.9.4-29.el7 <<>> tools.jboss.org ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 26373 ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 2, ADDITIONAL: 3 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;tools.jboss.org. IN A ;; ANSWER SECTION: tools.jboss.org. 20 IN A 10.5.105.17 tools.jboss.org. 20 IN A 10.4.129.25 ;; AUTHORITY SECTION: jboss.org. 254 IN NS ns01.intranet.prod.int.phx2.redhat.com. jboss.org. 254 IN NS ns02.intranet.prod.int.phx2.redhat.com. ;; ADDITIONAL SECTION: ns01.intranet.prod.int.phx2.redhat.com. 70 IN A 10.5.30.45 ns02.intranet.prod.int.phx2.redhat.com. 161 IN A 10.5.30.46 ;; Query time: 64 msec ;; SERVER: 10.34.32.1#53(10.34.32.1) ;; WHEN: Thu Jan 21 15:16:51 CET 2016 ;; MSG SIZE rcvd: 179 {code} But now it no longer happens. >From vvasilev: {quote} Hi, I moved the magnolia sites to new IP and hardware load balancer Looks like tools had two records. Now this is fixed. It will take 5-15 minutes to be visible world wide Sorry for the troubles {quote} was (Author: mmalina): It seems to be resolved. There are two name servers and each had a different record: {code} $ dig tools.jboss.org ; <<>> DiG 9.9.4-RedHat-9.9.4-29.el7 <<>> tools.jboss.org ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 26373 ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 2, ADDITIONAL: 3 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;tools.jboss.org. IN A ;; ANSWER SECTION: tools.jboss.org. 20 IN A 10.5.105.17 tools.jboss.org. 20 IN A 10.4.129.25 ;; AUTHORITY SECTION: jboss.org. 254 IN NS ns01.intranet.prod.int.phx2.redhat.com. jboss.org. 254 IN NS ns02.intranet.prod.int.phx2.redhat.com. ;; ADDITIONAL SECTION: ns01.intranet.prod.int.phx2.redhat.com. 70 IN A 10.5.30.45 ns02.intranet.prod.int.phx2.redhat.com. 161 IN A 10.5.30.46 ;; Query time: 64 msec ;; SERVER: 10.34.32.1#53(10.34.32.1) ;; WHEN: Thu Jan 21 15:16:51 CET 2016 ;; MSG SIZE rcvd: 179 {code} But now it no longer happens. >From vvasilev: {quote} Hi, I moved the magnolia sites to new IP and hardware load balancer Looks like tools had two records. Now this is fixed. It will take 5-15 minutes to be visible world wide Sorry for the troubles {quote} > Old webpages are displayed > -------------------------- > > Key: JBIDE-21514 > URL: https://issues.jboss.org/browse/JBIDE-21514 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: website > Affects Versions: 4.3.0.Final > Reporter: Radim Hopp > Assignee: Xavier Coulon > Priority: Critical > Fix For: 4.3.1.Beta2 > > > Almost everybody in our team (QA in Brno) is seeing old website tools.jboss.org (http://i.imgur.com/mJ0WUIU.png). Only one who is still getting new design is mmalina (we have no idea why... he is on same subnet). rawagner claims that yesterday everything was ok. > Somebody is able to get new design in private window... but is seems completely random. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 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 January 2016