May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21473) Server Adapter: Missing context menu item to show application details

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21473?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21473. --------------------------------- Verified in Red Hat Developer Studio 10.0.0.Alpha1 B5264. > Server Adapter: Missing context menu item to show application details > --------------------------------------------------------------------- > > Key: JBIDE-21473 > URL: https://issues.jboss.org/browse/JBIDE-21473 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Labels: openshift_v2, server_adapter > Fix For: 4.4.0.Alpha1 > > > In some commit context menu item to show application details of an OpenShift 2 application in OpenShift explorer view was changed from Application details to Properties, what is ok. But probably at same point context menu for properties/application details vanished from OpenShift 2 Server Adapter. There is no context menu "Properties" or "Application details" or any other. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

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

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21516?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21516. --------------------------------- Verified in Red Hat Developer Studio 10.0.0.Alpha1 B5264. > Explorer: Show build pod in explorer deployment view if it any state other then complete > ---------------------------------------------------------------------------------------- > > Key: JBIDE-21516 > URL: https://issues.jboss.org/browse/JBIDE-21516 > 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.4.0.Alpha1 > > > Display the build pod in the tree view when it starts. Once it gets to complete (success or failure) remove it from the viewer. This will allow a user to see the builds associated with a deployment and know something is happening. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22299) Application Wizard: Make OpenShift templates distinquished from builder images more explicit

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22299?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-22299 at 5/4/16 8:51 AM: ------------------------------------------------------------------ We could also provide cathegories in the tree like the web-ui does (instant-apps, xpaas, php, etc). As one already sees in the web-ui one can see that those can be achieved via the tags. WDYT? was (Author: adietish): We could also provide cathegories in the tree. WDYT? > Application Wizard: Make OpenShift templates distinquished from builder images more explicit > -------------------------------------------------------------------------------------------- > > Key: JBIDE-22299 > URL: https://issues.jboss.org/browse/JBIDE-22299 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Labels: application_wizard, openshift_v3 > Fix For: 4.4.0.Alpha2 > > Attachments: templates-and-builderimages.png > > > We are now supporting builder images in New OpenShift Application wizard, they are displayed together in one tree. User has to read labels in parenthesis to know whether its a builder or not (there is not explicit saying whether it is a template or not). It would be nice to have it distinguished more explicit. > Web UI use flash for templates and build icon for builder images. > !templates-and-builderimages.png! > We could use same in our wizard on the left side of each tree item to be aware of what we are going to work with (because following wizard pages are different for builder images than for templates). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21140) [application wizard] 2 connections from same server but for different users result in project mismatch

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21140?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21140. --------------------------------- Verified in Red Hat Developer Studio 10.0.0.Alpha1 B5264. > [application wizard] 2 connections from same server but for different users result in project mismatch > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-21140 > URL: https://issues.jboss.org/browse/JBIDE-21140 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Fred Bricon > Assignee: Fred Bricon > Labels: application_wizard, upstream > Fix For: 4.4.0.Alpha1 > > > In JBT, connecting 2 users on the same server, results in wrong projects being shown for the 2nd connection (in the new application wizard). > This is caused by calling Connection.ownResource(project), having > {code} > public boolean ownsResource(IResource resource) { > if (resource == null) { > return false; > } > IClient client = resource.accept(new CapabilityVisitor<IClientCapability, IClient>() { > @Override > public IClient visit(IClientCapability capability) { > return capability.getClient(); > } > }, null); > return ObjectUtils.equals(this.client, client); > } > {code} > The problem is the clients are equals for both connections. A check for token equality should be performed to distinguish them -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-689) Update test according to the new jBPM wizard

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-689?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky commented on JBTIS-689: ----------------------------------------- You can also take an inspiration at https://github.com/jbosstools/jbosstools-integration-stack-tests/pull/706 > Update test according to the new jBPM wizard > -------------------------------------------- > > Key: JBTIS-689 > URL: https://issues.jboss.org/browse/JBTIS-689 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: BPMN2, QE > Affects Versions: 4.3.0.Final > Reporter: Andrej Podhradsky > Assignee: Jozef Marko > Fix For: 4.3.0.Final > > > The wizard for creating a jBPM project has been changed. Please update your tests according to these changes (especially those included in AllWizardTests). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22299) Application Wizard: Make OpenShift templates distinquished from builder images more explicit

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22299?page=com.atlassian.jira.plugi... ] Marián Labuda commented on JBIDE-22299: --------------------------------------- I think web UI take it from "Annotations: iconClass=icon-php" to split templates/builders into categories. I would say it is nice to have but not mandatory, I would be satisfied even only with builder/template distinction. > Application Wizard: Make OpenShift templates distinquished from builder images more explicit > -------------------------------------------------------------------------------------------- > > Key: JBIDE-22299 > URL: https://issues.jboss.org/browse/JBIDE-22299 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Labels: application_wizard, openshift_v3 > Fix For: 4.4.0.Alpha2 > > Attachments: templates-and-builderimages.png > > > We are now supporting builder images in New OpenShift Application wizard, they are displayed together in one tree. User has to read labels in parenthesis to know whether its a builder or not (there is not explicit saying whether it is a template or not). It would be nice to have it distinguished more explicit. > Web UI use flash for templates and build icon for builder images. > !templates-and-builderimages.png! > We could use same in our wizard on the left side of each tree item to be aware of what we are going to work with (because following wizard pages are different for builder images than for templates). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3574) CDK username pulldown field is not tall enough (screenshot attached)

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBDS-3574?page=com.atlassian.jira.plugin.... ] Radim Hopp commented on JBDS-3574: ---------------------------------- [~ldimaggio] could you, please, verify this issue on your system? Thanks! > CDK username pulldown field is not tall enough (screenshot attached) > -------------------------------------------------------------------- > > Key: JBDS-3574 > URL: https://issues.jboss.org/browse/JBDS-3574 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Bug > Components: runtime > Affects Versions: 9.1.0.Beta1 > Environment: Version: 9.1.0.Beta1 > Build id: Beta1-v20151210-1215-B180 > Build date: 20151210-1215 > Reporter: Len DiMaggio > Assignee: Snjezana Peco > Fix For: 10.0.0.Alpha1 > > Attachments: Dec_10_username.png > > > See attached screenshot. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21526) Deploy from existing project git constraints are too stringent

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21526?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-21526. ------------------------------ Verified in JBDS 10.0.0.Alpha1. Closing. > Deploy from existing project git constraints are too stringent > -------------------------------------------------------------- > > Key: JBIDE-21526 > URL: https://issues.jboss.org/browse/JBIDE-21526 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Fix For: 4.4.0.Alpha1 > > > There are currently 2 constraints when deploying ane existing project to OpenShift 3 that are really really annoying: > - if the project is shared with git but dirty, you can't proceed with project deployment on openshift. This constraint is completely unnecessary and should be lifted > - if the project was cloned using git/ssh protocol, it can't be deployed directly (http(s) is required). This should actually just be a warning, the user can modify the git url to use http(s) in the next page -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-689) Update test according to the new jBPM wizard

by Andrej Podhradsky (JIRA)

Andrej Podhradsky created JBTIS-689: --------------------------------------- Summary: Update test according to the new jBPM wizard Key: JBTIS-689 URL: https://issues.jboss.org/browse/JBTIS-689 Project: JBoss Tools Integration Stack Issue Type: Task Components: BPMN2, QE Affects Versions: 4.3.0.Final Reporter: Andrej Podhradsky Assignee: Jozef Marko Fix For: 4.3.0.Final The wizard for creating a jBPM project has been changed. Please update your tests according to these changes (especially those included in AllWizardTests). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22299) Application Wizard: Make OpenShift templates distinquished from builder images more explicit

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22299?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22299: ------------------------------------- Description: We are now supporting builder images in New OpenShift Application wizard, they are displayed together in one tree. User has to read labels in parenthesis to know whether its a builder or not (there is not explicit saying whether it is a template or not). It would be nice to have it distinguished more explicit. Web UI use flash for templates and build icon for builder images. !templates-and-builderimages.png! We could use same in our wizard on the left side of each tree item to be aware of what we are going to work with (because following wizard pages are different for builder images than for templates). was: We are now supporting builder images in New OpenShift Application wizard, they are displayed together in one tree. User has to read labels in parenthesis to know whether its a builder or not (there is not explicit saying whether it is a template or not). It would be nice to have it distinguished more explicit. Web UI use flash for templates and build icon for builder images. We could use same in our wizard on the left side of each tree item to be aware of what we are going to work with (because following wizard pages are different for builder images than for templates). > Application Wizard: Make OpenShift templates distinquished from builder images more explicit > -------------------------------------------------------------------------------------------- > > Key: JBIDE-22299 > URL: https://issues.jboss.org/browse/JBIDE-22299 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Labels: application_wizard, openshift_v3 > Fix For: 4.4.0.Alpha2 > > Attachments: templates-and-builderimages.png > > > We are now supporting builder images in New OpenShift Application wizard, they are displayed together in one tree. User has to read labels in parenthesis to know whether its a builder or not (there is not explicit saying whether it is a template or not). It would be nice to have it distinguished more explicit. > Web UI use flash for templates and build icon for builder images. > !templates-and-builderimages.png! > We could use same in our wizard on the left side of each tree item to be aware of what we are going to work with (because following wizard pages are different for builder images than for templates). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 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 May 2016