June 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-18824) Server adapter: Remove replicated start-, stop-, restart-actions, use default actions instead

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18824?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-18824. --------------------------------- Resolution: Won't Fix Closing because there is not going to be any time to fix openshift related JIRAs with fixVersion set to LATER. > Server adapter: Remove replicated start-, stop-, restart-actions, use default actions instead > --------------------------------------------------------------------------------------------- > > Key: JBIDE-18824 > URL: https://issues.jboss.org/browse/JBIDE-18824 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.2.1.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: LATER > > Attachments: duplicate-application-actions.png > > > In JBIDE-11903 we added Start and Stop to the Explorer and Server adapter. In the server adapter we already have default items for start, stop and restart. We should remove our items from the OpenShift submenu and use the default actions instead: > !duplicate-application-actions.png! -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18715) [openshift Server Adapter] Notification should be shown once the server is started (e.g. EAP, AS...)

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18715?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-18715. --------------------------------- Resolution: Won't Fix Closing because there is not going to be any time to fix openshift related JIRAs with fixVersion set to LATER. > [openshift Server Adapter] Notification should be shown once the server is started (e.g. EAP, AS...) > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-18715 > URL: https://issues.jboss.org/browse/JBIDE-18715 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift, server > Affects Versions: 4.2.0.Final > Reporter: Marián Labuda > Labels: server_adapter > Fix For: LATER > > > Under "server" I mean EAP, AS, WildFly, Tomcat... catridges (server runtimes). > We talked with [~adietish] about having a notification about started server. It would help with application deployment to know, when the server is running and not to check/stare into the console. > Notification should be shown in the bottom right corner and at first it should inform user about server being started and that we are going to inform him/her once the server is started. Second notification would be shown once the server is started. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20106) OpenShift v2 plugins are installed even though I selected OpenShift v3 plugins only

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20106?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20106: ------------------------------------- Summary: OpenShift v2 plugins are installed even though I selected OpenShift v3 plugins only (was: OpenShift v2 plugin is installed even though I selected only OpenShift v3 plugin) > OpenShift v2 plugins are installed even though I selected OpenShift v3 plugins only > ----------------------------------------------------------------------------------- > > Key: JBIDE-20106 > URL: https://issues.jboss.org/browse/JBIDE-20106 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Priority: Critical > Fix For: 4.3.0.Beta2 > > > While I am installing JBT and I select only OpenShift v3, I expect that only v3 is going to be installed. Unfortunately v2 is installed too and it is possible to create v2 connection, domain, application... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20107) Browser connects on port 8080 instead of livereload custom port

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20107?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-20107: --------------------------------------- Will be fixed for 4.3.0.Beta2. The current workaround for desktop browsers is to use the LiveReload extension instead. It will work even if the application connects on port 8080. > Browser connects on port 8080 instead of livereload custom port > --------------------------------------------------------------- > > Key: JBIDE-20107 > URL: https://issues.jboss.org/browse/JBIDE-20107 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: livereload > Affects Versions: 4.3.0.Alpha2 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Priority: Critical > Fix For: 4.3.0.Beta2 > > > When selecting a module and calling {{Show In>Web browser via LiveReload}}, the browser connects on the default HTTP port of the app server instead of connecting on the LiveReload custom port (something like {{54321}}. > Digging with curl, it seems that the URL used to connect does not contain a trailing '/' and in return, WildFly responds with a {{302}} response and a new location which passes through the 8080 port: > {code} > curl -v http://192.168.0.10:55201/conferenceschedule > * Hostname was NOT found in DNS cache > * Trying 192.168.0.10... > * Connected to 192.168.0.10 (192.168.0.10) port 55201 (#0) > > GET /conferenceschedule HTTP/1.1 > > User-Agent: curl/7.37.1 > > Host: 192.168.0.10:55201 > > Accept: */* > > > < HTTP/1.1 302 Found > < Date: Wed, 17 Jun 2015 14:55:33 GMT > < X-Powered-By: Undertow/1 > * Server WildFly/8 is not blacklisted > < Server: WildFly/8 > < Location: http://192.168.59.103:8080/conferenceschedule/ > < Date: Wed, 17 Jun 2015 14:55:33 GMT > < Content-Length: 0 > < > * Connection #0 to host 192.168.0.10 left intact > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20107) Browser connects on port 8080 instead of livereload custom port

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20107?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-20107: ---------------------------------- Fix Version/s: 4.3.0.Beta2 > Browser connects on port 8080 instead of livereload custom port > --------------------------------------------------------------- > > Key: JBIDE-20107 > URL: https://issues.jboss.org/browse/JBIDE-20107 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: livereload > Affects Versions: 4.3.0.Alpha2 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Priority: Critical > Fix For: 4.3.0.Beta2 > > > When selecting a module and calling {{Show In>Web browser via LiveReload}}, the browser connects on the default HTTP port of the app server instead of connecting on the LiveReload custom port (something like {{54321}}. > Digging with curl, it seems that the URL used to connect does not contain a trailing '/' and in return, WildFly responds with a {{302}} response and a new location which passes through the 8080 port: > {code} > curl -v http://192.168.0.10:55201/conferenceschedule > * Hostname was NOT found in DNS cache > * Trying 192.168.0.10... > * Connected to 192.168.0.10 (192.168.0.10) port 55201 (#0) > > GET /conferenceschedule HTTP/1.1 > > User-Agent: curl/7.37.1 > > Host: 192.168.0.10:55201 > > Accept: */* > > > < HTTP/1.1 302 Found > < Date: Wed, 17 Jun 2015 14:55:33 GMT > < X-Powered-By: Undertow/1 > * Server WildFly/8 is not blacklisted > < Server: WildFly/8 > < Location: http://192.168.59.103:8080/conferenceschedule/ > < Date: Wed, 17 Jun 2015 14:55:33 GMT > < Content-Length: 0 > < > * Connection #0 to host 192.168.0.10 left intact > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20106) OpenShift v2 plugin is installed even though I selected only OpenShift v3 plugin

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20106?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-20106: ------------------------------------------ merged and pushed to upstream/master > OpenShift v2 plugin is installed even though I selected only OpenShift v3 plugin > -------------------------------------------------------------------------------- > > Key: JBIDE-20106 > URL: https://issues.jboss.org/browse/JBIDE-20106 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Priority: Critical > Fix For: 4.3.0.Beta2 > > > While I am installing JBT and I select only OpenShift v3, I expect that only v3 is going to be installed. Unfortunately v2 is installed too and it is possible to create v2 connection, domain, application... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19584) Explorer: exception child (error connecting happened) to v3 connection has "New" context menu

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19584?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19584: ------------------------------------- Summary: Explorer: exception child (error connecting happened) to v3 connection has "New" context menu (was: Explorer: exception for v3 connection is has "New" context menu) > Explorer: exception child (error connecting happened) to v3 connection has "New" context menu > --------------------------------------------------------------------------------------------- > > Key: JBIDE-19584 > URL: https://issues.jboss.org/browse/JBIDE-19584 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Priority: Minor > Labels: explorer, openshift_v3 > Fix For: 4.3.0.Beta2 > > Attachments: new-context-menu-for-exception.png > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19584) Explorer: error child (could not connect) to v3 connection has "New" context menu

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19584?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19584: ------------------------------------- Summary: Explorer: error child (could not connect) to v3 connection has "New" context menu (was: Explorer: exception child (error connecting happened) to v3 connection has "New" context menu) > Explorer: error child (could not connect) to v3 connection has "New" context menu > --------------------------------------------------------------------------------- > > Key: JBIDE-19584 > URL: https://issues.jboss.org/browse/JBIDE-19584 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Priority: Minor > Labels: explorer, openshift_v3 > Fix For: 4.3.0.Beta2 > > Attachments: new-context-menu-for-exception.png > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19817) Application wizard: v3 application wizard needs to be able to react to changing connections

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19817?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19817: ------------------------------------- Labels: openshift_v3 (was: ) > Application wizard: v3 application wizard needs to be able to react to changing connections > ------------------------------------------------------------------------------------------- > > Key: JBIDE-19817 > URL: https://issues.jboss.org/browse/JBIDE-19817 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Jeff Cantrill > Priority: Blocker > Labels: openshift_v3 > Fix For: 4.3.0.Beta2 > > > The current application wizard for OpenShift v3 takes a project in the constructor. It was designed to be launched from the explorer where a v3 connection/project is selected before the wizard is launched. The wizard is not able to react to changing connections. In order for the wizard to be able to get launched from File->New->OpenShift we need the wizard to be able to react to chaning connections. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19412) Cleanup ConnectionURL usage for v3 connections

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19412?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19412: ------------------------------------- Labels: openshift_v3 (was: ) > Cleanup ConnectionURL usage for v3 connections > ---------------------------------------------- > > Key: JBIDE-19412 > URL: https://issues.jboss.org/browse/JBIDE-19412 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: openshift_v3 > Fix For: 4.3.0.Beta2 > > > In ConnectionsRegistry connections are stored by ConnectionURL. ConnectionURL is also used to persist v2 connections. v3 connections on the other hand are persisted in their very own json format. We need to clean this discrepany/inconsistency. We should either only use ConnectionURL for v2 connections or also store v3 connections in the ConnectionURL format. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 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 June 2015