January 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21392) Composite install job is disabled and also component jobs are disabled therefore there is no nightly build

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21392?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-21392: ------------------------------- Fix Version/s: 4.3.1.Beta2 > Composite install job is disabled and also component jobs are disabled therefore there is no nightly build > ---------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21392 > URL: https://issues.jboss.org/browse/JBIDE-21392 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.1.Beta1 > Reporter: Marián Labuda > Priority: Blocker > Fix For: 4.3.1.Beta2 > > > Job https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-composite... is marked as disabled and also component jobs such as http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-openshift_... and others are disabled. There was no build since 2015-12-16. Maybe it was disabled as a consequence/side effect of JBIDE-21145. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21392) Composite install job is disabled and also component jobs are disabled therefore there is no nightly build

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21392?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-21392: ---------------------------------- Assignee: Nick Boldt > Composite install job is disabled and also component jobs are disabled therefore there is no nightly build > ---------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21392 > URL: https://issues.jboss.org/browse/JBIDE-21392 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.1.Beta1 > Reporter: Marián Labuda > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.3.1.Beta2 > > > Job https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-composite... is marked as disabled and also component jobs such as http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-openshift_... and others are disabled. There was no build since 2015-12-16. Maybe it was disabled as a consequence/side effect of JBIDE-21145. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21122) Port Forwarding: Start All button should be disabled if port forwarding is already active

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21122?page=com.atlassian.jira.plugi... ] Jeff Cantrill reassigned JBIDE-21122: ------------------------------------- Assignee: Viacheslav Kabanovich > Port Forwarding: Start All button should be disabled if port forwarding is already active > ----------------------------------------------------------------------------------------- > > Key: JBIDE-21122 > URL: https://issues.jboss.org/browse/JBIDE-21122 > 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 wizard is a button "Start All" which starts port forwarding for all services listed in a table. If user triggers the button and port forwarding is already active, Start All is still enabled and user can click on it again and again but nothing happens. Accessibility of this button should be similar as Stop All, which works as expected - if port forwarding is not active, it is disabled, otherwise it is enabled. > There is also a checkbox to find free ports for port forwarding. Once port forwarding is active, checking and unchecking this checkbox do nothing. It should have same accessibility as Start All button - if there is active port forwarding, the checkbox should be disabled, otherwise it should be enabled. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-471) Unify component versions

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-471?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-471: ---------------------------------- [~bbrodt] - could you check the feature list above and close this Jira when complete? It would be great to get this done for the Beta1 bode freeze on Jan 26 Thanks! > Unify component versions > ------------------------ > > Key: JBTIS-471 > URL: https://issues.jboss.org/browse/JBTIS-471 > Project: JBoss Tools Integration Stack > Issue Type: Enhancement > Components: distribution > Affects Versions: 8.0.3.GA > Reporter: Andrej Podhradsky > Assignee: Robert (Bob) Brodt > > Currently, JBDS-IS 8.0.3.CR2 contains components with different version format such as > BPMN2 1.1.3.Final > Fuse 7.3.1.v20150728-1330-H54-Final > Teiid Designer 9.0.3.Final-v20150728-2029-B1148 > I suggest to use the format used by Teiid Designer. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21356) Make OpenShift 3 resource edition more robust

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21356?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21356: ------------------------------------- Fix Version/s: 4.3.1.Beta2 > Make OpenShift 3 resource edition more robust > --------------------------------------------- > > Key: JBIDE-21356 > URL: https://issues.jboss.org/browse/JBIDE-21356 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Fred Bricon > Fix For: 4.3.1.Beta2 > > > Following [~scabanovich]'s comment in JBIDE-20761: > {quote} > My concern is that the default editor is called if it is set for .json without a fallback for a case of failure of that unknown editor. We cannot be sure what editor a user may have set to be default for .json. That editor may be expecting some specific instance of editor input object and fail on what is provided. As it is, then json will not be opened at all, neither fancy nor plain text. However, if it is just temporal, till the expected contribution to jsdt, and that editor is going to be hardcoded to be opened, then no problem. > {quote} > Until we can rely on Eclipse's upcoming JSON editor (in Neon), we should try to harden editor detection/opening -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21385) Add refresh of deployments

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21385?page=com.atlassian.jira.plugi... ] Jeff Cantrill updated JBIDE-21385: ---------------------------------- Summary: Add refresh of deployments (was: Add refresh of deploymens) > Add refresh of deployments > -------------------------- > > Key: JBIDE-21385 > URL: https://issues.jboss.org/browse/JBIDE-21385 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Fix For: 4.4.0.Final > > > Impl functionality to manually refresh a deployment which should > * Cause the children of deployment(e.g. pods) to be refreshed -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21385) Add refresh of deployments

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21385?page=com.atlassian.jira.plugi... ] Jeff Cantrill updated JBIDE-21385: ---------------------------------- Fix Version/s: 4.4.0.Final > Add refresh of deployments > -------------------------- > > Key: JBIDE-21385 > URL: https://issues.jboss.org/browse/JBIDE-21385 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Fix For: 4.4.0.Final > > > Impl functionality to manually refresh a deployment which should > * Cause the children of deployment(e.g. pods) to be refreshed -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21377) Include Yaml editor in JBoss Tools (& JBDS?) via feature dep, new Central connector, or just add to CoreTools category

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21377?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-21377: ---------------------------------------- +1 for [~maxandersen] suggestion. > Include Yaml editor in JBoss Tools (& JBDS?) via feature dep, new Central connector, or just add to CoreTools category > ---------------------------------------------------------------------------------------------------------------------- > > 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 > > 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]) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21375) Explorer: Missing label for a filter

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21375?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-21375: ---------------------------------------- Assignee: Viacheslav Kabanovich > Explorer: Missing label for a filter > ------------------------------------ > > Key: JBIDE-21375 > URL: https://issues.jboss.org/browse/JBIDE-21375 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Xavier Coulon > Assignee: Viacheslav Kabanovich > Labels: explorer > Fix For: 4.4.0.Alpha1 > > Attachments: Screenshot 2015-12-21 16.26.50.png > > > The list of filters on the OpenShift Explorer view shows 2 entres, but the first one seems to miss a proper label. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21394) Deploy docker: "Resource Name" should not error (but "*" required) if empty

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-21394: ---------------------------------------- Summary: Deploy docker: "Resource Name" should not error (but "*" required) if empty Key: JBIDE-21394 URL: https://issues.jboss.org/browse/JBIDE-21394 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Reporter: Andre Dietisheim Assignee: Viacheslav Kabanovich Priority: Minor Fix For: 4.3.1.Beta2 how to reproduce: # EXEC: in explroer: open up context menu on an openshift 3 project and choose "Deploy Docker Image..." # ASSERT: Deploy Docker Image wizard pops up empty Result: The "Resource Name" field is decorated with an error marker, it should be decorated with a "*" which is used all across OpenShift when required values are missing/empty !resource-name-empty.png! -- 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 January 2016