January 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20023) Show in browser: missing project/server that we're listing the routes of

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20023?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-20023: ----------------------------------------------- [~adietish], please take a look at the pull request. > Show in browser: missing project/server that we're listing the routes of > ------------------------------------------------------------------------ > > Key: JBIDE-20023 > URL: https://issues.jboss.org/browse/JBIDE-20023 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Priority: Minor > Labels: help_wanted, openshift_v3 > Fix For: 4.3.x > > Attachments: show-in-browser-routes.png > > > how to reproduce: > # ASSERT: make sure that you have a project with several routes on a v3 OpenShift server > # ASSERT: make sure that you have a connetion in explorer to this server > # EXEC: in Explorer: unfold Routes and pick "Show in->Web Browser" > Result: > !show-in-browser-routes.png! > A dialog requiring to select the route that you want to open up in the browser pops up. The dialog wont tell you what server, project the routes are listed for. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21405) Add RedDeer 1.0.1 to target platform

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21405?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-21405: ------------------------------------ Recap: * Martin: "now that RD is stable, we should put in in the TP" * Max: "this could incur more maintenance, but only one version of RD used across all of JBT is good" * Xavier: "good idea to include, but won't use it any time soon" * Ratislav: "jbosstools-integration-tests will be updated to use the version from the TP" So, is that: * +1 to include ("build it and they will come"), or * +0 to defer ("wait until someone actually will use it") ? Cast your votes below. > Add RedDeer 1.0.1 to target platform > ------------------------------------ > > Key: JBIDE-21405 > URL: https://issues.jboss.org/browse/JBIDE-21405 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.3.1.Beta2 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.3.1.Beta2 > > > We would like to add RedDeer 1.0.1 to target platform. > Note that we don't have 1.0.1 ready yet, it will be released soon (should be in time to make it to Beta2). Currently we have 1.0.0. But I'm creating this JIRA now to find out if anything is needed to be done for this to happen. > Github repo: https://github.com/jboss-reddeer/reddeer > Wiki: https://github.com/jboss-reddeer/reddeer/wiki > 1.0.0 repo: http://download.jboss.org/jbosstools/updates/stable/mars/core/reddeer/1.0.0/ > 1.0.1 repo: http://download.jboss.org/jbosstools/updates/stable/mars/core/reddeer/1.0.1/ (not available yet) > Feature: org.jboss.reddeer.eclipse.feature -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21290) CDK 2 is detected as version 1.0

by Hardy Ferentschik (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21290?page=com.atlassian.jira.plugi... ] Hardy Ferentschik commented on JBIDE-21290: ------------------------------------------- What are the columns here? They are not readable in the screenshot? Is this a specific column to display the CDK version? Is this a requirement or why do we even do that? > CDK 2 is detected as version 1.0 > -------------------------------- > > Key: JBIDE-21290 > URL: https://issues.jboss.org/browse/JBIDE-21290 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, runtime-detection > Affects Versions: 4.3.1.Beta1 > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.3.1.Beta2, 4.4.0.Alpha1 > > Attachments: cdk-runtime-detection.png > > > When you detect CDK using runtime detection, it will show you the name cdk-v2 which clearly shows it's version 2 (this is actually just based on the folder it seems). But the Version column says Version 1.0. > !cdk-runtime-detection.png! > Could we change it to version 2? > I know that this probably doesn't have any meaning right now - I noticed there is no runtime anymore, so the version is nowhere to be seen once you create the cdk server adapter. But it would still be nicer to show the correct version if possible. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21413) Updates to support api changes for Service#getTarget port in the restclient

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21413?page=com.atlassian.jira.plugi... ] Jeff Cantrill updated JBIDE-21413: ---------------------------------- Fix Version/s: 4.3.1.Beta2 > Updates to support api changes for Service#getTarget port in the restclient > --------------------------------------------------------------------------- > > Key: JBIDE-21413 > URL: https://issues.jboss.org/browse/JBIDE-21413 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Fix For: 4.3.1.Beta2 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21414) Application wizard: ConcurrentModificationException when creating a new appliaction

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21414?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21414: ------------------------------------- Attachment: concurrent-modification-exception.png > Application wizard: ConcurrentModificationException when creating a new appliaction > ------------------------------------------------------------------------------------ > > Key: JBIDE-21414 > URL: https://issues.jboss.org/browse/JBIDE-21414 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Andre Dietisheim > Labels: application_wizard, openshift_v3 > Fix For: 4.3.1.Beta2 > > Attachments: concurrent-modification-exception.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21414) Application wizard: ConcurrentModificationException when creating a new appliaction

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21414?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21414: ------------------------------------- Fix Version/s: 4.3.1.Beta2 > Application wizard: ConcurrentModificationException when creating a new appliaction > ------------------------------------------------------------------------------------ > > Key: JBIDE-21414 > URL: https://issues.jboss.org/browse/JBIDE-21414 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Andre Dietisheim > Labels: application_wizard, openshift_v3 > Fix For: 4.3.1.Beta2 > > Attachments: concurrent-modification-exception.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21414) Application wizard: ConcurrentModificationException when creating a new appliaction

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21414?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21414: ------------------------------------- Labels: application_wizard openshift_v3 (was: ) > Application wizard: ConcurrentModificationException when creating a new appliaction > ------------------------------------------------------------------------------------ > > Key: JBIDE-21414 > URL: https://issues.jboss.org/browse/JBIDE-21414 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Andre Dietisheim > Labels: application_wizard, openshift_v3 > Fix For: 4.3.1.Beta2 > > Attachments: concurrent-modification-exception.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21414) Application wizard: ConcurrentModificationException when creating a new appliaction

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-21414: ---------------------------------------- Summary: Application wizard: ConcurrentModificationException when creating a new appliaction Key: JBIDE-21414 URL: https://issues.jboss.org/browse/JBIDE-21414 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.1.Beta1 Reporter: Andre Dietisheim -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21376) Application wizard: should allow to create an app from an image (currently only from template)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21376?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-21376 at 1/6/16 1:40 PM: ------------------------------------------------------------------ We discussed how to provide this given the timely constraint we currently have. We currently also cannot provide a way for the user to create an app based on wildfly given we dont support app creation via images currently. We saw 5 different options: {quote} 1) Use server side template Pros: * Works today Cons: * requires server side setup of templates ** (e.g. pushing builder image up, possibly pushing template up) * We (jbossteam?) need to write and maintain template 2) Use server side image (conceptually create a template based on builder image + github info) (mimicking webconsole) Pros: * Will not require custom template setup on server side Cons: * needs new UI/workflow in New App to mimic webconsole 3) Use eclipse side template Pros: * will work without server side setup * faster to implement Cons: * fragile (requires specific builder images we rely on) * add custom logic for UI/workflow in "create from source" * Won't be (immediatly) visibile in eclipse 4) Create eclipse side templates based on server side builder images Pros: * will not require custom additional UX flow (or will it?) Cons: * will have to hardcode services/routes 5) rely on serverside new-app feature Pros: * no custom logic (we think) Cons: * don't know when {quote} We decided to go for now for eclipse side templates in a 1st step (*3*) since this is the option with the least effort. was (Author: adietish): We discussed how to provide this given the timely constraint we currently have. We currently also cannot provide a way for the user to create an app based on wildfly given we dont support app creation via images currently. We saw 5 different options: {quote} 1) Use server side template Pros: * Works today Cons: * requires server side setup of templates ** (e.g. pushing builder image up, possibly pushing template up) * We (jbossteam?) need to write and maintain template 2) Use server side image (conceptually create a template based on builder image + github info) (mimicking webconsole) Pros: * Will not require custom template setup on server side Cons: * needs new UI/workflow in New App to mimic webconsole 3) Use eclipse side template Pros: * will work without server side setup * faster to implement Cons: * fragile (requires specific builder images we rely on) * add custom logic for UI/workflow in "create from source" * Won't be (immediatly) visibile in eclipse 4) Create eclipse side templates based on server side builder images Pros: * will not require custom additional UX flow (or will it?) Cons: * will have to hardcode services/routes 5) rely on serverside new-app feature Pros: * no custom logic (we think) Cons: * don't know when {quote} We decided to go for now for eclipse side templates in a 1st step (*3*) since this is the option with the least effort. > Application wizard: should allow to create an app from an image (currently only from template) > ---------------------------------------------------------------------------------------------- > > Key: JBIDE-21376 > URL: https://issues.jboss.org/browse/JBIDE-21376 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Xavier Coulon > Labels: application_wizard, openshift_v3 > Fix For: 4.4.0.Alpha1 > > Attachments: Screenshot 2015-12-21 16.44.02.png, Screenshot 2015-12-21 16.44.24.png, Screenshot 2015-12-21 18.06.40.png > > > The application wizard in the Eclipse tooling currently only allows to create application from templates. The web console additionally allows creating from images and git source. > One can see the difference when comparing the listing of options in Eclipse vs the listing in the web console (which also includes images): > {quote} > Running OpenShift using our openshift-vagrant box, I can see different proposals between the web console and the Eclipse tooling when adding an application in a project. For example, {{jboss-eap64-openshift:1.1}} is not proposed in the Eclipse tooling. > See attached screenshots. > {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21376) Application wizard: should allow to create an app from an image (currently only from template)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21376?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-21376 at 1/6/16 1:39 PM: ------------------------------------------------------------------ We discussed how to provide this given the timely constraint we currently have. We currently also cannot provide a way for the user to create an app based on wildfly given we dont support app creation via images currently. We saw 5 different options: {quote} 1) Use server side template Pros: * Works today Cons: * requires server side setup of templates ** (e.g. pushing builder image up, possibly pushing template up) * We (jbossteam?) need to write and maintain template 2) Use server side image (conceptually create a template based on builder image + github info) (mimicking webconsole) Pros: * Will not require custom template setup on server side Cons: * needs new UI/workflow in New App to mimic webconsole 3) Use eclipse side template Pros: * will work without server side setup * faster to implement Cons: * fragile (requires specific builder images we rely on) * add custom logic for UI/workflow in "create from source" * Won't be (immediatly) visibile in eclipse 4) Create eclipse side templates based on server side builder images Pros: * will not require custom additional UX flow (or will it?) Cons: * will have to hardcode services/routes 5) rely on serverside new-app feature Pros: * no custom logic (we think) Cons: * don't know when {quote} We decided to go for now for eclipse side templates in a 1st step (*3*) since this is the option with the least effort. was (Author: adietish): We discussed how to provide this given the timely constraint we currently have. We currently also cannot provide a way for the user to create an app based on wildfly given we dont support app creation via images currently. We saw 5 different options: {quote} # Use server side template Pros: * Works today Cons: * requires server side setup of templates ** (e.g. pushing builder image up, possibly pushing template up) * We (jbossteam?) need to write and maintain template # Use server side image (conceptually create a template based on builder image + github info) (mimicking webconsole) Pros: * Will not require custom template setup on server side Cons: * needs new UI/workflow in New App to mimic webconsole * # Use eclipse side template Pros: * will work without server side setup * faster to implement Cons: * fragile (requires specific builder images we rely on) * add custom logic for UI/workflow in "create from source" * Won't be (immediatly) visibile in eclipse # Create eclipse side templates based on server side builder images Pros: * will not require custom additional UX flow (or will it?) Cons: * will have to hardcode services/routes # rely on serverside new-app feature Pros: no custom logic (we think) Cons: don't know when {quote} We decided to go for now for eclipse side templates in a 1st step (*3*) since this is the option with the least effort. > Application wizard: should allow to create an app from an image (currently only from template) > ---------------------------------------------------------------------------------------------- > > Key: JBIDE-21376 > URL: https://issues.jboss.org/browse/JBIDE-21376 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Xavier Coulon > Labels: application_wizard, openshift_v3 > Fix For: 4.4.0.Alpha1 > > Attachments: Screenshot 2015-12-21 16.44.02.png, Screenshot 2015-12-21 16.44.24.png, Screenshot 2015-12-21 18.06.40.png > > > The application wizard in the Eclipse tooling currently only allows to create application from templates. The web console additionally allows creating from images and git source. > One can see the difference when comparing the listing of options in Eclipse vs the listing in the web console (which also includes images): > {quote} > Running OpenShift using our openshift-vagrant box, I can see different proposals between the web console and the Eclipse tooling when adding an application in a project. For example, {{jboss-eap64-openshift:1.1}} is not proposed in the Eclipse tooling. > See attached screenshots. > {quote} -- 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