January 2016 - jbosstools-issues - Jboss List Archives

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

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21301?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21301. --------------------------------- Resolution: Done ok its working now. At first propagating of env. variables worked strange on my machine (when I was trying both, pointing to directory and precisely on binary), then I tried pointing only on binary. If directory containing OC binary is on Path, its prefilled on OpenShift 3 preference page. Verified in JBDS 9.1.0.Beta2 v20160122-0528-B256. > 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 > Assignee: Viacheslav Kabanovich > 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-21457) Explorer: Show build in explorer deployment view if it any state other then complete

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21457?page=com.atlassian.jira.plugi... ] Marián Labuda edited comment on JBIDE-21457 at 1/26/16 3:06 AM: ---------------------------------------------------------------- I think we don't understand each other ;) It's actually a build. When you create an app from eap 6.4. basic template, there is a build called "eap-app-1" and its state is running, but a pod where the build is being done is called "eap-app-1-build", maybe that's the reason why it is not working in this particular case, what do you think? was (Author: mlabuda): I think we don't understand each other ;) It's actually a build. When you create an app from eap 6.4. basic template, there is a build called "eap-app-1" and its state is running, but a pod where the build is done is called "eap-app-1-build", maybe that's the reason why it is not working in this particular case, what do you think? > 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.CR1 > > > 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, 4 months

1
0
0 / 0

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

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21457?page=com.atlassian.jira.plugi... ] Marián Labuda commented on JBIDE-21457: --------------------------------------- I think we don't understand each other ;) It's actually a build. When you create an app from eap 6.4. basic template, there is a build called "eap-app-1" and its state is running, but a pod where the build is done is called "eap-app-1-build", maybe that's the reason why it is not working in this particular case, what do you think? > 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.CR1 > > > 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, 4 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 Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21377?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-21377: --------------------------------------------- Yeah, I don't see anything on JBDS-3465 on testing the yaml editor as a standalone install. I don't care if it been repeatedly said YAML is less important or wont hurt anything nor if SpringIDE thinks its fine - what I care about is that we actually have someone *testing* what we include and stand behind it. Just adding stuff at random is *NOT* what we should be doing. We don't have unlimited time/resources to keep uptodate on every plugin out there. I realize it is in now and we can open (not reopen since we now got it in a release) jira if we find an issue and need removing it - but this is *backwards* IMO. The whole goal of getting QE closer is that dev and QE work together on what goes in, not that releng adds stuff and we then *maybe* want it. > 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-549) Incorrect version number (error in build process?)

by Tomáš Sedmík (JIRA)

Tomáš Sedmík created JBTIS-549: ---------------------------------- Summary: Incorrect version number (error in build process?) Key: JBTIS-549 URL: https://issues.jboss.org/browse/JBTIS-549 Project: JBoss Tools Integration Stack Issue Type: Bug Components: distribution Environment: JBDSIS 8.0.5.CR2 Reporter: Tomáš Sedmík Assignee: Paul Leacu Please see JBDSIS 8.0.5.CR2 update site - http://www.qa.jboss.com/binaries/RHDS/updates/development/luna/integratio... - and notice, that first four features have incorrect version _8.0.5.CR1_. The correct version should be _8.0.5.CR2_. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21574) Skins only have 2 positions when rotating

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21574?page=com.atlassian.jira.plugi... ] Jan Richter updated JBIDE-21574: -------------------------------- Description: Both rotate left and right then visually look like they do the same thing. (was: Both rotate the window left and then back when clicked again (visible when using skins). Having both then seems rather useless.) > Skins only have 2 positions when rotating > ----------------------------------------- > > Key: JBIDE-21574 > URL: https://issues.jboss.org/browse/JBIDE-21574 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Affects Versions: 4.3.1.Beta2 > Reporter: Jan Richter > Assignee: Konstantin Marmalyukov > Priority: Optional > Fix For: 4.3.x, 4.4.x > > > Both rotate left and right then visually look like they do the same thing. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21574) Skins only have 2 positions when rotating

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21574?page=com.atlassian.jira.plugi... ] Jan Richter updated JBIDE-21574: -------------------------------- Summary: Skins only have 2 positions when rotating (was: 'Rotate left' and 'Rotate right' do the exact same thing) > Skins only have 2 positions when rotating > ----------------------------------------- > > Key: JBIDE-21574 > URL: https://issues.jboss.org/browse/JBIDE-21574 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Affects Versions: 4.3.1.Beta2 > Reporter: Jan Richter > Assignee: Konstantin Marmalyukov > Fix For: 4.3.x, 4.4.x > > > Both rotate the window left and then back when clicked again (visible when using skins). Having both then seems rather useless. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21574) Skins only have 2 positions when rotating

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21574?page=com.atlassian.jira.plugi... ] Jan Richter updated JBIDE-21574: -------------------------------- Priority: Optional (was: Major) > Skins only have 2 positions when rotating > ----------------------------------------- > > Key: JBIDE-21574 > URL: https://issues.jboss.org/browse/JBIDE-21574 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Affects Versions: 4.3.1.Beta2 > Reporter: Jan Richter > Assignee: Konstantin Marmalyukov > Priority: Optional > Fix For: 4.3.x, 4.4.x > > > Both rotate the window left and then back when clicked again (visible when using skins). Having both then seems rather useless. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21291) require a credential composite for when there is no stored password,

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21291?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-21291: ------------------------------------- https://github.com/jbosstools/jbosstools-base/pull/479 > require a credential composite for when there is no stored password, > --------------------------------------------------------------------- > > Key: JBIDE-21291 > URL: https://issues.jboss.org/browse/JBIDE-21291 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: common/jst/core > Affects Versions: 4.3.1.Beta2 > Reporter: Rob Stryker > Assignee: Rob Stryker > Labels: respin-a > Fix For: 4.3.1.Beta2 > > Attachments: JBIDE-21291.png > > > Following up on https://issues.jboss.org/browse/JBIDE-21162 > If the credential framework can tell that a selected username has no stored password, it might be beneficial to have a composite that will have a password text field in the case that a given workflow does not wish to have a pop-up appear, but rather wishes to provide a text field instead. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21291) require a credential composite for when there is no stored password,

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21291?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-21291: ------------------------------------- I've replicated hte issue. Working on a fix. > require a credential composite for when there is no stored password, > --------------------------------------------------------------------- > > Key: JBIDE-21291 > URL: https://issues.jboss.org/browse/JBIDE-21291 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: common/jst/core > Affects Versions: 4.3.1.Beta2 > Reporter: Rob Stryker > Assignee: Rob Stryker > Labels: respin-a > Fix For: 4.3.1.Beta2 > > Attachments: JBIDE-21291.png > > > Following up on https://issues.jboss.org/browse/JBIDE-21162 > If the credential framework can tell that a selected username has no stored password, it might be beneficial to have a composite that will have a password text field in the case that a given workflow does not wish to have a pop-up appear, but rather wishes to provide a text field instead. -- 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